The fear I hear most from business owners is not about cost. It is this: “What if we switch and our ads stop working?” It is a fair worry. Ad algorithms depend on a steady flow of conversion data. Break that flow for a week and campaigns can wobble. The answer is not to avoid the move. It is to do it in stages.
The safe migration plan
- Audit what you have. List every pixel and tag on the site: in GTM, in the theme code, in apps and plugins. Write down which events each one sends. Most surprises live here.
- Write a simple tracking plan. One table: event name, where it fires, which platforms receive it, which parameters it needs.
- Set up the server foundation. Stape container, custom domain (Blog 1), Custom Loader, GA4 through the server (Blog 3).
- Run browser and server side by side. Keep the Meta and TikTok pixels. Add CAPI and Events API next to them with deduplication (Blog 2). Do not remove anything yet.
- Compare for 7–14 days. Check platform numbers against your shop or CRM. Check dedup rates and Event Match Quality (Blog 7).
- Clean up duplicates. Remove old hardcoded pixels and app integrations that send the same events outside GTM.
- Move Google Ads conversions to the server container (Blog 4), one conversion action at a time.
- Add the extras. Cookie Keeper or same origin (Blog 9), webhooks for offline conversions (Blog 8).
- Document and hand over. A short doc of what fires where saves hours later.
What to compare during the overlap
| Check | Where | What good looks like |
|---|---|---|
| Purchases | Platform vs shop backend | Close match, no doubling |
| Dedup | Meta Events Manager | Browser and server both shown, deduplicated |
| EMQ | Meta Events Manager | Same or higher than before |
| Sessions | GA4 | No sudden jump (would mean double tags) |
| Errors | Stape logs | Few or none |
Mistakes to avoid
- Switching everything on a Friday. Launch early in the week so you can watch it.
- Removing the pixel on day one. Meta recommends browser plus server together. Keep both.
- Changing ad campaigns at the same time. If numbers move, you will not know why. Freeze big campaign changes during the overlap.
- Not telling the media buyer. A sudden rise in reported conversions can look like a bug. Warn them ahead.
How it usually goes
On a well-run migration, the client barely notices the switch day. What they notice two or three weeks later is that platform numbers sit closer to the shop’s real numbers, and that the ad accounts stop “losing” conversions they used to lose. Quiet and boring is exactly the goal.
Bottom line
Do not rip and replace. Build the server side next to what works, compare, clean up, then expand. That is how you move to server-side without a single bad week.
Source reading: Stape — how to start with server-side tracking, Stape — Facebook event deduplication