GCLID vs UTM parameters and tracker click IDs

UTM parameters describe a campaign. A click ID identifies one tracked click. They solve different attribution problems, so replacing one with the other usually removes information you need.

Use UTMs to group traffic by source, medium, campaign, creative, or term. Use a click ID to connect a later event—such as an offer click, lead, or purchase—to the exact visit that produced it.

The difference in one URL

Consider this landing-page URL:

https://example.com/offer
  ?utm_source=meta
  &utm_medium=paid_social
  &utm_campaign=fall_test
  &utm_content=video_a
  &click_id=01K5ABC123

The UTM values can be shared by thousands of visits from the same ad. The click ID should be unique to one tracked visit.

That leads to two different questions:

• UTMs: Which campaign grouping sent this traffic?
• Click ID: Which specific click should receive this conversion?

Google Analytics documents UTM campaign parameters as a way to identify referring campaigns in acquisition reporting. It recommends consistent values for fields such as source, medium, and campaign. See Google Analytics’ campaign URL guidance.

What UTM parameters are good at

UTMs are readable campaign labels appended to a destination URL. Common fields include:

• utm_source for the platform or publisher;
• utm_medium for the channel type;
• utm_campaign for the campaign grouping;
• utm_content for creative or placement differences;
• utm_term for a paid keyword or another term-level distinction.

They are useful for aggregation. A report can group every visit tagged utm_campaign=fall_test, even when those visits came from different ads or occurred on different days.

UTMs also work across many analytics tools because they are conventions rather than a private identifier format. That portability is useful, but it creates a governance problem: every buyer and automation can invent new spellings.

These values are different report rows:

paid_social
Paid_Social
paid-social
paidsocial

Choose a naming contract before launch. Lowercase values, stable separators, and documented source names prevent accidental fragmentation.

GCLID vs UTM vs the Tracked click ID

gclid is a Google Ads click identifier, when Google supplies it for an eligible click. UTMs are readable campaign labels. Tracked's offer-click ID is the key an advertiser returns to Tracked for a later sale or lead. These values can coexist on one journey; they are not interchangeable.

For a Google Ads affiliate campaign, check that the landing request preserves the supplied Google identifier. When the visitor takes a tracked /click/N offer action, put {{click.id}} in the advertiser's supported sub-ID field. If the advertiser reports a conversion later, it returns that offer-click value to Tracked. A configured Google Ads offline upload can then use the stored Google click context when eligible. The Google Ads offline-conversions guide covers that provider-specific step.

What a click ID is good at

A click ID is a unique key generated or captured when a tracker receives a visit. The click record can carry campaign, page, offer, request, and timestamp context.

When a conversion happens later, the converting system returns that ID. The tracker uses it to find the original click.

This supports questions UTMs cannot answer alone:

• Which individual click produced this sale?
• Which landing-page variation did that visitor receive?
• Which offer link did the visitor choose?
• Did two conversion callbacks refer to the same original visit?
• Which request and redirect chain should be inspected when attribution fails?

A UTM combination may narrow the campaign group, but it does not uniquely identify one visit.

Why you normally need both

The click ID gives you a precise join. UTMs preserve portable campaign meaning.

If you keep only UTMs, you can report traffic by campaign but may not be able to connect a server-side conversion to one click.

If you keep only a click ID, the tracker may still know the campaign internally, but downstream analytics and landing-page systems lose readable acquisition labels.

A practical division of responsibility looks like this:

• The ad platform or link template supplies stable campaign parameters.
• The tracker captures those parameters and creates a click ID.
• The redirect carries required UTMs and the click ID to the page or offer.
• The advertiser stores the click ID with the lead or order.
• The postback returns the click ID for conversion attribution.
• Reports use UTMs for grouping and the click ID for event-level tracing.

Preserve values deliberately

Query parameters are easy to lose. Every redirect, page builder, form, checkout, and affiliate-network field has its own behavior.

Check these boundaries:

1. Ad to tracking URL: Did the platform expand its dynamic parameters?
2. Tracking URL to landing page: Did the redirect preserve the intended values?
3. Landing page to offer: Did the outbound link carry the click ID in the advertiser’s supported field?
4. Form or checkout: Was the ID stored with the conversion record?
5. Postback: Did the advertiser return the stored value using the correct macro?

Inspect real requests. A configuration preview showing {campaign.name} or {click_id} does not prove the live system replaced it.

Do not put sensitive data in campaign parameters

URLs can appear in browser history, analytics tools, referrer data, server logs, screenshots, support tickets, and copied links.

Do not put email addresses, names, phone numbers, authentication secrets, or other direct personal data in UTM values or click IDs. Treat the click ID as an opaque lookup key.

Also decide which parameters should continue to downstream systems. More propagation is not automatically better. Send only what the next owner needs.

A naming contract for UTMs

Before campaigns go live, define:

• allowed values for utm_source and utm_medium;
• how campaign names become URL-safe values;
• whether creative IDs, names, or both belong in utm_content;
• how dynamic macros are tested;
• whether values are case-sensitive in each reporting tool;
• who owns changes to the convention.

Keep human-readable names separate from stable IDs when names can change. An ad name edited mid-flight should not silently split a campaign’s history if the platform also provides an immutable ad ID.

A debugging example

Suppose a report shows 200 visits for utm_campaign=fall_test but no sales.

UTMs tell you the affected campaign group. The click chain tells you where attribution broke:

1. Pick one test visit from fall_test.
2. Capture its click ID.
3. Confirm the landing visit retained its campaign and source context.
4. Follow /click/N and confirm the resulting offer-click ID reached the advertiser.
5. Confirm the advertiser stored it.
6. Confirm the conversion callback returned it.
7. Confirm the tracker resolved it and recorded the expected event.

Without the click ID, the investigation stays at campaign level. With it, you can test each ownership boundary.

Where Tracked fits

Tracked can retain campaign parameters as click context while using its own click ID to attribute later conversions. Rules and request macros can also read query parameters when you deliberately use them for routing or page content.

That means one campaign can preserve recognizable source labels without asking those labels to perform event-level attribution.

The practical rule

Use UTMs to classify. Use click IDs to connect. Keep both stable, pass only what each system needs, and test the real values at every handoff.

Frequently asked questions

Can UTM parameters replace a click ID?

Usually not. UTMs group visits by campaign labels, while a click ID connects one visit to later events such as an offer click or conversion. A production attribution flow commonly preserves both.

Should a click ID contain customer information?

No. Treat it as an opaque lookup key and keep email addresses, names, phone numbers, and other direct personal data out of campaign URLs. The tracker can resolve the key without exposing identity in the URL.

How does a click ID work with a postback?

The destination stores the click ID with the lead or order, then returns it when the verified conversion occurs. The tracker uses that value to find the original visit, as explained in the postback URL guide.

Start free and build your campaign flow.