Workflow · Client Tracking Setup
Setup is route-dependent. Verification is universal. How we wire a client's conversion tracking depends on their platform. Some clients import our GTM container, and some must not, because it would double-fire their events. Every client, on every route, gets a live test before campaigns spend a dirham.
The route decision in Phase 1 is the one that matters most. Import our container onto a Shopify store that already fires a native Pixel and you double-count every purchase. Get the route right, then verify live. Phase 5 sign-off is the green light for campaign build.
The client grants access, the Paid Ads Strategist does the work, Rachel signs off. Exec chases any outstanding access. Phase 0 secures access and ownership, Phases 1 to 4 are the strategist's technical work, and Phase 5 is Rachel's sign-off. Use the role tabs to see only your items.
One tracking source of truth per event. If the platform already fires the Pixel and GA4 natively (Shopify, or Woo with the plugin), adding our GTM container duplicates every event. If it does not (custom and service sites), our container is the source of truth. The container never touches the Peach System's own container (GTM-TBQQ8JS8). It goes in the client's own GTM.
Templates come from the launch-gate repo. Everything else is the client's own property, reached through our shared logins.
launch-gate/gtm/. The two GTM container templates (container route only).The 6 phases of tracking setup. Same Planted / Ripening / Ready status the client sees in their portal. Click any phase to jump to its detail.
Showing all items. Switch tabs to filter by owner.
Syncing with the team.