Email

Klaviyo integration for digital marketing agencies

For e-commerce clients, Klaviyo often carries the email and SMS revenue. Documenting the Klaviyo account and what it connects to matters because its automations sprawl: an inherited Klaviyo account can carry many flows, some of them duplicates or paused and forgotten. Audit the flows in Klaviyo and record what you found on the client's map, so the next person on the account inherits it.

How Phloz models Klaviyo

What Phloz records about Klaviyo on each client's tracking map, and what it doesn't. Only GA4, Google Tag Manager and Google Ads connect to Phloz (read-only, through a connected Google account); everything else is recorded by your team. Health states are set by the person who checks, the structural audit re-runs weekly, and graph relationships show what each node connects to — so a node marked broken or overdue for verification shows up in the cross-client tracking-health view.

  • Klaviyo account as an email platform node with its name, list IDs, and notes
  • Flows and segments stay in Klaviyo — record anything worth keeping, like the flows you audited, in the node's notes
  • Edges to the Meta and Google Ads accounts it pushes audiences to, and from the store that syncs into it
  • Health status and last-verified date on the node, set by your team

Common Klaviyo configuration gotchas

The configuration mistakes agencies most often make with Klaviyo, surfaced here as a checklist agencies can run at every client onboarding. Honest, useful, not gated behind a sales pitch — these are real and you should audit for them regardless of whether you use Phloz.

  • Profile property mismatch: Klaviyo properties are case-sensitive but the Shopify integration sometimes sends mixed-case versions of the same property, fragmenting segment membership. Standardise property names at integration setup.
  • Flow trigger conflicts: two flows triggered by the same event (e.g., Order Placed) without exclusion rules cause subscribers to receive both flows. Audit "trigger and exit conditions" quarterly.
  • Segment refresh latency: most segments update in near real time, but a segment with a relative time condition ("in the last 30 days") adds or drops profiles on the passage of time only once every 24 hours. Agencies use such segments for time-sensitive sends and discover they are up to a day stale. Build time-sensitive sends on a flow, not on such a segment.

At launch (V1)

A Klaviyo account is an email platform node (vendor: Klaviyo) with its list IDs and notes; flows and segments aren't modelled. Edges show which ad platforms it pushes audiences to. There is no Klaviyo connection.

Not built yet

Klaviyo API sync: flow performance, list health, list-to-segment dependencies.

Why we built the integration this way

Most agency CRMs treat third-party tools as text fields: "GA4 Property ID" goes in a custom column on the client record. That works at one or two clients and breaks at five. With Klaviyo recorded on each client's tracking map — as its own typed node where Phloz has one, as fields and notes where it doesn't — the agency can answer "is this client's Klaviyo setup documented, and when was it last verified?" per client, and see every client ranked by tracking health.

Most of it is entered by hand at onboarding: only GA4 properties, GTM containers and Google Ads accounts can be imported from a connected Google account, and nothing syncs afterwards. The manual pass forces explicit verification at the exact moment the agency takes over the client's tracking — the cheapest moment to catch the gotchas listed above, before they become production issues.

When to use this in your client onboarding flow

The pattern we recommend: at every new client onboarding (see the client onboarding audit use case), spend 30 minutes documenting the client's Klaviyo configuration on the tracking map — IDs, tracking-code installations, conversion setup, the relationships to other systems. Verify each one fires by triggering a test event, then mark the node verified so the date is recorded. Add a recurring task (monthly, say) for the re-check, assigned to whoever owns tracking — the audit flags anything unverified for 30+ days either way.

Thirty minutes at onboarding costs far less than finding the same tracking issues during the first month of campaign optimisation — when finding them would mean a refund conversation. See the broader tracking infrastructure map use case for the agency-wide pattern.

Frequently asked questions

The three questions agencies ask most often about Phloz's Klaviyo integration. Honest answers — same data we'd give a friend evaluating the integration.

How does Phloz handle Klaviyo SMS alongside email?
On the same Klaviyo node, if at all: the email platform node has no SMS, consent, or opt-in fields, so note SMS in the node's notes. Phloz reads no Klaviyo data, so opt-in rates stay in Klaviyo.
Can Phloz import Klaviyo flows?
No. Flows aren't modelled at all — the Klaviyo node records the account and its list IDs — and there is no Klaviyo import or sync. Reviewing each flow by hand during onboarding is still worth doing; inherited accounts often carry obsolete flows that should be archived.
What about Klaviyo Reviews + Customer Hub?
There is no Klaviyo Reviews node. If a client uses Klaviyo Reviews as a review-collection channel, add it as a custom node linked to the store, or note it on the Klaviyo node.

Other integrations

Other email and adjacent tools, and how Phloz handles each.

Start your free trial

14 days free for new workspaces · No credit card · Starter tier free forever