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.
San Francisco, CA
Analytics, Tracking & Data in San Francisco, CA
This is the market where the most data is lost to blockers and opt-outs — and the one where decisions most need to be right.
Delivered remotely for brands across San Francisco and California.
Scale · San Francisco
Why San Francisco brands come to us for this
- Server-side GTM on a first-party subdomain, built for a market where blockers are the norm
- Consent and opt-out signals honoured across the stack, including automated browser preferences
- Meta CAPI and Google Enhanced Conversions with hashed identifiers and correct deduplication
- Cohort LTV, payback and involuntary-versus-voluntary churn reported without a manual export
- One reconciliation view across Shopify, the subscription platform, Klaviyo and the ad channels
Measurement here is harder than the vendor documentation assumes. Your customers use browsers that block by default, run extensions as a matter of course, decline tracking prompts at unusually high rates, and live under privacy rules that give them a real, enforceable opt-out — including automated browser signals that must be honoured. The result is that a browser-only pixel setup in this market can lose a large share of events, and the damage is not just reporting: the ad platforms optimise on what they receive, so lost signal becomes lost performance.
So the foundation is server-side. Server-side GTM on a first-party subdomain, Meta Conversions API and Google Enhanced Conversions with hashed identifiers and correct deduplication between browser and server, and consent state passed through properly rather than bolted on. Done right, that recovers signal while honouring the opt-out — the two are not in conflict, but achieving both takes deliberate configuration rather than an app install.
The second half of the work is reporting the number this city's businesses actually run on. A subscription brand cannot be managed from a monthly revenue figure: it needs cohort retention, contribution after acquisition cost, subscriber counts split from one-time buyers, involuntary versus voluntary churn, and payback measured at day 90 and 180. Most of the accounts we take on can produce none of those without a person exporting spreadsheets on a Monday, which is why they get produced monthly and trusted vaguely.
Local context
Reconciling four systems that will never agree, in front of an audience that opts out
Every subscription brand here ends up with the same standoff: Shopify says one revenue number, the subscription platform says another, Klaviyo attributes a third, and Meta and Google both claim the same orders. Nobody is lying — they are counting different events over different windows with different attribution — but the disagreement stalls decisions for months. We build a single reconciliation view with Shopify order data as the source of truth, state clearly what each platform is measuring and where the gaps come from, and quantify how much of the difference is opted-out or blocked traffic rather than a broken tag. California's rules make that last quantity larger here than almost anywhere, so it needs a number attached rather than a shrug. We also make sure consent signals are actually respected across the stack, including automated opt-out preferences, because the compliance risk of ignoring them is not worth the marginal data — and honestly, this customer base is more likely than any other to notice and say something publicly.
Scope
What Analytics & Data includes
The same standard of work we run for every client — applied to a San Francisco 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 San Francisco store
We do not work off a rate card. Every San Francisco 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 San Francisco — your questions
It varies by audience, and for a technical Bay Area customer base it is usually higher than the team expects. Rather than guess, we run a reconciliation between Shopify orders and what each platform recorded over the same window, which turns a vague suspicion into a percentage. That number then tells you whether the priority is server-side implementation, consent configuration, or simply resetting expectations about what platform reporting can ever show.
It means the site detects an opt-out preference, including automated browser signals, and actually changes behaviour in response: no sale or sharing of that visitor's data, tags suppressed or downgraded accordingly, and the state recorded so it persists. That is a configuration job across your tag manager, consent tool and server container. We implement to your privacy counsel's policy rather than writing the policy ourselves.
Both, for different questions. Shopify records orders as they process; the subscription platform tracks recurring contracts, upcoming charges and failed payments on its own clock. The confusion usually comes from failed and retried charges, prorated changes and refunds landing in different periods. We define one canonical revenue figure for decision-making and document exactly how each other system differs, so meetings stop relitigating the number.
The dashboard is the display layer, not the collection layer — it can only show what your tracking captured, so a clean interface over lossy data produces confident wrong answers. If your server-side setup, deduplication and consent handling are sound, keep the tool. If they are not, fixing the pipeline improves every dashboard you own, and most of what we do here sits below where those tools operate.
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 San Francisco 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.