Migrate to new tracking code

We are migrating to the new tracking snippet across the whole site this week. Replace the legacy tracker on all pages of shop.joyloom.com, blog.joyloom.com, and the checkout subdomain with the new implementation, verify that existing custom dimensions and ecommerce parameters are preserved, and run a parallel validation to ensure event counts match within 5% during the first 24 hours. Confirm rollback steps if the new code breaks purchase attribution.

Before I hand the migration plan to Priya in ops, make it approval-ready: list the exact custom dimensions and variables that must map from old to new, highlight any incompatible features that will need mapping work, and supply a short rollback checklist with the specific files and CDN paths to revert. Also estimate how much historical reporting will need reprocessing if mapping is off by one parameter.

I flipped the new snippet on staging and test orders appear in our payment logs but reported revenue halved. I’m afraid the ecommerce payload parameter names changed and revenue is being dropped or recorded under a different metric. I can’t tell if the problem is the payload naming, a missing currency code, or an order_id mismatch. Which three checks should I run now to pinpoint whether the issue is data mapping, currency, or deduplication, and what quick fix would restore revenue counts so we can proceed to production safely?

Every migration to a new tracker leaves us reconciling metrics for a week and losing trust with finance. Where should we change habit: run parallel tracking for a defined warm period, insist on a single mapping spec for commerce fields, or create an automated mapping verifier? Recommend one operational rule and one small script or check that prevents the most common migration errors in future rollouts.