Connect Klaviyo to Tatheon and email stops being reported in its own vocabulary of opens and clicks, and starts being reported as a channel with revenue against it. This guide is for whoever administers the Klaviyo account. It covers creating the connection key, what Tatheon does with the data, and why the revenue figure will differ from the one Klaviyo shows you.
Before you start
You need access to create a private API key in Klaviyo, which sits under Settings and then API keys. Owner or Admin can do this. Manager and below usually cannot.
Create a key specifically for Tatheon rather than reusing one that already exists for another tool. A dedicated key can be revoked without breaking anything else, and it makes it obvious later what each key is for.
Create the connection
Open the source wizard and choose Klaviyo. The wizard opens Klaviyo sign in first, then sends you into the API key setup path, so you do not have to hunt through the settings yourself.
Create the key with read access to campaigns, flows, metrics and profiles. Tatheon reads performance data and never sends, so write scopes are not needed and should not be granted. A key with send permission is a key that can email your list, and no reporting tool needs that.
Paste the key back into the wizard. Tatheon stores it in the secret provider rather than in configuration, so it is not sitting in a file anyone can read.
What arrives
Campaign and flow performance backfill and then sync nightly. Flows and campaigns are kept separate throughout, because they behave differently and averaging them together hides the thing worth knowing.
Campaigns are one off sends. Their revenue is spiky and tied to the day you sent. Flows are automated and their revenue accrues continuously, which means a flow that quietly earns every day is easy to undervalue when it is averaged against a campaign that earned a lot once.
Tatheon reports revenue per recipient alongside the totals, which is the figure that lets a small segment with a high response rate be compared fairly against a large send with a low one.
Why the revenue will differ from Klaviyo
Klaviyo attributes an order to an email using its own attribution window, typically several days after a click or open. It counts that whole order as email revenue.
Tatheon reconciles that claim against what the store recorded and against what other platforms claim for the same order. When Meta and Klaviyo both claim the same purchase, and they frequently do, Tatheon shows both claims and the overlap rather than silently awarding it to one.
So Klaviyo’s own number is usually higher than the reconciled figure. That is not an error in either system. Klaviyo answers whether email touched the purchase. Tatheon answers what share of it email should be credited with.
Confirm it is working
Compare a recent closed month of total email revenue in Klaviyo against the Klaviyo reported figure in Tatheon. Those should be close, because that is the same claim from the same source. Then look at the reconciled figure and expect it to be lower.
If both are zero, the key is likely missing the metrics scope, which is the scope that carries revenue rather than engagement.
Common problems
Engagement data arriving without revenue is almost always a scope problem rather than a connection problem. Recreate the key with metrics read access.
A connection that worked and then stopped usually means the key was revoked during an audit of API keys, which is exactly why the dedicated key is worth creating at the start.
Next
If you sell subscriptions, connect Skio so recurring revenue is separated from one off orders. Email and subscriptions together are where most of the retention picture comes from.