Facebook Pixel + Conversions API

Use the Facebook Pixel and Conversions API to measure conversions and optimize ad performance.

Open the dialog

Pixel settings

• Enter your Pixel ID (12 to 18 digits).
• Select Save Pixel ID before adding or testing a CAPI token.
• Use Verify to check the live HTML for the Pixel script.
• Select Disconnect to remove the Pixel ID.

Changing the saved Pixel ID disconnects the previous CAPI token so a token from another Pixel cannot be reused accidentally.

Conversions API (CAPI)

• Generate the CAPI Access Token from the same Pixel in Meta Events Manager, then add it here.
• Select Save token to store it securely. Saving does not send a request to Meta.
• Testing is optional. To test, add a Test Event Code and Test Email, then use Send Test Event to confirm the saved Pixel/token pairing and server-side event delivery.

Existing CAPI tokens saved before Pixel/token verification was introduced stay connected. A successful test event verifies the existing token automatically; you do not need to enter it again.

Events Hiveality tracks

When the relevant customer action occurs, Hiveality sends these Meta standard events automatically:

• PageView when a published page loads.
• ViewContent when a store product is viewed.
• InitiateCheckout when a customer reaches a store checkout.
• Lead after a website form is submitted successfully.
• Schedule after a free or paid booking is confirmed.
• CompleteRegistration after a member joins a community.
• Purchase after a store payment is confirmed.

Purchase events are sent from both the customer's browser and Hiveality's server with the same event ID. Meta uses that ID to count the purchase once while still preserving the server event when a browser blocks tracking or the customer closes the confirmation page.

Test orders do not send Purchase events. Missing or disconnected Meta settings never block checkout, form submission, or booking completion.

Cookie consent

If your website uses Hiveality's cookie consent banner, browser Pixel and server Conversions API events are sent only after the visitor grants marketing consent. If cookie consent is not enabled for the website, Meta tracking works normally.

Notes

• Pixel injection runs on published pages only (not the editor).
• CAPI tokens are stored encrypted and are not shown again after save.
• CAPI calls use Meta Graph API v25.0 by default.