Click ids
Keep the click
that brought them.
Browsers and blockers strip gclid and fbclid from your links before the page loads. Cookiebees reads every click id it can find, keeps it on the visitor, and puts it on the order, so the sale goes back to the ad that earned it.
30-day free trialNo card requiredSet up in minutes
Why do my Google Ads sales show up as Direct?
What happens when Safari strips gclid from the link?
Where they landed, 6 days before buying
yourstore.com/neem-face-wash?fbclid=IwAR9kQm…&utm_source=meta&utm_campaign=diwali_prospecting&utm_content=neem_video_02Then: 3 more visits, a closed tab, a checkout app. The order arrives on day 6.
Which Meta ad gets the credit when someone clicked two?
Can a WhatsApp link tell me who is browsing?
What it is worth
Fewer sales with no source
Fewer orders read as Direct
When a browser deletes the click id, the copy under a Cookiebees name still arrives, and the sale keeps its campaign.
Meta credits the ad they clicked last
_fbc always names the newest Meta click, in the cookie and in our record, so the latest ad gets the sale.
Known people, matched on later events
A tap on your WhatsApp or email link joins that browser to the contact, with every visit it made before.
Kept past stripping
A copy of each click id, under a name no browser strips.
Settings, Tracking gives you one string per ad platform to paste once. It keeps your normal utm_ tags and adds Cookiebees’ own copy of each value. When the original survives, the original wins. When a browser removes it, the copy fills the gap.
- Google, Microsoft, TikTok, LinkedIn and Meta, each with where to paste it
- gad_source read as a Google ad click, even with no gclid
- The same slot means the same level everywhere: campaign, ad set, ad
- Both prefixes, cb_ and the older mm_, are read for good
The ad's link
yourstore.com/neem-face-wash?gclid=Cj0KCQjw…&cb_gc=Cj0KCQjw…&gad_source=1&utm_source=google&utm_campaign=21447790A privacy browser removed gclid before the page loaded. cb_gc arrived.
Kept on the visitor, then on the order
The newest Meta click
Two ads, one shopper. _fbc names the one they clicked last.
Meta credits a sale to the click its _fbc cookie names. A new fbclid on the page replaces any older click, in the cookie and in our record together. A reload of the same click keeps its value and its time. With no fbclid on the page, nothing is built.
- Meta’s fbclid cannot be renamed, so it is recorded on the first visit and kept
- A lost _fbc is put back from the record, inside Meta’s 90 days
- A late write of an old value cannot undo a newer click
- The same rule in the store tag, the lead tag, forms and the WhatsApp widget
_fbc now
fb.1.1727712000000.IwAR1aXq…
Link identity
A tap on your own link says who is browsing.
A WhatsApp message or an email you send goes to one known person. When they tap a link to your site, the browser that opens it is joined to their lead or customer record, with every visit it made before. Later events from that browser reach Meta and Google with their hashed email and phone.
- Tracked WhatsApp links, emails from Cookiebees, and recovery messages
- Only links to your own site carry the short signed token
- It never creates anyone and never moves a browser from one person to another
- An edited token, or one tapped after 30 days, is refused
Visitor mmc_7f3e…a91
4 page views over 9 days · no name, no email
They tap the link in your WhatsApp message
yourstore.com/neem-face-wash?cb_pt=eyJvIjo…The message went to one known contact, so the tap says who opened it.
Every later event from this browser
Click IDs & UTMs, on your own site.
Start a workspace and watch it work on your next order or lead, or let us walk you through it.
Switching it on
Paste once per platform
The strings are ready-made for your workspace in Settings, Tracking.
- 1
Install the tag
Put the Cookiebees tag on every page. It reads the click ids and cookies on landing.
- 2
Copy each string
Pick an ad platform in the list. Google asks whether your account already has a tracking template.
- 3
Paste where it says
Google Ads into the Final URL suffix, Meta into the ad’s URL parameters, and so on.
- 4
Agree the naming
Tick that you will use it on every campaign, and press Agree. The card records who agreed, and when.
Inside the module
What is inside
Every click id is kept raw on the visitor and on the order, where you can read it.
gclid, gbraid, wbraid, gad_source and gad_campaignid, with Google’s own _gcl_aw cookie
Meta and Microsoft
fbclid with the _fbp and _fbc cookies; msclkid with the UET cookies
TikTok and ChatGPT Ads
ttclid with the _ttp cookie, and oppref
LinkedIn, Snapchat, Pinterest, Reddit
Their cookies on every site; on a lead site their click ids too, and X’s twclid
Campaign tags
utm_source to utm_content and utm_id, first touch and latest touch
Who tapped
Browsers recognised from your links, earlier page views joined, and taps not joined with the reason
Open any order and read the click ids and campaign tags it carried, raw, beside the journey they built.
Where this sits
One of the four steps an order goes through.
Every feature reads the same identity. Open any of them; each has its own page.
1Capture
Every visit, on your own domain.
2Understand
First click to delivered order.
3Send back
Real revenue back to the ads.
4Act
Turn it into the next sale.
Stop losing the click
Every click id kept.Every sale back to its ad.
Install the tag, paste one string per ad platform, and the next order arrives with the click that started it.