Since 28 October, Shopify has been surfacing supported app events inside Analytics — meaning the moment your email platform fires a campaign, or your loyalty app processes a redemption, that activity can show up on the same timeline as your sessions and your sales. That is the short answer to shopify analytics app events: it's a reporting layer that puts app activity and store performance in one place, so you stop flipping between four dashboards that each claim credit for the same order. Timing is convenient. You get to test it on the one weekend of the year where it matters most.
We've spent enough Black Fridays reconciling attribution reports at 11pm to have a strong opinion about this. The feature is useful. It is also narrower than people expect, and it will not settle the attribution argument. What it does is give you a baseline you own.
How to see app activity in Shopify Analytics
Open Analytics in your admin and look at your live view and your overview charts. Where an installed app publishes events to Shopify, those events appear alongside the session and sales data rather than buried inside the app's own reporting. You can see when something happened and line it up against what the store did in the following minutes and hours.
Two practical notes before you go hunting. First, this is new and the set of apps that publish events is being added to, so what you see in your admin this week may not match what a colleague sees in theirs. Check your own store rather than trusting a blog post, including this one. Second, your ability to build and save a custom report is plan-gated. On the entry plan you get the stock reports. Report building in any serious sense sits further up the plan ladder, and if you're on Plus you already have it.
Which apps support Shopify app events
The honest answer: it depends on whether the app's developer has implemented it, and the list is moving. The categories where it makes obvious sense are the ones that do things on a schedule — email and SMS platforms, loyalty and rewards, subscriptions, review request senders, back-in-stock alerts. An app that just renders a widget has nothing meaningful to publish.
So the way to find out is to go through your installed app list, open Analytics, and see what appears. If a tool you rely on isn't there, ask their support when it's coming. For apps you've had built in-house, this is now a thing worth adding to the backlog — we've started raising it in scoping conversations for custom app work, because an app that can place its own activity on the merchant's timeline is far easier to defend at renewal time.
The double-count problem, with actual arithmetic
Here's why this matters more than it sounds. The numbers below are invented to show the method, but the shape is something we see on nearly every BFCM post-mortem.
A store does $412,000 from Thanksgiving Thursday through Cyber Monday. Then you open the dashboards:
- Email platform: $186,000 attributed
- SMS app: $74,000
- Loyalty app: $63,000 in orders involving a redemption
- Meta Ads Manager: $158,000 on a 7-day click, 1-day view window
That adds to $481,000. Against $412,000 of actual revenue, the apps have collectively claimed 117% of the business — and that's before you count a single direct, organic or TikTok-sourced order. Nobody is lying. A customer who saw a Meta ad on Wednesday, opened the Friday email, clicked the Saturday SMS and spent points at checkout gets booked at full order value in four different systems.
Shopify's own session-based attribution might put email at $71,000 for the same window. The gap between $71,000 and $186,000 isn't an error. It's two different definitions of "caused." Most email platforms default to a conversion window measured in days and will credit a view or an open, not only a click. Go and look at yours before BFCM, because the default is doing a lot of work in that number.
Shopify attribution vs email app attribution: which one do you believe?
Neither, as a revenue figure. Both, as a trend line.
Shopify's attribution is last-click and session-based. It undercounts email badly, because a customer who reads the campaign on an iPhone at lunch and buys on a laptop at 9pm with no UTM in sight shows up as direct. Your email platform's attribution is generous by design, because a multi-day window with open-tracking credit will sweep up purchases that were always going to happen.
Use Shopify's number as the floor and the app's number as the ceiling. The truth is somewhere in between and it is not worth a week of your life to locate precisely. What app events give you is a third reading that doesn't depend on either model: did sessions actually move when the send went out?
Compare app events to sessions and you get something close to incrementality
This is the use that justifies the feature. You're not asking which channel owns the order. You're asking whether the activity produced traffic that wouldn't otherwise exist.
Take a baseline hour on a normal Tuesday: 1,200 sessions, $3,100 in revenue. Now the Black Friday 9:05am ET send goes out. The 9–10am hour shows 4,100 sessions and $11,900. Incremental lift is 2,900 sessions and $8,800 against baseline. The email platform will report that campaign at $26,400 once its five-day window closes.
Three to one. That ratio is the single most useful number you'll take out of the weekend, and you can only calculate it if you know exactly when the send fired and what the hour before looked like. Which is what the event marker on the chart is for.
Do the same for every send. You'll find the pattern fast: the first BFCM email produces a genuine spike, the Saturday reminder produces a smaller one, and the Cyber Monday "last chance, ends midnight" send often produces the largest lift of the lot for the smallest list segment. The 11am Sunday filler campaign that the platform credits with $14,000 frequently moves sessions by almost nothing. Cut it next year.
Loyalty redemptions reporting in Shopify, without the loyalty app's framing
Loyalty dashboards are the worst offenders for self-congratulation, because they report revenue from orders that included a redemption and present it as revenue the programme created. A customer redeeming 500 points for $5 off a $140 order was buying that order regardless.
Redemption events on the Shopify timeline let you ask better questions. Does redemption volume spike when the sale starts, or the day after the sale ends? If it's the day after, your loyalty programme is being used by people who missed the discount and want a substitute — useful, but not a sales driver. Does AOV on redemption orders sit above or below the weekend average? We've seen stores where redemption orders ran 20% below site AOV across BFCM, which is the opposite of what the loyalty vendor's deck promised.
And check redemption concentration. If a small group of repeat buyers accounts for most redemptions during the peak, you're discounting your most loyal customers at the one moment they'd have paid full price. That's a margin decision, not a reporting one, but you need the data to make it.
Track marketing emails sent in Shopify reports: what to build before Thanksgiving
An hour of setup, done in the week before the peak, not during it.
- Install nothing new. Confirm which of your existing apps are publishing events and what they're labelled as in your admin.
- Record a clean baseline. Pull hourly sessions and revenue for two ordinary weekdays and one ordinary Saturday in early November, before any promo activity starts. Put it in a sheet. This is the denominator for every lift calculation you'll do later.
- Write down your send schedule with exact times in ET, including the automated flows that will fire on their own.
- Tighten the attribution window in your email platform to something defensible for the weekend — click-based, short. Yes, your reported email revenue will drop. That's the point.
- Keep UTMs consistent across email, SMS and any paid retargeting. If Shopify's last-click model is going to be your floor, don't make the floor worse than it needs to be.
Then on the Monday after Cyber Monday, you reconcile once: total store revenue at the top, lift-per-event underneath, and the app dashboards in a column you label "claimed" so nobody confuses it with cash.
What app events still won't tell you
They won't resolve cross-device journeys. They won't tell you whether the discount was necessary. They won't model view-through effect from the Meta spend that warmed the list in the first place, and with acquisition costs where they are in the US right now, that effect is real even though you can't see it here.
They also won't tell you what each app is costing you in page weight, which during a traffic peak is the other half of the story — a loyalty widget and three tracking scripts can add 400ms to LCP on a mobile collection page, and that shows up as a conversion-rate dip you'll blame on the wrong thing. If you haven't audited script load before BFCM, do that too; our speed work starts with exactly that inventory, and SwiftStore will scan and monitor the score if you'd rather handle it yourself.
Questions we get asked
Can I see Klaviyo data in Shopify Analytics?
You'll see Klaviyo-sourced sessions and orders under Shopify's own marketing attribution already, provided your links carry UTMs. Whether campaign send events appear on your Analytics timeline depends on what that app publishes to Shopify and whether it's live in your admin yet — check your store rather than assuming. What you will not get is Klaviyo's attributed revenue figure inside Shopify, and you shouldn't want it there. Two attribution models in one report is how reconciliation meetings go badly.
Does this replace my email platform's reporting?
No. You still need open rates, click rates, deliverability and segment performance, and none of that lives in Shopify. Use the app for list health and creative performance. Use Shopify for whether the store moved.
We're on Shopify Plus with a headless front end. Does any of this work?
Session data depends on your analytics implementation on the custom front end, so the lift calculation is only as good as your tracking. Events from server-side apps still fire. If your headless build is sending partial session data to Shopify, fix that first or the baseline is fiction.
Is it worth changing anything mid-BFCM based on this?
Send times, yes — if the Friday 9am send underperformed baseline by a wide margin, move Saturday's to a different hour. Discount depth, no. Changing the offer mid-weekend confuses customers and poisons the data you're trying to collect.
Where to start
Pull your hourly baseline this week. It takes twenty minutes and it's the piece people skip, which is why every January someone sits down with four dashboards that sum to more than the bank balance.
If you want a second pair of eyes on the reporting setup before the peak — or on the app stack that's generating all these events — we run a free store audit, and our US team works in your timezone through the season.