Klaviyo flow stopped generating revenue — diagnose by symptom

---

title: "Klaviyo flow stopped generating revenue — diagnose by symptom" description: "A diagnostic decision tree for a Klaviyo flow whose attributed revenue went to zero — trigger failure, attribution drift, content issues, segment changes, and more." slug: "klaviyo-flow-stopped-generating-revenue" publishedAt: "2026-05-19" updatedAt: "2026-05-19" painCluster: 1 intent: 9 tier: 4 faq:

• q: "Why would a Klaviyo flow suddenly stop generating revenue?" a: "Four broad categories. The trigger event stopped firing (the most common). The flow has entries but no conversions (content or offer issue). The conversions are happening but not being attributed (attribution model or tracking issue). The audience that converts has shrunk (segment definition or list-quality issue). Each requires a different diagnostic path."
• q: "How do I tell if it's a trigger issue or a conversion issue?" a: "Open the flow → Latest Entries. If entries have dropped to near zero, it's a trigger issue. If entries are normal but the Performance view shows revenue collapsed, it's a conversion or attribution issue. The diagnostic path forks based on this single check."
• q: "What's the most common reason a flow stops generating revenue?" a: "The underlying trigger event stopped recording — Started Checkout, Placed Order, Viewed Product. The flow looks Live in the UI but isn't being triggered. This is most often caused by Shopify integration issues (expired token, theme regression, plugin conflict)."
• q: "Can attribution settings cause a flow's revenue to look like zero?" a: "Yes. If the attribution window was changed or the conversion event was reconfigured, revenue that's actually being driven by the flow may not be credited to it. Check Settings → Attribution and confirm the configuration matches expectations."
• q: "How long should I wait before declaring a flow's revenue is really gone?" a: "For high-volume flows (abandoned cart, post-purchase) — 24-48 hours is enough signal. For low-volume flows (replenishment, winback) — 7-14 days because the trigger volume is naturally lower and you need more sample to be confident."
• q: "Could the flow itself have been edited and broken?" a: "Yes. If someone on your team edited the flow recently (filter change, trigger change, template edit), the change may have broken something subtle. Check the flow's activity log — Klaviyo records every edit. Recent edits in the same window as the revenue drop are the prime suspect."
• q: "Does Apple MPP affect flow revenue reporting?" a: "Indirectly. MPP inflates open rates, which inflates engaged-30-day segment size, which can mean your flow's audience includes profiles that look engaged but aren't. The revenue itself isn't affected; the conversion-rate-per-recipient calculation can be distorted."
• q: "Will Playbook tell me which type of flow failure is happening?" a: "Yes. We diagnose down to one of the four categories — trigger failure (most common), conversion drop, attribution issue, audience change — and surface the specific finding with a deep link to the relevant Klaviyo screen for each." related:
• klaviyo-abandoned-cart-flow-not-firing
• klaviyo-revenue-attribution-missing
• klaviyo-checkout-started-event-not-working
• klaviyo-shopify-integration-not-syncing

---

A Klaviyo flow whose attributed revenue went to zero is one of the more confusing diagnostic situations in the product. The flow shows Live. The dashboard shows zero (or close to zero) revenue. The symptom is clear but the cause could be in any of four categorically different places. This page is a decision-tree-style diagnostic for working through which one.

The fork in the road

The first decision tells you which half of this page applies.

Open the flow. Look at the "Latest Entries" tab. Count the entries from the last 24 hours (high-volume flows) or last 7 days (low-volume flows).

If entries are at or near zero: the flow isn't being triggered. The diagnostic path is "trigger and integration health." Skip to Path A below.

If entries are normal but revenue dropped: the flow is firing but not converting (or not being attributed). The diagnostic path is "conversion, content, and attribution." Skip to Path B below.

Don't skip this fork. The two paths are entirely different and trying to debug one when the answer is in the other wastes hours.

Path A: the flow isn't being triggered

If entries have dropped sharply, the trigger isn't firing. Work through these in order.

A1. The trigger event has stopped recording

The single most common cause of a silent flow failure. The flow editor shows everything green. The trigger metric has gone silent.

How to verify. Analytics → Metrics → [your flow's trigger event]. Look at the chart. A flat right edge — no events in the last 12+ hours when the previous week shows steady volume — means the event has stopped recording.

Common causes.

• Shopify OAuth token expired (Settings → Integrations → Shopify will show the error explicitly).
• Klaviyo onsite tracking snippet removed from theme (after Shopify theme update).
• WooCommerce plugin conflict broke the webhook handshake.
• Custom-storefront API integration broke.

Fix. Depends on the cause. Reconnect Shopify, re-enable onsite tracking, fix the WooCommerce plugin, restore the API integration. Once the event flows again, the flow resumes triggering within the trigger's natural delay.

A2. A flow filter is blocking every profile

The event is firing, profiles are eligible, but a filter on the flow is filtering everyone out.

How to verify. Open the flow's trigger node. Read every filter that's been applied. For each, ask: could this filter evaluate true for every profile? A common offender is "[Event] zero times since starting this flow" where the event is also the flow trigger — every profile that enters satisfies the exit condition immediately.

Fix. Remove the conflicting filter or rewrite it to reference a different event.

A3. Smart Sending is suppressing every send

Less common as a complete shutdown but possible — if Smart Sending is on and your broadcast cadence is high, the suppression rate on a flow can approach 100%.

How to verify. Open the flow → Performance. Look at the Skipped column. If skipped is a large percentage of attempted, Smart Sending is the culprit.

Fix. Turn Smart Sending off on the flow's emails (especially for time-sensitive flows like abandoned cart).

A4. The flow itself was changed

Someone edited the flow recently and the change broke it. The trigger configuration, filter logic, or status flipped from Live to Draft or Manual.

How to verify. Open the flow → check the activity log (top right typically shows a "View edit history" or similar). Look at edits in the same window as the revenue drop.

Fix. Revert the breaking edit if possible. If reverting isn't possible, identify exactly what changed and undo that specific change.

Path B: the flow is firing but not converting

If entries are normal but revenue collapsed, the issue is downstream of the trigger. Work through these in order.

B1. The conversion event isn't being attributed correctly

Klaviyo's attribution model can be misconfigured or affected by integration changes. The flow may be driving real conversions that aren't being credited.

How to verify. Settings → Attribution → check the configuration. The default is 5-day click attribution for email; if it's been changed, that's a possible cause. Check the conversion event (typically Placed Order) — confirm it's the right event and is firing.

Fix. Restore the attribution configuration. If the conversion event has changed (e.g., from Placed Order to a custom event), update flows to reference the new event.

B2. The discount code expired

If the flow's emails contain a discount code that's no longer valid, conversion rate drops sharply. The recipients click through to checkout, find the code doesn't apply, and bounce.

How to verify. Open the flow's emails. Click any discount-code links. Apply the code in checkout. Does it work?

Fix. Update the code. For ongoing protection, use Klaviyo's dynamic-code generation (creates a unique code per profile, expires on schedule).

B3. The product or offer in the template is stale

The flow references a specific product that's been discontinued, renamed, or sold out. Recipients click through to a 404 or to an unrelated page. Conversion drops.

How to verify. Click every product link in the flow's templates. Confirm each one lands on a real, available product page.

Fix. Update the template to reference current products. Consider using dynamic product blocks (recommended-product, recently-viewed, category-default) instead of hardcoded products so the flow self-updates as your catalog evolves.

B4. The sender reputation has slipped

Recipients are still entering the flow, but the messages are landing in spam (or being filtered before inbox). Open and click rates drop, conversion follows.

How to verify. Klaviyo deliverability hub → per-ISP open rates for the affected flow. If opens dropped uniformly across ISPs, reputation is the issue. Check complaint rate — if it's climbed near Gmail's 0.3% threshold, you're in the deliverability spiral.

Fix. Reduce sending volume. Suppress non-engaged subscribers. Improve content quality. Verify authentication (DKIM/SPF/DMARC) is intact. Recovery takes 30-90 days.

B5. The audience that converts has shrunk

The flow is firing to a different population than before — typically because a segment definition changed, a list was edited, or the underlying customer base shifted.

How to verify. Look at the flow's audience over time. Has the composition changed? Compare engagement metrics for the flow's audience now vs 60 days ago.

Fix. Depends on the cause. If a segment was edited, audit the change. If the customer base shifted, the flow may need to be updated to match the new audience.

B6. The flow was edited in a way that broke conversion (not entries)

Someone updated the flow's template, subject lines, or content in a way that hurt conversion without affecting entries. Recipients still enter; they just don't convert at the same rate.

How to verify. Check the flow's edit history. Look at edits in the same window as the revenue drop. Are there template changes? Subject-line changes?

Fix. Revert the breaking edit or test the change against the old version to confirm it's the cause.

How to verify the fix

Once you've identified and addressed the cause:

1. Watch entries for 24-48 hours (Path A) or conversion for 7 days (Path B). The change should be visible within these windows.
2. Compare to a healthy baseline. Pull metrics from before the issue started and compare against current metrics. Restored to baseline is the goal.
3. If the original cause was integration health (Path A1), set up monitoring so the next occurrence is caught within an hour, not days or weeks.

Why this fork-in-the-road matters

Most operators, when they see a flow's revenue drop, start by examining the flow itself — content, templates, sequencing. That's Path B thinking. But Path A failures (trigger and integration issues) are more common in practice and the symptoms look identical at the dashboard level. Wasting hours debugging templates when the answer is "the Shopify token expired three days ago" is the most common diagnostic mistake we see.

The "Latest Entries" check is the 30-second triage that puts you on the right path. Always start there.

What Playbook flags

We monitor flow revenue across these dimensions: trigger event freshness, entry count vs baseline, conversion rate vs baseline, attributed-revenue vs baseline. When any of these signals drift outside normal variation, we surface the finding categorized by which path applies — so the operator opens an alert and immediately knows whether they're debugging an integration issue or a conversion issue.

The deep link goes to the relevant screen — trigger metric for Path A, flow performance for Path B. The 30-second triage we describe above is the same triage Playbook does on the backend, just continuously instead of post-hoc.