Back to resources

Marketing & Measurement · 10 min

Meta Offline Conversions: Measure Sales, Not Just Leads

, Founder, Evolve StrategistsPublished Updated

A cheap lead is only useful if it has a reasonable chance of becoming a customer. When sales happen by phone, in person or after several follow-ups, the ad platform may see the form submission but miss the outcome.

Sending those outcomes back from your CRM changes the information available for campaign decisions. It's the approach we use to connect CRM sales records with Meta advertising. This guide covers why that matters, how the connection works in principle, who owns each part of the setup and how to keep the data trustworthy.

Why Cost Per Lead Can Point You the Wrong Way

Cost per lead is easy to see in the ads manager, so it often drives decisions. It can mislead when lead quality differs between campaigns.

Illustrative comparison: same spend, different outcomes
CampaignSpendValid leadsPaid salesCost per leadMedia cost per sale
AA$3,00030015A$10A$200
BA$3,00015030A$20A$100

Made-up figures to show the arithmetic. They are not Evolve client results.

Campaign A looks twice as efficient on cost per lead. Campaign B produces twice as many sales for the same spend. The comparison only holds if both groups of leads come from the same period and use the same attribution window, and you'd still need revenue per sale and gross margin before calling either campaign profitable.

The difference comes from the leads each campaign attracted, not from the tracking. Sending sales data back makes the difference visible; it doesn't create it.

Decide What Counts as a Sale, and Where It's Recorded

Before anything is sent, the team needs to agree a written conversion definition: the event that counts as a sale in your reporting. There's no universal answer. A signed contract, a deposit, a collected payment and the revenue your accounts recognise can fall on different dates and carry different values.

Then agree which system is the source of truth for each fact. Often the CRM holds the lead, its source and its stage, and the accounting or payment system holds whether money arrived, how much, and whether any of it went back.

The example below counts a sale when payment is collected. Under that definition, a sale is reported once a payment is matched to a CRM deal through a stable sale reference.

Illustrative definitions: a sale counted when payment is collected
StatusCounts whenSource of truthHow to treat it
BookedAn appointment, job or order is confirmedCRMA pipeline stage, not a sale
PaidPayment is collected and matched to the CRM dealAccounting or payment systemThe sale in this example, valued at the amount collected
CancelledA booking or order is withdrawn before paymentCRMNever counted as a sale
RefundedMoney is returned after payment, in full or in partAccounting or payment systemSubtracted in your own net-sales reporting

These rows apply to this example only. If your business counts a signed contract or a deposit as the conversion, they change, and accounting revenue recognition may differ again. Write down the definition you choose and use it in every report.

Under a collected-payment definition, sending a booking as a sale is an easy mistake to make. If the booking is later cancelled, it looks like revenue in the ad platform and nowhere else.

If the CRM is new or being rebuilt, settle these definitions as part of the launch. Our CRM implementation checklist covers stage definitions and the record IDs that make matching possible.

Connect the Lead Record to the Eventual Sale

Closing the loop starts in your own systems:

Capture campaign and ad identifiers when the lead arrives, where they're available and appropriate to collect.
Record the lead source consistently, with a stable CRM identifier for each lead.
Update the record as real events happen: qualified, booked, paid and cancelled.

From there, use your CRM's currently supported Meta Conversions API integration for eligible CRM and offline events. Check current Meta documentation and your CRM's integration before following an older tracking walkthrough.

Conceptually, each event carries:

The event type, such as a qualified lead or a purchase
When it happened
Its value and currency, where relevant
The matching details you're permitted to share, prepared in the way the platform requires
A stable reference for the sale, so the same event isn't counted twice

Share the minimum needed. Never send sales notes or sensitive personal information as marketing data, and make sure your privacy policy and consent practices cover what you share.

Keep Reporting and Optimisation Separate

Two different questions often get mixed up:

Reporting: which ads get credit for sales?
Delivery optimisation: which event is the campaign set up, and eligible, to pursue?

Sending sales data doesn't by itself change what a campaign optimises for. Meta's lead generation guide describes connecting CRM data through the Conversions API alongside a conversion leads performance goal for suitable instant form campaigns. It's a 2023 overview rather than current setup instructions, and what's available for a particular campaign or account changes, so check before planning around it.

Be wary of simple claims in either direction. Lead campaigns don't necessarily chase the cheapest leads, and sending conversion data doesn't automatically teach the platform to find buyers just like yours.

Setup Checklist: Owners and Evidence

Before you rely on the data, give each part of the setup an owner and something you can inspect. The roles below are typical; in a small business one person may hold several.

Setup responsibilities
CheckOwnerEvidence
Conversion definition agreedSales lead and financeThe written definition matches the one used in sales reporting
Stable sale referenceCRM administratorEvery sale in a sample has a unique reference that also appears on the payment or accounting record
Lead details capturedMarketing or website ownerA test enquiry shows the stored campaign details and the CRM lead ID
Supported integration in placeCRM administratorThe connection uses the CRM's currently supported Meta integration, and test events appear in the platform's diagnostics
Minimum data sharedBusiness ownerA list of the fields sent, checked against the privacy policy and the consent wording people saw
One sender per eventCRM administrator or developerA retried test sale is counted once, and no second tool sends the same event
Optimisation checked separatelyCampaign managerCampaign settings reviewed in their own right, without assuming the reporting setup changed delivery
Monthly reconciliationFinance or reporting ownerSales in the CRM and accounting, under the agreed definition, compared with the sales the platform received and attributed

Keep the evidence with the setup notes. When someone changes the CRM or the integration later, the same checks show whether anything broke.

Make the Sales Data Dependable

Campaign decisions are only as good as the events behind them. Check:

Precise definitions. Send a purchase only when a purchase has happened, using the same definition as your sales reporting.
Correct timestamps and currency. Use the time the event happened, and one consistent currency.
Duplicate protection. Retries and overlapping integrations can send the same sale twice. A stable event reference helps prevent double counting.
Received, matched and attributed are different stages. The platform can receive an event without matching it to a customer, and a matched event may still not be credited to any ad. Review the diagnostics for gaps and delays, and don't treat a good match rate as proof that the ads drove the sales.

Reconcile your CRM and accounting totals separately from the sales the platform attributes. Cancellations and refunds belong in your own net-sales reporting, whatever the platform shows.

Troubleshooting: When the Numbers Don't Line Up

Most problems show up as one of four symptoms. Start with your own records, because the platform can only report on what it received.

Common problems and where to look
SymptomLikely causesWhat to check
Sales with no sale referenceDeals created by hand, invoices raised outside the CRM, or a reference field that isn't requiredMake the reference required when a deal reaches the agreed sale status, and report weekly on payments or invoices with no matching deal. Fix the link before sending, rather than sending without it.
Duplicate eventsTwo tools sending the same sale, retries after a timeout, or a trigger that fires on every editKeep one sender per event type, reuse the same reference on every retry, and trigger on entering the sale status rather than on any update.
Events received but not attributed to adsMatching gaps are one possible cause: details missing or not prepared as required. Others include customers who didn't come from Meta ads, events sent late or with the wrong time, and sales outside the attribution settings in useReview the platform's event diagnostics, the share of leads with captured campaign details, and the platform's current guidance on event timing. An accepted event, or one matched to a customer, doesn't guarantee that any ad gets credit for it.
Platform and CRM totals disagreeThe same sale assigned to different dates, overlapping credit across campaigns or channels, refunds the platform doesn't see, or different time zonesCompare the same group of enquiries over the same window and time zone, and reconcile totals separately. Don't force the two to agree.

A gap between the platform's figures and yours isn't automatically an error. Attribution is a model of credit; your CRM and accounting records are a count of what happened. Report both, clearly labelled, and treat your own records as the count of sales.

Use a Scorecard the Sales Team Recognises

A shared scorecard keeps marketing and sales looking at the same numbers:

A marketing-to-sales scorecard
MeasureNotes
SpendAdvertising spend for the period
Valid leadsAfter spam, tests and duplicates are removed
Qualified leadsUsing the sales team's definition
Paid or net salesNet of cancellations and refunds
Media cost per saleAdvertising spend divided by the relevant sales
Revenue and contribution marginWith the included costs written down

Media cost per sale isn't the full cost of winning a customer. Full acquisition cost also includes defined sales, agency and system costs. Keep the two separate and label them clearly.

Compare mature cohorts, meaning groups of enquiries that have had time to buy, and use the same windows and attribution definitions each time. Campaigns can claim overlapping credit, and the return on ad spend a platform reports isn't profit, or proof that the ads caused the sales.

Change Decisions, Then Measure the Effect

Once the sales data is reliable, use it to guide budgets, creative, targeting and which leads the sales team should prioritise. Check the volumes before making big changes; a handful of sales is too few to judge a campaign.

Improvements after a change can have other causes: sales training, seasonality, a new offer, a different attribution setting or a change in cancellations. Where it's feasible, a controlled test or holdout gives a better read on what the ads actually added.

Start with one sales event and one reliable data flow. Check it against your own records before expanding. Most of the work is coordinating marketing and the CRM, not buying another tracking tool.

Revision note

Updated 25 October 2026: we added guidance on agreeing a conversion definition, illustrative status definitions with a source of truth for each, a setup checklist with owners and evidence, and a troubleshooting table for missing sale references, duplicate events, events not attributed to ads and reporting mismatches. Originally published 5 October 2026.