For $5M+ DTC brands, the analytics stack typically includes GA4, Meta Pixel, Klaviyo events, possibly a CDP (Segment, Rudderstack), and an attribution tool (Triple Whale, Northbeam, Rockerbox). Each one is a separate migration with its own failure modes. The combined work is the analytics workstream, and it deserves its own owner.
This page is the operator playbook: what tracking infrastructure must transfer, how to maintain attribution windows through cutover, and how to validate that the post-migration analytics stack produces the same data the team relies on.
Symptoms
How the problem surfaces
Revenue in analytics tools disagrees with Shopify reporting
GA4, Triple Whale, or other reporting tools show revenue numbers that diverge from Shopify's native reporting by 5-30% after migration. The root cause is usually tracking that fires partially — captures some events, misses others — producing systematic under-reporting downstream.
Conversion events stop firing for specific page templates
Tracking that fired on every page on the source platform suddenly only fires on some pages on Shopify. Usually because tracking was embedded in template patterns that did not survive theme migration. New product pages, custom collection pages, or post-purchase pages miss tracking that they should have.
Attribution shifts in unexpected directions
Channels that were attributed 30% of revenue now show 50%, or vice versa. The shift is usually driven by attribution-window resets or by tracking-event order changes between platforms, not by actual channel performance changes. Decisions made on the new numbers misallocate spend.
Meta or Google Ads optimisation deteriorates
Ad platform algorithms depend on conversion event signal to optimise. Reduced or noisy conversion tracking degrades the algorithm's ability to find conversions, leading to higher cost-per-acquisition for weeks until tracking stabilises.
Solution
The operator playbook
Inventory the tracking stack during discovery
During discovery, build the inventory: every tracking pixel and tag, every event being captured, every analytics tool consuming the data, every downstream report or model depending on each tool. Most $5M+ brands have 10-20 tracking integrations active; missing one means the downstream tools relying on it break silently.
The inventory exercise should include the downstream consumers, not just the source tracking. A Meta Pixel that nobody is actually using in ads is lower priority than a GA4 event feeding a retention model. Prioritise the tracking that drives real decisions and budget accordingly.
Migrate tracking with explicit owners per platform
Each tracking platform needs an explicit owner with the responsibility of validating that tracking works correctly post-migration. GA4 owner verifies GA4 events. Meta Pixel owner verifies Meta events. Attribution platform owner verifies attribution. The owner is operational, not technical — they consume the data and notice gaps the technical team would not.
Without explicit owners, tracking migration becomes a vague responsibility shared between engineering, marketing, and analytics teams. The vagueness produces gaps; explicit ownership produces accountability and faster issue detection.
Implement and test tracking on staging before cutover
The Shopify-side tracking implementation should be complete and tested on the staging environment before cutover, not after. Use Tag Assistant for GA4, Meta Pixel Helper for Meta, and equivalent debugging tools for other platforms. Test each tracking event firing on each page template the brand uses.
Brands that skip the staging tracking validation consistently discover post-launch that specific events miss or fire incorrectly. Catching these in staging takes hours; catching them in production after a week of incomplete data costs the analytics gap itself plus the work to backfill or reconstruct the missing data.
Document expected attribution shifts before launch
Some attribution shifts are unavoidable through migration: attribution windows reset, first-click models lose the cookie history, last-touch data restarts. Document the expected shifts before cutover so downstream teams (marketing, finance, growth) know the data they will see in the first month is not directly comparable to pre-migration.
The documentation prevents the most common analytics-migration failure: teams making decisions on the new data without recognising it represents partial reality. With explicit documentation, the team waits for stable attribution before re-tuning spend; without it, they react to noise.
Validate against Shopify native reporting weekly
For four to eight weeks post-launch, validate downstream analytics revenue against Shopify's native order reporting weekly. The two numbers should agree within 5%; if the gap is larger, tracking is incomplete and the gap will compound across reporting cycles. Find the tracking source of the gap quickly; do not let analytics tools and Shopify reporting drift apart.
The validation is an operational task, not an engineering one. The analytics owner runs it weekly; the engineering team fixes specific tracking issues that surface. Brands that defer validation to monthly reviews consistently let gaps compound for weeks longer than they need to.
Cost
Cost range: $10K-$60K (inside the broader replatforming engagement)
| Cost line | Range |
|---|---|
| Tracking stack inventory and prioritisation | $2K-$8K |
| GA4 / Meta Pixel / event implementation | $3K-$20K |
| Attribution platform reconfiguration | $2K-$15K |
| CDP migration (if applicable) | $3K-$15K |
| Staging validation and testing | $2K-$8K |
| Post-launch validation and reconciliation | $1K-$5K |
Cost scales with the number of tracking platforms and the complexity of the attribution model. Brands with standard GA4 + Meta + Klaviyo stack land at the lower end. Brands with multi-touch attribution, CDPs, and sophisticated marketing analytics models land at the upper end. The cost of skipping the work and recovering data later is consistently higher than the cost of doing it correctly.
Timeline
Timeline: 5-9 weeks (parallel to broader replatforming)
Inventory
Weeks 1-2
Tracking stack audit, downstream consumer mapping, ownership assignment
Implementation
Weeks 3-7
Tracking re-wiring on Shopify, event mapping, integration setup
Staging validation
Weeks 6-8
Per-platform tracking validation, event firing tests, debugging
Cutover monitoring
Weeks 8-10
Real-time tracking monitoring at launch, immediate issue response
Validation
Weeks 10-14
Weekly revenue reconciliation, tracking gap closure, attribution stabilisation