Visibility shows the market. Analytics shows the usage.
Google Analytics 4 shows what visitors do on the website. BrandZaps connects read-only and uses sessions, page views and conversions as page and usage context in keyword research and as a performance metric on the dashboard.
How the connection is made.
Each source is authorised separately. An error with one source takes nothing away from the others – it appears as a warning on the source concerned.
The access scope is strictly read-only and has been reviewed and approved by Google. BrandZaps changes no settings and no data in Google Analytics.
A 90-day period is fetched. Google keeps 16 months – BrandZaps uses this history for trends and also keeps its own daily series without page path.
What BrandZaps fetches.
Last 90 days, plus its own daily series without page path. The connection delivers data to BrandZaps and changes nothing in the connected accounts.
Where the data makes a difference.
GA4 shows which pages bring sessions, page views and conversions. BrandZaps places this data alongside topics, search queries and company context – so you can see which pages have a business impact.
GA4 provides additional page and usage context. It creates no keywords and no topics. The overview in the “Keywords & clusters” area shows the context of the data sources.
DashboardA source card shows sessions and conversions, a sparkline and a comparison with the previous period. Usage sits alongside search visibility, not in an isolated report.
Project BrainThe data is stored as part of the project’s knowledge context.
Research only starts once Analytics 4 and Google Search Console are connected and selected. Together, both sources are the prerequisite for the research run.
Access tokens are encrypted with AES-256-GCM before they are stored. Sign-in runs via OAuth with PKCE.
All integrations →Usage as context, not as automatic strategy.
Google Analytics 4 is connected per project and only ever read.