Connecting Meta ads (Conversions API)

meetpiloot sends your leads to Meta from the server. An enquiry still gets through when an ad blocker or the cookie banner stops the pixel on your site. Meta learns which ads bring in real jobs, and aims your campaigns at people who look like your buyers.

You choose which moments are sent:

• New lead: always, as soon as an enquiry comes in. Leads from Meta lead forms are skipped, because Meta already counts those itself.
• Qualified lead: as soon as a lead reaches a pipeline stage you choose, for example a booked appointment.
• Sold: as soon as a lead reaches the stage where the customer signs, with the quote value.

Each moment goes to Meta once per lead, even if you later move a card back or forward.

How to connect your Meta account

You give meetpiloot access to your pixel and your ad account through its parent company Metino, just as you would with a marketing agency. You do this once, in your own Meta environment.

1. Go to business.facebook.com/settings and, at the top right, choose the business that manages your ads.
2. Share your dataset (pixel) with Metino: Data sources → Datasets → choose your pixel → Assign partners → enter Metino's Business ID: 919556990740037. Grant access to manage the dataset and click Assign.
3. Share your ad account with Metino: Accounts → Ad accounts → choose your account → Assign partners → the same ID → grant access to view performance. That lets meetpiloot show your ad spend next to your leads and revenue.
4. In meetpiloot, open IntegrationsMeta ads (conversions) and enter your two IDs. You find the dataset ID in Events Manager, in your pixel's settings. The ad account ID is in the Ads Manager address bar, after act=. Then click Check connection.
5. Under Which moments do we send to Meta?, choose the stages for a qualified lead and for sold, and switch the conversions on.

Testing

In Events Manager, open your dataset, go to Test events, choose the Offline channel and copy the test code. Paste it into meetpiloot under Test and click Send test event. meetpiloot then sends a fake lead that does not affect your real statistics.

Use Chrome, because Events Manager does not work in Safari. If nothing shows up but meetpiloot says Meta received the event, the connection is fine. Meta does not always show test events.

Together with the pixel on your site

If your site also sends a Lead event from the Meta pixel, pass meetpiloot's event ID as eventID. You find it as mp_event_id in the dataLayer and as eventId in the meetpiloot event. Meta then recognises that the pixel and the server are reporting the same enquiry, and counts it once. How to set that up is in Measuring conversions with Google Tag Manager and Google Ads, GA4, Microsoft Ads and Meta without GTM.