Close CRM · Meta CAPI

Close CRM Meta CAPI Integration

The Meta pixel fires when someone visits your page. After that, everything that happens in Close CRM is invisible to Facebook's algorithm. When a prospect enters your pipeline, progresses through follow-ups, and closes as a won deal, Meta never sees it. ConversionLoop captures the fbclid at ad click, then sends a server-side CAPI Purchase event the moment Close marks the opportunity as Won. Meta stops optimizing for people who fill out forms and starts finding people who pay.

Close CRM
Your CRM
webhook
ConversionLoop
API upload
Meta CAPI
Ad platform
10-min setupNo code required14-day free trialReal-time upload
10 min
Setup time
30-40%
Event match improvement
0
Developer needed
Server
Event delivery method

Why Meta pixel tracking misses your Close CRM revenue

When someone clicks your Facebook ad and submits a form, Meta registers a Lead event. That is where pixel tracking ends. The follow-up calls, the discovery sessions, the proposals, and the closed deal all happen inside Close CRM over the following days or weeks. Meta never sees any of it. The algorithm builds its understanding of your best customers from people who submit forms, not from people who actually buy. Over time your Lookalike Audiences drift toward form-fillers, your ROAS numbers understate the real picture, and your cost per closed deal stays high.

Ad click
GCLID assigned
Landing page visit
GCLID captured by cl.js
Booking made
Patient books through Pabau
Invoice paid
Without CL — Google sees nothing
Invoice paid
With ConversionLoop — conversion uploaded

ConversionLoop vs. manual CSV upload

Why the manual process breaks — and what changes when you automate it

Feature
Manual / No tool
ConversionLoop
iOS 14+ resistance
Pixel blocked on 30-40% of traffic
Server-side CAPI, unblockable
Close deal as CAPI Purchase
Not possible with pixel alone
Automatic via Close webhook
Deal value passthrough
Not tracked
Exact deal value sent to Meta
Event match quality
Low, browser pixel only
High, hashed PII and fbclid server-matched
Developer required
Yes for custom CAPI builds
No

How Close CRM deal events reach Meta CAPI

ConversionLoop captures the fbclid when a contact first clicks your Facebook ad. That ID is stored server-side. When Close CRM fires an Opportunity Won webhook, ConversionLoop sends a CAPI Purchase event to Meta with hashed contact data for matching.

1

Contact clicks your Facebook or Instagram ad. cl.js captures their fbclid and stores it against their email.

2

Contact fills out a form and enters Close CRM as a new lead.

3

Lead progresses through the Close pipeline. Activity gets logged. Calls happen.

4

Close fires an Opportunity Won webhook to ConversionLoop.

5

ConversionLoop sends a CAPI Purchase event to Meta with hashed email, phone, and the stored fbclid for high-quality matching.

Ready to connect Close CRM?

14-day free trial. No credit card. Setup takes 10 minutes.

Start free trial

Step-by-step: Connect Close CRM to Meta

Follow these steps once. Everything after is automatic.

1
Create a Close CRM + Meta integration
In ConversionLoop, select Close CRM as source and Meta as destination. You receive a webhook URL and ingest secret.
2
Add cl.js to your landing pages
Paste the ConversionLoop snippet in your page head or deploy via Google Tag Manager. It captures the fbclid on every Facebook and Instagram ad click.
3
Register the webhook in Close CRM
In Close CRM Settings, go to Integrations, then Webhooks. Add your ConversionLoop URL and select the opportunity.won event.
4
Add your Meta Pixel ID and CAPI token
In ConversionLoop, enter your Meta Pixel ID and a CAPI access token from Meta Events Manager under Settings.
5
Verify in Meta Events Manager
ConversionLoop fires a test event. Confirm it appears under Test Events in Meta Events Manager within a few minutes.

Close CRM events worth tracking

Purchase

Opportunity Won in Close CRM with deal value. Highest-quality signal for ROAS optimization and Lookalike Audience building.

Lead

New lead created in Close CRM. Maps to Meta Lead event. Helps Meta find prospects likely to enter your pipeline.

Schedule

Call or demo booked. Maps to Meta Schedule. Mid-funnel signal for longer B2B or high-ticket sales cycles.

Key takeaways

  • 1Meta pixel only sees landing page visits and form fills. Close CRM deal stages and won opportunities never reach Meta without CAPI.
  • 2iOS 14 and ad blockers suppress a large portion of pixel events, reducing match quality and algorithm accuracy.
  • 3Server-side CAPI events from ConversionLoop reach Meta regardless of browser restrictions.
  • 4Sending Opportunity Won events as CAPI Purchase events teaches Meta what a real buyer looks like.
  • 5Lookalike Audiences built on buyers outperform audiences built on leads every time.

Frequently asked questions

Will I double-count conversions with both the Meta pixel and CAPI running?

No. ConversionLoop sends a unique event ID with every CAPI event. Meta uses this ID to deduplicate against any matching pixel event. Your conversion count stays accurate.

What event match quality score can I expect?

Match quality depends on the data available. ConversionLoop sends hashed email, phone when available, and the fbclid. This combination typically produces high or very high match quality scores in Meta Events Manager.

Do I need the Meta pixel if I am using CAPI?

You can use both, and Meta recommends it for deduplication. ConversionLoop handles the server-side piece. Keep your existing pixel for page-level events. CAPI handles the downstream pipeline events that the pixel cannot reach.

Close CRM
Your CRM
webhook
ConversionLoop
API upload
Meta CAPI
Ad platform

Connect Close CRM to Meta today

Stop optimizing on guesswork. Every invoice, treatment, and booking — tracked and attributed automatically.

Start free — 14 days on us

No credit card required · 10-minute setup · Cancel anytime