Use OAuth, not private API keys
Adynamite connects to Klaviyo through Klaviyo OAuth. You do not need to create, copy, or store a private API key to connect your account.
During setup, Klaviyo shows the permissions Adynamite is requesting. Review those permissions in Klaviyo, approve access if they match your team policy, and return to Adynamite to finish the connection.
Settings > Sources
Connect Klaviyo with OAuth
Meta Ads
2 mappedGoogle Ads
1 mappedKlaviyo
ConnectShopify
1 mappedOAuth approval
Approve Klaviyo access
Review the permissions in Klaviyo, then return to Adynamite to finish setup.
Before you start
Make sure you have access to the Adynamite workspace where Klaviyo should be connected. You also need a Klaviyo account role that can approve OAuth access, usually an admin or owner role.
If your company requires approval for marketing platform permissions, confirm that you are allowed to approve the requested Klaviyo scopes before starting the connection.
Connect Klaviyo
Sign in to Adynamite, open Settings, then choose Sources. Select Klaviyo from the available sources and start the connection flow.
Klaviyo will ask you to sign in if you are not already authenticated. Review the permission screen carefully, approve the requested access, and wait to be returned to Adynamite.
After the redirect, confirm that the Klaviyo account appears as connected in Adynamite. If your team manages more than one workspace or Klaviyo account, map the connected account to the right workspace before using it in reporting.
Workspace source mapping
Demo Lifecycle Workspace
Source
Klaviyo
Demo Lifecycle Account
MappedEU Newsletter Program
ReadyLegacy Test Account
Not mappedLinked accounts
Demo Lifecycle Account
Campaigns, flows, metrics, templates
Source readiness
Auth
Ready
Sync
Queued
Reports
Next refresh
What becomes available
After connection, Adynamite can use the Klaviyo data your approved permissions make available. This may include campaigns, flows, metrics, templates, images, lists, segments, tags, catalogs, coupons, and profile or subscription data where enabled.
When your Klaviyo setup includes translations or related content tools, Adynamite can use the enabled fields to support reporting, content review, and lifecycle analysis inside the workspace.
Klaviyo Reporting
Stored sync snapshot - demo data
Sent
128k
Open rate
42.8%
Click rate
3.9%
Conversions
612
Revenue
$84.2k
Flow share
37%
| Email asset | Type | Sent | Open | Click | Revenue | Suggested next step |
|---|---|---|---|---|---|---|
| Spring Sale Campaign | Campaign | 48k | 44.1% | 4.3% | $31.8k | Scale offer angle |
| Welcome Flow | Flow | 19k | 51.6% | 6.8% | $18.4k | Test proof block |
| Abandoned Cart Flow | Flow | 27k | 39.2% | 5.1% | $23.7k | Review discount step |
Main use cases
Teams use the Klaviyo connection to review campaign and flow performance, understand how lifecycle messaging contributes to the broader paid-media operating picture, and compare email movement with ads, analytics, and commerce results.
Adynamite can also support email content analysis, creative intelligence, offer review, and AI recommendations for hooks, message angles, tests, and follow-up actions.
Troubleshooting
If Klaviyo asks you to sign in again, complete the login and restart the approval step. If you cannot approve access, confirm that your Klaviyo role has the right admin or owner permission.
If the wrong workspace is selected, return to Adynamite and map the Klaviyo account to the correct workspace. If campaigns or flows are not visible yet, the data may still be syncing or the approved permissions may not include the required access.
If a connection stops working, reconnect Klaviyo from Settings > Sources so Adynamite can refresh authorized access.
Privacy and safety
Adynamite uses authorized Klaviyo API access and respects the workspace permissions configured in your account. Connected data is used to power reporting, analysis, recommendations, and approved workflows inside Adynamite.
Write actions and supervised changes are gated by Adynamite's confirmation and safety controls, so teams can review actions before they are applied.