GCLID and FBCLID Explained: What Click IDs Actually Do

That long, ugly string tacked onto the end of a URL right after someone clicks an ad — ?gclid=Cj0KCQ... — isn't junk. It's the one piece of data that lets a platform connect that specific click to whatever happens after it, sometimes minutes later, sometimes months.

What a click ID actually is

When someone clicks a paid ad, the platform appends a unique identifier to the destination URL before the click even lands on your site. That identifier is a click ID — a single value that uniquely represents that specific ad interaction: which ad, which campaign, which exact moment.

Why this one value matters so much

Click IDs are what make offline conversion tracking possible at all. If a visitor clicks a Google ad, fills out a form, and becomes a customer six weeks later inside your CRM, the gclid captured at that original click — stored against the lead record — is the only thing that lets you tell Google Ads "this specific click eventually became a $12,000 customer." Without it, there's no way to connect the two events.

Click IDs vs. UTM parameters

These solve related but different problems. A UTM parameter tells you the general source, medium, and campaign of a visit, in a format any analytics tool can read. A click ID is platform-specific, opaque (not human-readable), and exists specifically to let that platform match a conversion back to the precise originating click — useful for offline conversion import, but not for general cross-platform reporting the way UTMs are.

How to actually capture and use a click ID

• Read the relevant URL parameter (gclid, fbclid, ttclid) from the landing page when a visitor first arrives
• Store it in a hidden form field, or against the session/cookie, so it's available at the point of conversion — even if that's a form fill much later in the same session, or a stored lead record days later
• When the real outcome (a sale, a qualified lead, a closed deal) happens, send it back to the originating platform's offline conversion import, matched by that stored click ID

Where this commonly breaks

• Click IDs get dropped by redirects that strip query parameters — the same failure mode covered in the direct/(none) traffic problem
• Forms that don't capture the URL parameter at all, only asking for name/email
• CRM records that don't have a field to store the click ID, so it's captured but then discarded