Skip to main content
Search Console tells you how content performs in search. Analytics tells you what happened after the click — sessions, engagement, conversions, and how much of your traffic now arrives from AI assistants.
We request one scope — analytics.readonly. Read-only access to your GA4 reporting data; we can’t change property settings or write events.

​
Before you start

You need at least Viewer access to the GA4 property. If you only have access to a Universal Analytics property, it won’t appear — UA stopped collecting data in 2023 and has no API we can read.

​
Step 1 — Connect

Project Settings → Integrations → Google Analytics 4 → Connect, choose your Google account, and approve the consent screen. If you see “Google hasn’t verified this app”, click Advanced → Go to seosorted (unsafe) — the same step as Search Console. Search Console and Analytics are separate connectors with separate consent screens, even when both live on the same Google account.
While our own Google app finishes verification, the connection may run through Composio, our OAuth partner. In that case Google’s consent screen names Composio as the app asking for access, and the page you return through is branded SEOsorted. The access is the same read-only scope either way.

​
Step 2 — Choose the property

Google returns you to Choose a Google Analytics property.
Choose an Analytics property screen listing six GA4 properties grouped by account, with nothing preselected

Every GA4 property on the account, with its parent account underneath

Each row is property name above account name — useful when an agency account carries a dozen similarly-named properties. Pick the one that receives traffic from the site this workspace tracks, then Connect.
Pick the property, not the account, and make sure it’s the one that actually receives your traffic. A placeholder property (the kind a Firebase project creates automatically) connects fine and then syncs zero rows forever.Nothing is preselected unless it matches your workspace domain or is the only property on the account — so Connect stays disabled until you make a deliberate choice.
You can change it later from the Analytics card’s ⋮ menu → Change property. If the property doesn’t match your project’s domain, the card shows Setup required — property doesn’t match your domain and the menu offers Choose property instead.
Choose an Analytics property dialog opened from the Integrations tab

Changing the property later

​
Step 3 — Sync

The first sync backfills 28 days and then runs every 24 hours. Use the ↻ icon for an on-demand sync; the completion toast reports how many rows landed:
If it reports no new rows for this property yet, the connector worked and the property has no data in the window — you almost certainly picked the wrong property. When a property keeps returning nothing, the card says Connected, but this property has no traffic — check the GA4 tag is installed on your site. Either the GA4 tag isn’t on your site, or you picked the wrong property.

​
What you get

  • Traffic trend — daily pageviews against AI-referred visits
  • Engagement metrics — sessions, engaged sessions, conversions
  • Per-article attribution — traffic mapped to the articles that earned it
  • AI referral tracking — visits arriving from ChatGPT, Perplexity, Claude and friends
GA4 needs 24–48 hours after property creation before its API returns anything. A new property will sync clean and empty until then.