WebmasterID logoWebmasterID
Analytics dimensions

Campaign ID dimension: the machine key for campaigns

Campaign ID is the dimension fed by the utm_id parameter (and by ad-platform IDs on auto-tagged traffic). Unlike the human-readable campaign name, the ID is a stable machine key meant to survive renames and to join analytics with ad-platform cost data. GA4 uses it to reconcile manual tags with imported campaign metadata, which makes it the durable join key for cross-system reporting.

Verified against primary sources

What this means

Campaign names change — a team renames 'Spring Sale' to 'Spring Promo' mid-flight and the historical data fragments. Campaign ID solves this: utm_id carries a stable identifier that GA4 maps to the Campaign ID dimension, independent of the display name.

On auto-tagged paid traffic, the ad platform supplies its own campaign ID, which analytics resolves automatically.

Why it matters for cost joins

To report return on ad spend, analytics must join click and conversion data to the cost data exported from ad platforms. Names are unreliable join keys; IDs are not. GA4's data-import and campaign reconciliation rely on a consistent campaign ID to attach imported cost to sessions.

The failure mode is sloppy tagging: omit utm_id and you fall back to fragile name matching; reuse one id across distinct campaigns and they merge.

How it appears in analytics and logs

A campaign ID value is a durable identifier for a campaign. A missing or inconsistent utm_id means analytics cannot reliably join to cost data; duplicate IDs across campaigns collapse them in joined reports.

Diagnostic use case

Use campaign ID as the stable join key between analytics and ad-cost data, so reporting survives the inevitable campaign renames.

What WebmasterID can help detect

WebmasterID parses utm_id alongside the campaign name, so the stable ID is available as a join key for cost reconciliation without any cross-site identity.

Common mistakes

Privacy and accuracy notes

Campaign ID identifies a campaign, not a person. As long as the ID is not a per-user token, it carries no personal data; WebmasterID reads utm_id first-party.

Related pages

Sources and verification notes

Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.