Klaviyo Browse Abandonment on Shopify: 6 Checks Before BFCM
A browse abandonment flow that receives no events sends no emails, however good the messages are. Before Black Friday (Friday, November 27, 2026) and Cyber Monday (Monday, November 30, 2026), the first task is to check that Klaviyo actually sees the product pages viewed on your Shopify store. Here are six checks in the order we would run them, with what the Klaviyo documentation says and what is our own reading.
TL;DR. The browse abandonment flow is triggered by the Viewed Product metric. On Shopify, this tracking goes through the Klaviyo app embed, turned on in the theme, with the Add Viewed Product tracking to my site box checked in the integration. Klaviyo may not track visitors in the EU, EEA, UK and Switzerland without their consent, and only tracks browsers it has identified. In our view, these checks come before any copy tweak.
Want an outside view before you build? We offer a Q4 readiness audit: 30 minutes, free, no strings attached.
This article complements our Klaviyo BFCM guide. For building the flow, our article on Klaviyo browse abandonment details the structure; here, we check what already exists.
Why start with tracking
According to the Klaviyo page on creating a browse abandonment flow, this flow is triggered by the Viewed Product metric and therefore requires Viewed Product tracking to be enabled on the site (Klaviyo, how to create a browse abandonment flow). For Shopify, the page states that this tracking is enabled by Klaviyo's app embed.
In our view, a flow in Live status with polished emails but no incoming events is a case to rule out first: it produces no visible error, the flow simply stays empty.
Check 1: the app embed and the Viewed Product box
The page on onsite tracking for Shopify describes the path (Klaviyo, how to enable onsite tracking for Shopify). In Klaviyo, Integrations tab, then Shopify, Onsite Tracking section:
- Check Track behavioral events if you also want to track Viewed Collection, Submitted Search and Added to Cart. Viewed Product is enabled by default: it starts tracking once the app embed is enabled, along with Active on Site.
- If the app embed is turned off, click Turn on: Klaviyo opens Shopify, on the App embeds tab of the theme settings. Make sure the Klaviyo app embed is toggled on, then click Save.
- Back in Klaviyo, refresh the page: a green banner indicates that the app embed is enabled.
- Make sure Add Viewed Product tracking to my site is checked. If you change it, click Update Settings and complete the confirmation prompts.
Two points from the page matter before a busy season. A Klaviyo account's app embed can only be associated with 1 Shopify store. And if you have added a brand new theme, you need to re-enable the app embed.
In our view, the second point is the most useful in November: a store that changes theme for the season is exactly in that case. Checking a freshly published theme should be part of the go-live routine.
Check 2: test with your own address
The same page gives the test procedure for Active on Site and Viewed Product, which are tracked via the app embed. Klaviyo recommends waiting 15 minutes after enabling. Then:
- Add
?utm_email=followed by your email address to the URL of your store's homepage. - Reload the page, then open a product page.
- In Klaviyo, search for your email address: a profile is created if one did not exist, and the Active on Site and Viewed Product events appear in the activity feed.
If the store requires consent before onsite tracking, the troubleshooting page asks you to accept tracking cookies during the test (Klaviyo, troubleshooting viewed product tracking). To see all Viewed Product events over time: Analytics > Metrics, the Viewed Product metric, then Activity feed.
Check 3: consent from European visitors
The Shopify, troubleshooting, getting started and flow creation pages repeat the same warning: based on your Customer Privacy settings in Shopify, Klaviyo may not track onsite events for visitors to your Shopify store in the EU, EEA, UK and Switzerland, unless they have provided consent. The flow creation page draws the consequence: the browse abandonment flow will not include non-consented individuals.
In our view, a flow that looks under-fed can therefore come down to this rule, with no Klaviyo setting at fault. Compare what you see with the consent your store requires before concluding there is a breakdown. We have not reread the Shopify-side configuration here.
Check 4: who Klaviyo recognizes
The getting started page on onsite tracking states that Klaviyo associates onsite activity with a profile once it identifies the visitor's browser, for example through a Klaviyo email or SMS link, or through a Klaviyo form that submits identifying information (Klaviyo, getting started with Klaviyo onsite tracking). A visit alone does not make a browser known, and until you have sent messages and grown your lists, you will probably see little tracked onsite activity. If anonymous visitor tracking is enabled, Klaviyo can store events in the browser before identification, then add them to the profile.
In our view, this sets expectations: a large share of the traffic acquired during BFCM will be visitors Klaviyo does not know yet, and the flow will not see them. Browse abandonment works on the already identified base. Measuring it against total traffic would amount to blaming it for not seeing what it cannot see.
The pages differ on this point: Shopify and the Browse Abandonment Flow cites only two ways of identifying a visitor (a click from a Klaviyo email, a sign-up through a Klaviyo form). We rely on the getting started page, which is more detailed and was updated on October 22, 2026.
Check 5: the flow filters
For a flow you build yourself, the creation page gives the following profile filters:
- Placed Order zero times since starting this flow.
- Started Checkout zero times since starting this flow.
- Hasn't been in this flow in the last 30 days.
- Added to Cart zero times since starting this flow, only if you also have a flow triggered by Added to Cart: without it, a customer can receive emails from both flows.
It adds a time delay of at least one hour before the first message, and also calls leaving Smart Sending on a good idea. Klaviyo presents this flow as a lighter touchpoint than the abandoned cart.
Two pages seem to contradict each other. The one on list- and segment-triggered flows states that Re-entry criteria become the single source of truth for flow entry behavior, that you no longer need "has not been in flow" filters, and that the setting will be available for everyone "soon" (Klaviyo, how to create a segment- or list-triggered flow). It gives Allow re-entry as the default for metric-triggered flows, and converts a "has not been in flow in X days" filter into Allow re-entry after a time period. The flow creation page, updated on October 7, 2026, still lists the 30-day filter.
In our view, look at what your flow's trigger displays: if the Re-entry criteria are there, check that they express the frequency you want, rather than stacking both logics without comparing them.
Check 6: the Static block and the variables
To show the product viewed, the creation page asks for a Static block, not Dynamic as for the abandoned cart. It advises against copying the default abandoned cart message; if that is already done, copy the tags before changing the block type, because the change erases them. The image takes event.ImageURL, the text {{ event.Name }} and {{ event.Price }}, and the link {{ event.URL }}. Preview & test should display the product data.
If a customer views several products, the product shown depends on the filter: the first viewed with "hasn't been in this flow in the last X days", the most recent with "has viewed product zero times since starting this flow". Klaviyo recommends starting from a pre-built flow so that the dynamic variables work. For Shopify, the page also mentions an abandoned collection flow and an abandoned search flow. In our view, they rely on Viewed Collection and Submitted Search, and therefore on the Track behavioral events box from check 1; the page does not word it that way.
A trap: the product.liquid page
The page Shopify and the Browse Abandonment Flow is dated July 23, 2026 in the help center, but describes a different installation: pasting a code snippet at the bottom of the product.liquid template (Klaviyo, Shopify and the browse abandonment flow). The two more recent pages we read describe the app embed.
We found no page that says whether the manual code and the app embed can coexist. In our view, follow the app embed route and do not paste the old snippet without confirmation from Klaviyo support. This point remains a doubt on our side.
When it fails: the troubleshooting order
The troubleshooting page asks its questions in this order: is Active on Site enabled, did the platform change, was the theme updated (if so, check that the app embed is active on the current theme), does the store require consent from visitors in the EU, EEA, UK and Switzerland. If the problem persists after a new test, it points to Klaviyo support or the Community.
Trade-offs in our view for BFCM week
These points are Deliver readings, not Klaviyo rules.
- Check tracking before touching the copy: a perfect message on an empty flow produces nothing.
- If you swap the theme, add the check 2 test to the go-live list.
- Align the flow's offer with the campaigns' offer. Klaviyo says a discount code can help turn a casual browser into a customer, and that you may not want a discount for a customer who has already bought: in our view, the two audiences should not receive the same offer.
- Before changing filters or re-entry in the middle of a campaign, test the message with Preview & test.
For the last days before the event, see our last-minute Klaviyo flows before Black Friday.
FAQ
Which metric triggers the browse abandonment flow?
Viewed Product. The flow requires Viewed Product tracking to be enabled on the site.
Why does my flow receive almost no one despite high traffic?
Klaviyo only tracks identified browsers, and may not track visitors in the EU, EEA, UK and Switzerland without consent.
Do I need to re-enable anything after a theme change?
Yes: after a brand new theme is added to the Shopify store, Klaviyo says to re-enable the app embed.
How long should I wait before testing the tracking?
Klaviyo recommends waiting 15 minutes after enabling.
A question about your flows before BFCM? You can talk directly with the Deliver team.
Provenance and verification
Faithful English translation of the French source. On November 14, 2026, the six Klaviyo pages listed in sources were opened through the help center article body, converted to plain text and read in full, then compared with the article page by page: creating a browse abandonment flow (updated October 7, 2026), enabling onsite tracking for Shopify (October 22, 2026), troubleshooting Viewed Product tracking (October 22, 2026), getting started with onsite tracking (October 22, 2026), list- and segment-triggered flows and re-entry criteria (October 8, 2026), the page Shopify and the Browse Abandonment Flow (July 23, 2026). Interface labels, scope (Shopify, consent in the EU, EEA, UK and Switzerland) and the verbs of the pages are kept as written. Differences between pages are flagged in the text. The trade-off readings are Deliver readings, flagged with In our view, with no prices, figures or real account examples.
- Sources checked on
- Reviewed by
- Claude (Claude Code session, November 14, 2026) English localization of the French source, with every vendor-documentation claim checked against the Klaviyo help pages listed in sources, reopened in raw form the same day.
- AI assistance
- Yes
- Sources
Want to apply this to your stack?
Spend 30 minutes with Charlotte to review your CRM setup, size the opportunity and leave with a practical action plan.
Book a 30-minute call →