About Tracking

Ad Platform Tracking

Meta Pixel + CAPI TikTok CAPI LinkedIn CAPI Snapchat CAPI Pinterest CAPI Quora Pixel Bing + UET Tag

Google Ecosystem

Google Ads Tracking GA4 Setup & Audit Google Tag Manager

Advanced Solutions

Server-Side Tracking Looker Studio Offline Conversion
Case Studies Blog Free Checklist Book Free Audit →

If you run Meta Ads lead generation campaigns and use Salesforce as your CRM, you have a significant opportunity to improve campaign performance by sending qualified lead and closed deal data from Salesforce back to Meta via the Conversions API. This creates a feedback loop where Meta’s algorithm learns to target users similar to your actual customers rather than optimising purely for form completions.

Why CRM Data Back to Meta Matters

Meta’s algorithm optimises for the conversion signal you give it. If your conversion signal is “Lead Form Completion,” it optimises for users most likely to complete a form — which includes low-intent, accidental, and unqualified submissions.

When you send Salesforce data back to Meta:

How to Connect Salesforce to Meta CAPI

Option 1: Meta’s Native Salesforce Integration

Meta has a native CRM integration for Salesforce. In Meta Business Manager, go to Events Manager → Data Sources → Create Data Source → CRM → Salesforce. Follow the setup wizard to connect your Salesforce instance and configure which Salesforce objects and events to send to Meta.

This is the simplest approach if your Salesforce account is eligible for the native integration. It handles authentication and data mapping without custom development.

Option 2: Zapier/Make Automation

Set up a Zapier or Make scenario that:

  1. Triggers when a Salesforce Lead or Contact status changes (e.g. to MQL, SQL, or Closed Won)
  2. Sends a CAPI event to Meta with the hashed contact email and the appropriate event type

This approach is more flexible than the native integration and works for any Salesforce setup. It requires a Zapier/Make account and a basic understanding of the Meta CAPI event format.

Option 3: Custom Salesforce Apex Trigger

For Salesforce-heavy organisations with developer resources, build a custom Apex trigger that fires a callout to your server when a Lead or Opportunity status changes. Your server then sends the CAPI event to Meta. This approach provides full control over the data and logic but requires Salesforce development.

What Data to Send from Salesforce to Meta

Required fields

Recommended optional fields

Deduplication with Browser-Side Lead Events

If you are also tracking form submissions via the browser-side Meta Pixel (Lead event), your CAPI events need deduplication. Without it, a single lead submission generates two Lead events — one from the browser pixel and one from Salesforce CAPI when the lead is created.

To deduplicate: include the same event_id in both the browser pixel Lead event and the CAPI Lead event. The event_id should be a unique identifier for the form submission (e.g. a timestamp + form ID combination, or the Salesforce Lead ID).

Expected Impact on Campaign Performance

After enabling Salesforce → Meta CAPI for qualified leads:

The impact is larger for higher-volume campaigns. Accounts with 50+ qualified leads per month will see faster algorithm learning than smaller accounts.

Book your free audit here and we will help you set up the Salesforce to Meta CAPI data flow that improves your lead gen campaign performance over time.

Leave a Reply

Your email address will not be published. Required fields are marked *