Tracking Audit & Reconciliation
A full event inventory across GA4, Meta, Google Ads, Klaviyo and Shopify, reconciled against order data to quantify exactly where and how much data is lost.
Minneapolis, MN
Analytics, Tracking & Data in Minneapolis, MN
Tracking and reporting for brands whose revenue arrives through two channels and two very different sets of economics.
Delivered remotely for brands across Minneapolis and Minnesota.
Scale · Minneapolis
Why Minneapolis brands come to us for this
- Contribution margin defined per channel, so a dealer pallet and a full-retail direct order stop being averaged into one useless number
- Outbound freight, oversize surcharges and winter carrier delay costs carried in the margin view, not treated as a rounding error
- Return rate and return reason instrumented alongside conversions, because technical apparel margin lives or dies there
- Seasonal comparison logic and alert thresholds so a normal January does not read as a crisis and a flat October does
- Server-side tracking, Conversions API and consent mode implemented so measurement survives browser restrictions and privacy settings
A brand selling both wholesale and direct has two P&Ls pretending to be one. A direct order at full retail with a paid-media cost attached and a freight bill behind it is a completely different unit of economics to a pallet on a PO, and blending them produces a number that guides nobody. The first job here is usually not a tracking fix — it is agreeing a definition of contribution margin per channel that finance, marketing and the founder all recognise, and then building the reporting to it.
The tracking work underneath is the standard, unglamorous version done properly: a reconciliation of what Shopify recorded against what GA4, Meta and Google each claim, server-side event collection so ad blockers and browser restrictions stop deleting your conversions, Conversions API with correctly normalised identifiers, a GA4 event schema that matches how your catalog actually works, and consent mode configured so measurement survives a privacy setting.
Then the reporting layer, which has to carry the costs this market actually incurs. Bulky and heavy items make outbound freight a material margin line, not a rounding error. Winter carrier surcharges and weather delays affect both cost and refund rate. Returns in technical apparel are large enough that a channel looking profitable on gross revenue can be underwater on net. We put those in the same view as ad spend, because a decision made without them is a guess with a dashboard attached.
Local context
Reporting that survives a year where two months carry the revenue
Standard ecommerce reporting assumes a reasonably flat year, and it misleads badly here. Month-on-month growth is meaningless when the first hard freeze can move a category in a week; a 40% month-over-month drop in January is not a problem, and a flat October is a five-alarm one. So we build reporting on same-period year-over-year comparisons, rolling cohorts and a documented seasonal index rather than the default month-on-month view, and we set the alerting thresholds seasonally so nobody gets paged for a normal February. The second local requirement is that the wholesale side has to be visible in the same place. Direct revenue, dealer orders through the B2B portal, and — where you can get it — retail sell-through sit in one weekly view so a decision about paid media is made knowing what the other channel did. And the Minnesota Retail Delivery Fee on qualifying in-state deliveries needs a home in the order record and the reconciliation, so it never quietly distorts your average order value comparisons against prior years.
Scope
What Analytics & Data includes
The same standard of work we run for every client — applied to a Minneapolis brand’s realities.
Full service detailServer-Side Tracking
Server-side GTM on a first-party subdomain, resilient to ad blockers and ITP, with deduplication between browser and server events done properly.
Conversions API Integration
Meta CAPI, Google Enhanced Conversions and TikTok Events API with hashed identifiers, targeting event match quality of 8 or above.
GA4 Event Schema
A documented, consistent eCommerce event and parameter specification across every surface, so reports mean the same thing in six months as they do today.
Consent Mode & Privacy
Consent mode v2 wired to your CMP with modelled conversions, plus Shopify's customer privacy API and regional compliance handled correctly.
Executive Reporting Layer
One dashboard for blended MER, contribution margin, cohort LTV, new-versus-returning revenue and channel payback. Reconciled to Shopify, refreshed daily.
Scoped and quoted for your Minneapolis store
We do not work off a rate card. Every Minneapolis engagement starts with a fixed statement of work — named deliverables, named dates, one number — written after we have looked at your store, not before. If a smaller first step would serve you better, we will say so.
Get this scopedHow it runs
From kickoff to results
Audit & Quantify
We measure the gap between platform-reported and actual orders per channel. Most stores we audit are losing 15-30% of conversion signal before we start.
Specification
A written measurement plan: events, parameters, identifiers, consent states and destinations. Signed off before implementation begins.
Implement
Server-side container, CAPI, enhanced conversions and consent mode built in a staging environment and validated event by event.
Validate
Order-level reconciliation against Shopify for a full week, plus match-quality checks in each platform. We do not sign off on a screenshot of a tag firing.
Report & Maintain
Dashboards built, team trained, and monitoring in place to alert on event volume anomalies before someone spots them in a monthly report.
Proof
Analytics & Data results
Anonymised under NDA. Figures pulled from the client’s own analytics.
Consumer Electronics & Accessories
~$9M/yr, 210 SKUs, US + AU · Shopify Plus (migrated from BigCommerce)
Meta ROAS had slid from 3.6x to 1.9x in a year and the team had spent twelve months buying new creative to fix it. The real cause was measurement: the BigCommerce checkout dropped 22% of purchase events and the Conversions API had never been installed, so both ad platforms were optimising on incomplete data. The named constraint: peak season was 14 weeks out, and the replatform had to be live and stable well before Black Friday traffic arrived.
1.9x → 3.4xMeta ROAS, once the 22% event gap closed60 days after server-side tracking went live, spend up 18%. Most of that is signal we recovered, not performance we invented — the honest number is the blended CAC below, which is measured against Shopify orders
-32%customer acquisition cost$44 to $30 blended across Meta and Google
4.1s → 1.7smobile LCPdesktop went 2.9s to 1.2s over the same window
+47%peak-season revenueBlack Friday through Cyber Monday, year over year
In their words
Clients on this work
GA4/Shopify gap 14% → under 2%
“Paid audit, and worth every dollar. Forty pages on where our measurement was lying to us — duplicate purchase events, CAPI never configured, GA4 and Shopify off by 14% — each one ranked by the revenue it was hiding. No pitch deck at the end. We fixed six of the items ourselves before we ever signed a retainer.”
FounderHome goods brand, ~$3M/yr · Denver, CO
Verified client, 2026FAQ
Analytics & Data in Minneapolis — your questions
Yes, and it is usually the first thing we build. B2B orders placed through Shopify come in natively, and where wholesale still runs through an ERP we pull it in through the same middleware layer that syncs inventory. The important part is that the two are reported side by side rather than summed — different margin, different cost to serve, different growth levers. Retail sell-through can be added where your accounts share it, on whatever lag they provide.
By comparing it to the same weeks last year and to a seasonal index built from your own history, not to the month before. We also set alert thresholds per period rather than one flat rule, so the system tells you when November is tracking 12% behind last November instead of when January is down against December. That change alone removes most of the false alarms that make teams stop trusting a dashboard.
By pulling actual shipping cost per order from your carrier or 3PL data and joining it to the order record, rather than using the shipping revenue collected as a proxy. For bulky and heavy goods the gap between the two is often the entire margin on a discounted order. Once it is in place you can see which products, which regions and which promotions are quietly unprofitable, which usually changes a free-shipping threshold within a month.
Yes, through the Customer Events and Web Pixels API rather than by injecting scripts into checkout, plus server-side event forwarding for the conversion itself. That is the supported route and it survives platform updates. On Plus you also get more control over checkout-stage events. What matters more than the mechanism is deduplication — if browser and server events are not matched correctly you will double-count purchases and make every downstream number wrong.
Browser tracking loses 15-30% of conversions to ad blockers, ITP and consent rejections. Server-side sends events from your own infrastructure, which recovers most of that signal. Better signal means better algorithmic bidding, so it usually pays for itself in media efficiency within a quarter.
Four to six weeks for a typical Shopify store, including the validation week. Complex setups with subscriptions, multiple markets or a headless front end run six to ten. The audit and specification phase takes about a third of that and is the part that determines quality.
Yes. We use Shopify's Web Pixels API and customer events for checkout tracking, which is the supported path since checkout.liquid was retired. Order-level data comes through the server side, so checkout tracking no longer depends on scripts Shopify will not let you inject.
Next step
Analytics & Data for your Minneapolis brand.
Thirty minutes with the strategist who would actually run your account. We screen-share your store, read your data live, and tell you the three highest-value things we can see from the outside.
Shopify or Shopify Plus stores doing $150k/mo or moreFounder, CEO or eCommerce lead on the callNo deck and no pitch — we open your store instead
Prefer to write it out? [email protected] gets a real reply the same business day, Mon-Fri, 9am-6pm MT.