How to Track Facebook Ads Attribution with fbclid

When someone clicks your Facebook ad and lands on your website, Meta appends a unique identifier to your URL called the fbclid. This Facebook Click Identifier is your key to accurate attribution, but most advertisers either ignore it or don't know how to use it properly. The result: broken attribution, wasted ad spend, and Meta's algorithm optimizing on incomplete data.

fbclid is automatically added to URLs when users click Facebook or Instagram ads, enabling click-level attribution by linking user engagement to conversion events within Meta's ad ecosystem. This guide shows you how to capture, store, and use fbclid for accurate Facebook Ads attribution.

What is fbclid?

fbclid stands for Facebook Click Identifier. When a user clicks your ad on Facebook or Instagram, Meta automatically appends this parameter to your destination URL. The fbclid looks like this:

yoursite.com/landing-page?fbclid=IwAR3xJ2kL5mN7pQ9rS1uV3wX5yZ7aB9cD1eF3gH5iJ7kL9mN1oP3qR5sT7uV

This unique string identifies the specific click event, connecting it to the user, ad, campaign, and placement that generated the click. When that user later converts, the fbclid allows Meta to attribute that conversion back to the original ad interaction.

fbclid vs UTM Parameters

fbclid and UTM parameters serve different purposes. UTM parameters are manual tags you create to track traffic across platforms in tools like Google Analytics. They tell you which campaign, source, and medium drove the traffic, but they're platform-agnostic.

fbclid is Meta-specific and automatic. It enables click-level attribution within Meta's ecosystem, allowing the platform to match conversions to specific ad interactions for optimization.

The best practice is using both together. UTM parameters give you visibility in your analytics tools. fbclid feeds conversion data back to Meta for algorithmic optimization. Without fbclid, Meta can't accurately attribute conversions, and your campaigns won't optimize effectively.

How fbclid Attribution Works

The Click Event

When a user clicks your Facebook ad, Meta generates a unique fbclid and appends it to your URL. This happens automatically for all ad clicks. You don't need to configure anything for fbclid to appear.

The Cookie Connection

When the user lands on your site, Meta's Pixel reads the fbclid from the URL and stores it in a first-party cookie called _fbc. The _fbc cookie format is: fb.1.timestamp.fbclid_value. This cookie persists for 90 days by default.

Meta also sets an _fbp cookie (Facebook Browser ID) on first pageview with the Pixel, which identifies the browser independently of click events.

The Conversion Match

When the user converts (makes a purchase, submits a form, etc.), you send the conversion event to Meta with the fbc and fbp values. Meta matches these identifiers to the original ad click and attributes the conversion to the correct campaign, ad set, and ad.

Capturing fbclid for Attribution

Method 1: Meta Pixel (Client-Side)

The Meta Pixel automatically captures fbclid from the URL and stores it in the _fbc cookie. If you have the Pixel installed, this happens automatically.

However, browser privacy features, ad blockers, and iOS restrictions can prevent the Pixel from firing. When that happens, fbclid is never captured and the conversion can't be attributed.

Method 2: Server-Side Capture

For reliable attribution, capture fbclid server-side. When a user lands on your site with an fbclid parameter, extract it from the URL and store it in your database associated with that session. This works regardless of browser settings or ad blockers.

Store the fbclid along with: session ID, timestamp, landing page URL, and any user identifier if they're logged in or identified later.

Method 3: Google Tag Manager

You can configure Google Tag Manager to capture fbclid from the URL and pass it to your data layer or directly to Meta's Conversions API. This provides a middle ground between pure client-side and server-side approaches.

Connecting fbclid to Meta Conversions API

Meta's Conversions API (CAPI) is the server-side complement to the Pixel. Instead of relying on browser-based tracking, CAPI sends conversion events directly from your server to Meta. For accurate attribution, you should send both fbc and fbp values with every conversion event.

Required Parameters

When sending a conversion to Meta's Conversions API, include: fbc (the Facebook Click ID from the _fbc cookie or captured fbclid), fbp (the Facebook Browser ID from the _fbp cookie), and at least one customer information parameter like email or phone for matching.

Event Deduplication

If you're using both the Pixel and Conversions API, implement event deduplication. Without it, Meta counts each conversion twice, once from the Pixel and once from CAPI. Use an event_id parameter on both the Pixel event and CAPI event to allow Meta to deduplicate.

Troubleshooting fbclid Issues

fbclid Not Appearing in URLs

Sometimes fbclid doesn't appear in your ad URLs. Check that URL Parameters are enabled in your ad settings, your destination URL doesn't have URL redirects that strip parameters, and your website doesn't remove query parameters on page load.

_fbc Cookie Not Set

If the _fbc cookie isn't being created, verify the Meta Pixel is firing on the landing page, check that cookies aren't blocked by consent settings, and ensure the domain matches your Pixel configuration.

Low Match Rates in Events Manager

If your Conversions API events show low match rates, make sure you're sending fbc and fbp with every event, verify the fbc format is correct (fb.1.timestamp.value), and include additional customer parameters like hashed email.

Best Practices for fbclid Attribution

Always Use UTM Parameters Too

Since fbclid may not always be appended, deploy UTM parameters across all Facebook campaigns as backup. This ensures you have campaign-level attribution in your analytics even if fbclid-based attribution fails.

Capture fbclid Server-Side

Don't rely solely on the Pixel. Capture fbclid from URLs server-side for more reliable tracking that isn't affected by browser restrictions.

Refresh Values Regularly

Cookies and sessions expire. If a user returns days later to convert, their _fbc cookie might have expired. Store the original fbclid in your database to maintain attribution for longer conversion windows.

Implement Proper Deduplication

If using both Pixel and CAPI, always send matching event_id values to prevent double-counting conversions.

Arktis automatically captures fbclid and connects it to your conversion data, enabling accurate Facebook Ads attribution without manual configuration.

Track Facebook Attribution with Arktis →

Sources

1. Northbeam, "What is fbclid? A Complete Guide to Facebook Click Identifiers"

2. Justuno, "UTMs, FBCLIDs, & TTCLIDs - Building a Better Audience"

3. Watsspace, "Meta Conversions API fbc and fbp Parameters"

4. Stape, "Facebook Conversions API - Extended 2026 Setup Guide"

5. Triple Whale, "Facebook CAPI (Meta Conversions API) in 2026"

6. Mercado Global Media, "How to Pass FBCLID, FBP & FBC to Meta Ads with GTM"

7. CustomerLabs, "What is FB Click ID and Why It Is Important"