<aside> 💡
This page explains how the Kinetic platform connects to your Klaviyo account, what permissions (“scopes”) we request, and why they are required. Our aim is to be transparent about the data we access so you can connect with confidence.
</aside>
Kinetic enables you to create, edit, and send interactive, website-like emails directly from Klaviyo. With the integration in place, you can:
When you connect Kinetic to Klaviyo, you will be asked to grant specific permissions. These are Klaviyo API scopes, and they map directly to the features you can use within Kinetic.
Below is a summary of each scope, why it’s needed, and how we use it.
| Scope | Why We Need It | Example Use |
|---|---|---|
| accounts:read | Retrieves your account name and default sender details when first connecting. | Display your Klaviyo account info in Kinetic. |
| templates:read | Loads your existing templates into Kinetic for editing. | View and select templates to work on. |
| templates:write | Creates, updates, or deletes templates with interactive content. | Save changes, add new templates, or remove unused ones. |
| campaigns:read | Retrieves campaign details when assigning templates or checking status. | View campaign info before sending AMP whitelisting emails. |
| campaigns:write | Creates and updates campaigns for sending AMP whitelisting or interactive content. | Only used one-time if 1-click-whitelisting is used. |
| flows:read | Lists available flows so you can insert interactive templates. | When creating an interactive template for a flow, choose a flow to get detailed instructions on how to integrate that template into your flow. |
| events:read | Retrieves event data for triggers like abandoned carts. | Send a flow preview mail from Kinetic by selecting a recent checkout event. |
| flows:write | Creates or updates flows with interactive content. | Automatically create a flow with our interactive template. |
| metrics:read | Lists available metrics so you can select them in flows. | Chose the metric to use as the flow trigger. Used for the automatic creation of flows. |
| lists:write | Creates temporary lists and adds contacts for test sends. | Prepare lists for AMP approval emails. Only used one-time for 1-click-whitelisting. |
| profiles:read | Checks if a profile exists before adding it to a list. | Avoid duplicate test contacts. Only used one-time for 1-click-whitelisting. |
| profiles:write | Creates or updates profiles for flow renders. | Add HTML parts to a Klaviyo profile to be used in an interactive email. Removed directly after usage. |
| events:read | Reads abandoned checkout events. | Select a recent abandoned checkout event and send yourself a test mail before pushing to Klaviyo. |
We only store the minimum information necessary to power the integration. Specifically:
All other data is not stored in any way. Your Klaviyo data is never sold, shared with third parties, or used for unrelated purposes.