Google Analytics: connect a property, report, and change its settings
Google Analytics connects with Google sign-in, one row per property. Reports are read-only and run at once, in the property's own reporting time zone. Changes to the property — key events, audiences, custom dimensions and metrics, channel groups, annotations, data streams, Google Ads links and retention — go through the Admin API; by default each waits for your approval, and a named set always waits for a person. Every write goes to the property you connected.
Connect
- 1On Integrations, press Connect on the Google Analytics card and sign in with a Google account that can see the properties.
- 2Turning on writes re-authorizes with a wider permission; reads need only read access.
- 3Pick the property and ask, for example: "Compare last month with the month before by channel, and tell me what actually changed."
Reports
- Standard, realtime, funnel, cohort and pivot reports, and several reports in one call.
- The property's own day. The agent reads the property's settings (get_property) — its reporting time zone, currency and service level — and a range like "last 7 days" means the 7 full days ending yesterday in that zone.
- Unassigned traffic is diagnosed by its source and medium, with the likely tagging cause.
- Anomalies on a metric's daily series.
Property settings
| Area | Tools | Waits for a person? |
|---|---|---|
| Key events | list, create, update, delete | Deleting one always does |
| Audiences | list, create, update, archive | Archiving always does |
| Custom dimensions and metrics | list, create, update, archive | Archiving always does |
| Channel groups | list, create, update, delete | Deleting one always does |
| Annotations | list, create, update, delete | Deleting one always does |
| Google Ads links | list, link one, link up to 20 at once, update, delete | Unlinking always does |
| Data streams, enhanced measurement, event create rules | list / read, create, update | Follows your approval setting |
| Attribution settings | read, update | Always does — it changes the conversion credit Google Ads imports |
| Data retention | read, update | Shortening it always does — older data is deleted |
| Property name, time zone, currency | update_property | A time zone or currency change always does — Google never restates the days before |
Bound to your property
A write names the property it changes. The agent sends it to the property you connected, or to another property that has its own connection in this workspace, and refuses any other before calling Google — one Google sign-in usually reaches many properties.
Linking several Google Ads accounts is one link per account (Google has no batch call), and the answer lists each account as linked, already linked or failed.
Data from outside the site
- Measurement Protocol: server-side events from the last 72 hours. The agent validates them with Google's validation server first (nothing is recorded); a real send always waits for a person, because Google Analytics cannot delete an event it has received.
- Data Import files (cost data from other ad platforms, items, users) have no upload API. The agent builds the file in Google's format and gives you the steps to upload it in Admin → Data import.
Not available through Google's API
- Data filters (internal or developer traffic), unwanted referrals, cross-domain measurement and IP exclusion — the agent tells you where to set them in Google Analytics Admin.
- Calculated metrics, and links to products other than Google Ads, are not built yet (BigQuery links can be read, not created).
Frequently asked questions
- Which time zone do the agent's Google Analytics reports use?
- The property's own reporting time zone, read from the property's settings. "Yesterday" and "last 7 days" are the property's days, not UTC.
- Can the agent link Google Ads accounts to my property?
- Yes — one account, or up to 20 at once with a result for each. By default each link waits for your approval; unlinking always waits for a person.
- Can it change a property I did not connect?
- No. A write goes only to the connected property, or to another property with its own connection in this workspace.