Connect analytics

A Google Analytics 4 connection is how per-article traffic arrives: pageviews and sessions, one reading per calendar day, collected every six hours over your published articles. The connection is read-only. CommandChain never writes anything to your analytics.

Two IDs, and only one of them works

Your analytics property has two identifiers, they look nothing alike, and the wrong one is the one you see most often.

• The property ID is a plain number, found in Google Analytics under Admin → Property Settings.
• The measurement ID starts with G- and is the one embedded in your site’s page tag, which is why it is the one people have on hand.

The reporting side of Google Analytics accepts only the numeric property ID. The connection form asks for it by name, but it cannot tell the two apart, so pasting the measurement ID is accepted quietly and fails later.

If you pasted the G- ID

Nothing objects at the moment of the mistake. It surfaces when you verify the binding, as the provider’s own answer, shown to you verbatim: Invalid property ID, followed by A numeric Property ID is required. That message means exactly one thing: go back to the connection settings and replace the G- value with the number from Property Settings.

The Google account you authorize with must be able to see the property: Viewer access or better, on that specific property. An account that opens the wrong organization’s Analytics, or none at all, fails at the consent screen or at verify, never at the form.

The Google side, once per workspace

Google connections go through an OAuth app that you register, the same shape as the social platforms setup:

1. In the Google Cloud console, create (or reuse) a project and an OAuth client of type Web application.
2. Enable two APIs on that project: the Google Analytics Data API, which answers the traffic queries, and the Google Analytics Admin API, which answers one question only: how far back your property retains data, the bound the history backfill respects. Miss the second and everything works except backfill.
3. Register the redirect URL. It is shown on the integration’s Connections tab; copy it unchanged.
4. If the OAuth consent screen is in testing status, add the Google account you will authorize with as a test user. Without that, Google refuses the consent screen outright.

The same OAuth client serves Search Console too; you register it once.

Connect it

1. In Settings → Integrations, import Google Analytics 4 from the catalogue.
2. Create a connection: the GA4 property ID goes in settings, the OAuth client’s ID and secret in credentials.
3. Press Connect with OAuth2 and authorize as the Google account with access to the property. The consent screen names the account it will act as.
4. On the Categories tab, verify the proposed binding and activate it. The verify runs a real report query, so a wrong property ID fails here, with Google’s error in front of you.

When the numbers appear

Traffic is the fast half of measurement, and it is still not instant. Analytics serves processed data: an article published this morning usually has pageviews by the evening, and a day still in progress can keep changing for up to two more days as processing finishes. The collector restates whole days as the provider settles them, so a recent number that moves and then holds is the system working, not a bug. The full timing story, including how search differs, is on Metrics and attribution.

History does not start at the moment you connect, either. The content view’s Backfill history action pulls daily readings for everything already published, as far back as your property’s own data retention setting allows, and states the exact range before it asks.

Next steps

• Connect Search Console: the other half, whether search can find you.
• Publish an article: the whole path, from draft to measured.
• Metrics and attribution: what the collected numbers actually are.