Connect Klaviyo

Create the private API key

• lists:read and segments:read are optional: without them everything else still syncs and Abaxar records a warning naming the missing scope, but audience-growth questions can’t be answered. Adding them later is an edit to the same key; the daily size snapshots then start from that day forward, because Klaviyo reports only a current count and keeps no history.

1. Open Klaviyo and go to Settings → API Keys.
2. Create a private API key and grant it these read scopes: campaigns:read, flows:read, metrics:read, lists:read and segments:read.
3. Copy the key. It starts pk_.

Paste into Abaxar and verify

1. In Abaxar, open Settings → Connectors and scroll to the Klaviyo card.
2. Paste the key into KLAVIYO_PRIVATE_API_KEY and click Save Klaviyo keys. The card reads Credentials saved.
3. Click Verify, then choose the backfill window and click Run backfill.

The conversion metric (usually nothing to do)

Abaxar finds your purchase metric by itself: on every sync it looks for the metric named Placed Order or Ordered Product, which Klaviyo’s Shopify integration creates. Most accounts are done at the step above.

Only if a sync error says a conversion metric id is required, or your account has several metrics with those names and detection picks the wrong one: open Klaviyo’s metrics list, click your purchase metric, copy the metric id from the address bar, and save it in the optional KLAVIYO_CONVERSION_METRIC_ID field on the card.

Worth knowing

• Klaviyo allows two report requests per minute per endpoint, so Abaxar paces itself with a wait between report calls. An account with six flows takes roughly three minutes to sync; a multi-year backfill takes far longer. That is Klaviyo’s speed limit, not a fault.
• List and segment sizes are recorded from the day the scopes exist onward. A historical backfill cannot recover past audience sizes; only a window containing today writes a snapshot.

Set up the next connector