Facebook Ads Lead Attribution: Tracking Conversions After iOS 14

In early 2021, Apple released iOS 14.5 with App Tracking Transparency (ATT), a feature that requires apps to ask permission before tracking user activity across other companies' apps and websites. Most users chose not to be tracked. The impact on Facebook Ads was immediate and severe.

Advertisers saw their reported conversions drop by 30% to 60% overnight. Not because fewer people were converting, but because Facebook could no longer track them. Campaign optimization broke down. Audience targeting became less precise. And ROAS reporting became unreliable.

More than four years later, Facebook Ads attribution is still fundamentally broken for businesses that rely solely on Facebook's pixel-based tracking. But there is a solution, and it does not depend on Facebook's tracking infrastructure at all.

What iOS 14 Actually Broke

To understand the fix, you need to understand what broke. Before iOS 14, Facebook's tracking worked like this:

The Facebook pixel on your website tracked visitor behavior and matched it to Facebook user profiles.
When someone clicked a Facebook ad and later converted on your site, the pixel reported the conversion back to Facebook.
Facebook used this conversion data to optimize ad delivery, find similar audiences, and report ROAS.

iOS 14 disrupted this system at multiple levels:

Cross-app tracking restrictions. The Facebook pixel relies on third-party cookies and cross-site tracking. iOS now blocks this by default for users who opt out of tracking.
Delayed reporting. Facebook switched to a modeling-based approach for conversions it cannot directly observe, introducing delays and estimates instead of real data.
Reduced attribution windows. Facebook shortened its default attribution window from 28-day click to 7-day click, missing conversions that happen after a week.
Limited event reporting. Advertisers are now limited to 8 conversion events per domain, and each event must be prioritized.
Audience degradation. Lookalike audiences and retargeting pools became smaller and less accurate as Facebook lost visibility into user behavior.

Facebook's Proposed Solutions (and Their Limitations)

Conversions API (CAPI)

Facebook's primary recommended solution is the Conversions API, which sends conversion data from your server to Facebook's servers. This bypasses browser-level restrictions because the data is sent server-to-server.

While CAPI is an improvement over pixel-only tracking, it has practical challenges:

Requires server-side implementation or a compatible integration platform
Works best when you can match website visitors to Facebook users using hashed email addresses or phone numbers, which only works for logged-in users or form submissions
Only reports data back to Facebook, so you are still dependent on Facebook's dashboard for attribution insights

Aggregated Event Measurement

Facebook's Aggregated Event Measurement protocol attempts to report conversions in an aggregate, privacy-preserving way. In practice, it limits data, delays reporting, and introduces modeled (estimated) conversions that many advertisers find unreliable.

The First-Party Attribution Solution

The most effective response to iOS 14 is not trying to fix Facebook's tracking. It is implementing your own first-party attribution system that works independently of any ad platform's tracking infrastructure.

Here is the fundamental difference:

Facebook's pixel relies on third-party cookies and cross-site tracking (broken by iOS 14)
First-party attribution uses your own website's first-party cookies and does not depend on any external tracking system

First-party cookies are set by your own domain and are not affected by iOS 14 restrictions. When a visitor clicks your Facebook ad and lands on your site, a first-party attribution script captures:

The fbclid parameter (Facebook Click ID) from the URL
The UTM parameters you set on the ad URL
The landing page URL
The referrer (facebook.com)

This data is stored in a first-party cookie on your domain and persists as the visitor browses your site. When they fill out a form, the attribution data is submitted alongside their contact information into your CRM.

How to Set Up First-Party Facebook Ads Attribution

Step 1: Tag All Facebook Ad URLs with UTM Parameters

In Facebook Ads Manager, set UTM parameters at the ad level:

utm_source=facebook&utm_medium=paid_social&utm_campaign={{campaign.name}}&utm_content={{ad.name}}

Facebook's dynamic parameters (double curly braces) automatically populate with the actual campaign and ad names.

Step 2: Install a First-Party Attribution Script

Add a JavaScript attribution script to your website that captures UTM parameters, fbclid, and referrer data on every page load. SourceStream does this automatically with a single script tag.

Step 3: Add Hidden Fields to Your Forms

Add hidden fields to your website forms for each attribution data point. The script populates these fields when the visitor reaches a form page.

Step 4: Analyze in Your CRM

With attribution data in your CRM, you can build reports showing:

How many leads came from Facebook Ads (by source = facebook, medium = paid_social)
Which Facebook campaigns generate the most leads
Which campaigns produce leads that actually close (lead quality)
True cost per customer for each Facebook campaign

Why First-Party Tracking Works Where Facebook's Pixel Does Not

First-party attribution is immune to the iOS 14 restrictions because it operates entirely on your own domain:

No third-party cookies. First-party cookies are set by your domain and read by your domain. No cross-site tracking is involved.
No reliance on Facebook's pixel. You do not need the Facebook pixel to track conversions on your site. The attribution script captures the data independently.
Complete conversion data. Every form submission includes attribution data, regardless of the visitor's iOS version, browser settings, or tracking consent choices on Facebook's platform.
No 7-day limitation. First-party cookies can persist for weeks or months. If a visitor clicks a Facebook ad today and converts three weeks later, the attribution data is still there.

Beyond Conversion Counting: Real Attribution

The biggest advantage of first-party attribution over Facebook's pixel is that you are not just counting conversions. You are connecting Facebook Ad clicks to named leads in your CRM, tracking them through your sales pipeline, and measuring actual revenue generated.

This means you can finally answer the questions that iOS 14 made unanswerable within Facebook's own reporting:

What is the true ROAS for each Facebook campaign?
Which audiences produce the highest-value customers?
How does Facebook Ads lead quality compare to Google Ads or organic?
Should we increase or decrease Facebook Ads spend?

The answers are in your CRM data, not in Facebook's dashboard. First-party attribution is how you get them there.

Getting Started

SourceStream captures fbclid, UTM parameters, and all referrer data using first-party cookies. It works regardless of iOS version, browser privacy settings, or ad blocker configuration. Install it once, and every Facebook Ads lead in your CRM comes with complete attribution data.

iOS 14 broke Facebook's tracking, but it did not break attribution. You just need to do it on your own terms.