Marketing Data Analytics for DTC: One Source of Truth or Twelve Opinions
Meta, Google Ads and Klaviyo can each claim the same order in full, so their totals can add up to more than the store sold. The fix is a written rule for which source answers which question, plus one view that shows the gap.

A DTC brand gets one source of truth for marketing data by deciding, in writing, which system is canonical for each question: the store for revenue, the ad platforms for spend, the ratio of the two for efficiency, and platform-attributed results only as labeled claims. Then it builds one weekly view that shows store revenue, spend, and the gap between what the platforms claim and what the store actually sold. Below: why the tools disagree (with numbers from one real account), the hierarchy, a worked reconciliation, the four metrics the view needs, and the rules that turn it into decisions. This is the setup our custom reporting work is built around.
Key takeaways
- Platforms disagree by design: each counts a different event, over a different window, with a different view of who the customer is. In one DTC account in Level, Meta's ROAS for the same quarter ranged from 0.52× to 2.53× depending on the attribution setting alone.
- A single source of truth is a ranking of sources, not a bigger dashboard: money from the store, spend from the platforms, efficiency from the ratio, platform ROAS as a claim.
- Track the claim-versus-actual gap as a metric. In the worked example below, platforms claim 127% of the revenue the store recorded.
- The view needs four numbers: blended efficiency (MER) against its break-even line, new-customer CAC, per-channel spend versus claimed return, and the claim gap.
- Buy attribution help for tracking plumbing and interpretation. No attribution model is "the truth"; incrementality is measured with tests.
Why your marketing tools never report the same number
Each tool answers a different question. An ad platform counts conversions it can attribute to its own ads within its own window. GA4 counts what its tag could observe. Klaviyo credits orders that follow a message within its window. Shopify counts orders, the only number tied to money actually moving, and has no opinion about which ad earned them. Here are the default rules (checked Oct 2026):
| Source | What it counts | Default rule |
|---|---|---|
| Meta Ads | Purchases attributed to Meta ads | 7-day click, 1-day engaged view and 1-day view; Jon Loomer's 2026 guide documents the current settings |
| Google Ads | Conversions after an ad click | 30-day click-through window unless you change it (Google Ads Help) |
| GA4 | Sessions and events its tag observed | Data is missing for visitors who decline consent; behavioral modeling estimates part of it (Analytics Help) |
| Klaviyo | Orders after an email or SMS | Last touch; 5 days after an email click or open for new accounts (Klaviyo Help) |
| Shopify | Orders, refunds, revenue | No attribution, just the ledger |
Two things follow. First, overlap is guaranteed: a customer who clicks a Meta ad, later clicks a branded search ad, and buys from an email the next day sits inside all three windows, so all three can claim the full order. Second, no settings work makes the numbers match, because the difference lives in the measurement rules. The useful question is "what is each tool measuring, and where is the money number?" The incentive side, why reports flatter by default, is covered in why most agency reports lie.
What that looks like in one real account
We pulled numbers for one anonymized DTC brand whose Meta Ads and Google Ads accounts are connected to Level. Same brand, same quarter (Q3 2026), Meta only, four attribution settings:
| Meta attribution setting | Platform-reported ROAS |
|---|---|
| Account's default setting | 2.53× |
| 1-day view only | 0.88× |
| 28-day click only | 0.59× |
| 7-day click only | 0.52× |
Same spend, same purchases. On click-only settings the account does not return its ad spend; on the default it returns 2.5×. Neither is "the real ROAS"; they answer different questions. Our ROAS formula guide walks through this table in detail.
The two platforms also disagree with each other, every quarter:

Google's own ROAS claim ran 1.45× to 2.40× Meta's in every quarter. Source: Level, anonymized DTC brand, Meta Ads (default attribution) and Google Ads (Shopping App purchase action), Q1 2025 – Q3 2026.
Part of that gap is real: Shopping ads catch shoppers who are already searching for the product, while Meta mostly reaches people who weren't. Part of it is measurement: a 30-day click window versus Meta's 7-day click and 1-day view, and orders both platforms claim. From platform data alone you can't tell those two parts apart, and that is the argument for ranking sources instead of picking a favorite platform.
The same account showed two more ways claims go wrong. Meta returns one website purchase under five event names (purchase, omni_purchase, offsite_conversion.fb_pixel_purchase, onsite_web_purchase, onsite_web_app_purchase) with identical values; summing them by name gave 12.63× for a quarter whose real figure was 2.53×. On Google, an old and a new purchase action ran side by side for about two weeks during a tracking migration, so those two weeks counted orders twice.
The canonical hierarchy: which number answers which question
A single source of truth comes from ranking sources, not from displaying them side by side. Piping five disagreeing tools into one BI screen just moves the argument onto one screen. Write the hierarchy down once:
| Question | Canonical source | Why |
|---|---|---|
| How much did we sell? | Store backend (Shopify): revenue, orders, refunds | The only source tied to money that moved |
| How much did we spend? | Ad platforms' billed spend | It's an invoice; platforms report it accurately |
| Is marketing efficient overall? | Store revenue ÷ total marketing spend (MER) | Built from two numbers no platform can inflate |
| What should we change inside Meta or Google? | Platform metrics (ROAS, CPA, CTR), labeled as claims | Useful for within-platform optimization, never read as profit |
This doesn't settle the disagreements; it ranks them. The gap between platform-claimed revenue and store revenue stops being something to smooth over and becomes a metric you monitor. Level dashboards cover the paid-media rows of this table (spend and platform-reported results across ad accounts); store revenue and margin come from your store and finance data.
A worked reconciliation
Illustrative numbers for one month at a DTC brand (not client data). Replace them with yours; the arithmetic is the point.
| Line | Value | How it's computed |
|---|---|---|
| Store net revenue (Shopify, after refunds) | $100,000 | Canonical |
| Meta spend / Google Ads spend | $18,000 / $10,000 | Billed spend |
| Total marketing spend | $28,000 | Sum |
| Meta-claimed revenue | $52,000 (2.89× ROAS) | Platform claim |
| Google-claimed revenue | $41,000 (4.10× ROAS) | Platform claim |
| Klaviyo-attributed revenue | $34,000 | Platform claim |
| Sum of claims | $127,000 | 127% of store revenue |
| Claim-to-actual ratio | 1.27 | $127,000 ÷ $100,000 |
| MER (blended efficiency) | 3.57× | $100,000 ÷ $28,000 |
| Break-even MER at 40% contribution margin | 2.50× | 1 ÷ 0.40 |
| New customers / new-customer CAC | 650 / $43 | $28,000 ÷ 650 |
What the table says: the platforms together claim $27,000 of revenue that didn't happen in the store, so their numbers can't be added up. Blended efficiency of 3.57× sits above the 2.50× break-even line, so this month's spend paid for itself before fixed costs (store revenue includes repeat and organic orders, which is why MER is a health check, not a channel verdict). A claim-to-actual ratio of 1.27 means nothing on its own; it matters when it moves, because a jump usually means tracking changed, not buyers.
What the single view must carry
Marketing analytics for DTC has to answer one question fast: is acquisition spend coming back with margin attached? Four numbers do that; everything else is an appendix.
- Blended efficiency (MER) with its break-even line. Total revenue over total marketing spend, from the canonical sources, with its break-even threshold drawn on the same chart. At a given contribution margin there is an efficiency below which marketing spend exceeds the contribution it brings in. ROAS vs ROI vs MER covers when to use which ratio.
- New-customer CAC. Acquisition spend divided by new customers, not blended across the repeat base, which flatters it. CAC rising while spend and creative hold steady is an early sign the channel is saturating.
- Per-channel spend versus claimed return. Each channel's spend next to its self-reported return, labeled as attributed. Watch the movement, not the level: a channel whose claimed return falls against its own history is showing decline even in its own flattering numbers.
- The claim-versus-actual gap. Sum of platform-attributed revenue over store revenue, tracked weekly with the attribution settings written next to it. A stable ratio is normal; a jump means tracking broke or buying behavior shifted.
Impressions, follower counts, raw sessions, open rates: none of them changes a spend decision this week, and the single view is a decision instrument.
For the revenue-side layer underneath (cohorts, repeat rate, margin structure), see our piece on ecommerce analytics; the cohort trap gets its own look in the LTV-by-cohort reality check. If you're choosing a tool rather than designing the view, our guide to ecommerce analytics software compares the options.
Where marketing attribution services fit (and where they don't)
Marketing attribution services earn their fee in two places: building the measurement plumbing correctly and interpreting the output honestly. They don't earn it by selling a "true" attribution model, because every model, from last-click to algorithmic multi-touch, is a set of assumptions about credit, and changing the assumptions changes the answer. Our attribution modeling deep dive covers what each model can and cannot tell you.
The plumbing is unglamorous and decides everything downstream: server-side events (Meta CAPI set up properly alongside the pixel; the Meta CAPI for Shopify guide covers the failure modes), a GA4 property that's configured rather than left on defaults (the GA4 audit checklist is the one we run), consistent UTMs so channels don't leak into (direct), and one purchase event per platform. The five-event-names error above is a plumbing error, not a model error; in Level, conversion mapping is where you pick the one conversion event that counts as revenue.
Interpretation is where a provider changes decisions: labeling every attributed number as a claim, watching deltas rather than absolutes, and, when the budget question is big enough, recommending a holdout or geo test instead of another model debate, because incrementality is measured, not modeled. A good provider also says "this can't be known from this data" when that's the honest answer. Email and SMS attribution belongs in the same conversation; in the Marketing Bar family that side is Synergy.
Turning the single view into decisions
A data-driven marketing decision happens when a number crosses a threshold and triggers an action agreed in advance, not when a team looks at a dashboard and votes. Write the rules before the numbers come in:
- A weekly cadence. One fixed session where the view is read and the rules are applied. Daily numbers are too noisy for budget moves; monthly is too slow to stop a loss. A scheduled report can deliver the view before the session.
- A pre-agreed response to the gap metric. If the claim-to-actual ratio jumps outside its usual range, audit tracking that week, before any budget decision uses the corrupted numbers.
The rules only work if the reconciled number outranks the most persuasive person in the meeting. A single view makes that enforceable, because there's no second version of the numbers to appeal to.
The reconciled number outranks the persuasive narrative — there's no second version of reality to appeal to.
Level: a DTC ad analytics platform for the paid-media view
Level is our reporting product, and it covers the paid-media slice of this problem: it connects Meta Ads and Google Ads (its docs also list Microsoft Ads) and keeps spend, delivery and platform-reported results in one view, synced hourly on paid plans and daily on Free. Revenue in Level is a metric mapped to one conversion event per platform, using each platform's own attribution setting, so the five-names double count above doesn't happen in its reports. Book a Level demo to see it on your own ad accounts.
The boundary matters: Level holds the spend and platform-claim rows of the hierarchy. The full decision layer, with store revenue and margin thresholds alongside, is what a reporting engagement builds on top: marketing data in one view, scoped to how your team decides. How that consolidation extends across the rest of the stack is mapped in our cross-channel marketing dashboard piece.
Meta and Google data from one Level account, plus 18 search results
Every real-account number in this article is from one DTC brand's Meta Ads and Google Ads accounts connected to Level, Q1 2025 – Q3 2026 (Google purchase tracking starts Dec 2024). ROAS is platform-reported purchase value ÷ spend per quarter, counting one purchase event per platform (Meta purchase; Google's Shopping App purchase action). The attribution-window comparison uses the per-window values Meta returns alongside the default. We did not adjust or model the values. The brand is anonymized and absolute amounts are withheld. Read them as one account's history, with no claim to be a benchmark. The reconciliation table is illustrative arithmetic, not client data.
We also checked what currently ranks. On a DataForSEO snapshot (US, desktop) for "marketing data analytics" on 2026-10-24, the 9 organic results were career pages, a certificate course, a Reddit thread on courses and general definitions; the AI Overview cited reddit.com, park.edu and tbs-education.com. For "single source of truth marketing data" on 2026-10-26, the 9 results were general SSOT explainers (IBM, Sigma, Skyvia), product-data pieces (PIM vendors) and one marketing-specific article (Adverity). None of the 18 showed which source should answer which marketing question or treated the platform-claim gap as a metric.
Getting to one source of truth
The order that works: fix tracking first (events, CAPI, GA4, UTMs), write the canonical hierarchy second, build the reconciled view third, and write the decision rules last, then keep the weekly cadence.
For the wider KPI picture, our marketing KPI dashboard guide covers what else earns a tile, and our marketing reporting software roundup compares the platforms that can build the view. If the view keeps getting ignored, choosing a marketing dashboard tool looks at why; if you're an agency reporting these numbers to clients, our agency reporting software guide covers what to demand from the tooling. To have it built rather than debated: Level for the live paid-media layer, and a reporting engagement for the decision layer on top.
