Shopify Integrations: What to Connect, What to Fix, and Why It Matters
Shopify Integrations: What to Connect, What to Fix, and Why It Matters
This article explains why a “connected” status in an app’s integration settings is not the same as that integration actually working for customers. As Clear.io’s Sebastian Brown Glad noted on Episode 3 of the DTC Revenue Rocket Podcast, it is surprisingly common to see brands with a best-of-breed tech stack where none of the apps talk to each other — and nobody has told them to connect them or how. The result is a customer who bought, left a review, and emailed support still receiving the same emails as someone who has never heard of the brand.
The post walks through a three-question test using one real customer’s Klaviyo profile to identify which of three problems exists: the integration was never switched on, it is connected but misconfigured, or it works but the data is never used. It then covers which integrations to prioritize and how to decide. The main takeaway is that before adding another app, the right move is to check how the ones already being paid for actually work together — and whether any of what they know about customers is changing a single email or text.
- A green checkmark means two apps can share data, not that they are Following one real customer through Klaviyo — checking whether their order, review, and support ticket all arrived correctly and whether any of it changed what they received — is the fastest way to find which of the three problems is present and where to start fixing it.
- Misconfigured integrations are harder to spot than missing ones A new Shopify theme can silently turn off browsing data. Two metrics sharing one name in Klaviyo mean a flow built on the wrong one never sends. Partial refunds do not sync. One review event in REVIEWS.io only covers company reviews, not product ones. Each of these looks connected on the dashboard while producing wrong or missing results.
- The right question before connecting any app is whether it would change a specific email For each unconnected app, the test is: what does it know that Klaviyo does not, and which email or text would change if Klaviyo knew it too? If a specific email can be named, connect the app. If not, it can wait.
There’s a special kind of frustration in answering the same question twice. Worse if it’s three times. Any more than that, and the friendship starts to feel a little worse than just one-sided. You told your friend you went vegetarian back in March, and you’re pretty sure you mentioned the new job last month, yet here you both are at dinner while they ask if you want to split the ribs and how things are going at the old place.
It’s not that they don’t care (we hope). They heard you; it just never stuck. And now you’re the one doing the work of catching them up.
Shoppers go through the same thing with brands every day. Over the life of a single order, a customer tells you what they wanted, what they thought of it once it arrived, and what confused them enough to email your support team. Every app you use catches some piece of that conversation. Whether any of them hold onto it, or pass it along to the others, is a different story.
When they don’t, it shows. The customer who just left a glowing review gets the same 15 percent off as someone who’s never heard of you. Or worse, an email recommending the exact thing they bought last week. Once, that’s a mistake. Twice, that’s a pattern. And patterns add up: a scroll past your next email, a cold shoulder to your next offer, and eventually an unsubscribe from a customer who was ready to buy again.
When our CEO, Zak, hosted a panel with leaders from Klaviyo, Shopify, PostPilot and Clear.io on Episode 3 of the DTC Revenue Rocket Podcast. Sebastian Brown Glad, who heads up partnerships at Clear.io, didn’t mince words: “I’m always really surprised when I see a brand, and they have like this really luscious best-of-breed tech stack and like none of them are connected, and no one’s telling them to connect them or how to do that.”
In some cases, nobody ever connected the apps. In others, the problem is harder to spot. Your Shopify integrations are switched on, every dashboard says it’s syncing, and still nothing a customer sees has changed. That’s the friend who heard you and forgot.
So before you add another app to the mix, check how the ones you already pay for work together.
How to Tell If Your Shopify Integrations Are Working
Open any app’s integration settings, and you’ll usually see the word “connected” or a green checkmark. All that tells you is that two apps are allowed to share information. It doesn’t tell you whether your customers’ orders, reviews and support tickets are reaching Klaviyo, or whether they change which emails and texts each customer gets.
Follow one real customer through your apps. Pick someone who ordered last week, ideally someone who also left a review or contacted your support team. Open their profile in Klaviyo, the record Klaviyo keeps for each customer, and answer three questions in order.
Did their order, review and support ticket reach Klaviyo?
On the profile, you should see:
- “Placed Order” for the order itself, and “Ordered Product” for each item in it
- “Fulfilled Order,” once it shipped
- Whether they agreed to receive your emails and texts
- Any tags your team gave them in Shopify, like “VIP” or “wholesale”
- If you track browsing, the products they viewed and added to their cart before buying
Their review and their support ticket should be on the profile as well.
Did each one arrive correctly and trigger the right emails?
Check that the dates and products on the profile match the order in Shopify. Then check that the customer entered the flows meant for new orders. A flow is an automated series of emails or texts, like a post-purchase series or a review request.
Did any of it change what they received?
Look at the emails and texts they’ve gotten since the order. If they’re the same ones everyone else on your list got, nothing this customer bought, reviewed or asked about made a difference.
Your first “no” tells you which of the three problems below you have.
It Was Never Connected
If the order is on the profile but the review or the ticket isn’t, the reviews app or the help desk was never connected to Klaviyo. The review stays in the reviews app and the ticket stays in the help desk, so neither can change what that customer receives.
Apps get added one at a time, often by different people solving different problems, and an integration can sit available for years without anyone switching it on.
To find every gap, not just this one, open the Integrations page in Klaviyo and compare it with the apps installed on your Shopify store. List each app that collects something about your customers, like reviews, support conversations, quiz answers or loyalty points, and isn’t connected. Not all of them need to be. The next section covers how to decide which ones do.
It’s Connected but Set Up Wrong
If the order, review and ticket all reached Klaviyo but something is wrong or missing, the connection exists and isn’t set up correctly. A product might be missing from the order, a date might not match, their browsing history might be blank even though you track it, or the customer never entered a flow they should have. This is harder to spot than a missing connection, because most of the information still arrives and only some of it is wrong.
Klaviyo’s and REVIEWS.io’s own documentation describe four setups that cause exactly this:
- A new theme switches off browsing data. After a new theme goes live, the Klaviyo app embed, the setting in your Shopify theme that lets Klaviyo see what shoppers do on your site, has to be turned back on. Until it is, product views stop reaching Klaviyo, and browse abandonment emails stop going out.
- Two metrics share one name. Klaviyo can show two metrics called “Viewed Product,” one tracked by Klaviyo and one from Shopify. Klaviyo’s advice is to check which one a flow uses, because a flow built on the one you aren’t collecting won’t send.
- Partial refunds don’t sync. “Refunded Order” only records full refunds, so a follow-up for refunded customers misses everyone who got part of their money back.
- One review event only covers company reviews. In REVIEWS.io’s integration, “ReviewsIOReview” fires for reviews of your company, not your products. A flow meant for people who reviewed a product has to use “ReviewsIOProductReview.”
Shopify’s Dwayne Doshier was talking about AI tools on the panel, but his advice fits here just as well: “We’re not operating in a trust but verify type of situation. We’re operating in a check.”
If anything on your test customer’s profile was missing or wrong, check those four first. If your revenue reports in Klaviyo look off too, your attribution settings are the next place to look.
It Works, but the Data Isn’t Being Used
If your test customer passed the first two questions but failed the third, the integration works. The order, review and ticket all reached Klaviyo correctly, but none of your segments or flows use them. A segment is a group of customers that Klaviyo sorts by a rule you set, like “tagged wholesale” or “left a five-star review,” so you can send that group different emails.
Say your team tags every wholesale buyer as “wholesale” in Shopify. The tag reaches Klaviyo, but those buyers still get the same first-order discount as a brand-new shopper when they should be getting reorder reminders and wholesale pricing updates. The integration settings are fine. What’s missing is a decision: which emails should a wholesale buyer get that a new shopper doesn’t? Once you answer that, you can build a segment of everyone with the tag and a flow that sends to it.
Is it one forgotten tag, or does the same thing happen across your account? To find out, open your segments and flows in Klaviyo. Each one shows the conditions that decide which customers it includes. Look for any condition based on a Shopify tag, a product review or a support ticket topic. If you can’t find one, you’re paying for apps whose information doesn’t change a single email or text. Other parts of your account may be going unused too, and these six signs your Klaviyo account is underused show where to look.
Which Shopify Integrations Should You Prioritize?
Go back to the list of unconnected apps you wrote down. For each one, ask two questions. What does this app know about a customer that Klaviyo doesn’t? And which email or text would change if Klaviyo knew it too? If you can name the email, connect the app. If you can’t, it can wait.
For most stores, three connections pass that test before any others. They match the three parts of the conversation from earlier: the order, the review and the support ticket.
Shopify and Klaviyo
If your test customer’s order showed up in Klaviyo, this one is already connected. It still comes first, because every other connection depends on it: a review or a ticket tells you more when Klaviyo also knows what the customer bought. What matters here is how much of that data your emails use.
Klaviyo’s Shopify integration sends:
- Every order, with one entry for each product in it
- Fulfillments, cancellations and full refunds
- Shipping updates, including delivery, for certain carriers
- The products a customer viewed and added to their cart, if browsing data is turned on
- Whether the customer agreed to receive your emails and texts
- The tags your team gave the customer in Shopify
If you’re connecting Shopify for the first time, Klaviyo starts with your last 90 days of orders and then goes back as far as 10 years, so your past customers’ order history is there from the start.
A thank-you email after an order is the obvious use. The same data can do more. You can time a reorder reminder to how long a product usually lasts. You can keep customers out of a promotion for a product they just bought, so nobody gets an email recommending last week’s purchase. And if your carrier reports deliveries, you can send the review request once the package arrives instead of a fixed number of days after the order.
Your Reviews App and Klaviyo
A review tells you how a customer felt about a specific product, in their own words and with a star rating. Without the integration, your emails can’t tell a five-star review from a one-star one.
What comes through depends on the app. REVIEWS.io, for example, sends separate events for 4- and 5-star product reviews, 1- to 3-star product reviews, photo and video reviews, and survey answers. It also adds details the customer shares in a review, like their size or skin type, to their Klaviyo profile. Sebastian pointed to this on the panel: once reviews feed into Klaviyo, “you have so much profile data that you can then fill out.”
That’s what lets two customers who bought the same product get different emails. A five-star review can lead to a request for a photo or a referral, instead of the same 15 percent off everyone else gets. A one-star review can take that customer out of promotions for the product and send the review to your team for a personal reply. And a skin type, entered once on a review form, can shape every product recommendation that customer gets afterward.
If you use a different reviews app, look up which events its Klaviyo integration sends before you plan flows around them.
Your Help Desk and Klaviyo
A support ticket means a customer had a problem big enough to write in about. If Klaviyo doesn’t know that, the next email they get could be an upsell sent the same afternoon.
Many help desks have a Klaviyo integration that adds the ticket’s topic to the customer’s profile, like “sizing,” “damaged item” or “where’s my order.” With that on the profile, a customer who asked about sizing can get your fit guide before your next new-arrivals email. A customer who reported a damaged item can be left out of promotions for a set time while your team sorts it out. We go further into how support conversations can shape your emails in [our post on customer service data].
What gets sent depends on the help desk. Check its Klaviyo integration settings to see which ticket details reach the profile.
Apps Without a Klaviyo Integration
Sometimes the app holding the information you need doesn’t connect to Klaviyo at all, or its integration leaves out the detail you care about. A product quiz, for example, might tell Klaviyo that someone finished the quiz but not what they answered.
In that case, a developer can build the connection directly. Shopify and Klaviyo both have APIs, which let other software send information in and pull it out, so the app’s data can reach the customer’s profile automatically. That takes more work than switching on an integration, so save custom Shopify development for information that would change an email you’ve already named.
How ECD Helps Brands Get More From Their Shopify Integrations
Switching on a Shopify integration takes a few minutes. Deciding what its information should change takes longer, because the answer depends on your store: what you sell, how often people buy it and what your customers keep telling you.
So that’s where we start. We look at the emails and texts your customers get today and compare them with what your apps already know about those customers. Where the two don’t line up, we work out what to do first. Sometimes that’s connecting an app. Sometimes it’s fixing a setting that’s been sending the wrong data. And sometimes it’s building a segment or flow on information that’s been sitting in Klaviyo for months.
We know these platforms well. ECD is a Klaviyo Master Elite Partner, one of about 35 agencies worldwide out of more than 22,000 to hold that status, and Klaviyo named us its Agency Partner of the Year for the Americas in 2026. We’re also a Shopify Partner, and when an app needs a custom connection, our developers can build it.
If you want to find out what your apps already know about your customers and which emails should change because of it, let’s talk.
Get Your Free Revenue ForecastFrequently Asked Questions
How can an ecommerce brand tell if its Shopify integrations are actually working?
Follow one real customer — someone who ordered last week and ideally also left a review or contacted support — through their Klaviyo profile and answer three questions in order. First, did their order, review, and support ticket all reach Klaviyo? The profile should show a Placed Order event, an Ordered Product entry for each item, a Fulfilled Order once it shipped, their email and SMS consent status, any Shopify tags, their browsing history if tracked, and both the review and any support ticket. Second, did each item arrive correctly and trigger the right flows? Check that dates and products match Shopify and that the customer entered the automated sequences meant for new orders. Third, did any of it change what they received? If the emails and texts since the order are identical to what everyone else on the list got, the integration is not doing anything for that customer.
What are the most common reasons a Shopify integration appears connected but is not working correctly?
Four specific misconfigurations show up most often. A new Shopify theme can silently turn off the Klaviyo app embed — the setting that lets Klaviyo see what shoppers do on the site — which stops product views from reaching Klaviyo and prevents browse abandonment emails from sending until it is turned back on. Klaviyo can show two metrics both called “Viewed Product,” one tracked by Klaviyo and one from Shopify, and a flow built on the one not being collected will never send. Partial refunds do not sync to Klaviyo through the “Refunded Order” event, which only records full refunds, so a flow targeting refunded customers misses anyone who received partial money back. And in REVIEWS.io’s integration, the “ReviewsIOReview” event only fires for company reviews, not product reviews — a flow meant for product reviewers needs to use “ReviewsIOProductReview” instead.
What should a brand do when an integration works correctly but the data is not being used?
This is the third and often most overlooked problem: the order, review, and support ticket all reach Klaviyo correctly, but no segments or flows use them, so nothing changes for the customer. The fix is a decision, not a technical one — which emails should a customer who left a five-star review get that a first-time shopper does not? Which emails should a wholesale buyer tagged in Shopify receive instead of the standard new-customer discount? Once those questions are answered, the segments and flows can be built around the data that is already there. To find how widespread this is, open the segments and flows in Klaviyo and look for any conditions based on a Shopify tag, a product review, or a support ticket topic. If none exist, the apps are being paid for without any of their information changing a single email or text.
Which Shopify integrations should be prioritized first?
Three connections pass the prioritization test before any others for most stores. The Shopify–Klaviyo integration comes first because every other connection depends on it — a review or support ticket tells Klaviyo more when it also knows what the customer bought. The reviews app integration comes second: a review tells Klaviyo how a customer felt about a specific product, with a star rating, and without it every customer gets the same email regardless of whether they left a glowing review or a complaint. The help desk integration comes third: a support ticket means a customer had a problem big enough to write in about, and if Klaviyo does not know that, the next email could be an upsell sent the same afternoon. For each remaining unconnected app, the test is simple — what does it know about a customer that Klaviyo does not, and which specific email or text would change if Klaviyo knew it? If a specific email can be named, connect the app. If not, it can wait.
What happens when an app does not have a Klaviyo integration or its integration leaves out key details?
When the app holding the information needed does not connect to Klaviyo at all — or when its integration sends only partial data, such as confirming a quiz was completed without passing through what the customer answered — a developer can build the connection directly using the APIs that both Shopify and Klaviyo provide. This lets the app’s data reach the customer’s profile automatically without relying on a built-in integration. It takes more work than switching on a standard integration, so custom development is worth prioritizing only for information that would change a specific email or flow that has already been identified. The test is the same: name the email it would improve before deciding the custom work is worth doing.