Connect your Klaviyo account to Didivio

You need three things:

• A Didivio workspace. Didivio is invitation-only. Your account manager creates the workspace and invites you by email; you set a password from that invitation.
• The Admin role on that workspace. Only a company admin can attach a Klaviyo account. If you sign in and the connect buttons are missing, you are a viewer — ask an admin on your team, or your account manager.
• Access to your Klaviyo account. Either the ability to sign in to Klaviyo and approve access, or permission to create an API key in it.

You do not need to prepare anything inside Klaviyo first. Reporting is configured on the Didivio side by your team after the account is attached.

Sign in at didivio.com/login, then go to Settings → Integrations → Klaviyo.

The page shows the account currently attached, when it last synchronised, and a status badge. Before you connect anything it reads Not connected.

Two routes lead to the same reports. Pick one.

Sign in through Klaviyo (recommended). Press Connect with Klaviyo. You are taken to Klaviyo, you sign in there, and you approve the read permissions listed below. Klaviyo returns you to the same settings page with the connection in place. Your Klaviyo password is never entered into Didivio and is never seen by it.

Use a read-only private API key. Press Use a private API key instead, then paste a key created in Klaviyo under Settings → API keys. Give the key read access to accounts, campaigns, templates, flows, lists, segments and metrics. Didivio checks the key against Klaviyo before saving it, warns you if a permission is missing, stores it encrypted, and never displays it again.

If the Connect with Klaviyo button is unavailable on your server, the page says so and points you at the private key route. The key route gives exactly the same reports.

Connecting does the work; there is no sync button for you to find.

• Didivio identifies the conversion metric your reports are measured on — normally Placed Order — and queues the first read of your account.
• When that metric resolves, Didivio backfills a rolling 13 months of history, so your first report can compare this month against the same month last year. Where no unambiguous metric exists, only the current month is read and your team selects the right metric before the history is pulled.
• Your account manager is notified that the account is connected, including when a metric choice is the step blocking your first report.

The status badge moves to Preparing reports, not to a green tick. That is deliberate: connected is not the same as reported on.

Between a connection and a report you can open, there are up to three steps on the agency side: the conversion metric, a period-by-period verification of the figures, and publication. This is why Didivio does not show a finished report the moment data lands — every number a client sees has been checked against the source first.

Published reports appear under Reports in your workspace, and the Klaviyo settings page moves to Connected, naming the month your reports run through. From then on the account synchronises daily and nothing further is asked of you.

Both routes request the same seven read-only permissions, and nothing else:

• accounts:read — account name, currency and time zone, so months and money are reported in your own terms.
• campaigns:read — campaign sends, recipients, engagement and attributed revenue.
• templates:read — the creative behind a campaign, so a report can show what was sent.
• flows:read — flow and flow-message performance.
• lists:read and segments:read — audience size and growth.
• metrics:read — the conversion metric your revenue figures are attributed against.

Email, SMS, MMS, RCS and other channels are reported separately and never merged. Gmail deliverability data, where you also connect Google Postmaster Tools, is kept separate from Klaviyo data and never blended into it.

• Not connected — no Klaviyo account is attached to this workspace yet.
• Preparing reports — connected, history is being read, and your team is preparing the first report.
• Connected — connected, synchronising, and reports are published through the month shown.
• Reconnect required — Klaviyo has stopped accepting the access, which happens when a connection is revoked or a key expires. Reporting resumes when you reconnect.
• Needs attention — Didivio is having trouble reading the account. Your team is alerted automatically; reconnecting often resolves it.

The connect buttons are not shown. Attaching Klaviyo is limited to company admins. Ask an admin on your team or your account manager.

Klaviyo said access was not granted. The approval screen was declined or closed. Nothing was connected; start again from the same page.

The attempt expired or was already used. Connection attempts are single-use and short-lived. Start a new one from the settings page rather than reusing an old browser tab.

Your key is missing permissions. The key saved, but one of the seven read scopes was not granted, so part of the reporting cannot be built. Create a replacement key with all seven and connect again — the new one replaces the old in place.

You connected the wrong Klaviyo account. Run either route again with the correct account. Connecting replaces the existing connection; you do not need to disconnect first.

You want to stop sharing the account. Removing the credential also stops your reporting, so it is not a self-service button — ask your account manager and it is done together.

Every workspace has a Support section in the portal that reaches your account manager directly, and it is the fastest route to an answer about your own reports.

If you cannot sign in, or you are asking about Didivio itself rather than a workspace you belong to, email info@didoagency.com. Questions about this integration, the permissions Didivio requests, and removing a connected Klaviyo account are all answered there.

How Didivio handles your information is set out in our Privacy Policy and Terms of Service.