# Enhanced tracking (server side) Records page created, page updated, comment created, comment updated and search events that a browser cannot see, sent server-to-server to Google. --- ## How it works Confluence notifies the app when these things happen and the app posts an event to Google's Measurement Protocol. These are separate from the browser tracking and use a different Google mechanism. --- ## What it needs A GA4 Measurement ID plus a Measurement Protocol API secret, plus an active licence. --- ## 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 * Searches can be counted twice on sites where Confluence emits its own search event, because the browser and the server both record one. * Server-side events all share one Google client identity across every user and every site, and logged-out actors become one "anonymous" identity. Users and Sessions from that stream are not meaningful. This is a deliberate continuity decision carried over from the older Connect app. --- ## Related [Reports inside ConfluenceAnother part of how this works.](https://help.gocapable.com/google-analytics/reports-inside-confluence.html) [Space-scoped reportsAnother part of how this works.](https://help.gocapable.com/google-analytics/space-scoped-reports.html) [How it worksThe rest.](https://help.gocapable.com/google-analytics/how-it-works.html) --- _How it actually behaves._