Prooflytics + Meta Ads: Real CAC per Campaign from CRM

Meta Ads Manager shows CPL — cost per lead. But if your funnel runs through a CRM, the bottom-line metric is the cost of a closed deal per campaign. A campaign with CPL of $30 and a 10% close rate actually costs $300 per customer. A campaign with CPL of $80 and a 40% close rate costs $200. Meta doesn’t know this — it cannot see what happens in the CRM after a lead is generated. Prooflytics closes this loop: Meta click -> first session -> CRM -> Won deal -> real CAC per campaign.

Why CPL from Meta Is Misleading

Marketers optimize campaigns by CPL: they reduce bids on ads with expensive leads and scale the cheap ones. This is logical — if CPL correlates with actual lead quality. But in B2B, it doesn’t.

A typical picture:
— Campaign “retargeting to pricing page visitors”: CPL $85, but close rate 38% -> $224/closed deal
— Campaign “broad interest targeting”: CPL $22, close rate 6% -> $367/closed deal

By CPL, the marketer scales the broad campaign and cuts retargeting. By cost per closed deal — the opposite. Without linking Meta Ads to the CRM, this decision is made in the dark.

Prooflytics is an attribution tool that connects Meta Ads data with the CRM pipeline via a first-party Pixel. It does not replace Meta Ads Manager — it adds the dimension Meta cannot see: what happened to the lead after the click.

How Prooflytics Attribution Works for Meta Ads

Step 1: Pixel captures fbclid. When a user clicks an ad, Meta appends the fbclid (Facebook Click ID) parameter to the URL. The Prooflytics Pixel is installed on the site and captures fbclid at the first session — along with UTM parameters, campaign ID, and ad ID.

Step 2: fbclid is linked to a CRM contact. When the visitor submits a form on the site — the Prooflytics Pixel passes the email (or other identifier) along with the stored fbclid. The CRM contact receives attribution: source = Meta campaign, ad, and audience.

Step 3: CRM pipeline -> cost per closed deal. When the deal moves to Won, Prooflytics knows: this contact came from a specific Meta campaign with a specific fbclid. The Meta Ads API spend for that campaign is divided by the number of Won deals — producing the real CAC.

fbclid in URL
  ↓ Prooflytics Pixel
  -> save {fbclid, utm_campaign, utm_medium, ad_id, timestamp}
  ↓ user submits form
  -> pass {email, fbclid} to Prooflytics
  ↓ CRM: lead created, contact with email linked
  -> Prooflytics: {contact_id -> fbclid -> campaign_id}
  ↓ CRM: deal Won
  -> Prooflytics: cost_per_deal = campaign_spend / won_count

What the Prooflytics Dashboard Shows for Meta Ads

Daily AI briefing (04:00 UTC, Campaign Intelligence section):

Cost per closed deal by campaign over the last 30 days
Comparison: CPL from Meta vs real CAC from CRM
Underperforming campaigns: high CPL, low close rate -> recommendation to reduce budget
Top-performing campaigns: low CAC -> recommendation to scale

Example briefing structure (data is Meta-reported, not Pixel-verified — the discrepancy is noted explicitly):

Campaign "Retargeting Pricing"
Meta-reported CPL: $82
CRM close rate: 41%
Real CAC: $200
Recommendation: scale (+30% budget)

Campaign "Lookalike 2% US"
Meta-reported CPL: $19
CRM close rate: 5%
Real CAC: $380
Recommendation: pause or revise audience

Configuring the Prooflytics Pixel for Meta Ads

The Pixel is installed on all site pages — one JS snippet. For accurate Meta attribution:

1. Do not strip fbclid from the URL. Some cookie-consent solutions or SPA routers trim query parameters during navigation. The Prooflytics Pixel is SPA-aware — it captures fbclid before any URL manipulation.

2. Pass email on conversion. When the user submits a form, call prooflytics.identify(email) — this links the session to a CRM contact. Without this step, attribution is lost for anonymous sessions.

3. Configure UTM parameters in Meta campaigns. In Ad Set -> URL Parameters, add:

utm_source=meta&utm_medium=paid&utm_campaign={{campaign.name}}&utm_content={{ad.name}}

This provides redundant attribution via UTM — Prooflytics uses both signals: fbclid (precise, while valid) and UTM (stored in cookie for up to 90 days).

iOS 14+ Limitations and Prooflytics’ Solution

Apple ATT (App Tracking Transparency) from iOS 14+ limits fbclid: some users don’t have it. Meta addresses this through Aggregated Event Measurement, but that provides aggregate data, not individual-level data.

Prooflytics operates as first-party: the Pixel is your own JavaScript, data is stored on your domain, with no third parties. This bypasses iOS 14+ restrictions in most cases. For users without fbclid — UTM attribution via cookie (fallback, less precise, but better than nothing).

Real-World Case Study

B2B SaaS (EU, $40k/month Meta Ads budget, Kommo + Stripe, 2–6 week deal cycle):

Before: the marketer optimized by CPL from Meta. Retargeting campaigns seemed “expensive” ($90–120 CPL). Broad prospecting seemed “cheap” ($18–25 CPL).
After connecting Prooflytics: it turned out retargeting campaigns had a 35–45% close rate, broad prospecting had 4–8%. Real CAC: retargeting $220, prospecting $390.
Result: 40% of budget was reallocated from prospecting to retargeting. CAC dropped from $310 to $240 over the quarter. Monthly new customers grew by 18% on the same budget.

A similar pattern is described for Google Ads attribution via Prooflytics — attribution there works via gclid, same principles.

Who This Is For

B2B SaaS or services with a Meta Ads budget of $10k+/month
Sales cycle running through a CRM (Kommo, HubSpot, Pipedrive) with a sales rep involved
Marketers optimizing by CPL — but without visibility into close rates per campaign
The gap between “leads are cheap” and “deals aren’t closing” — with no clear explanation

Frequently Asked Questions

Does Prooflytics require access to the Meta ad account?

Yes. Prooflytics connects to Meta Ads via the official Marketing API to retrieve campaign spend data. This is read-only access — Prooflytics does not manage ads. Connection is via standard OAuth flow in the /connect section.

What if fbclid isn’t passed (iOS, ad blockers)?

Prooflytics uses fallback attribution via UTM parameters stored in a first-party cookie (90 days). For users without fbclid or UTM — direct/none attribution. On average, precise attribution loss is 15–25% of Meta traffic for EU markets (iOS users).

How quickly does data appear after connecting?

Meta Ads spend — within 24–48 hours after the first sync. Attribution for closed deals — as deals close: retroactively for the past 90 days (if the Pixel was already installed). Full CAC picture by campaign — within 30 days of installation.

Does Prooflytics replace the Meta Pixel?

No. Prooflytics Pixel and Meta Pixel run in parallel and independently. Meta Pixel is needed for campaign optimization within Meta (Conversions API, custom events). Prooflytics Pixel is needed for CRM-level attribution. Install both.

How does Prooflytics handle a long deal cycle (3–6 months)?

Prooflytics stores contact attribution for a configurable window (90 days by default, extendable for Enterprise). If the deal cycle exceeds 90 days — the Scale or Enterprise plan is needed with an extended attribution window.

Summary

Prooflytics connects Meta Ads (fbclid) with the CRM pipeline via a first-party Pixel
Result: cost per closed deal per campaign, not CPL
Daily AI briefing highlights top and bottom performers by real CAC
iOS 14+ fallback: UTM in first-party cookie (90 days)
Connection: OAuth to Meta Ads + Pixel on site + CRM connector

If you’re spending more than $10k/month on Meta Ads and don’t know your cost per closed deal by campaign — connect Prooflytics and within the first 30 days you’ll see which campaigns are actually bringing in customers. Exceltic.dev helps with Pixel installation and initial funnel configuration.

Prooflytics + Meta Ads: Cost per Closed Deal Instead of CPL