Before you start
- A workspace owner/admin in a concrete Data Weaver client; Viewer and all-clients contexts cannot manage this connection.
- A customer-created Klaviyo private API key with the required read permissions. Enter it only into Nango's hosted credential form, never chat or support messages.
Set up the connection
- In Sources, connect Klaviyo using the hosted private-key form. Data Weaver verifies account identity, timezone, currency and available conversion metrics through Nango.
- Explicitly select the verified account to sync; selecting none syncs none.
- Open Klaviyo Settings, choose and save the exact conversion metric, then sync and inspect coverage. Reconnecting with a different account is rejected; disconnect before changing accounts.
Permissions requested
- Verified required private-key permissions: accounts:read to verify account settings; metrics:read to list conversion metrics; campaigns:read and flows:read to retrieve aggregate performance reports.
- No profile, recipient, forms or segments permissions are requested for this workflow. Nango holds the credential; Data Weaver does not directly read or store the private key.
Data read and actions performed
- Aggregate campaign/flow message reports include available delivery, open, click and conversion measures with metric identity, account timezone and currency.
- Conversion value is Klaviyo-attributed revenue for the selected metric, not payment-processor revenue or causal lift. No customer-profile ingestion is performed.
Refresh and sync
- Default cadence is daily, with manual Sync available. Bounded, resumable history and recent overlap can take multiple runs; quotas can leave partial coverage.
Limitations
- History begins no earlier than June 1, 2023 and is subject to provider/report availability. Daily/message unique counts are not deduplicated people over a whole date range.
- Reports use send-date attribution, unlike event-time aggregates. Apple Mail Privacy Protection can inflate opens; do not combine incompatible currencies.
- This beta private-key workflow is not OAuth or evidence of Klaviyo App Marketplace approval.
Troubleshooting
- For setup-required status, verify the saved conversion metric and explicit account selection.
- For denied reports, check the key's four read permissions; for account mismatch, reconnect the original account or disconnect first. Review quota retry/coverage rather than interpreting missing values as zero.
Disconnect and delete
- An owner/admin can remove the connection in the selected client. Opt-out and disconnect remove cached reports owned by that connection and initiate remote Nango cleanup.
- Separately revoke/delete the private key in Klaviyo's API-key settings. Local removal alone is not provider-wide key revocation; deleting a shared key affects its other users. Retained answers require separate deletion.
Privacy and help
You stay in control of what you connect. Review how we handle information, request deletion, or contact us.