TRACKING SPECIALIST — BARIS ASA · LONDON
Synctag
Start the check → TRACKING SPECIALIST — BARIS ASA · LONDON

READING ROOM › SYMPTOM FILES › SYM-061

SYMPTOM FILE SYM-061 FILED 11 NOV 2026 · REVISED 11 NOV 2026

Do gclid and fbclid survive your checkout? Where click IDs get lost on the way to the order.

ALSO FILED AS
  • “does gclid survive checkout”
  • “where do click IDs get lost”
  • “gclid lost at checkout”
  • “fbclid present but _fbc missing”
  • “fbc missing from Conversions API purchase events”
  • “click ID not passed to purchase event”
  • “_gcl_aw cookie missing on thank you page”
  • “Google Ads conversions not attributed after PayPal checkout”
  • “how to test if gclid reaches the order”
  • “store gclid with the order”

Baris Asa, tracking specialist, London · Filed 11 November 2026 · Last checked: November 2026

Yes, gclid and fbclid usually survive checkout, as long as a tag saved them in a cookie on your own site when the visitor landed. If Google Ads or Meta credit fewer orders than your store took, one of six places is dropping them: a second checkout domain, buyers paying off-site and not returning, server events without the ID, Safari, phone sales, or declined cookies. The check below shows which.

The gclid is the ID Google Ads adds to an ad click; the fbclid is Meta’s. This note follows them from landing page to order. If the gclid never reaches the landing page, start with auto-tagging and the missing gclid. If the problem is GA4 filing sales under the wrong channel, that is the order to work in. This page is about what Google Ads and Meta can credit.

Where it gets lostWhere you’d see itFault
Checkout on a second domainAds and Meta credit fewer orders than the store; GA4 referrals list your checkout domainF-204 F-205
Buyer pays off-site, doesn’t come backPayPal or Klarna orders credited less often than card ordersF-401
Server event without the click IDMeta server purchases arrive, few credited to an adnone, add fbc to the event
Safari deletes the cookieiPhone and Mac orders credited less often than Chrome and AndroidF-401
Sale closes by phone or invoiceThose sales never appear in Google Adsnone, needs offline import
Visitor declines advertising cookiesA gap about the size of your decline rate is expected; well above it is a faultF-201

How do I tell which one is mine?

Start with a spreadsheet, not DevTools. Put Google Ads and Meta purchases beside your store’s orders for four closed weeks. Split by device, by payment method and, if you take them, by phone orders.

Read the share credited in each segment, not the totals. Platforms never credit every order, so a gap on its own means little. A segment sitting well below the others is the signal. Safari low and Chrome fine points at the Safari row. PayPal low and cards fine points at the off-site row. Everything low on the day a new checkout went live points at the second-domain row.

Each row is a separate check. Don’t fix all six before you know which one is costing orders. To find the exact step, run the test order further down.

How does a click ID get from the ad to the order?

It only has to arrive once. A tag on the landing page copies it into a first-party cookie, meaning one set on your own domain, and whatever reports the order reads that cookie later.

  • Google Ads. The Google tag or GTM’s Conversion Linker stores ad click information in cookies named _gcl_*, such as _gcl_aw, and in local storage under _gcl_ls (Conversion Linker). Google lists _gcl_aw with a 90-day lifespan (Google’s advertising cookies). Some iOS clicks carry wbraid or gbraid instead of a gclid (iOS measurement), so check the other _gcl_ cookies before deciding the ID was lost.
  • Meta. The Pixel stores the click ID in the _fbc cookie once it sees an fbclid in the URL (fbp and fbc parameters).

So a thank-you page with no gclid in the address is normal.

Does the click ID survive a separate checkout domain?

Not unless the two domains are linked. A cookie belongs to the domain that set it, so a hosted checkout or booking engine on its own address starts with none of yours. A subdomain of your shop is a different case and usually shares them.

  • Google Ads. In the Conversion Linker, tick “Enable linking across domains” so the tag reads an incoming linker parameter, list the checkout domain under “Auto Link Domains” so links to it carry one, and tick “Decorate Forms” if checkout starts with a form post (Conversion Linker). The same tag has to run on the checkout domain.
  • GA4. The same _gl parameter, and the same breakages: a redirect that drops it, navigation by script, a domain missing from the list. Diagnosis in cross-domain tracking not working; filed as F-204 , and the split session as F-205 .
  • Meta. _fbc stays on the domain that set it. Meta’s guidance for a missing cookie is to build fbc from the fbclid, so on a second domain either the fbclid travels in the link or your systems pass the value along.

What happens on the trip to PayPal, Klarna or the card provider?

The trip deletes nothing. The cookies wait in the buyer’s browser while they pay. Two things can stop the conversion firing.

  • The buyer doesn’t come back. They pay, close the tab and never load your confirmation page, so a conversion tag on that page never fires.
  • The confirmation page isn’t yours. If the provider shows it, your tags were never there.

The fix is a server event: your own server, or your shop platform, reports the purchase to Google or Meta directly, so it doesn’t depend on the buyer’s browser. Browser-only collection is filed as F-401 . GA4 has a separate problem on the same trip, the provider showing up as a referral source. The click ID is fine there; the fix is in payment gateway showing as referral.

Does the server event carry the click ID?

Only if you hand it over. A server sees the order, not the buyer’s cookies. Send a purchase without the stored ID and it arrives with no click attached.

  • Meta. Meta recommends sending fbc with every Conversions API event. Your server can read the fbclid from the request URL when it is there. The value is case sensitive, so don’t lower-case or trim it (fbp and fbc parameters). If server events don’t arrive at all, see Meta CAPI server events not showing.
  • Shopify. A Customer Events pixel reads cookies on the top frame through the async browser.cookie API (Web Pixels browser API), so it can pick up _gcl_aw and _fbc unless a server set them as httpOnly, which no script can read. To keep the IDs on the order itself, the theme can write them as cart attributes; Shopify says private cart attributes are hidden at checkout but visible on the order details page (Cart API). What the pixel can’t see: the custom pixel sandbox.
  • Phone and CRM sales. Google’s guide captures the GCLID on landing, keeps it in a cookie or local storage, passes it in a hidden form field and stores it with the lead (offline conversion import). Google now recommends enhanced conversions for leads, with the GCLID kept in the same upload: enhanced conversions for leads or GCLID import.

How long does the click ID last?

Ninety days in most browsers. Google lists _gcl_aw at 90 days, and Meta says to set _fbc for 90 days if your server writes it.

Safari is shorter. WebKit deletes cookies created in JavaScript after 7 days of no user interaction with the website. When it detects link decoration, such as a click ID in the URL, it caps cookies created in JavaScript on that landing page at 24 hours (WebKit tracking prevention). A Safari buyer who clicks an ad and orders days later, without visiting in between, can arrive with no click cookie. Short buying cycles barely notice. Anything with a consideration window longer than a week will.

The fix is to change who writes the cookie. The caps are on cookies created in JavaScript. A cookie your own server sets in its response, for example from server-side GTM on a subdomain of your site, isn’t one, though WebKit still caps it if the subdomain is CNAME-cloaked or on a third-party IP address. Google Tag Gateway doesn’t change who writes it: Tag Gateway doesn’t fix Safari.

Safari Private Browsing is different again: WebKit’s Safari 17 notes list “blocking for known tracking query parameters in links”, without publishing which ones. Check whether the fbclid or gclid arrives in a Private Browsing test before blaming this (Safari 17.0).

Is the click ID stored if the visitor declines cookies?

Not in a cookie. With ad_storage (advertising cookies) denied in Google’s advanced consent mode, no advertising cookies are written or read. In basic mode the tags don’t fire at all (consent mode overview). A banner that holds the Meta Pixel until consent does the same to _fbc.

What you get back from wiring it properly: URL passthrough keeps the gclid in the address on same-domain pages (consent mode guide), and consent mode models part of what the banner hides. A gap about the size of your decline rate is expected. A gap well above it is F-201 .

What if the click ID is already lost?

Fix the path for future orders, and send hashed customer data so the platforms can still match some sales.

  • Google. Enhanced Conversions sends a hashed email, phone or address with the conversion and matches it to signed-in Google accounts (about enhanced conversions). Not set up is F-402 ; set up but not matching is Enhanced Conversions not working. It does not remove duplicates.
  • Meta. Conversions API events also match on hashed email, phone and the fbp browser ID: Meta Event Match Quality low. Build fbc only from a real fbclid; with no click, leave it out.

Neither recovers every click. They are the fallback, not the fix.

How do I trace one test order?

In Chrome or Edge with cookies cleared, not Safari Private Browsing.

  1. Land. Open a product page with ?fbclid=TestFbclid123 added. Add &gclid=TeSt-123 only if you won’t read this session in GA4: with a linked Ads account, a fake gclid can change the GA4 source. Accept the cookie banner.
  2. Check storage. DevTools, Application, Cookies, your domain. Look for _gcl_aw (if you added the gclid) and _fbc, whose value should end in TestFbclid123 exactly as typed.
  3. Walk to checkout. If the address changes domain, check the link carried _gl, then look for the cookies under the new domain.
  4. Pay. Use the provider’s sandbox, or a small real order you refund. Return to your confirmation page; then repeat once without returning.
  5. Read what each system received. Tag Assistant should show the Google Ads conversion firing on your confirmation page. In Meta Events Manager, Test events, a server event only appears if sent with the test_event_code from that tab (using the Conversions API); check the Purchase carries fbc. Then open the order record and check the IDs were saved.
  6. Decline and repeat. Clear cookies, decline advertising cookies, land again. No _gcl_aw is expected; with URL passthrough on, the gclid stays in the address on same-domain pages.

The step where a value disappears is your answer. Two cautions. Meta says test events still flow into Events Manager and measurement, so remove test_event_code afterwards. A refunded real order stays counted in Google Ads and Meta unless you adjust it.

What fixes each one?

In the order of the table:

  1. Second domain: link it in the Conversion Linker and GA4, and carry the fbclid across.
  2. Off-site payment: report the purchase from your server.
  3. Server event without the ID: save the click IDs with the order and send them on that event.
  4. Safari: have your own server write the cookie.
  5. Phone sales: import them with the stored GCLID and hashed email.
  6. Declined cookies: wire consent mode so URL passthrough and modelling do their part.

Redirects and the confirmation page are developer work. Rows 1 to 4 and 6 are measurement work, and each can be proved with the test order above. Campaigns and the attribution model stay with your marketers.

Rows 1 and 6 also change which channel GA4 gives the sale: cross-domain measurement keeps one visit across the checkout step, and URL passthrough keeps the click when a visitor declines cookies. If GA4 files those sales under Referral or Direct as well, I fix both in one pass, as repair for sales credited to the wrong channel.

Common questions

Does the gclid need to be in the URL of the checkout and thank-you page?

No. It only has to reach the landing page. A Google tag stores it in a cookie on your own domain (_gcl_aw, which Google lists with a 90-day lifespan), and the conversion tag on the order page reads the cookie. A thank-you page address with no gclid is normal.

No. The cookies stay in the buyer’s browser while they pay. The order goes uncredited when the buyer doesn’t come back to your confirmation page, so a browser conversion tag never fires. Reporting the purchase from your server, with the stored click ID, closes that gap.

How do I get the gclid and fbc into a server-side or offline conversion?

Read them in the browser on landing and save them with the order or lead, then send them with the conversion. Meta recommends sending fbc with every Conversions API event; the click ID is case sensitive, so pass it unchanged. For phone and CRM sales, Google recommends enhanced conversions for leads, with the GCLID kept in the same upload.

What if the click ID is already lost?

Fix the path for future orders, and send hashed customer data so the platforms can still match some sales: Enhanced Conversions for Google, email, phone and the fbp browser ID for Meta. Neither recovers every lost click, and Enhanced Conversions does not remove duplicates.

Can I check this myself without a developer?

The first part, yes. Compare Google Ads and Meta purchases with your store’s orders for four closed weeks, split by device and by payment method. A segment credited well below the others points to the leak. Finding the exact step needs one test order with DevTools open.

Sources

Read on 11 November 2026:

  • Tag Manager Help, Conversion Linker (stores ad click information in _gcl_* cookies and _gcl_ls local storage; Enable linking across domains, Auto Link Domains, Decorate Forms)
  • Google, advertising cookies (_gcl_aw and other _gcl_ cookies, 90-day lifespan)
  • Google Ads Help, iOS measurement (no GCLID for some iOS 14 traffic; wbraid and gbraid)
  • Google, consent mode overview (advanced mode with ad_storage denied: no advertising cookies written or read; basic mode blocks tags)
  • Google, consent mode guide (URL passthrough conditions; same domain only)
  • Google Ads Help, offline conversion import (GCLID in cookie or local storage, hidden form field, stored with the lead)
  • Google Ads Help, about enhanced conversions (hashed first-party data matched to signed-in Google accounts)
  • Meta for Developers, fbp and fbc parameters (_fbc set by the Pixel; build from fbclid; 90-day expiry; case sensitive; send with every event)
  • Meta for Developers, using the Conversions API (Test events need test_event_code; test events are not dropped; remove it in production)
  • WebKit, tracking prevention (JavaScript cookies deleted after 7 days without interaction; 24-hour cap after link decoration; CNAME and third-party IP cloaking defence)
  • WebKit, features in Safari 17.0 (Private Browsing blocks known tracking query parameters in links)
  • Shopify, Web Pixels browser API (async browser.cookie on the top frame) and Cart API (cart attributes; private attributes visible on the order details page)

← back to the reading room