Connect Klaviyo

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.

Connect

Open Integrations, find Klaviyo, and open its setup. Enter the fields above and save with Connect (or Save changes for an existing connection).

1. Create a private key in Klaviyo Settings → API keys with those two permissions.
2. Open Klaviyo in AXO Integrations, paste the private key, and select the site events to forward.
3. Triggers are optional: use one for a condition-driven event instead of a subscribed site event. Its JSON can use event, customer_properties with $email or $id, and properties. See the payload example below.

Optional trigger payload

{
  "event": "AXO Documentation Test",
  "customer_properties": {
    "$email": "test@example.com"
  },
  "properties": {
    "source": "controlled_test"
  }
}

Replace the example address with an authorized test recipient. In a live template, bind the visitor’s identifier instead of sending every event to this fixed address. A provider 202 means accepted for processing; it does not prove that an email flow ran.

Verify the result

Health → Send test event reads the Klaviyo account. A successful check reports klaviyo_credentials_valid. It does not create a customer event. For delivery verification, subscribe to profile.identified, identify a controlled test visitor using the tag or ingestion API, then open that email’s profile in Klaviyo and find profile.identified in its activity. Check the same event in the connector tile’s Health log.

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

A public Site ID will fail. A 403 can mean Accounts: Read is missing even when Events: Write works. Replace the private key with the required scopes.

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.

Provider reference: Klaviyo API authentication and scopes. Reviewed October 2026.

Next: create an event-triggered action, or implement a webhook receiver.