E-COMMERCE ANALYTICS

US DTC brands running paid media without an independent measurement layer are optimising to platform-reported ROAS numbers that systematically overcredit the platform doing the reporting

Meta says Meta drove 5x ROAS. Google says Google drove 4x ROAS. Total attributed revenue across platforms is twice what Shopify recorded. Someone is wrong — and no individual platform will tell you it is themselves.

This is for you if

This is for US DTC brands that need measurement independent of the platforms they are paying

You are running significant paid media budgets on Meta and Google and the total attributed revenue across platforms is higher than your actual Shopify revenue

You have not implemented Meta Conversions API or Google Enhanced Conversions and are running on browser-side-only tracking post-iOS14

You migrated from Universal Analytics to GA4 and the e-commerce tracking is not working correctly in GA4's event schema

Your Klaviyo email revenue attribution and GA4 channel attribution are counting overlapping orders and you do not have a reconciliation methodology

You are making channel budget allocation decisions — shifting spend from Meta to Google or vice versa — based on platform-self-reported ROAS with no third-party validation

You have heard of Triple Whale or Northbeam but are not sure whether your current revenue scale justifies the investment or how they fit into your existing GA4 setup

What's broken

Four measurement failures that affect US DTC brands running paid media at scale

No Conversions API for Meta or Enhanced Conversions for Google

US brands running significant annual paid media budgets are doing so on browser-only tracking post-iOS14. Meta and Google are both reporting 2-3x inflated conversion counts relative to GA4 — not because CAPI or Enhanced Conversions would reduce their numbers, but because the browser Pixel is misfiring and deduplication is not configured correctly. Server-side tracking through CAPI and Enhanced Conversions is required for both channels. Meta CAPI sends purchase events from the server. Google Enhanced Conversions sends hashed first-party data (email, phone number) with conversion events to improve match rates in Google's attribution model. Both are required for conversion data quality at meaningful ad spend levels.

No independent attribution model

The brand is making channel budget allocation decisions based on platform-self-reported ROAS. Meta says Meta drove 5x ROAS. Google says Google drove 4x ROAS. The total attributed revenue across platforms is 2x actual Shopify revenue. No third-party media mix model exists to arbitrate. Triple Whale and Northbeam are the two most widely used independent attribution tools for US DTC brands — they pull spend data from all paid channels, order data from Shopify, and apply their own attribution models that are not beholden to any individual platform's reporting. At $5M+ annual revenue with meaningful paid media spend, the investment in a third-party attribution tool is typically returned in the first month of identifying misallocated budget.

Klaviyo revenue attribution not reconciled against GA4

Klaviyo is reporting email-attributed revenue based on 5-day click attribution. GA4 is attributing a portion of the same orders to direct, organic, or paid channels. The total revenue across Klaviyo and GA4 exceeds actual Shopify revenue because both systems are claiming credit for the same purchases. No reconciliation methodology exists between the two attribution systems. The correct approach is to define a primary attribution system (typically GA4 with UTM-based last-click for channel decisions, Klaviyo for email program evaluation), document the expected overlap, and evaluate each channel against its appropriate metric rather than attempting to make Klaviyo revenue and GA4 channel revenue sum to Shopify total.

GA4 e-commerce event schema not updated from Universal Analytics

Brands that migrated from Universal Analytics to GA4 using an automatic migration path or an outdated GTM tag template may still have the old Enhanced E-commerce event structure firing alongside or instead of the correct GA4 schema. GA4 requires specific event names — purchase, add_to_cart, view_item, begin_checkout — with an items array parameter containing product-level data. The UA Enhanced E-commerce schema used different event names and a different data layer structure. If the migration was done by adding the GA4 config tag to an existing UA GTM container without rebuilding the e-commerce events, the GA4 e-commerce reports will show incomplete data: sessions and page views will be present, but the purchase funnel and product performance reports will be empty or incorrect.

What we engineer

What the US analytics build covers

Meta CAPI and Google Enhanced Conversions implementation

We implement Meta Conversions API using server-side GTM or Shopify's native CAPI integration with deduplication configured against the browser Pixel. We implement Google Enhanced Conversions by passing hashed email and phone data with purchase events in GA4, and importing the GA4 purchase event into Google Ads as the primary conversion action.

GA4 e-commerce event schema audit and rebuild

We audit the current GA4 e-commerce implementation against the correct GA4 schema, identify events firing with incorrect names or incorrect parameter structures, and rebuild the GTM e-commerce tags using the correct GA4 event names and items array configuration. We verify the purchase funnel, product performance, and checkout behaviour reports are populated correctly after the rebuild.

Klaviyo attribution reconciliation

We document the Klaviyo attribution window settings, configure consistent UTM parameters across all Klaviyo campaigns and flows, define the reconciliation methodology between Klaviyo-attributed revenue and GA4 channel revenue, and deliver a measurement policy document your team can apply when evaluating email program performance vs. channel acquisition performance.

Third-party attribution tool evaluation and setup

We evaluate whether Triple Whale, Northbeam, or Rockerbox is the appropriate tool for your revenue level and channel mix, set up the integration with Shopify and your paid media accounts, and configure the dashboard to your primary business metrics.

What changes

What the measurement stack looks like after the build

Before
After
Before US brands running significant annual paid media budgets are doing so on browser-only tracking post-iOS14. Meta and Google are both reporting 2-3x inflated conversion counts relative to GA4 — not because CAPI or Enhanced Conversions would reduce their numbers, but because the browser Pixel is misfiring and deduplication is not configured correctly. Server-side tracking through CAPI and Enhanced Conversions is required for both channels. Meta CAPI sends purchase events from the server. Google Enhanced Conversions sends hashed first-party data (email, phone number) with conversion events to improve match rates in Google's attribution model. Both are required for conversion data quality at meaningful ad spend levels.
After Conversion signal quality is improved for both Meta and Google — CAPI and Enhanced Conversions reduce the signal loss that causes platform-reported conversions to diverge from actual Shopify revenue
Before The brand is making channel budget allocation decisions based on platform-self-reported ROAS. Meta says Meta drove 5x ROAS. Google says Google drove 4x ROAS. The total attributed revenue across platforms is 2x actual Shopify revenue. No third-party media mix model exists to arbitrate. Triple Whale and Northbeam are the two most widely used independent attribution tools for US DTC brands — they pull spend data from all paid channels, order data from Shopify, and apply their own attribution models that are not beholden to any individual platform's reporting. At $5M+ annual revenue with meaningful paid media spend, the investment in a third-party attribution tool is typically returned in the first month of identifying misallocated budget.
After GA4 e-commerce reports are populated correctly — purchase funnel, product performance, and checkout behaviour reports all reflect actual buyer behaviour in the correct GA4 schema
Before Klaviyo is reporting email-attributed revenue based on 5-day click attribution. GA4 is attributing a portion of the same orders to direct, organic, or paid channels. The total revenue across Klaviyo and GA4 exceeds actual Shopify revenue because both systems are claiming credit for the same purchases. No reconciliation methodology exists between the two attribution systems. The correct approach is to define a primary attribution system (typically GA4 with UTM-based last-click for channel decisions, Klaviyo for email program evaluation), document the expected overlap, and evaluate each channel against its appropriate metric rather than attempting to make Klaviyo revenue and GA4 channel revenue sum to Shopify total.
After An independent attribution view exists — Triple Whale or Northbeam provides a cross-channel revenue attribution view that is not controlled by any individual platform
Before Brands that migrated from Universal Analytics to GA4 using an automatic migration path or an outdated GTM tag template may still have the old Enhanced E-commerce event structure firing alongside or instead of the correct GA4 schema. GA4 requires specific event names — purchase, add_to_cart, view_item, begin_checkout — with an items array parameter containing product-level data. The UA Enhanced E-commerce schema used different event names and a different data layer structure. If the migration was done by adding the GA4 config tag to an existing UA GTM container without rebuilding the e-commerce events, the GA4 e-commerce reports will show incomplete data: sessions and page views will be present, but the purchase funnel and product performance reports will be empty or incorrect.
After Klaviyo email evaluation is separated from channel attribution — email program performance is evaluated in Klaviyo against email-specific metrics; channel acquisition performance is evaluated in GA4 against channel metrics; overlap is documented and expected
How it works

How the US analytics engagement works

  1. 01

    Audit

    Days 1-4

    We audit GA4 e-commerce event schema compliance, Meta CAPI and Google Enhanced Conversions status, Klaviyo attribution window configuration, and your current attribution methodology across channels. We produce a written audit document before any implementation begins.

  2. 02

    Implementation plan review

    Day 5

    We present findings and proposed scope. You confirm priorities.

  3. 03

    GA4 e-commerce schema rebuild and CAPI/Enhanced Conversions setup

    Days 6-11

    We rebuild GA4 e-commerce events in the correct schema, implement CAPI with deduplication, and configure Google Enhanced Conversions. We run verification in GTM Preview, GA4 DebugView, Meta Events Manager, and Google Ads diagnostics before publishing.

  4. 04

    Third-party attribution tool setup

    Days 11-14

    We connect your Shopify store and paid media accounts to the selected attribution tool, configure the attribution model and channel definitions, and validate that order data is importing correctly.

  5. 05

    Klaviyo reconciliation documentation and handover

    Days 14-16

    We deliver the attribution reconciliation methodology, the implementation documentation for every GTM tag and trigger, and a measurement policy document covering how to read each platform's numbers against the others.

Common questions

E-commerce analytics questions for US DTC brands

What is the difference between Meta Conversions API and Google Enhanced Conversions for US Shopify stores?

Meta Conversions API and Google Enhanced Conversions both address post-iOS14 signal loss but work differently. Meta CAPI sends conversion events from a server directly to Meta's CAPI endpoint, bypassing the buyer's browser entirely. It requires you to send event data — including customer identifiers like email or phone number for matching — from your server to Meta. Google Enhanced Conversions supplements the existing Google Ads conversion tag by sending hashed first-party data (email, phone, name, address) alongside the conversion event, which Google uses to improve conversion matching accuracy across devices and browsers. CAPI is a server-to-server event pipeline; Enhanced Conversions is a data enrichment layer on top of the existing browser-based conversion tag. Both are necessary for accurate conversion measurement on US campaigns at scale.

How do I reconcile Klaviyo email revenue attribution with GA4 for US e-commerce?

Klaviyo and GA4 use different attribution models that will always produce overlapping revenue counts for the same orders. Klaviyo uses a 5-day click, 24-hour open attribution window by default — any purchase within that window by a recipient who clicked or opened an email is attributed to the email. GA4 uses last-click UTM attribution — the same purchase is attributed to whichever channel's UTM parameter was most recently present in the session. The reconciliation methodology is to treat these as separate measurement systems for separate decisions: use Klaviyo revenue for evaluating email program performance (revenue per recipient, flow conversion rate, campaign lift), and use GA4 for channel acquisition decisions (which paid channels are driving new customer sessions). Do not add Klaviyo-attributed revenue and GA4 channel revenue together and compare to Shopify total — the overlap will make the sum exceed actual revenue.

What is media mix modelling and how is it different from last-click attribution for US DTC brands?

Media mix modelling (MMM) is a statistical method that estimates the revenue contribution of each marketing channel by analysing the relationship between spend levels and revenue outcomes over time, without relying on individual purchase attribution. Last-click attribution assigns 100% of a purchase to the final touchpoint before conversion. MMM looks at aggregate patterns — when Meta spend goes up, does revenue go up? By how much? With what lag? — to estimate incrementality across channels. For US DTC brands, MMM through tools like Northbeam or Triple Whale's attribution model gives you a channel contribution estimate that is not dependent on tracking pixels or cookies, making it more reliable in a post-iOS14 environment where individual-level attribution is increasingly degraded. MMM is a complement to GA4 last-click attribution, not a replacement — GA4 tells you which channels are driving sessions; MMM tells you whether those channels are driving incremental revenue.

How do I migrate UA Enhanced E-commerce events to the correct GA4 e-commerce event schema?

The GA4 e-commerce schema uses different event names and a different data layer structure from UA Enhanced E-commerce. In UA, the purchase event was typically pushed to the data layer as ecommerce.purchase with a products array. In GA4, the correct event is named "purchase" and the product data lives in an items array with specific parameter names: item_id, item_name, price, quantity, item_brand, item_category, and item_variant. The migration requires updating the data layer push in your Shopify theme files (or in your GTM custom HTML tag) to use the GA4 items array structure, and updating the GTM GA4 event tags to read from the new data layer variables. Running both structures simultaneously during a transition period is possible but requires careful deduplication to avoid double-counting events in GA4.

What US e-commerce analytics tool — Triple Whale, Northbeam, or Rockerbox — is right for a $5M+ DTC brand?

Triple Whale, Northbeam, and Rockerbox serve different needs at the $5M+ revenue level. Triple Whale is the most widely adopted among Shopify DTC brands in the $1M-$30M range; it offers a pixel-based attribution model, a summary dashboard (the "Whale Dashboard") consolidating key metrics, and a creative analytics view for Meta ad performance. Northbeam uses a more sophisticated algorithmic attribution model that tends to better handle brands with longer consideration cycles and multi-touch customer journeys; it requires 60-90 days of data to calibrate its model fully. Rockerbox is a cleaner channel-level attribution tool without creative analytics, making it a better fit for brands that want channel-level MMM without the creative performance layer. At $5M revenue with heavy Meta and Google spend, Triple Whale or Northbeam are the two most common choices — Triple Whale for brands that prioritise creative performance visibility, Northbeam for brands that prioritise attribution model accuracy.

Our team

The people behind the work

Not a black box. Real specialists you can call, with their names on the work.

Niraj Raut

Niraj Raut

Founder — Ecommerce SEO
Keshab Joshi

Keshab Joshi

PPC Expert
Hawrry Bhattarai

Hawrry Bhattarai

Google Ads Expert
Arogya Rijal

Arogya Rijal

SaaS SEO Expert
Start here

Request an analytics audit for your US DTC brand

The audit documents your GA4 e-commerce schema compliance, CAPI and Enhanced Conversions configuration, Klaviyo attribution setup, and whether your current measurement stack can support independent channel evaluation. You receive the written audit before any implementation work begins.