Reports inside Confluence
Overview, Spaces, Content and (opt-in) Searches and Raw report tabs, on a global page and on every space's page.
#How it works
The app asks Google for the data using the Google account you connected once at site level, and renders it in Confluence. The browser never talks to Google directly for reports.
#What it needs
A connected Google account and a chosen GA4 property.
#Where you do it
Task | Where |
|---|---|
Open the settings page | Confluence > Settings > Apps > Google Analytics |
Connect Google (do this first) | Connect Google panel > Connect Google Analytics |
Pick the GA4 property | Connect Google panel > GA4 property |
#Settings that affect this
Setting | Where | What it does |
|---|---|---|
Connect Google Analytics / Disconnect | Settings > Apps > Google Analytics > Connect Google | Starts a Google sign-in popup. The connection is site-level: one admin connects once and the whole Confluence site uses it. Disconnect revokes access at Google and deletes the stored tokens. |
GA4 property | Settings > Apps > Google Analytics > Connect Google | Which GA4 property the in-Confluence reports read from. Also scopes the data stream, API secret and custom dimension controls. |
Custom dimensions (GA4) - Sync / Refresh | Settings > Apps > Google Analytics > Enhanced tracking | Creates the app's 14 custom dimensions in your GA4 property. Five are required (space key, hashed account id, content id, content type, content version) and back the core reports; nine are optional and each unlocks a rep |
#Worth knowing
There is no consent mechanism inside Confluence at all. Setting a Measurement ID starts collecting from every reader on the next page load, with no banner and no opt-out. The only consent gate in the product is the cookie consent popup on published Capable Sites.
"Allowed groups" restricts who can READ reports. It never restricts who is tracked. Excluded users and anonymous readers keep being recorded.
"Hide Google Analytics pages in Confluence" only hides the app's own pages from navigation. Page titles are still sent to Google.
Report rows are not filtered by the viewer's Confluence permissions. Metrics come from Google keyed on page id and are shown to anyone who passes the Allowed groups check; only the titles are resolved with the viewer's own access. Use Allowed groups if this matters, and leave the Raw paths panel off, as that is the sharper exposure.
Reports go empty rather than erroring when no GA4 property is selected, which looks exactly like a data-lag problem.
GA4 takes up to 48 hours to surface new events and newly created dimensions. Empty reports right after setup are expected, not a misconfiguration.
#Limits that apply here
Reports page date range
#Related
How it actually behaves.
