Meta Conversions API (CAPI) lets PromoPilot tell Meta when a lead in your CRM moves to a meaningful stage: qualified, applied, booked, or purchased. Meta then optimises your ad delivery toward people likely to take that action.
How to connect
- Open Meta Events Manager and create or open a CRM data source. Meta gives you a 16-digit Dataset ID.
- Under the dataset Settings tab, click Generate access token and copy the value. (PromoPilot stores it Fernet-encrypted - never in plain text.)
- In PromoPilot, open Ads > Conversions API, pick your pipeline, and connect a Meta ad account via the OAuth flow. PromoPilot auto-discovers your datasets from that account.
- Pick the right dataset from the dropdown, then map each pipeline stage to a Meta event name (Lead, SubmitApplication, Schedule, CompleteRegistration, Purchase). PromoPilot suggests defaults based on your stage names.
- Click Send test event. A 200 response with
events_received: 1means you are set up correctly.
What PromoPilot sends
- Event_name, event_time, action_source=system_generated per Meta spec.
- custom_data.event_source=crm and lead_event_source=your brand so Meta diagnostics show the CRM.
- user_data: SHA256-hashed email, phone (digits only), first name, last name. Meta-generated lead_id and fbc/fbp click cookies pass through raw per Meta spec.
- An initial raw-lead event fires the moment an Opportunity is created, so Meta sees the top of the funnel.
- A daily heartbeat keeps the dataset active even in slow weeks.
Troubleshooting
- If Events Manager Diagnostics flags errors, look for a "Last event failed" badge on the CAPI page.
- Open Django admin under Ads > CapiEvent to see the raw Meta response.
- Most errors are revoked access tokens (re-connect the ad account) or a typo in the Dataset ID.
