Shopify Analytics with New vs Returning Customer Split: A Practical Guide
by Trivas.ai
|
6 min read
Sep 08, 2026
Two stores can post the same $500K month and be running completely different businesses. One got there by pouring money into cold traffic and converting new shoppers. The other got there because its existing customers keep coming back. Blended revenue numbers don't tell you which one you're running, and that's a problem if you're making decisions based on the top-line figure alone. This is where Shopify analytics with new vs returning customer split actually earns its keep, and where most dashboards quietly fail you.
Why New vs Returning Customer Data Changes How You Run the Store
A blended revenue number hides the thing you actually need to know: is growth coming from acquisition or retention? Get that wrong and you'll misread everything downstream, from ad budgets to inventory buys.
Picture two stores, both doing $400K last month. Store A gets 70% of revenue from new customers. Store B gets 70% from returning ones. Store A needs to worry about CAC creeping up and whether its funnel can keep feeding new traffic. Store B has a retention engine working, but it should be nervous if new customer acquisition has basically stalled. Same revenue number, opposite risk profiles, opposite next moves.
Most Shopify dashboards treat this split as a nice-to-have chart buried three tabs deep. It should be a first-class metric, sitting next to revenue and ROAS, not an afterthought you dig for once a quarter.
What Shopify's Native Analytics Actually Show (and Where It Stops)
Shopify's built-in reports give you a starting point. "Customers over time" and "Returning customer rate" will tell you basic counts: how many first-time buyers you had, how many repeat purchases happened in a window. That's useful, but it's shallow.
There's no cohort-level LTV in there. No way to see if your returning customers from a specific acquisition channel are worth more than others. No overlay that connects a customer's origin campaign to their long-term value. You get counts, not context.
There's also a lag. Shopify's native analytics update on a delay, and you can't cross-filter returning customer rate by channel or campaign without exporting data and rebuilding the view yourself. Merchants doing 7 or 8 figures usually hit this wall fast. They start pulling CSVs into spreadsheets to bridge the gap, and that works fine until order volume passes a few thousand a month. After that, manual joins between orders, customers, and campaigns become a part-time job nobody signed up for.
How Trivas Builds the New vs Returning Split
Trivas pipes Shopify order and customer data straight into Amazon Redshift, and that's where the actual segmentation logic runs. Every order gets tagged as new or returning based on first-purchase date logic, not a Shopify tag field that can be stale or missing entirely.
That distinction matters more than it sounds. Guest checkouts, merged customer profiles, multi-store setups: all of these break simple tagging approaches. A customer who checked out as a guest in January and created an account in March shouldn't show up as "new" twice. Trivas resolves identity at the data layer so the split holds up even when Shopify's own customer records get messy.
The segmentation refreshes on the same schedule as the rest of your dashboard. You're not running a separate export or a special report to see it. If you're already looking at revenue, ROAS, or margin inside Trivas, the new vs returning breakdown is sitting right there next to it. For merchants running Shopify alongside other channels, this connects to the broader Shopify solution rather than living as a standalone report.
Metrics You Can Actually Slice by Segment
The split is only useful if it touches the metrics you actually make decisions on. Trivas breaks out AOV, LTV, repeat purchase rate, CAC, gross margin per order, and discount usage rate by new vs returning customer, not just by total store performance.
CAC is the one that changes the conversation fastest. Most dashboards calculate payback period against blended revenue, which flatters your numbers because returning customer revenue costs you nothing to acquire that month. Compare CAC against new-customer revenue only, and you get a payback period that reflects what your acquisition spend is actually earning back.
Here's a concrete example. Say a store's blended AOV sits at $45 and hasn't moved in two months. Looks flat, looks fine. But split it and you find new customers are averaging $38 while returning customers are at $62. A "flat" month might actually mean new customer AOV dropped while returning customer AOV rose enough to mask it. Two very different stories, one number.
Turning the Split into Decisions: Ad Spend, Email, and Retention
Once you can see the split cleanly, it starts driving real budget calls. If new-customer CAC is climbing while returning-customer revenue share is growing, that's a signal to shift dollars out of cold acquisition and into retention and email. You're already earning more from the customers you have. Chasing more expensive new ones at the same rate doesn't make sense.
The split also works as an early warning system. If returning customer share drops month over month, that's a churn signal, and it usually shows up here before it shows up in a lagging LTV report. Catch it early enough and you can trigger win-back flows before the cohort is actually gone.
This is also the argument marketing leads bring into budget conversations with finance. Blended ROAS is a weak defense for a budget increase because it doesn't separate what's working from what's masking a problem. Segment-level payback periods, new customer CAC against new customer revenue, are a much harder number to argue with.
Setting This Up on Your Shopify Store
Setup starts with connecting your Shopify store. From there, historical order data syncs into Redshift, and the new/returning tagging applies retroactively across your past orders, not just from the connection date forward. You're not starting with a blank slate.
Most merchants see their first dashboard view within the standard Trivas onboarding window, no custom scripting and no Liquid changes required on the storefront side. If you'd rather start from inside Shopify itself, you can install Trivas AI on the Shopify App Store and connect from there. For a deeper look at what the integration covers beyond this specific split, the Shopify integration guide walks through the rest of the data pipeline, and the broader BI reporting product page covers how this segmentation sits alongside your other dashboards.
See the Split on Your Own Store Data
The real test isn't a demo dataset, it's your own orders. Connect your store and look at your actual new vs returning breakdown, not a sanitized example built to look clean.
This split lives inside the same dashboard as your ad spend, GA4 funnels, and revenue data, so it's not one more tool you have to log into separately and reconcile by hand.
If you want to see where your store actually falls before booking a call with anyone, start a trial and pull up your own numbers first.
Content author and contributor at Trivas.ai, sharing insights on e-commerce analytics, business intelligence, and data-driven strategies to help businesses grow.
Continue Reading
explore more insights
Ecommerce Analytics for a 2-Person Team: What to Track Without Hiring an Analyst
3 min read
Best Triple Whale Alternative That Sends Slack Alerts (2024)
3 min read
AI Agents for Ecommerce Explained: What They Are and How They Actually Work
.d53b12e5.png&w=3840&q=75 "Trivas.ai")
by Trivas.ai
