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.
Washington, DC
Analytics, Tracking & Data in Washington, DC
In an institution the reporting problem is not just accuracy — it is producing a number a finance office and a board will both sign off on.
Delivered remotely for brands across Washington and District of Columbia.
Scale · Washington
Why Washington brands come to us for this
- POS, web, conference table and membership system revenue reconciled to one agreed source of truth per type
- Member versus public revenue reported as a standing cut, because that is the first question a board asks
- Exhibition and annual meeting periods measured as defined windows, not inferred from a monthly chart
- Shutdown and disruption periods annotated in the reporting layer so demand pauses are not read as performance drops
- Consent mode v2 and Shopify's privacy API configured for organisations with international members in scope
Everywhere else, bad measurement causes arguments in a weekly meeting. In a Washington institution it causes a problem at a board meeting, a grant report or an audit, because the number in the deck has to reconcile with the number in the accounting system. That raises the bar. The measurement layer is not just there to make media decisions; it has to survive someone whose job is to check it.
The specific complexity here is that revenue arrives from several places that rarely agree. The web store, the gift shop register, the conference merchandise table, the membership system and sometimes a donation platform all record transactions, and only some of them talk to each other. We reconcile them against Shopify order data first, establish which system is the source of truth for each revenue type, and only then build reporting on top. Attribution modelling before reconciliation is building on sand.
Then the standard rebuild, done properly: server-side tracking on a first-party subdomain, Conversions API with genuine match quality, a documented GA4 event schema, and consent mode wired to your CMP. Consent matters more than average for organisations here — .org and .edu properties get scrutinised, international members bring GDPR into scope, and a privacy misstep is a reputational issue for an institution long before it is a compliance fine.
Local context
Reporting for a board, not just for a media buyer
The reporting layer for a Washington institution has to answer questions no DTC dashboard is built for. What share of revenue came from members versus the public? How did the shop perform during the exhibition versus the quarter around it? What did the annual meeting actually produce, in-person and online combined? Did the September fiscal-year push land where it did last year? And, in a shutdown quarter, how much of the shortfall was a local demand pause rather than a performance failure — a distinction a board will ask about directly. We build those cuts into the reporting layer explicitly, reconciled to Shopify and to the accounting system, so the discussion at the meeting is about what to do next rather than about whose number is right.
Scope
What Analytics & Data includes
The same standard of work we run for every client — applied to a Washington 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 Washington store
We do not work off a rate card. Every Washington 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 Washington — your questions
Usually neither, until they share inventory and customer records. On Shopify POS the register and the web store run off the same data, which removes most of the discrepancy at source. What remains is timing and returns handling, and we document how each is treated so the monthly figure is repeatable. The goal is not a perfect number, it is the same number every time from the same rules.
Yes, once membership status exists as a customer property in Shopify rather than only in the membership system. Then revenue splits by tier, by member versus public, and by lapsed-then-repurchased become standing report lines. That last cut is often the most useful thing on the page, because it quantifies what the shop contributes to retention rather than just what it sells.
If you are offering goods to people in the EU or UK and processing their data, treat it as in scope. Practically that means consent mode v2 wired to a real CMP, honouring Shopify's customer privacy API, a documented data retention position and no marketing pixels firing before consent. For an organisation whose credibility is its main asset, this is worth doing properly rather than at the level of a banner someone installed once.
By annotating the period and comparing like with like: local versus non-local sessions and revenue, member versus public, and the same window in prior years. That separates a regional demand pause from anything the shop did wrong, which is the distinction the question is really about. It also makes the case for the diversification work — national reach and owned channels — with evidence rather than assertion.
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 Washington 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.