Moving from Stape, PixelFly or server-side GTM without double counting

A step-by-step switch to Trakero from another server-side tracking setup: what to check first, the order to switch each platform, and how to avoid counting purchases twice.

Guides

Reading time
6 min
Checked
2026-10-24
Against
Platform docs
Sources
1 linked below

Your ad accounts keep their history when you switch: the pixel ids, datasets and GA4 properties stay the same, only the system that sends to them changes. The one real risk is a few days where both systems send the same purchase, each with its own event id. Meta can merge copies only when they share an event id, so two systems sending one order look like two orders. The steps below switch one platform at a time so that never happens.

1. Write down what you have

  • Run the free tracking scan on your home page. It lists every pixel and Google id it sees, and whether they go through your own domain.
  • In your current tool, note each destination: Meta dataset (pixel) id, GA4 measurement id, TikTok pixel code, Google Ads conversion actions.
  • Note when your current setup counts a cash-on-delivery order as a purchase: when placed, confirmed or delivered. Use the same moment in Trakero, or your ad reports will jump on the day you switch.

2. Install Trakero, but don't connect any platform yet

Install the WooCommerce plugin, the Shopify app or the snippet. With no destination connected, Trakero collects and deduplicates events but sends nothing, so nothing is counted twice. Place a test order and open the event debugger: you should see the page views, add to cart and the purchase with the right value and currency.

3. Switch one platform at a time

  • Connect the platform in Trakero with the same pixel or dataset id you use today, and send a test event from the dashboard.
  • In the same sitting, turn off the old system's server tag for that platform: pause the Meta Conversions API tag in your server GTM container, or remove that destination in PixelFly or Stape's gateway.
  • Browser pixel: turn the platform on in Trakero's pixel manager and remove the old pixel code from your theme or web GTM container at the same time. The pixel and the server copy then carry the same event id, and Meta keeps one.
  • Repeat for GA4, TikTok and the rest. One platform per sitting keeps any problem easy to trace.

4. Watch for two days

  • Meta Events Manager: the purchase count should match your orders, with events shown as received from both browser and server and deduplicated.
  • The Trakero debugger shows each order's journey: what every platform received, and why anything was held or skipped.
  • If a number doubles, an old tag is still on. The scan shows browser tags; your old tool's logs show server tags.

5. Move your first-party domain, then cancel

Add Trakero's tracking subdomain in your DNS. Keep the old tracking subdomain until the old plan ends, then delete its DNS record. Cancel the old plan only after two clean days.

Try it on your store

Trakero applies all of this for you: first-party SDK, server-side delivery to Meta, TikTok, GA4, Snapchat and Pinterest, deduplication by order id, and a debugger that explains every event.

Start free

Tracking rules change. We'll tell you.

A short email when Meta, Google or TikTok change a tracking rule that affects stores, and when we add a free tool. A few a year. Unsubscribe in one click.

We use your address only for these emails. Privacy policy.