A direct-to-consumer e-commerce brand typically runs on seven or more disconnected tools: Shopify for orders, ReCharge for subscriptions, Klaviyo for email, Google Ads and Search Console for acquisition, Judge.me for reviews, and Zendesk for support. The problem is not any single tool. The problem is that the decisions that matter most, like true customer acquisition cost by channel or subscriber churn risk, live in the joins between those tools, so they never get made.
Quick Summary (TL;DR)
- Most DTC brands check performance by opening a dozen tabs and logging into separate platforms, which means no one ever sees the full picture in one place.
- The highest-value e-commerce metrics are cross-source: they require joining ad spend against actual Shopify customers, or ReCharge subscription data against Shopify order history.
- Single-source tools like Shopify Analytics or Klaviyo reports cannot calculate true lifetime value versus customer acquisition cost per channel, because they only see their own data.
- Generic BI tools can join sources but usually require an ETL pipeline and a data engineer to model the data first.
- A real Knowi dashboard tour shows one direct-to-consumer company running four snack brands unify all seven sources into a single view.
- The unlock is not prettier charts. It is answering questions like “which campaigns actually acquire profitable customers” that were previously impossible to answer with any one tool.
Table of Contents
Why the E-Commerce Stack Fragments in the First Place
Every tool a DTC brand adds solves one job well. Shopify runs the store, ReCharge runs subscriptions, Klaviyo runs lifecycle email, and Zendesk runs support. Each is best-in-class in isolation.
The cost shows up at the seams. Revenue lives in Shopify, but subscription retention lives in ReCharge, and the ad spend that drove those customers lives in Google Ads. No single platform can see across all three, so the operator becomes the integration layer, exporting CSVs and reconciling numbers by hand.
This is the same pattern we see in other multi-tool workflows, like the way engineering teams stitch ClickHouse and Jira into one DevOps view. The e-commerce version just has more sources and higher stakes, because the gaps hide money.
The Metrics That Only Exist in the Joins
Here is the core argument: the most valuable e-commerce metrics do not belong to any one tool. They only exist when two or more sources are joined.
True LTV versus CAC by store
Lifetime value versus customer acquisition cost per store is effectively impossible to generate with a single tool. It requires joining ad spend from Google Ads against real Shopify customers to get a true acquisition cost per channel, then measuring what those customers actually spent over time. Shopify does not know your ad spend, and Google Ads does not know which clicks became repeat buyers.
Subscriber cohort churn signal
A subscriber cohort order-activity view shows how many subscribers place orders in their first subscription month, and then every month after. That is a strong early churn indicator: if you have many subscribers but their order frequency is falling, they are likely to cancel soon. That signal only appears when ReCharge subscription data is joined against Shopify order history, which is why most brands never see it until the cancellations land.
Want to see how AI agents work with your data? Request a demo at knowi.com.
What One Unified Dashboard Actually Looks Like
In a recent Knowi product tour, one dashboard covered a DTC company running four snack brands, with every widget pulling from where the data actually lives. It was organized into four sections that map to how the business actually runs.
The orders section pulls from Shopify: key metrics up top, weekly revenue split by subscription versus retail, average order value by store, and top-selling products color-coded by brand. Dashboard-level filters let you narrow the entire view to one snack brand or to subscription-only sales in a single click.
The subscription section joins ReCharge and Shopify for active subscriptions, cohort lifetime value, and the churn signal described above. The marketing section brings in Google Ads, Search Console, and Klaviyo to compare spend against new customers acquired, cost per conversion by campaign, and organic versus paid clicks. The final section joins Judge.me and Zendesk for review distribution, a low-rating word cloud, ticket volume, and average reply time.
Threaded through the dashboard are AI recommendation widgets, each pointed at a specific data context: one analyzing Shopify order history for revenue ideas, another on ReCharge and Shopify together for retention, and another on ad data for ways to reduce spend.
Watch a video walkthorugh
How Teams Typically Build This, Compared
There are a few common ways DTC brands try to get a unified view. Here is how they compare on the thing that matters, joining across sources without a data team.
| Approach | Multi-source joins | Setup effort | Cross-source metrics (LTV:CAC, cohort churn) |
|---|---|---|---|
| Manual CSV exports and spreadsheets | Possible but manual and error-prone | Low to start, high ongoing time cost | Rebuilt by hand every reporting cycle |
| Single-source tools (Shopify Analytics, Klaviyo reports) | No, each sees only its own data | None | Cannot be calculated |
| Generic BI (needs ETL pipeline) | Yes, after modeling | High: requires ETL and a data engineer | Available once the pipeline is built and maintained |
| Knowi | Yes, queries and joins sources directly | Connect sources, no ETL pipeline required | Built as native widgets on joined data |
The honest trade-off: a generic BI tool with a full data team behind it can model anything, and for a large org with existing pipelines that may already be the right home. Where Knowi fits best is the brand that has the seven tools but not the data engineer, and needs the cross-source metrics without standing up an ETL stack first. Much of this comes down to connecting sources directly, including the ones that are just REST APIs like ReCharge, Klaviyo, and Judge.me.
Want to see how AI agents work with your data? Request a demo at knowi.com.
Frequently Asked Questions
How do I combine Shopify, ReCharge, and Klaviyo data in one dashboard?
You need a tool that can connect to all three sources and join their data, rather than one that reports on a single source. Shopify holds orders, ReCharge holds subscriptions, and Klaviyo holds email engagement, so a unified view requires querying and joining across them. Platforms like Knowi connect to each source and build widgets on the joined data without a separate ETL pipeline.
Why can’t I calculate true LTV to CAC in Shopify alone?
Shopify knows what customers spent but not what you spent to acquire them. True customer acquisition cost requires ad spend data from Google Ads or other channels, joined against the Shopify customers those ads actually produced. Without that join, any LTV to CAC number is missing half its inputs.
What data sources does a typical DTC e-commerce dashboard need?
A common DTC stack includes Shopify for orders, ReCharge for subscriptions, Klaviyo for email, Google Ads and Google Search Console for acquisition, Judge.me for reviews, and Zendesk for support. That is seven sources for one business. The value of a dashboard comes from unifying them rather than checking each separately.
Do I need a data engineer to build a cross-source e-commerce dashboard?
Not necessarily. Generic BI tools usually require an ETL pipeline and someone to model the data first. Tools that query sources directly, including REST APIs, let a non-engineer connect the sources and build joined views without standing up a pipeline.
How does subscription cohort analysis predict churn?
Cohort order-activity analysis tracks how often subscribers place orders in their first month and every month after. A declining order frequency across a cohort is an early signal that those subscribers are likely to cancel. This requires joining subscription data from ReCharge with order history from Shopify.
Can AI help surface insights from an e-commerce dashboard?
Yes. AI recommendation agents can analyze a specific data context, such as Shopify order history or joined ad-spend data, and surface actions like where to reduce spend or how to lift retention. You can compare approaches in this overview of agentic BI tools.