Connect Customer.io
Record identified-customer events through a trigger.
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 |
|---|---|
cio_site_id | Tracking API site ID. |
api_key | Tracking API key for that site. |
Connect
Open Integrations, find Customer.io, and open its setup. Enter the fields above and save with Connect (or Save changes for an existing connection).
- Create a trigger, select this integration as its destination, and render the provider’s expected payload in its template. Selecting Events to forward alone does not invoke this native trigger adapter.
- Use an identified visitor and a template containing the event name and data.
Verify the result
The check sends axo_connection_test to customer axo_connection_test. This is a real event and can enter workflows.
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
Keep test-event workflows disabled for that test customer. Verify the customer ID, site ID, key, and template if authentication succeeds but the expected event is missing.
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.