Why Meta Ads Manager conversions don't match your CRM

Are you counting the same conversion?

Compare completed website enquiries with website Lead events. A CRM contact, a qualified lead and a booked appointment are different actions. Keep each total separate before deciding that Meta under-reports your client's results.

If the client cares about booked consultations, use the form and booking checks to confirm what fires on completion. Calling every enquiry a booking hides the stage where the numbers diverge.

Most gaps close once the definitions and settings match. If you have matched them and a Meta notice names your Lead or Schedule event as restricted, skip to when Crisper fits.

How do you make the reports comparable?

Write down each report's filters before exporting it. Matching the visible date labels isn't enough if the reports use different time zones, timestamps or definitions of a conversion.

Keep a private list of the records you're investigating, with their completion times and an internal ID. You don't need to upload a clinic's enquiry text or treatment information to Meta to explain a reporting difference.

Which attribution settings can explain the gap?

Meta can credit an ad interaction that your CRM's source field doesn't record. Its attribution documentation distinguishes standard, incremental and custom models, which use different counting mechanisms. Inspect the model in the actual ad set.

Under standard attribution, Meta describes click-through, view-through and engage-through credit. A person can see an ad and later enquire without clicking its tagged URL. Some accounts still use earlier click definitions during rollout, so record what your account shows instead of assuming one universal window.

1. In Ads Manager, select the campaigns and reporting dates you want to compare.
2. Open Columns: Performance, then choose Performance and Compare attribution settings.
3. Select the available attribution windows relevant to your comparison.
4. Choose All conversions or First conversion where that control is available, then select Apply.
5. Export the comparison and save its settings beside the CRM export. Explain any change in the total before changing the tracking installation.

These controls come from Meta's comparison instructions. All conversions and First conversion answer different questions. Neither option automatically means unique people in your CRM.

When does the gap point to broken tracking?

Look for a missing step in event collection before calling the difference attribution loss. A successful CRM submission establishes that the business received an enquiry. It doesn't establish that the intended Meta source received the event.

For missing events, start with Facebook Ads Manager not showing conversions. After a repair, follow the verification procedure rather than treating a successful request as the finished result.

If a notice confirms restricted Lead or Schedule events on a clinic domain, Crisper's recovery workflow is relevant. It recovers usable standard events on the existing domain. It doesn't make the CRM and Ads Manager adopt the same counting rules. Read the restriction guide before choosing that path.

What should you tell the client?

Report the business totals and the advertising totals with their definitions. Say how many website enquiries the CRM recorded, what Meta credited under the selected model, and which collection checks passed. Keep purchases, leads and appointments separate.

1. State the action and date range each number describes.
2. Name the filters or attribution settings that explain a known difference.
3. Separate those explained differences from events you couldn't verify.
4. Assign the remaining investigation to the person who owns that step, then repeat the same exports after the fix.

Do not label the whole difference wasted spend or calculate recovered revenue from it. That would require evidence about what the ads caused, beyond a mismatch between two reports.

When should you use Crisper?

A mismatch between Meta and the CRM is usually a counting difference, and the steps above settle it. Crisper fits when a notice confirms a restriction and the website's Lead or Schedule event is unusable. A fix for that has to make the standard event usable again on the clinic's existing domain. Crisper recovers the standard event server-side, with no new domain, no redirect landing page and no pixel reset, as the recovery setup describes. It does not change how the CRM and Ads Manager count.

Your CRM can send its conversions through Crisper too. Connect your CRM by webhook: any CRM that can send an outbound webhook, including GoHighLevel or Salesforce, can do this. If your CRM cannot send a webhook, that route is not available. Agree with the clinic whether the conversion is an enquiry or a booked appointment, and keep that definition in the worksheet.

Scaled AI runs Meta lead-gen for addiction treatment and behavioral health centers. It has 10+ treatment-center domains recovered on Crisper, with usable Lead events on the same restricted domains. The Scaled AI case study shows the setup and the result in its own words.

Crisper does not win Meta appeals or change how Meta classifies the site, and a received event is not proof of attribution. The clinic stays responsible for what it shares with Meta. Setup takes about 5 minutes when you have DNS access, access to the Meta integration and the ability to add the tracking snippets, and the founder sets up the first client domain with you.