The algorithm's audience-optimization history, if the pixel isn't carried over to a stable domain.
Pixel and Conversion Tracking: Don't Lose Data
How to build tracking so an account replacement is a technicality, not a reset of months of optimization data.
A suspended ad account isn't just lost spend — it's a risk of losing your accumulated conversion data too, if pixel and tracking aren't set up correctly. Here's how to build tracking so a replacement account doesn't reset your optimization back to zero.
The pixel lives on your domain, not inside the ad account
A principle new advertisers often miss: a Facebook, Google, or TikTok pixel is installed on your landing page's domain — it doesn't "live" inside a specific ad account. When a suspended account is replaced, the pixel on your site stays exactly as it was; the new account simply connects to that existing data source.
Why attribution breaks down without a tracker
A platform's built-in reporting only shows what that platform can see. Without a third-party tracker (Keitaro, Binom, RedTrack, and similar), it's hard to reconcile conversions across multiple traffic sources into one clear picture — especially with parallel campaigns or after an account replacement.
What gets lost without the right setup
- The algorithm's audience-optimization history, if the pixel isn't carried over to a stable domain
- The ability to accurately calculate ROI across the before/after of a replacement
- Retargeting data (Criteo and similar), if the audience was only ever built inside the old account
Building tracking correctly from day one
- Install the pixel on your own domain, not a disposable one-off page
- Mirror events into a third-party tracker alongside the platform's own analytics
- Use server-side tracking (Conversion API for Facebook, Enhanced Conversions for Google) — it holds up better against ad blockers and browser cookie limits
- Keep a dated log of account replacements — it makes any unexplained data dip easier to diagnose
Server-side tracking and account replacement
Server-side integration (Facebook's Conversion API or equivalents) sends conversion data directly from the server, bypassing the browser session entirely — that makes it resilient not just to ad blockers, but to the ad account switch itself, since the data ties to the on-site event rather than a specific account's session.
Before requesting a replacement after a suspension, confirm your pixel and tracker are set on the domain, not just inside the old account — otherwise the new account launches blind, with no conversion history.
The takeaway
Setting the pixel and tracker up at the domain level, rather than inside the ad account, is what turns replacing a suspended agency account into a formality instead of losing months of optimization.
Ready to put this into practice? Get an agency account today.
Get an Account Today →