Integrations and alerts
Connect Meta CAPI
Send business events to Meta from the server and check the connection with a test event.
Before you start
You need access to the dataset in Meta Events Manager. Before enabling the connection, inform your contacts and confirm the legal basis and any required consent.
Step by step
- Open Meta Events Manager and copy the ID of the dataset that will receive events.
- In Events Manager, go to Settings → Conversions API → Generate access token. Keep the token secure: it is an access credential.
- In Nod, open Meta Ads → Connect Meta CAPI and enter the dataset ID and token.
- To check the connection, open the Test Events tab in Events Manager and copy the test code.
- Enter that code in Nod’s CAPI settings and select Send test event.
- Check receipt in Test Events for the same dataset. Once the connection is validated, remove the test code.
- Send test event sends the test event. Check the test code in your configuration first. Disconnect disables the connection and is not part of testing.
Which events are sent
Lead: form or landing page submission. Schedule: scheduled call. Purchase: collected sale, including amount and currency. Subscribe: subscription. CompleteRegistration: customer signup.
Events are sent from the server. Email address, phone number, and name are hashed using SHA-256 before transmission; fbc, the click identifier, is included when available. Hashing does not make this data anonymous.
What to explain to your contacts
Your business chooses to enable the connection and is responsible for informing contacts and having a legal basis. Nod sends the data on your behalf.
The Connect Meta Ads guide includes an adaptable privacy policy template. Also review Meta’s Business Tools Terms: https://www.facebook.com/legal/terms/businesstools.
Disable the connection
You can disable Conversions API in Meta Ads. Campaign reporting, attribution in Nod, and sending events to Meta are separate functions.
What to expect
The test event arrives in the selected dataset. After removing the test code, the settings are ready to send business events.
Troubleshooting
If the event does not appear, check that the ID, token, and test code belong to the same dataset.
Do not share the token in a screenshot, support request, or privacy policy.
Receiving a test event checks the connection; it does not, by itself, prove that all real events are arriving.