Data Foundations · Measure

eCommerce Analytics & Tracking

We build the GA4, Google Tag Manager, data layer and server-side setup behind your store, so revenue, margin and LTV reports match what actually happened, and every channel is judged on numbers you can defend.

  • GA4 & Google Tag Manager
  • Shopify, WooCommerce & Magento
  • Server-side & Conversions API
  • Consent-aware by default

Why tracking comes first

Every budget decision runs on your tracking

Google Ads and Meta bid on the conversions you send them. Klaviyo flows trigger on the events your store reports. Your monthly review moves budget based on what GA4 says each channel earned. If a purchase fires twice, bidding algorithms chase customers who look twice as valuable as they are. If checkout events go missing, your funnel report blames the wrong step.

Most stores don't have a tracking problem they can see. They have numbers that look plausible and are quietly wrong. Data Foundations is the part of The Profit Loop that fixes this: one clean measurement layer that your ads, your email program and your P&L all read from. It's also why we insist on clean tracking and consent before scaling spend.

Common failure points

Where eCommerce tracking usually breaks

These show up in almost every store we audit. None of them throw an error.

Duplicate purchases

An app pixel and a GTM tag both send the purchase. GA4 and ad platforms count many orders twice, and reported ROAS looks better than reality.

Missing checkout events

Checkout changes, a new upsell app or an off-site payment gateway stops the purchase event from firing for part of your orders.

Revenue definition drift

One tool reports revenue with tax and shipping, another without. Nobody agrees on which number is real, so nobody trusts any of them.

Consent that blocks everything, or nothing

The banner shows, but tags fire before the visitor chooses. Or every tag waits forever and GA4 loses most of its data.

Self-referrals and lost sources

Customers return from PayPal or a payment gateway and the order is credited to that domain instead of the campaign that earned it.

Ad platforms learning from bad signals

Smart Bidding and Meta's delivery optimize toward the conversions they receive. Wrong values in means wrong customers out.

Working with us

An analytics team that ships, documents and checks its own work

We work as an extension of your in-house team. A dedicated strategist owns the measurement plan, and an analytics specialist builds and QAs it. Your developers only step in where the platform requires code, with a written spec. Everything is tested before it's published and documented after.

  • A written measurement plan: events, parameters, key events and who owns each one
  • Builds tested in GTM preview, Tag Assistant and with real test orders
  • A change log for every container version we publish
  • Monthly reconciliation of GA4 purchases against store orders
  • Reporting on revenue, contribution margin and LTV, not just sessions

How a rebuild runs

From audit to numbers you trust

  1. Diagnose

    Find what's broken

    We inventory every tag, pixel and app, place test orders and match GA4 purchases to store orders by transaction ID. You see the gap and its causes.

    Data Health Check
  2. Plan

    Write the measurement plan

    Which events matter, which parameters they carry, which tool receives what, and which conversion each ad platform should optimize toward.

    GA4 · Data layer
  3. Build

    Rebuild the layer underneath

    Data layer, GTM container, GA4 configuration and, where it pays off, server-side tagging with Meta Conversions API and enhanced conversions.

    GTM · Server-side & CAPI
  4. Verify

    Test every path

    Test orders across payment methods, devices and consent states. Nothing is published until the numbers line up.

    QA
  5. Maintain

    Keep it accurate

    Monthly reconciliation, a review after every theme, checkout or app change, and alerts when purchase volume drifts from orders.

    Ongoing

The difference

Tracking that is installed vs. tracking that is correct

Most setups pass the "does GA4 have data?" test. Few pass "does GA4 match our orders?"

What we usually inherit

  • Every app adds its own pixel, plus a GTM container on top
  • Success is judged by whether reports show numbers at all
  • Purchase value sent with tax and shipping in one tool, without in another
  • Ad platforms optimize toward add-to-cart or page views

What we build

  • One source per event, decided and written down
  • Success is judged by order-level reconciliation, every month
  • One revenue definition, documented and used everywhere
  • Ad platforms optimize toward purchases, with values that reflect margin where possible

What the data is for

The numbers we make reliable, and what they feed

Analytics is not the goal. Profit decisions are, and each one depends on tracking being right first.

MetricBuilt fromUsed for
Purchases and revenueGA4 purchase event with a unique transaction ID, reconciled against store ordersChannel reporting, Smart Bidding, budget allocation
Contribution margin per orderOrder value minus product cost, shipping, payment fees and discountsPOAS, break-even ROAS, promotion decisions
Funnel step ratesview_item, add_to_cart, begin_checkout and purchase eventsConversion work on product, cart and checkout pages
Channel and campaignUTM parameters, click IDs and clean referral rulesComparing paid, email, SMS and organic on the same terms
First-to-second order rateCustomer ID and order sequence from store dataRetention planning and lifecycle flow priorities
Cohort LTVOrders by acquisition month and first channelHow much you can afford to pay for a customer

GA4 is one input. Margin and LTV usually come from order and cost data joined to it. Try the POAS calculator to see why margin, not revenue, belongs in your ad reporting.

The tools and platforms we implement and audit

  • GA4
  • Google Tag Manager
  • GTM Server-Side
  • Google Ads Enhanced Conversions
  • Meta Conversions API
  • Shopify Customer Events
  • Shopify Plus
  • WooCommerce
  • Magento / Adobe Commerce
  • Klaviyo
  • BigQuery
  • Looker Studio
  • CookieYes

Platforms

Built for how your platform actually tracks

Each platform breaks tracking its own way. On Shopify and Shopify Plus, checkout runs through customer events and sandboxed pixels, and overlapping apps cause most duplicates. On WooCommerce, caching and off-site payment gateways decide whether the order-received page fires. On Magento and Adobe Commerce, full-page cache and multi-store setups can send stale or wrong-currency data. If GA4 and Shopify already disagree, start with why GA4 doesn't match Shopify revenue.

Free Profit Audit

See what blurry data is costing you

The Free Profit Audit scans your store, detects your tags and stack, and scores tracking and consent health alongside retention, cart recovery and ad efficiency. You get a profit-leak estimate and a prioritized 90-day plan.

About 4 minutes · No login · Results on screen before we ask for your email

FAQ

eCommerce analytics questions we hear most

What does an eCommerce analytics agency actually do?

We design and build the tracking that every other channel relies on: the data layer, Google Tag Manager, GA4, ad platform conversions and, where useful, server-side tagging. Then we check it against your real orders and keep it accurate as your store changes. The output is reporting your team can make budget decisions on, measured in revenue, margin and LTV.

Why doesn't GA4 revenue match Shopify?

Shopify records every order. GA4 only records purchases that a browser tag reports, and some visitors block or decline tracking. Large gaps usually come from comparing different things, such as all sales channels against online orders, or revenue with and without tax. The rest is missing or duplicated purchase events. We reconcile order by order to find which it is.

Do we need server-side tracking?

Not always. If your browser tracking is broken, server-side tagging won't fix it. Once the basics are clean, server-side tagging, Meta Conversions API and enhanced conversions can recover signal lost to blockers and browser limits and give you more control over what data leaves your site. We recommend it when ad spend is large enough for better signals to matter.

Which platforms do you work with?

Shopify and Shopify Plus are most of our work. We also build tracking on WooCommerce and on Magento and Adobe Commerce. On the marketing side, we connect GA4, Google Ads, Meta, Klaviyo and the consent platform you use, so every tool reads the same events and the same revenue definition.

How long does a tracking rebuild take?

It depends on how much is broken and how much developer time your platform needs. A Data Health Check is a short, fixed-scope project. A full rebuild of the data layer, GTM and GA4 usually runs over several weeks, because testing across payment methods and consent states takes time. Your roadmap will show the order and the timing.

Make decisions on numbers you trust

Start with a free audit. You'll see how healthy your tracking and consent setup looks from the outside, and get a prioritized plan whether or not we work together.

Free Profit Audit