What is fbclid? Meta's click ID explained
fbclid is Meta's click ID. See what it does, how it ties to the _fbc and _fbp cookies and the Conversions API, and what strips it from the URL.

TL;DR
- fbclid is Meta's click ID. It shows up at the end of a link (
?fbclid=...) when someone clicks a link on Facebook or Instagram and lands on your site. - The Meta Pixel stores that value in the
_fbccookie. The_fbpcookie is something else: it identifies the browser, click or no click. - In the Conversions API, the two values go in the
fbcandfbpfields, next to other customer data. - An fbclid in the URL shows the click came from Facebook or Instagram. On its own, it doesn't prove the click was a paid ad.
- Redirects, link shorteners, URL-cleaning scripts, cookie banners and Safari's link protection can wipe the fbclid before anything reads it.
What is fbclid?
fbclid is a code Meta adds to your site's address when someone clicks a link on Facebook or Instagram. The name stands for "Facebook click identifier", and Meta calls the value ClickID. Meta uses it to tie the visit, and any purchase that follows, back to the click that started it.
The link that reaches your store looks like this (Meta's own example):
Meta's page on ClickID and the fbp and fbc parameters describes fbclid on clicks from Facebook and Instagram ads. The same page says Meta attaches the ClickID automatically and that this doesn't touch your other parameters, such as UTMs. The value is case sensitive, and Meta asks you not to change it in any way.
Does fbclid only show up on ads?
No. The ClickMagick knowledge base and Northbeam's docs say it is also added to organic links: posts, links in comments and the profile link. Northbeam classifies visits that arrive with only an fbclid and no UTMs as "Facebook Organic" by default. It also notes that some of those visits can come from ads whose UTMs got lost on the way.
So fbclid tells you which network the click came from. To know whether the click was paid, and from which campaign, you need UTMs or another parameter you put on the ad. The guide How to Use UTM Parameters for Meta Ads shows how to set them up.
What are the _fbc and _fbp cookies?
They are two cookies the Meta Pixel writes on your store's domain when it is set to use first-party cookies, meaning cookies that belong to your own site.
| Cookie | What it holds | When it is created | Format example |
|---|---|---|---|
_fbc | The fbclid, with a version and a creation time | When someone arrives with fbclid in the URL and the Pixel runs on that page | fb.1.1554763741205.<fbclid> |
_fbp | A random browser identifier | When the Pixel loads and there is no _fbp yet | fb.1.1596403881668.1116446470 |
Both follow the same pattern: fb, a subdomain index, the creation time in milliseconds and, at the end, the fbclid (in _fbc) or a random number generated by the Pixel (in _fbp). Meta warns that these values can change from one browser session to the next.
_fbp exists for any visitor the Pixel loads for, wherever they came from. _fbc only appears after a visit with an fbclid.
How does fbclid reach the Conversions API?
The Conversions API sends events from your server to Meta. In its list of customer information parameters, Meta has an fbc field (click ID) and an fbp field (browser ID), next to email, phone, IP address, user agent and others. fbc and fbp are sent unhashed. Email and phone must be hashed.
Meta recommends sending fbc and fbp with every event whenever they exist. If the site has no Pixel, the server can read the fbclid from the URL and build fbc in the same format. In that case Meta suggests setting _fbc as an HTTP cookie with a 90-day expiration, or keeping the value in your own database.
fbc is one identifier among several. Meta requires at least one customer information parameter per event, and it doesn't have to be fbc. The score Meta gives this data is covered in What is Event Match Quality in Meta Ads?, and sending from the server is covered in What Is Server-Side Tracking?.
What wipes out fbclid before it is read?
fbclid is only useful if it reaches, intact, the page where the Pixel or your server reads it. These are the usual places it gets lost:
| What happens | Why fbclid disappears | What to do |
|---|---|---|
A redirect: http to https, non-www to www, a country domain | The redirect rule doesn't pass the parameters along | Use the exact final URL in the ad, or set the redirect to keep the query string |
| A Shopify product page linked without the variant | Northbeam reports that Shopify can rewrite the URL with ?variant= and drop the parameters | Use the link that already includes the variant in the ad |
| A link shortener or vanity URL | Meta mentions cases where the & before fbclid turns into ?, or the reverse, and the page returns a 404 | Test the shortener first, or stop using it in ads |
| A site that rejects unknown parameters | The page errors out or drops the query string | Meta advises adjusting the site to accept or ignore fbclid |
| A script that cleans the URL on load | The address loses fbclid before the Pixel runs | Read and store fbclid before cleaning the URL |
| A cookie banner | The Pixel writes no cookies while it is blocked; if it only runs on a later page, the URL no longer has fbclid | Check that the Pixel runs on the landing page itself right after consent |
| Safari Private Browsing, links opened from Mail and Messages | Apple's link protection removes tracking parameters | You can't prevent it. See the next section |
The redirect and Shopify causes come from Northbeam's docs. The shortener and parameter-rejecting site causes come from Meta's Pixel support page. Google says the same about gclid: if your site uses redirects, the parameter has to reach the final page (About auto-tagging).
What does Apple remove from links?
Apple announced Link Tracking Protection in 2023, with iOS 17. In its announcement, Apple says the extra information some websites add to URLs to track users is now removed from links shared in Messages and Mail, and from links in Safari Private Browsing.
The Safari User Guide says that in Private Browsing, advanced tracking and fingerprinting protection is on by default and removes known tracking parameters from all URLs. Users can turn the same setting on for all browsing in Safari's settings.
Apple doesn't publish the list of parameters. The WebKit team, which builds Safari's engine, explains in Private Browsing 2.0 that Safari removes parameters used to track individual users or clicks before the page loads, and lets through the ones used only for campaign attribution. In Private Browsing, third-party scripts that try to read the full address get the URL without its parameters. Tests published by AppsFlyer report that fbclid and gclid are removed while UTMs stay.
On those visits, fbclid never reaches your store. No Pixel or server can recover it afterwards. UTMs get through, so they remain the way to know which campaign the click came from.
What's the difference between fbclid, gclid, gbraid and wbraid?
Each ad platform has its own click parameter. These are Meta's and Google's, plus two from other networks:
| Parameter | Platform | What it is |
|---|---|---|
fbclid | Meta (Facebook and Instagram) | The click ID Meta adds to the link |
ctwa_clid | Meta (WhatsApp) | The click ID Meta generates for ads that click to WhatsApp. It has its own field in the Conversions API |
gclid | Google Ads | Google's click ID, added by auto-tagging, which is on by default for new accounts |
gbraid and wbraid | Google Ads | Parameters Google introduced in 2021 to measure conversions on iOS under Apple's policies (iOS 14 updates). Google describes GBRAID as an identifier that measures conversions without linking them to individual users or events |
msclkid | Microsoft Advertising | Microsoft's click ID, added by auto-tagging |
ttclid | TikTok | The click ID TikTok adds to the ad's link |
They all only work if the parameter reaches the page intact and gets read there. As with fbclid, Google asks you not to change the case of gbraid.
How do I see fbclid and the _fbc and _fbp cookies?
You can check this in your own browser, with no paid tool.
- Click one of your ads, or a link to your store posted on Facebook or Instagram. On the page that opens, look at the address bar.
fbclid=should be there. - In Chrome, open DevTools, go to Application, then Storage and Cookies, and pick your store's domain. Chrome's guide shows the path.
- Look for
_fbpand_fbc. The text after the last dot in_fbcshould match the fbclid in the URL. Meta uses that same rule to compare the two. - If the URL has an fbclid and there is no
_fbc, the Pixel didn't run on the landing page, isn't using first-party cookies, or something removed the parameter first. If there isn't even an_fbp, the Pixel didn't load or the cookie banner is blocking it. - To test redirects without waiting for a click, open the ad URL with
?fbclid=test123at the end and check whether the parameter is still in the address bar once the page loads. Clear your store's cookies after the test so the fake value doesn't stay in your browser.
The walkthrough How to check if your ad tracking is working covers the rest: the store, Events Manager and Google Ads.
Can I remove fbclid from the URL?
It depends on when. If you strip fbclid before the Pixel or your server reads it, you lose the link to the click, and Meta gets no fbc for that visit. If you strip it afterwards, only from the address bar, the cookie that was already written stays.
For SEO, fbclid creates versions of the same page at different addresses. Google recommends declaring a canonical URL, and the example in its canonical URL guide is a URL with ?gclid= that should be grouped with the clean version. With the canonical tag pointing to the page without parameters, you don't need to touch fbclid.
If the page breaks when fbclid shows up, follow Meta's advice: adjust the site to accept or ignore the parameter.
Where does Clakta fit in?
fbclid helps Meta measure its own ads. It doesn't tell you how much the store sold or which orders were paid. For that you have to start from the order.
Clakta records every visit with the UTMs and the click IDs that arrive in the URL, such as fbclid, and matches each store order to the click behind it. To identify the ad, it uses its own key, the clkt parameter, which you add to the ad's URL (Tag your ad URLs). That key also gets lost if a redirect drops the parameters, so the address bar test applies to it too. In the dashboard, the numbers Meta and Google Ads report sit next to the store's orders, in one place. Clakta doesn't send events to Meta, doesn't change the Pixel or the Conversions API, and doesn't replace the Pixel (What is Clakta). For stores, see the e-commerce page.
FAQ
What does fbclid stand for?
Facebook click identifier. It's the value Meta adds to the link when someone clicks from Facebook or Instagram to your site. Meta calls it ClickID.
If the URL has an fbclid, did the visit come from an ad?
Not necessarily. ClickMagick and Northbeam report that fbclid also appears on organic links, such as posts and comments. To know whether it was an ad, and which one, use UTMs or another parameter set on the ad itself.
What's the difference between _fbc and _fbp?
_fbc holds the fbclid from the latest click that came from Meta. _fbp identifies the browser and is created when the Pixel loads, even without a click. In the Conversions API they go in the fbc and fbp fields.
Does fbclid expire?
Meta doesn't state a lifetime for fbclid itself. For an _fbc cookie set by your server, it recommends a 90-day expiration. A new click brings a new fbclid, and Meta says to update _fbc when the value in the URL differs from the one in the cookie.
Does Safari remove fbclid?
In Private Browsing and in links opened from Mail and Messages, Apple's link protection removes tracking parameters, and AppsFlyer's tests report fbclid among them. Outside those cases, in regular browsing, this only happens if the user turns advanced protection on for all browsing. UTMs stay in the URL.
Can I delete fbclid from the URL?
Only after the Pixel or your server has read it. Deleting it earlier makes Meta lose the link to the click. To avoid duplicate pages in Google, use a canonical tag.
Does Clakta use fbclid?
Clakta records fbclid and other click IDs that arrive in the URL. To match the order to the ad, it uses the clkt key you add to the ad. It shows Meta and Google Ads numbers next to the store's orders and doesn't send events to Meta.