Connecting Facebook (Meta) CAPI

Overview

Facebook Conversions API (CAPI) enables server-side event tracking between DealOracle and your Facebook (Meta) pixel. Unlike browser-based pixel tracking, CAPI sends conversion data directly from DealOracle's servers to Facebook, providing several key advantages:

• Bypasses ad blockers — Server-side events are not affected by browser ad blockers or tracking prevention features, ensuring you capture every conversion.
• Improves match quality — By sending hashed first-party data (email, phone, name) directly, Facebook can match conversions to ad clicks with higher accuracy.
• Enables offline conversions — Track phone calls, in-person sales, and other offline events that happen after a lead is captured.
• Better attribution — Combined with browser pixel data, CAPI provides a more complete picture of your ad performance.

Why this matters for lead gen: If you're running Facebook lead ads or driving traffic to landing pages, CAPI ensures that downstream outcomes (qualified leads, booked appointments, closed deals) get reported back to Facebook's algorithm — even if they happen days or weeks after the initial click.

Prerequisites

Before connecting Facebook CAPI, make sure you have the following:

• Facebook Business Manager — You need an active Business Manager account at business.facebook.com.
• Admin role on the pixel — You must have Admin access to the pixel you want to connect. Go to Business Settings → Data Sources → Pixels to verify.
• Events Manager access — You'll use Events Manager to verify that events are being received correctly.
• An active ad account — The pixel must be associated with an ad account that has active or recent campaigns.

Tip: If you manage multiple clients, make sure you're connecting the correct Business Manager. You can switch between Business Managers during the OAuth flow.

Connection Steps

Follow these steps to connect your Facebook pixel to DealOracle:

Step 1: Navigate to Integrations

From your DealOracle dashboard, go to Settings → Integrations → Facebook.

Step 2: Start the OAuth Flow

Click Connect Facebook Account. You'll be redirected to Facebook to authorize DealOracle. Grant the following permissions when prompted:

• ads_management
• ads_read
• business_management

Step 3: Select Your Pixel

After authorization, DealOracle will display all pixels available in your Business Manager. Select the pixel you want to use for conversion tracking.

Step 4: Choose Events to Track

Select which DealOracle disposition events should be sent to Facebook. Common choices include:

• Lead qualified → sent as a Lead event
• Appointment booked → sent as a Schedule event
• Deal closed → sent as a Purchase event

Step 5: Set Event Mapping

Map each DealOracle disposition to a Facebook standard event or custom event. See the Event Mapping section below for details.

Step 6: Test the Connection

Click Send Test Event. Then open Facebook Events Manager → Test Events to verify that the event was received.

Important: Test events may take up to 60 seconds to appear in Events Manager.

Event Mapping

DealOracle dispositions map to Facebook standard events as follows:

DealOracle Disposition	Facebook Event	Description
New Lead	Lead	A new lead has been captured
Qualified	CompleteRegistration	Lead has been qualified by your team
Appointment Set	Schedule	An appointment or demo has been booked
Appointment Shown	ViewContent	The prospect attended the appointment
Closed Won	Purchase	The deal has been closed successfully
Closed Lost	Custom: ClosedLost	The deal was lost (useful for negative signals)

Custom Events

If your funnel doesn't fit the standard events, you can create custom events. In the event mapping screen, select Custom Event and enter a name (e.g., QualifiedLead, DemoCompleted).

Custom events can be used in Facebook for:

• Custom conversion tracking
• Audience building (retarget people who reached a specific stage)
• Optimization goals (tell Facebook to optimize for your custom event)

Event Parameters

DealOracle automatically includes these parameters with each event:

• event_time — Timestamp of the disposition change
• event_source_url — Original landing page URL (if available)
• user_data — Hashed email, phone, first name, last name, city, state, zip
• custom_data — Lead value, disposition, source, campaign info

Troubleshooting

Here are solutions to common issues when setting up Facebook CAPI:

"Pixel not found" during setup

• Check Business Manager permissions — Make sure you have Admin access to the pixel in Business Settings → Data Sources → Pixels.
• Verify the correct Business Manager — If you manage multiple BMs, ensure you authorized the right one during the OAuth flow.
• Re-authorize — Disconnect and reconnect the integration to refresh permissions.

Events not showing in Events Manager

• Check Test Events tab — Go to Events Manager → Your Pixel → Test Events. Events sent via CAPI appear here with a slight delay (up to 60 seconds).
• Verify event mapping — Ensure at least one disposition is mapped to a Facebook event in DealOracle.
• Check the event log — In DealOracle, go to Integrations → Facebook → Event Log to see if events were sent and their delivery status.

Duplicate events (browser pixel + CAPI)

If you're running both the Facebook browser pixel and CAPI, Facebook may count conversions twice. To fix this:

• Use the event_id parameter — DealOracle automatically includes a unique event_id with each CAPI event. Make sure your browser pixel sends the same event_id for deduplication.
• Set up deduplication in Events Manager — Facebook automatically deduplicates events with the same event_id and event_name within a 48-hour window.

Low Event Match Quality (EMQ)

• Send more user data — Ensure your leads have email addresses and phone numbers. DealOracle hashes this data before sending.
• Include location data — City, state, and zip code improve match rates.
• Use fbclid passthrough — If you capture the Facebook click ID (fbclid) from the URL, DealOracle will include it for 1:1 click-level attribution.

Need help? Contact DealOracle support at [email protected] or use the in-app chat.