Which Facebook ads bring paying customers: matching CRM sales to ads

Why Ads Manager can’t answer this

Ads Manager counts what Meta sees: lead form submissions, and website events from the pixel or Conversions API that happen within its attribution setting — 1 or 7 days after a click, or 1 day after a view.

A sale closed on the phone two weeks later, paid by bank transfer and recorded in Pipedrive, isn’t one of those. And even for events Meta does count, it warns that tools disagree:

there can be differences in how different tools detect, define and calculate conversions.

Three ways a lead reaches your CRM

How the ad travels into the CRM depends on where the lead fills in their details:

Most businesses have all three. Fix the first two; for the third, keep it as a known gap rather than guessing.

Tag every link with the ad ID

Meta fills dynamic parameters into the ad’s link for you. Its official list: {{campaign.id}}, {{adset.id}}, {{ad.id}}, the matching .name versions, {{placement}} and {{site_source_name}}. You add them under Tracking → URL parameters when you create the ad (source).

Use IDs, not names. Meta’s own page explains why:

Campaign, ad set or ad names can still be changed, but the parameters will refer to the original names.

A string that works with any CRM:

utm_source={{site_source_name}}&utm_medium=paid&utm_campaign={{campaign.id}}&utm_term={{adset.id}}&utm_content={{ad.id}}

Two cautions from Meta. Changing URL parameters after publishing may cause your ad set to re-enter the learning phase, so set them on new ads. And A URL parameter is only applicable to the first product page — your site has to keep the tags until the form, usually in hidden form fields filled from the landing page address.

Meta lead forms already carry the ad

Every lead from a Meta lead form comes with the ad it came from. The download file has ad_id, adset_id and campaign_id next to the lead’s answers (source), and the lead webhook sends ad_id within minutes (source). Leads from organic reach have no ad.

The weak spot is the integration in between. Meta’s own documentation notes:

Hubspot’s Lead Sync integration does not store the Meta Lead ID.

Open one lead in your CRM and check that the ad ID, or at least the lead ID, is saved on it. If not, map it in the integration or add tracking parameters to the form — Meta passes them to the CRM with the lead.

What your CRM keeps on its own

Don’t assume the CRM fills this in for you:

• Pipedrive records where a deal came from as a channel and origin, such as Web forms (source) — but not which ad. Its web form documentation mentions neither UTM tags nor hidden fields.
• HubSpot sets the original source automatically, down to Paid social → Facebook → the campaign name taken from utm_campaign (source). That is campaign level; ads need utm_content.

So for either, store the tags from the link in deal fields of your own — one per tag.

Match payments to ads

Once deals carry tags, the match is mechanical:

1. Export paid deals with the amount, the payment date, the lead date and the tags.
2. Match from precise to rough: ad ID first, then ad set, then campaign.
3. Don’t guess. If a name fits several ads, leave the payment unmatched and count it separately — spreading it over the ads invents half the report.
4. Compare money with spend per ad for the same leads, not per day.
5. Group by creative when the same creative runs in several ad sets, to see which message sells.

Give leads time to pay

The most common mistake is judging a campaign by payments before its leads could pay. A week-old campaign in a business with a three-week sales cycle always looks unprofitable.

Your curve will differ — a shop paid on the spot is near 100% on day one, a complex B2B sale may be 20% after a month. Measure it from your own payments: for each paid deal, the days between lead and payment.

Then count money two ways. By payment date shows what arrived this month. By lead date shows what the leads of a period have paid so far — the fair way to compare campaigns, as long as the period is old enough.

Send CRM stages back to Meta

The other direction is worth doing too. With the Conversions API for CRM, you send lead stages — qualified, opportunity, converted — back to Meta, so delivery can aim at leads that turn into customers (source). Meta’s guidance:

• it works with Meta lead forms (Instant Forms), and at least 200 leads a month;
• upload at least once a day, and send each stage change within 7 days (source);
• the stage you optimise for should happen within 28 days of the lead.

Since April 2026 the qualified leads goal needs this integration for new campaigns (source), and the old Offline Conversions API was discontinued in May 2025 (source).

It improves who Meta shows ads to. It doesn’t tell you which ads to keep: that still comes from your own match of payments to ads. Setup, fields and deadlines are in Meta Conversions API for CRM.

Mistakes that break the match

1. Tagging with names. Renamed ads keep their old names in the link, and shared names can’t be told apart.
2. Losing tags after the first page. The visitor browses, then fills in the form — and the tags are gone.
3. An integration that drops the ad ID. Leads arrive in the CRM without the ad they came from.
4. Judging too early. Payments for this week’s leads arrive next week or next month.
5. Expecting Ads Manager and the CRM to match. They count different things in different windows.

How Variafy does it

Variafy connects your Meta ad accounts to an AI assistant and does this match for you:

• Payments in. From Pipedrive, a Google Sheet or an uploaded file — only the columns it needs: amounts, dates and tags.
• Matched by tags, precise first: ad, then ad set, then campaign, by ID or by name. When no tag names one ad alone, the tags together often do. A name several ads share is never guessed — that money is reported as unmatched, with its tags.
• Your own payment curve. It measures how long your leads take to pay, and doesn’t call a campaign a loss before its leads have had that time.
• By payment date or by lead date, and by creative across ad sets.

Add https://www.variafy.com/mcp to your assistant. Variafy is in private beta: join the waitlist.

How we checked

Questions

Related guides

• Meta Conversions API for CRM: send lead stages and sales back to Meta
• Why is my Facebook cost per lead going up — and what’s a good CPL?
• Facebook ads alerts: what to watch and how to get notified