Connect Meta CAPI
Forward conversion signals to a Meta pixel.
All connectors · Checked against AXO’s implementation in October 2026.
Prepare access
Use an owner or admin account in AXO and confirm the selected site. Have permission to authorize the external account or create its server credentials. Keep secrets in the connector’s protected configuration.
| Setting | Value to prepare |
|---|---|
pixel_id | Pixel ID. |
access_token | Token authorized for the pixel. |
test_event_code | Optional code from Meta Test Events. |
Connect
Open Integrations, find Meta CAPI, and open its setup. Enter the fields above and save with Connect (or Save changes for an existing connection).
- Copy the pixel ID and token for the same Meta asset. Enter the test-event code while validating.
- Select the conversion events you intend to forward; save the connector.
- Verify the event in Meta Events Manager before removing the test code.
Verify the result
The connection check POSTs a synthetic event. It uses the configured test code or AXO’s fallback test code; inspect Meta’s response and Test Events.
Record the AXO integration or trigger result and the receiving system’s result. A saved configuration, credential check, and completed delivery establish different things. Use a controlled destination for a test that writes data or sends a message.
Fix a failed connection
Confirm pixel ownership, token access, event match data, and deduplication with any existing browser pixel. A successful upload does not prove attribution.
For a saved catalog connector, open Health to read the latest error, then repair the settings through the setup method on this page. Pause delivery while correcting an unintended destination. Reconnect OAuth when its grant is revoked; for key-based connections, save the replacement key, verify it, then revoke the old key at the provider.
Next: create an event-triggered action, or implement a webhook receiver.