Published site tracking (Capable Sites)
Pages published as a Capable Site report into the same GA4 property and join up with the in-Confluence data.
#How it works
A small loader script is baked into the published pages, tagged with the Confluence space key, page id, page type and version. It looks the measurement ID up live, so changing the ID does not require republishing. Published views are always anonymous.
#What it needs
Capable Sites, a Google Analytics ID entered in that site's Integrations settings, and the "Capable analytics integration" switch turned on.
#Where you do it
Task | Where |
|---|---|
Open the settings page | Confluence > Settings > Apps > Google Analytics |
Set the Measurement ID and start collecting | View tracking panel > Data stream (if connected) or Measurement ID (manual) |
Turn on search, comment and page-edit events | Enhanced tracking panel > Measurement Protocol API secret |
#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. |
Data stream | Settings > Apps > Google Analytics > View tracking | Picking a web data stream fills in the Measurement ID for you. |
Measurement ID | Settings > Apps > Google Analytics > View tracking | The GA4 tag ID (G-XXXXXXXXXX). This is the single required setting: nothing is collected anywhere until it is set. |
#Worth knowing
Published Capable Site views can never be attributed to a person. They are always anonymous, with no account type and no guest status.
If the Capable Sites cookie consent banner is on and a visitor never clicks Accept, no analytics load on that published site for them at all.
In production an unlicensed site collects nothing at all, including from published sites.
#Related
How it actually behaves.
