Google Analytics: 1 read and 2 writes, one client

Traffic and audience reports. Every call below is available over HTTP, through the SDK and as a tool for a coding agent, with the same arguments and the same meter.

What Google Analytics can do here

The integration exposes 1 read and 2 writes, each with a declared input and output schema rather than a page of documentation you would have to translate. Traffic and audience reports.

How it authenticates

Google Analytics uses OAuth, so you link the account once and we hold the refresh token rather than a key you have to paste. The link is the credential: revoke it at Google Analytics and the calls stop here too, immediately, without anyone deleting anything on our side.

Called by name, not by capability

Google Analytics does not currently map onto a vendor-neutral capability, so you call its operations by name. That is the right shape when you genuinely mean this provider — which, for a service with its own model of the world, is most of the time.

• runReport — write: Run a GA4 report over a date range.
• runRealtimeReport — write: Who is on the site right now (last 30 minutes).
• getMetadata — read: Every metric and dimension this property supports.

Questions

Do I have to bring my own API keys?

You can, and that lane is free for ever — pass your key on the request or store it against your account, and we are one proxy hop. The paid lane is the other direction: we call 226 providers with our credentials so you never register anywhere. Both go through the same client and the same operation names.

What happens to a key I store here?

It is sealed with AES-256-GCM before it reaches the database and is only ever opened to make the call you asked for. It is scoped to your account, it is never logged, and deleting the connection deletes it. For an OAuth provider we hold a refresh token instead, and revoking the link at the provider stops the calls here immediately.

What happens when a provider changes its API?

The operation contract is declared, so a response that no longer matches is a refusal rather than a silently wrong answer. The contract does not coerce types — a field declared a number that arrives as a string is rejected at the edge, on the way in and on the way out.