Klaviyo
Category: Email & SMS · Connection: API key (private)
Klaviyo is connected via api key (private).
Before connecting
Section titled “Before connecting”- Source-platform requirement: Klaviyo account access with permission to create private API keys.
OAuth scopes
Section titled “OAuth scopes”Read access to campaigns, flows, metrics
All scopes are read-only.
Connecting
Section titled “Connecting”- Go to Settings → Integrations and select Klaviyo.
- Paste the API key from the source platform.
- Click Connect.
- The integration appears as Connected, with initial sync running.
For the full connection-method walkthrough, see Connect a datasource.
Data provided
Section titled “Data provided”- Campaigns and flows
- Sends, deliveries, opens, clicks
- Attributed revenue per send/flow
- Recipient list and segment data
What this powers
Section titled “What this powers”- Email & SMS dashboard
- Brand Overview Retention section
- Customer-level engagement signals
Troubleshooting
Section titled “Troubleshooting”- Connection fails — confirm the API key is a Private API key (not a Public key) generated under Klaviyo Settings → API Keys → Create Private API Key. Public keys can’t read campaign and flow data.
- Attributed revenue doesn’t match Klaviyo’s dashboard — Klaviyo defaults to a 5-day attribution window after a send; that window is configurable per account. Check Klaviyo’s Account → Attribution Settings and compare against the same window in Ignyte IQ.
- Flow metrics show fewer sends than expected — Klaviyo may be filtering out test sends or suppressed recipients in its dashboard but counting them in API responses. Match by send-status filter, not raw send count.
- General connection issues — see Datasource won’t connect.
- Other reconciliation differences — see Why numbers don’t match.