Data Foundations · Measure
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.
Why tracking comes first
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
These show up in almost every store we audit. None of them throw an error.
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.
Checkout changes, a new upsell app or an off-site payment gateway stops the purchase event from firing for part of your orders.
One tool reports revenue with tax and shipping, another without. Nobody agrees on which number is real, so nobody trusts any of them.
The banner shows, but tags fire before the visitor chooses. Or every tag waits forever and GA4 loses most of its data.
Customers return from PayPal or a payment gateway and the order is credited to that domain instead of the campaign that earned it.
Smart Bidding and Meta's delivery optimize toward the conversions they receive. Wrong values in means wrong customers out.
What's included
Use one, or all five as a single rebuild. Every engagement starts with knowing what's broken today.
Working with us
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.
How a rebuild runs
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.
Which events matter, which parameters they carry, which tool receives what, and which conversion each ad platform should optimize toward.
Data layer, GTM container, GA4 configuration and, where it pays off, server-side tagging with Meta Conversions API and enhanced conversions.
Test orders across payment methods, devices and consent states. Nothing is published until the numbers line up.
Monthly reconciliation, a review after every theme, checkout or app change, and alerts when purchase volume drifts from orders.
The difference
Most setups pass the "does GA4 have data?" test. Few pass "does GA4 match our orders?"
What the data is for
Analytics is not the goal. Profit decisions are, and each one depends on tracking being right first.
| Metric | Built from | Used for |
|---|---|---|
| Purchases and revenue | GA4 purchase event with a unique transaction ID, reconciled against store orders | Channel reporting, Smart Bidding, budget allocation |
| Contribution margin per order | Order value minus product cost, shipping, payment fees and discounts | POAS, break-even ROAS, promotion decisions |
| Funnel step rates | view_item, add_to_cart, begin_checkout and purchase events | Conversion work on product, cart and checkout pages |
| Channel and campaign | UTM parameters, click IDs and clean referral rules | Comparing paid, email, SMS and organic on the same terms |
| First-to-second order rate | Customer ID and order sequence from store data | Retention planning and lifecycle flow priorities |
| Cohort LTV | Orders by acquisition month and first channel | How 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
Platforms
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.
FAQ
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.
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.
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.
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.
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.
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.