Everything else
Start from what you are seeing rather than from what you think is broken. Each page below names the symptom, explains why it happens, and says what to do about it.
Several of these are the product working as designed, which is worth knowing before anybody raises a ticket.
#At a glance
Symptom | Usually because |
|---|---|
No page views appear in Google Analytics at all, even hours after setup | The most common cause is a Measurement ID that is not a GA4 ID. Anything not starting with G- switches off every collection path silently. The next most common causes are that you saved less |
Views seem to be sent (no errors anywhere) but nothing lands in the property you are looking at | A valid-looking G- ID that belongs to a different or non-existent property. Google accepts the events without complaint, so both the browser and the server report success while the data goes |
Search, comment and page create/update events never show up, but page views work fine | No Measurement Protocol API secret is stored. Google requires one for server-sent events; the Measurement ID alone is not enough. |
Enhanced tracking worked, then silently stopped after you saved settings again | A manually pasted API secret is wiped by the next Save configuration unless you retype it. Secrets picked or created through the Google picker survive; hand-typed ones do not. |
Search counts look roughly double | Searches can be recorded twice on sites where Confluence emits its own search event: once from the reader's browser and once from the server-side event. |
You entered a Universal Analytics (UA-) ID and nothing is tracked | The "Use UA tag instead" checkbox only changes the hints and validation on the ID field. Universal Analytics is not supported by any part of the app, and Google stopped processing UA data in |
Users you excluded with Allowed groups are still being counted in Google Analytics | Allowed groups restricts who can OPEN the reports. It has never restricted who is tracked, and the tracker deliberately keeps working for excluded and anonymous readers. |
You want page titles kept out of Google, so you ticked "Hide Google Analytics pages in Confluence" | That setting only hides the app's own report pages from Confluence navigation. It has never affected what is sent to Google, and titles are still reported. |
Logged-out visitor's views are showing but with no user identity | This is by design. Logged-out readers are recorded with the account dimension set to "anonymous" and deliberately no Google user id, so they are not all merged into one person. |
Macro shows a "connect Google" panel instead of a chart | The site's Google connection is missing, expired or unhealthy. Reports and the macro both read data through that one site-level connection. |
You disconnected Google and expected data collection to stop | Disconnecting only removes the ability to read reports and manage streams, secrets and dimensions. The stored Measurement ID and API secret keep collecting. |
Tracking stopped after you changed the GA4 property | Changing the property deliberately clears the Measurement ID and the API secret selection, because a data stream and its secrets belong to one property. |
Refined or Scroll Viewport pages report nothing after pasting the snippet | Usually the other product's content security policy is blocking the lookup request, or the snippet was pasted in the wrong place. |
Some report rows show a bare page id instead of a title | Report data comes from Google keyed on page id, and titles are looked up separately using the viewer's own Confluence access. If the viewer cannot see the page, or it was deleted, the title |
#In this section
#Related
Most of these are expected behaviour.
