Track Facebook Ad Conversions from Your CRM — Meta CAPI Integration

← Back to Help Center

Fire Meta (Facebook) conversion events automatically when leads reach specific stages in your pipeline. This helps Facebook optimize your ads for leads that actually convert — not just clicks.

Business Impact: Teams using conversion tracking see 24% lower cost per quality lead because Facebook learns which ads produce leads that reach Site Visit, Booking, or Won stages — not just form fills.

What You Need

• A Meta Business Manager account (business.facebook.com)
• A Meta Pixel (also called Dataset) — created in Events Manager
• Admin access to your ClosingFox account

This takes about 5 minutes to set up.

Step 1: Get Your Pixel ID

1. Open Meta Events Manager
2. In the left sidebar, click your Pixel (it might say “Closingfox’s Pixel” or your business name)
3. Your Pixel ID is the number shown below the pixel name — something like 1230960299186890
4. Copy this number. You’ll need it in the next step.

Don’t have a Pixel? In Events Manager, click Connect Data → Web → Connect → name it → Create Pixel. Your Pixel ID will appear immediately.

Step 2: Generate Your Access Token

The Access Token lets ClosingFox send events to your Pixel securely. There are two ways to get it:

Option A: Quick Way (Events Manager)

1. In Events Manager, click your Pixel
2. Go to the Settings tab (top bar)
3. Scroll down to Conversions API section
4. Under “Set up manually”, click Generate access token
5. Copy the token immediately — it won’t be shown again!

Option B: System User (Recommended for Teams)

System user tokens don’t expire when someone leaves your team.

1. Go to Meta Business Settings
2. Left sidebar → Users → System Users
3. Click Add → name it “ClosingFox CRM” → role: Admin
4. Click the system user → Add Assets → assign your Pixel with full access
5. Click Generate New Token
6. Select permissions: ads_management and business_management
7. Click Generate Token → Copy it immediately

Important: Save the token somewhere safe (like a password manager). If you lose it, you’ll need to generate a new one.

Step 3: Add Credentials in ClosingFox

1. Open ClosingFox → go to Pipeline Config (Settings → Pipeline Config)
2. Select the pipeline you want to track (e.g., “WEB Sales”)
3. Click Pipeline Settings (gear icon, top right)
4. Scroll down to Meta Conversions API
5. Paste your Pixel ID
6. Paste your Access Token
7. You’ll see the status change to Connected
8. Click Save

Step 4: Set Conversion Events on Stages

Now tell ClosingFox which stages should fire a conversion event.

1. In Pipeline Config, click Rules to expand any stage
2. You’ll see a new Meta Event field at the bottom
3. Type the event name you want Facebook to receive. Use Meta’s standard event names (no permission prompt needed):

   Stage	Meta Event Name	What Facebook Learns
   Demo Scheduled	Schedule	“This ad produced a lead that booked a demo”
   Site Visit Done	ViewContent	“This ad produced a lead that visited the site”
   Proposal Sent	Lead	“This ad produced a serious buyer”
   Final Negotiation	InitiateCheckout	“This ad produced a negotiation-stage lead”
   Won	Purchase	“This ad produced a closed deal” (Facebook optimizes hardest for this)

   Why standard names? Custom event names (like “DemoScheduled”) require manual permission approval in Meta. Standard names like Schedule, ViewContent, Purchase are recognized by Facebook automatically — no extra steps.

4. Click Save

Pro tip: Start with just 1-2 stages (like Site Visit + Won). You can always add more later. Don’t set events on every stage — Facebook works better with fewer, meaningful signals.

Step 5: Test It

1. Open Meta Events Manager → click Test Events tab
2. Note the Server test event code shown on the page (e.g., TEST15393)
3. In ClosingFox, move any lead to a stage that has a Meta Event configured
4. Go back to the Test Events tab — your event should appear within a few seconds
5. The Overview tab shows events after 15-20 minutes

How It Works (Behind the Scenes)

Click to expand — technical details

When you move a lead to a configured stage, ClosingFox automatically:

1. Detects the stage change on the server
2. Looks up the Meta Event name for that stage
3. Reads the lead’s phone, email, and name
4. Hashes this data with SHA-256 (industry standard privacy protection)
5. Sends it to Facebook’s Conversions API (server-to-server, not via browser)

Your team doesn’t have to do anything. It fires automatically on every stage move — from kanban drag, lead detail, disposal, or bulk actions.

This is different from the Meta Pixel (which runs in the browser). Since ClosingFox fires from the server, it works even when your team uses the mobile app. No browser pixel needed.

FAQ

I don’t see events in Meta Pixel Helper browser extension?

That’s expected. ClosingFox uses Meta’s Conversions API (server-to-server), not the browser pixel. Pixel Helper only shows browser events. Check Events Manager → Test Events tab instead.

Does this work on the mobile app too?

Yes. The conversion fires from the server when the lead changes stage — it doesn’t matter if your team uses the app, the web version, or both.

Will this slow down the CRM?

No. The conversion fires in the background on the server. Your team won’t notice any difference in speed.

What if Facebook is down?

Nothing happens to your CRM. The stage move works normally. The conversion event is logged as failed and skipped — no retry, no delay.

Can I use different events for different pipelines?

Yes. Each stage in each pipeline can have its own Meta Event name. The Pixel ID and Access Token are shared across all pipelines (they’re org-level).

What if I change my Access Token?

Go to Pipeline Config → Pipeline Settings → update the Access Token → Save. It takes effect immediately.

Next Steps

• Set up your pipeline stages — configure the stages that matter for your business
• Set up assignment rules — auto-assign leads from Facebook Ads to your team
• Connect Facebook Lead Ads — get leads into ClosingFox automatically

---

Need help?
WhatsApp us at +91 90169 09590 or email support@closingfox.com