# Send CRM conversions to Facebook (Meta Conversions API)

> To send CRM conversions to Facebook from SkedX CRM: open Settings → Integrations → Meta Conversions API and click Connect. Copy your Pixel ID from Events Manager → Datasets (the number labelled ID under your dataset), generate an access token from that dataset’s Settings tab under “Set up direct integration”, paste both into SkedX and click Connect. Then switch on the conversion events Facebook should learn from: Lead created, Lead qualified, Deal won, or one of your own. Click Edit on an event to choose which profile it applies to, add conditions and pick what Facebook receives. The filter window has its own Profile dropdown, and its fields follow the profile you pick. Each event sends once per person when they enter it; Deal won sends the deal amount. The page also shows what reached Facebook, what failed and why, and which of Facebook’s requirements you meet.

Product: SkedX CRM · Topic: Integrations · Draft — steps not yet re-verified in the live product

Facebook only knows when someone fills in a form. Tell it which of those people actually became customers and it stops optimising for form-fills and starts finding you more people who buy. SkedX CRM sends that back for you, from the conversion events you choose, for the profiles you choose. About six minutes, and you’ll need the Facebook account that runs your ads.

## Step 1: Open Meta Conversions API in SkedX

Go to **Settings -> Integrations**, find the **Meta Conversions API** card and click **Connect**. You need the **Manage integrations** permission.
Open it directly: https://crm.skode.ai/settings/integrations

## Step 2: Open Facebook’s Events Manager

Click **Open Events Manager** on the page (or go to **business.facebook.com/events_manager**). Sign in with the Facebook account that runs your ads. In the left menu, open **Datasets**. That is Facebook’s name for your Pixel now; older accounts still say **Data Sources**.

## Step 3: Copy your Pixel ID

The number labelled **ID** under your dataset’s name is your Pixel ID, 15 or 16 digits. Copy it and paste it into the **Pixel ID** box in SkedX. It is not your ad account number (that one starts with **act_**).

## Step 4: Generate an access token

Click your dataset, open its **Settings** tab and scroll to **Set up direct integration**. Leave the “Dataset Quality API” choice as it is and click **Generate access token**. If a “Select datasets” dialog appears, keep your dataset selected and confirm.

## Step 5: Copy the token

Facebook shows the token once, in a grey box: “Copy and save this token somewhere safe.” Select all of it. It starts with **EAA** and runs to about 200 characters. You won’t need to save it anywhere yourself; SkedX keeps it encrypted.

## Step 6: Paste the token and connect

Paste the token into the **Access token** box in SkedX and click **Connect**. SkedX checks it with Facebook before saving, then opens your Pixel with **Lead created** switched on. The button reads **Connect anyway** when one of Facebook’s requirements is not met yet. It still connects. The token is encrypted and never shown again; if you ever need to change it, use **Replace access token**.

## Step 7: Choose what CRM sends

Use the switch to turn on each conversion event Facebook should learn from: **Lead created**, **Lead qualified**, **Deal won** (sent with the deal amount) or one of your own. Each event sends once per person, when they enter it. The **30 days** column shows how many people it would have sent in the last 30 days. **Edit** changes an event, and **Add a conversion event** adds your own.

## Step 8: Say which people an event counts

Click **Edit** on an event. **Applies to** sets the profile it counts people from, and every event can use a different one. **Add conditions** opens the filter window. **Facebook receives** is a dropdown of Facebook’s standard events, and you can type your own name there too. The event shows how many people it counted in the last 30 days.

## Step 9: Pick a profile and filter on its fields

In the filter window, pick the **Profile**. The fields change to that profile’s own, so you can filter on anything it holds. **Save conditions** saves the profile and its filters together. If a filter uses a field the new profile doesn’t have, the save is refused and nothing changes.

## Step 10: Add a conversion event of your own

Click **Add a conversion event** for a moment that matters to your business, such as a site visit booked or a quote accepted. Give it an **Event name**, choose what it **Applies to** and click **Add event**. Conditions and what Facebook receives come next, on the event. **Deal won** can’t be narrowed: it also feeds your revenue reports.

## Step 11: Check Facebook’s requirements

**Facebook’s requirements** checks your setup against what Facebook asks for: Lead Ads, leads a month, the Facebook lead id, sending within 28 days and the rate of leads that become customers. Click it to see each one with your own number.

## Step 12: See what reached Facebook

Each Pixel shows **Sent**, **Failed** and **Not sent** for the last 14 days. Click a number to open **Activity**, one row per person. [See what reached Facebook](https://skode.ai/help/crm/integrations/see-what-reached-facebook/) explains each row and how to send a failed one again.

## Step 13: Use it on a phone

On a phone, the page shows your Pixel’s numbers, then its conversion events with each one’s count. Tap an event to turn it on or off, or to change who it applies to. **Requirements met** shows how many of Facebook’s requirements you meet.

## Common questions

### Can I send from any profile?

Your own events can count people from any profile. Lead created and Lead qualified can use any profile built on Enquiries, because they fire on an enquiry. To send from Contacts, add your own event. Deal won always counts every won deal.

### My event has a filter but sends nobody. Why?

Enquiries hides people who have moved into another profile, so a filter on Enquiries cannot find them. Set the event to the profile those people are in now. If the page shows a number in another profile, click its button to move the event there.

### Are the people already in a profile sent when I switch to it?

No. They count as history, and only people who enter after the switch are sent.

### My Lead Ads come in through Zapier or the API — can Facebook still match them?

Yes, when your connection sends Meta’s lead ID as **meta_lead_id**. SkedX keeps it on the enquiry and sends it with each conversion, and it is the identifier Facebook matches best. Lead Ads connected to SkedX directly already send it. Before 8 October 2026 an ID sent this way was put aside and not used.

Videos and screenshots © 2026 SkedX, with sample data only. Share and link to them freely; copying the SkedX product or its design is not allowed. Terms: https://skode.ai/terms/

## Related guides
- See what reached Facebook, and send a failed conversion again: https://skode.ai/help/crm/integrations/see-what-reached-facebook/
- Send conversions to more than one Facebook Pixel: https://skode.ai/help/crm/integrations/send-conversions-to-more-than-one-pixel/
- See how a person found you: the Signal tab: https://skode.ai/help/crm/integrations/see-how-a-person-found-you/
- Import profiles from a spreadsheet: https://skode.ai/help/crm/profiles/import-profiles-from-a-spreadsheet/
- Assign profiles to your team: https://skode.ai/help/crm/profiles/assign-profiles-to-your-team/
- Connect Meta Lead Ads (Facebook and Instagram): https://skode.ai/help/crm/integrations/connect-facebook-lead-ads/
- Send Flow conversations to Facebook (Meta Conversions API): https://skode.ai/help/flow/marketplace/send-flow-conversations-to-facebook/
- Turn your website forms into enquiries: https://skode.ai/help/crm/integrations/capture-enquiries-from-your-website-forms/
- Put SkedX Signal on your website: https://skode.ai/help/accounts/your-organization/put-skode-signal-on-your-website/

Source: https://skode.ai/help/crm/integrations/send-crm-conversions-to-facebook/