Kwern
Connectors

Google Analytics 4

How to bind a GA4 property to a Kwern product, which traffic numbers it keeps, and how Kwern stays inside the property quota.

What you need

A Google account with read access to the GA4 property, and a product whose Site surface points at the site the property measures.

Connect it

The same authorization as Search Console: one Connect Google in Settings · Add an account asks for both read-only scopes. If the Google account is already connected, you do not authorize anything again.

Open the product's Apps page and choose the GA4 property. It is its own connector: you can bind the property without binding a Search Console site, or the other way round.

What Kwern reads

A snapshot a day:

  • sessions, users, new users, page views and the engagement rate of the window
  • the traffic channels and the landing pages behind them

Sessions, users, new users, page views and conversions accumulate as the connector's series, day by day and never windowed.

What Kwern can change

Nothing. The scope is analytics.readonly: every read answers and every change comes back refused. Kwern cannot create a property, an audience or a conversion, and reads no individual — the reports come back as counts by channel and by landing page.

The agents that use it

No agent needs it to run. Search Console stops at the click; Analytics is what happened after it, and it is how the SEO and GEO agents tell a page that ranks from a page that works. It is what the Traffic tab of Analytics charts.

When it breaks

A GA4 property spends a token quota shared by everyone reading it, hourly and daily, and a broad report costs thousands of them. Kwern asks for the dimensions the question needs and reads the quota the response carries, rather than paging through the property. If the quota is exhausted by another tool, the sync fails for the day and the previous snapshot stays latest; the series is extended only once the source answered.

Google Analytics connector · All connectors · SEO agent

On this page