Features
Google Analytics integration
Connect your GA4 property to Peekaboo: permissions, property selection, sync cadence, and fixing a connection that will not complete.
3 minute read · Last reviewed: August 14, 2026
You can see that ChatGPT and Perplexity name your brand, but not whether any of those conversations end with a real person landing on your website. Connecting your own Google Analytics 4 property closes that loop, using your analytics data rather than an estimate from a third party.
What the connection gives you
Once your GA4 property is connected, Peekaboo pulls the sessions arriving at your site from AI assistants and puts them next to the visibility it already measures for the same brand. Traffic is broken out by AI platform, landing page and device, with your Peekaboo visibility score aligned to the same days.
The AI traffic article covers how to read those numbers, including why confirmed referrals are a floor and why suspected AI traffic sitting inside Direct is shown as a range. Getting connected, granting the right permission and fixing a connection that will not complete are covered here.
What you need before you connect
| Requirement | Detail |
|---|---|
| Plan | An active paid subscription, including a running 14-day trial. Free workspaces cannot connect a property. |
| Google account | The account you authorize must already have access to the GA4 property. Read-only access is enough. |
| Property type | A Google Analytics 4 property. Universal Analytics properties are not supported by the API Peekaboo reads. |
| Scope granted | Read-only Analytics access. Peekaboo never gets write access to your Analytics account. |
The connection is stored per brand, so each brand in your workspace connects its own GA4 property.
Connecting your property
- Open the Google Analytics page for the brand you want to connect.
- Click Connect Google Analytics and sign in with the Google account that has access to the property.
- Approve the read-only Analytics permission on Google's consent screen.
- If the account can see exactly one GA4 property, Peekaboo connects it straight away. If it can see several, pick the property that tracks this brand's website from the list.
- The first sync starts on its own and pulls the last 90 days.
Picking the right property
The property list shows each property's display name, its owning Analytics account, and its numeric property ID, so two similarly named properties can still be told apart. Pick the one that measures the website for the brand you are working on, not a staging or aggregate property.
You can change property later from the GA4 button in the page header.
What Peekaboo pulls, and how often
The first sync covers 90 days. After that, Peekaboo re-reads a rolling 30-day window once a day, and you can trigger an extra pull at any time with the Sync button. Each pull replaces the window it covers rather than adding to it, so re-syncing is safe and never doubles a number.
For each day in the window, Peekaboo stores:
- Sessions, active users, total users and engaged sessions per AI platform
- AI sessions and all sessions split by device category
- Landing pages, with sessions, engagement and average duration, for AI visits and for all visits
- Site totals and Direct session volume, which anchor the share-of-traffic and suspected-Direct figures
Sessions are classified against Peekaboo's own AI source list: ChatGPT, Perplexity, Gemini, Copilot, Claude, Grok, DeepSeek and Mistral, plus a catch-all for anything GA4 itself flags as AI assistant traffic that is not yet on the list. That list is deliberately wider than GA4's built-in AI Assistants channel, which does not recognize Perplexity or Claude.
What the connection cannot see
Traffic from Google AI Overviews and AI Mode arrives without a distinct referrer, because the answer appears inside a Google search results page. No analytics tool can isolate it as AI traffic, so it is not counted here. Use the Search Console integration for that side of the picture.
Plain search engines are never classified as AI. A visit from google.com or bing.com counts as organic search, since treating it as AI traffic would inflate every number on the page.
When the connection will not complete
| What you see | What it means and what to do |
|---|---|
| Your Google account has no access to any GA4 property | You authorized with an account that has no Analytics access. Ask an Analytics admin to add you under Property Access Management, then connect again. |
| No GA4 properties found on that Google account | Right person, wrong Google account. Reconnect with the account that manages your Analytics. |
| Google didn't issue offline access | Google reused a previous grant instead of issuing a fresh one. Remove Peekaboo from your Google account permissions, then connect again. |
| Google access was declined | The consent screen was cancelled or closed. Start the connection again and approve the permission. |
| Brand not found | The connection started against a different brand. Switch to the brand you want connected and retry. |
| First sync failed | Use Retry sync on the same card. If it keeps failing, contact support with the brand name and the error text. |
A connected property with no AI sessions yet is not a failure. AI referral volume usually starts small, so an empty chart in the first days is a real reading, not a broken connection.
Disconnecting
Disconnecting removes the connection and deletes the GA4 data Peekaboo stored for that brand. It has no effect on your Google Analytics account itself, and it leaves any Search Console connection on the same brand untouched. Reconnecting starts a fresh 90-day sync.