What happens to tracking codes and DNS in a move

Nothing moves by itself. This is how we keep it from getting lost, and what we cannot see.

Tags and pixels

Before anything starts, the scan finds the tags on every page and what Tag Manager holds: GTM, GA4, Google Ads, the Meta pixel, TikTok and more.
The settings themselves live at Google and Meta, so the code only needs to be on the new site with the same number.
After the build, the check compares the old site with the preview, and the agent puts back whatever is missing.
A private report opens in the browser and shows what was found and what moved. You can send it to whoever runs your campaigns.

A conversion breaks silently: the campaign keeps running and conversions drop to zero. This is the biggest risk, so it is checked on its own.
We keep the form's id, the hidden fields that carry the ad source, the events and the thank-you page.
Only you can see that Google and Meta received the event. Each tag has a link to check and a mark that you did.

We copy every record we can read, subdomains like track. included, and replace only the site records.
Nobody can see every record from outside, so you can also add the file from your old provider, the only full list there is.
The copy is kept, and you can download it any time and load it at any provider. It is also the way back.
Before you cancel your old host, the DNS tab shows what still points at it.

A server side pixel (Conversions API or server side tagging) leaves no trace from outside. When there are signs, we ask you. It stops in a move unless it is rebuilt.
A Search Console verification file that nothing links to. Verification by DNS record moves with the domain.
Pages behind a login, and code loaded only after something a visitor does.
We add no cookie banner and do not say whether a site meets the law. A banner you already have stays, and legal help is among the add-ons.

Need help? Talk to us