Start free

Email marketing · USE CASE

Find Klaviyo flows that stopped sending.

Compare each order-triggered Klaviyo flow with the orders Shopify recorded on the same days. See which flow went quiet while orders kept coming, which one is waiting for manual review and which ones are still sending at their usual rate.

Data sources
Assistant
Destination
Try it with your data Free with up to 3 data sources · No credit card
A WORKED EXAMPLE

Did any order-triggered Klaviyo flow stop sending while orders kept coming in?

Order-triggered emailSent Nov 3–12Per 100 orders
Post-purchase · Thank-you email00, was 60
Review request6649, was 50

Oct 16–Nov 12, complete days in the Klaviyo account time zone (New York) · Both sources read Nov 13, 18:00 UTC

Shopify recorded 132 orders from Nov 3 to Nov 12, but the post-purchase thank-you email sent to no one. Before Nov 2 it reached about 60 customers for every 100 orders. The review request flow kept its usual rate, and the cross-sell flow has been on manual review since it was created.

WHERE THE RESULT GOES

Google Sheets

Export each data source report to Google Sheets, then add your analysis or checklist to the review Sheet.

Example use case

Ask. Follow up.
Take the next step.

✦ AI assistantSample use case
KlaviyoShopify
YOU

  1. 01
    Flow live · Email action set to draft Nov 2 · 0 sent Nov 3–12Fix first

    Next

  2. 02
    Flow manual since Sep 30 · No rows in the performance reportConfirm the intent

    Next

  3. 03
    49 sent per 100 orders a week earlier, was 50No action

    Next

Oct 16–Nov 12, complete days in the Klaviyo account time zone (New York) · Both sources read Nov 13, 18:00 UTC

01 · CONNECT YOUR DATA

Your tools. One place to ask.

2 of 3 Free data sources
No credit card · Daily refresh

DatapipeYour project
Your AI assistantor a report in Sheets / Data Studio
  1. Create your free workspace

    Sign up with your company email. Your first project opens on Data sources.

  2. Add the data sources

    Choose the accounts for this use case. Authorize access and select the property or site.

  3. Bring your question

    Connect your project to a supported AI assistant, or build your source reports.

Create a free account →
Setup steps & what you need

Email/password signups confirm their email first. Use Google signup with a company account if you prefer.

  • Klaviyo: Add the intended Klaviyo account using its supported sign-in or a private API key that can read flows, metrics and account settings. Setup guide ↗
  • Shopify: Enter your shop, authorize it, and add that store to the project. Setup guide ↗

Free includes 3 data sources across the workspace. One account/property added to one project counts as one. Extra properties or the same account in another project use another slot.

02 · ASK A USEFUL QUESTION

Start with a prompt.
Follow the evidence.

Copy these in order into your connected assistant.
Each builds on the answer before it.

01

List our flows and the metric to measure them with

Read the full prompt
Use only this Datapipe project’s authorized data. Discover the connected accounts, datasets and compatible fields first. Confirm dates, timezones, currencies and data coverage. Keep missing or unmatched rows visible; never substitute sample data. Compare the sources explicitly and explain every match. Do not change source records or send messages.

From the connected Klaviyo account, read Flows inventory with Flow ID, Flow name, Flow status, Archived and Trigger type, and Account reporting settings for the account time zone and currency. Then read Metrics inventory and show every metric named Placed Order with its Metric ID and the source Klaviyo lists for it, so I can choose the one from Shopify. List the flows that are not archived and say which ones look order-related from their name and trigger type, but treat that as a guess: the trigger type does not say which event starts a Metric flow. Also list the fields available in Shopify Orders (GraphQL).
02

Read daily flow sends next to daily orders

Read the full prompt
Read Klaviyo Flow performance over time with a daily interval for the last 29 days, using the Shopify Placed Order metric ID I chose. Return Flow ID, Flow message ID, Flow name, Flow message name, Send channel, Bucket starts at, Recipients and Delivered. Klaviyo uses the account time zone for these days; keep each bucket’s offset as returned. From Shopify, read Orders (GraphQL) created in the same dates with Order name, Created at, Cancelled at and Financial status, convert Created at to the Klaviyo account time zone and count orders per day, including cancelled ones. Drop today’s partial day from both. Tell me which flows from the inventory have no rows in the report instead of assuming they sent zero.
03

Prepare the flow check for the email owner

Read the full prompt
For each flow message I confirm is triggered by an order, compare daily recipients with Shopify orders: the same day for a message that sends right away, seven days earlier for one that waits a week. Show recipients per 100 orders before and after any day the rate changes sharply, and list the dates when orders came in but the message sent nothing. For each flagged flow, read Actions for a flow and show each action’s type, status, name and last update. Prepare one table: flow, message, trigger, flow status, action status, rate before, rate after, orders since the change and an estimate of customers who missed it, labelled as an estimate. Draft it in this conversation. Do not change any flow or message in Klaviyo.
Need to connect your assistant?Claude guide ↗ChatGPT guide ↗

03 · USE WHAT YOU FIND

Compare each order-triggered message with orders.

  1. 01

    List the flows and find the right conversion metric.

  2. 02

    Read daily flow sends and the orders behind them.

  3. 03

    Compare each order-triggered message with orders.

Check the result at your next review.

After the email owner switches the thank-you email back on, read the same report a week later. Recipients per 100 orders should return to around 60 from the day it was restored, and the action status should read live. Run the check every week so a stopped flow shows up within days rather than weeks.

Implementation tips for this use case

For each flow message triggered by an order event, divide recipients by orders on the same day, or by orders a week earlier for a message that waits a week. Compare the rate before and after any day it changes. Flag a message that falls to zero while orders continue, and a flow with no rows at all. Read Actions for a flow for anything flagged to see each action’s current status. Take the list to the email owner, who checks the flow in Klaviyo and decides what to switch back on.

WHEN YOU NEED MORE CONTEXT

Go a little deeper.

The method and reporting checks
behind this example.

How to find Klaviyo flows that stopped sending while Shopify orders continued

  1. List the flows and find the right conversion metric.

    Add your Klaviyo account and your Shopify store to one project. Read Flows inventory for each flow’s ID, name, status, archived flag and trigger type, and Account reporting settings for the account time zone. Flow reports ask for one conversion metric, so read Metrics inventory and pick the Placed Order metric that comes from Shopify by its ID. Trigger type only says Metric, Added to List and so on; confirm in Klaviyo which event triggers each flow.

  2. Read daily flow sends and the orders behind them.

    Read Flow performance over time with a daily interval for the last 29 days: Flow ID, Flow message ID, Flow name, Flow message name, Send channel, Bucket starts at, Recipients and Delivered. Klaviyo places those days in the account time zone. Read Shopify Orders (GraphQL) for the same dates with Order name, Created at, Cancelled at and Financial status, and count orders per day after converting Created at to the Klaviyo time zone. Drop today, because neither source has a complete day yet.

  3. Compare each order-triggered message with orders.

    For each flow message triggered by an order event, divide recipients by orders on the same day, or by orders a week earlier for a message that waits a week. Compare the rate before and after any day it changes. Flag a message that falls to zero while orders continue, and a flow with no rows at all. Read Actions for a flow for anything flagged to see each action’s current status. Take the list to the email owner, who checks the flow in Klaviyo and decides what to switch back on.

See the complete example report
EXAMPLE REPORT

Did any order-triggered Klaviyo flow stop sending while orders kept coming in?

Oct 16–Nov 12, complete days in the Klaviyo account time zone (New York) · Both sources read Nov 13, 18:00 UTC

Did any order-triggered Klaviyo flow stop sending while orders kept coming in?
Order-triggered emailSent Nov 3–12Per 100 orders
Post-purchase · Thank-you email00, was 60
Review request6649, was 50
WHAT TO LOOK ATShopify recorded 132 orders from Nov 3 to Nov 12, but the post-purchase thank-you email sent to no one. Before Nov 2 it reached about 60 customers for every 100 orders. The review request flow kept its usual rate, and the cross-sell flow has been on manual review since it was created.

Compare each order-triggered message with orders.

From Oct 16 to Nov 1 the thank-you email went to 148 customers while Shopify recorded 247 orders, about 60 for every 100. On Nov 2 it sent 3, then nothing for ten days while Shopify recorded 132 orders. The flow is still live, but its email action now reads draft, last updated Nov 2 at 15:40 New York time. At the earlier rate, about 79 customers would have received it. This flow is set to manual, so Klaviyo queues each message for someone to review instead of sending it. The performance report returned no rows for it in the window. That is consistent with nothing being sent, but a missing row is not proof, so check the flow’s Needs Review queue in Klaviyo. This flow waits about a week after the order, so it is compared with orders placed seven days earlier. It reached 73 customers from 146 orders before Nov 2 and 66 from 135 after. Its trigger comes from Shopify too, which suggests order events kept reaching Klaviyo and the problem sits inside the thank-you flow.

Try the example with sample CSVs

Fictional rows matching the example above. Attach these files to your assistant for a sample analysis.

Data method, reporting checks & sources

Add your Klaviyo account and your Shopify store to one project. Read Flows inventory for each flow’s ID, name, status, archived flag and trigger type, and Account reporting settings for the account time zone. Flow reports ask for one conversion metric, so read Metrics inventory and pick the Placed Order metric that comes from Shopify by its ID. Trigger type only says Metric, Added to List and so on; confirm in Klaviyo which event triggers each flow. Read Flow performance over time with a daily interval for the last 29 days: Flow ID, Flow message ID, Flow name, Flow message name, Send channel, Bucket starts at, Recipients and Delivered. Klaviyo places those days in the account time zone. Read Shopify Orders (GraphQL) for the same dates with Order name, Created at, Cancelled at and Financial status, and count orders per day after converting Created at to the Klaviyo time zone. Drop today, because neither source has a complete day yet. For each flow message triggered by an order event, divide recipients by orders on the same day, or by orders a week earlier for a message that waits a week. Compare the rate before and after any day it changes. Flag a message that falls to zero while orders continue, and a flow with no rows at all. Read Actions for a flow for anything flagged to see each action’s current status. Take the list to the email owner, who checks the flow in Klaviyo and decides what to switch back on.

Klaviyo daily buckets and Shopify order dates use the same time zone: the Klaviyo account time zone, with the offset changing when daylight saving ends. Only flows triggered by an order are compared with orders; list sign-up and date-based flows are left out. Messages that wait after the trigger are compared with orders from the matching earlier days. A flow with no rows in the report is shown as missing, not as zero sends, and checked in Klaviyo.

  • Klaviyo daily buckets and Shopify order dates use the same time zone: the Klaviyo account time zone, with the offset changing when daylight saving ends.
  • Only flows triggered by an order are compared with orders; list sign-up and date-based flows are left out.
  • Messages that wait after the trigger are compared with orders from the matching earlier days.
  • A flow with no rows in the report is shown as missing, not as zero sends, and checked in Klaviyo.
  • Access to the intended Klaviyo account or property.
  • Access to the intended Shopify account or property.
  • Klaviyo daily buckets and Shopify order dates use the same time zone: the Klaviyo account time zone, with the offset changing when daylight saving ends.

For blended reports, align dates, normalized URLs, and reporting grain. Query-level search rows must not duplicate page-level sessions.

Klaviyo API: query flow series (intervals and time zone) ↗Klaviyo: flow and message statuses (draft, manual, live) ↗Klaviyo: Shopify data reference (Placed Order and other events) ↗Report starting points ↗

A FEW USEFUL ANSWERS

Before you start.

Why do I need Shopify as well as Klaviyo?

Klaviyo shows how many people each flow message reached. Shopify shows how many orders could have triggered it. A drop in sends only means something when you know whether orders dropped too.

Why is the rate around 60 and not 100 per 100 orders?

Not every order produces a recipient. Customers without email consent, flow filters, Smart Sending and repeat buyers inside a short period all reduce it. What matters is a sudden change in the rate, not its level.

Does Klaviyo count cancelled orders?

Klaviyo records Placed Order when the order is created, so a later cancellation does not remove the trigger. That is why cancelled orders stay in the daily count, unless your flow filters exclude them.

Which time zone should I use?

The Klaviyo account time zone. Flow reports place each day in it, and Shopify order times can be converted to match. Around daylight saving changes the day’s offset changes too, so keep the offset each bucket returns.

Can the report tell me why a flow stopped?

Not on its own. The action status and last update show what changed and when. The person who edited the flow can say why, and Klaviyo’s flow analytics and recipient activity show who was skipped.

Does the assistant turn the flow back on?

No. It prepares the check in your conversation. The email owner reviews the flow in Klaviyo and decides what to switch back on.

YOUR NEXT STEP

Try it with your own data.

Start free with up to 3 data sources. No credit card.

Start free →