What does Kwern ask Google for?

The read-only Analytics scope. Every read answers and every change comes back refused: Kwern cannot create a property, an audience or a conversion.

Which numbers does it read?

Sessions, users, new users, page views and conversions, day by day, plus the traffic channels and the landing pages of the window.

No agent needs it to run. It is the traffic half of the picture the SEO and GEO agents argue from, and what the Traffic tab of Analytics charts.

Will Kwern exhaust my property quota?

A GA4 property has an hourly and a daily token quota shared by everyone reading it, and a broad report costs thousands. Kwern asks for the dimensions the question needs and reads the quota the response carries.

Is this the same connection as Search Console?

One grant, two connectors. You can bind the property without binding a Search Console site, or the other way round.

Google Analytics 4

Search Console stops at the click. Google Analytics is what happened after it, and it is how an agent tells a page that ranks from a page that works.

What Kwern reads

Sessions and engagement

Sessions, users, new users, page views and the engagement rate of the window.

Channels and landing pages

The traffic channels and the landing pages behind them.

Kept day by day

sessions, users, new users, page views, conversions. Every day ever seen is kept and never windowed, so a range you ask for a year from now still answers.

What Kwern can change

Nothing

Nothing. The grant Kwern holds reads and cannot write, so there is no proposal that ends here.

How the connection is made

Connecting the account

The same Google authorization as Search Console, with the read-only Analytics scope alongside it.

Binding it to a product

A GA4 property. The same Google account can also bind a Search Console site, as its own connector.

What Kwern never does

Never a write

Kwern never writes to Analytics. The scope it holds is read-only.

Nothing per person

No individual is read: the reports come back as counts by channel and by landing page.

Questions

The agents that use it

Every agent of the product reads what this connector syncs. These are the ones that work on the same surface:

SEO Agent

Crawls the site every week and turns what it finds into pull requests on the repository that serves it.

GEO Agent

Probes the engines that answer questions and fixes what keeps your pages out of their answers.

Competitors Agent

Re-reads your competitors' public pages every week and writes one digest of what substantively changed.

Writer Agent

Writes the day's article from a roadmap Kwern keeps for your site, with the front matter done; you publish it.

The other connectors

App Store Connect Apple Ads Google Play RevenueCat Stripe PostHog Google Search Console Google Ads X Reddit LinkedIn GitHub

Read on

Connecting Google Analytics 4, step by step

What to click, what each sync leaves behind, and what to do when the connection breaks.

The MCP server

Read the last sync of every connector, and approve what waits, from your own MCP client.

Someone is asking for what you built today.

On Reddit, on X, in ChatGPT's answers. Kwern finds them every morning and drafts the reply in your voice; you decide what goes out.