Nobody switches tracking vendors for fun. The nightmare is specific: a week of half-migrated purchase events, an attribution hole in the middle of a campaign, and a boss asking why revenue "dropped". HeySignal's ecommerce tooling exists to make that week boring.
Turn on Discovery and HeySignal observes what your store actually pushes into the dataLayer: which events, which keys, which types. Shapes only. Values are never recorded, so there is zero personal data in the exercise. You get an inventory of your real tracking surface before you commit to mapping anything, which beats archaeology in a fourteen-tab GTM container.
Presets install real, editable tracking rules mapped to your platform's conventions, with ecommerce items[] arrays handled as first-class data all the way through. Products, quantities, prices and currencies arrive intact at GA4, become contents[] for Meta, and map cleanly to TikTok.
Presets are versioned and honestly reversible: uninstalling removes exactly the rules the preset created and nothing else. Installed rules are yours to edit; the preset is a starting point, not a cage.
DATALAYER items[] extracted intact
GA4 items[]
META contents[]
TIKTOK ecommerce fields
Keep your existing GA4 tracking running. HeySignal mirrors it in shadow mode: our SDK observes your gtag calls, sends nothing that would double-count, and compares. For GA4 you get client-id parity checking, so you can verify that sessions would stitch identically before a single production event moves.
Deduplication modes govern the dual-running period, so browser pixels and server events coexist without inflating a single platform number. When the parity numbers satisfy you, cut over. Not before.
A purchase flows through the consent gate, gets deduplicated three ways, fans out to every destination the visitor's consent allows, retries platform hiccups, and lands in delivery logs you can actually read. Offline refunds and CRM events can join through signed webhooks.
You need whoever can add a script tag and a DNS record, once. From there presets and rules are point and click.
No. Shared event IDs plus per-destination dedup modes exist precisely so browser and server events reconcile during dual-running.
Discovery shows you exactly how nonstandard, and installed rules are editable field by field. Nonstandard is normal; invisible is the problem.
No. It records structure only: key names and value types. A privacy tool that started by hoarding your dataLayer values would be a strange thing for us to ship.
BRAND