Click IDs Explained

What a click ID is

When someone clicks an ad, the platform appends a parameter to the landing page URL that identifies that click: which campaign, ad and person it belongs to. Send that identifier back with a conversion and the platform can attribute the conversion to the click with certainty, without cookies or device identity.

For lead generation this is the single most valuable field you can store with a lead.

The identifiers by platform

Platform	URL parameter	Stored as	Notes
Meta (Facebook, Instagram)	fbclid	_fbc cookie value, fb.1.<timestamp>.<fbclid>	Send as fbc with Conversions API events; _fbp is the browser ID
Google Ads	gclid, gbraid, wbraid	as-is	gbraid and wbraid are the iOS privacy variants; all three work for offline import and Enhanced Conversions
TikTok Ads	ttclid	as-is	Sent with Events API events
Microsoft Advertising	msclkid	as-is	Offline conversion import
LinkedIn Ads	li_fat_id	as-is	Conversions API
Snapchat Ads	ScCid	as-is	Conversions API
Pinterest Ads	epik	as-is	Conversions API

DealOracle captures every one of these automatically when the pixel is installed on the landing page.

How DealOracle captures and stores them

1. The pixel reads the parameters from the landing page URL on the first page view of a session.
2. It stores them first-party on your domain, in both a cookie and local storage, so a visitor who browses several pages before the form still carries them.
3. On form submit it attaches them to the lead: through hidden fields the form posts to your CRM, through the identify call, or through the DealOracle ingestion webhook.
4. The lead record in DealOracle keeps the click IDs alongside the hashed email and phone, and every conversion sent for that lead includes them.

If your form lives inside an iframe (LeadConnector-hosted forms, some Typeform and Calendly embeds), the frame cannot read the parent page's URL. The GoHighLevel guide covers passing the identifiers into the frame.

How long each one stays valid

• Meta: the click ID must be sent within seven days of the click for click-through attribution.
• Google Ads: offline conversions can be uploaded up to 90 days after the click (the conversion action's click-through window applies).
• TikTok: seven days for click attribution.
• Microsoft, LinkedIn, Snapchat, Pinterest: vendor windows vary between 7 and 90 days; DealOracle sends the event as soon as the stage changes, which is almost always inside every window.

DealOracle sends the event at the moment the CRM stage changes. If a deal closes 60 days after the click, Meta will not attribute it to the click (outside its window) but will still match it to the person through the hashed email and phone; Google will attribute it if the conversion action's window allows.

When the click ID is missing

A lead with no click ID is usually one of these:

• The visitor arrived organically or from a share, not an ad.
• The form stripped the parameters (iframe, a redirect that dropped the query string, a form builder that only posts its own fields).
• The pixel was not installed on the page the ad landed on.

DealOracle still sends the conversion with the hashed email and phone, which the platforms use to match the person to any ad exposure they have on record. The match is weaker than a click ID but far better than nothing. The Lead Manager shows which leads carry a click ID so you can find the pages that lose them.