Klaviyo has separate read scopes for profiles, lists, segments, campaigns, and flows.
Before you start
- A Klaviyo account that can approve the requested OAuth read scopes.
1. Add Klaviyo in Permute
In your workspace, open Connectors, select Add Connector, choose Klaviyo, and name the account.
2. Authorize Klaviyo
- Select Connect with OAuth.
Permute starts Klaviyo OAuth when you select Connect with OAuth. Sign in to the account that holds the profiles and marketing data you want. Review the account and requested scopes on Klaviyo’s approval screen.
The setup screen does not ask for a private API key. Klaviyo supports both private keys and OAuth, but this Permute connection uses OAuth.
Understand read scopes
Klaviyo uses scopes to decide which API records an app may read. Profile data needs profiles:read; lists, segments, campaigns, and flows have their own read scopes. The connection can only access the data allowed by the approved OAuth scopes.
If one data group is missing, check the approved read scopes and the account’s data. Klaviyo lists separate read and write scopes; review the exact scopes requested on its approval screen.
3. Check the first result
- Find a known Klaviyo profile in the account you approved.
- If checking a list or segment, verify the profile’s membership in that source group.
Available data
| Data group | What the setup screen covers |
|---|---|
| Audience | Profiles, lists, and segments. |
| Marketing | Campaigns and flows. |
Read the Klaviyo data model
A Klaviyo profile represents a person. Lists hold chosen memberships; segments use rules to include profiles whose data matches them. A profile may exist without belonging to a particular list or segment. Campaigns are a separate marketing group.
When comparing data, identify whether you expect the profile, its list membership, or a segment result. A changing segment count can reflect its rules or profile data rather than a connector issue. Check the source group in the Klaviyo account approved during OAuth.
Check the profile before its groups
Klaviyo’s Profiles API retrieves profile records under profiles:read. A list or segment then describes membership for profiles. If a named person is absent from a list, search for the profile first, then inspect the list or segment in Klaviyo.
This check separates a missing person from a membership difference. It also helps when the same person has changed details: the profile record and a dynamic segment can change at different times as Klaviyo evaluates its rules.
Troubleshooting
| Problem | What to check |
|---|---|
| One group is absent | Check the group’s read scope and that it contains records in Klaviyo. |
| A person is absent from a list | Find the profile first, then check its list membership. |