What a move puts at risk in a TikTok account
The pixel and Events API tutorial sets up TikTok measurement from nothing; this tutorial protects that work when the site is replaced beneath it. A move differs from a fresh install in three ways. The pixel already holds the history that delivery learns from. Audiences are already built on its events. And campaigns carry on spending while the switch is made, with the old platform perhaps doing jobs nobody recorded, such as sending server events. What the account needs is continuity: the same TikTok pixelAn ad platform's browser code that reports page views and events on a site back to the platform. still receiving the same events, carrying the same parameters, from the new pages, and every ad pointing at an address that still exists.
| Part of the account | What it needs from the site | How a move breaks it |
|---|---|---|
| Pixel and base code | One pixel held by the business's Business Center, loading on every page including checkout and confirmation | The new platform installs a pixel of its own, a second one is created, or a template, subdomain or hosted checkout sits outside the container |
| Standard events and parameters | Documented event names, a trigger at the real moment, value, currency and contents supplied by the data layer, an event identifier | New templates fire nothing, fire twice, read values from page text or send the purchase when a page loads |
| Server route | The Events API sending the same events under the same identifier, for example through the shop platform's integration | A route that lived inside the old platform can end with it, or a test code stays in live sends |
| Consent | A banner that tells the container when the pixel may fire | The new banner records the choice and never signals the container, or gates nothing |
| Click identifier and campaign parameters | The identifier TikTok adds to the destination address and the parameters the business appends | A redirect, a shortener or a cleaning rule drops the query string |
| Ad destinations and links | Each ad's destination, links in owned profiles and the links creators carry | Links point at redirects or at removed pages |
| Audiences and landing page goals | Website audiences built from pixel events, and landing page view optimisation that needs the pixel on the destination | The pixel is absent from the new landing template, or consent changes who it records |
| Product matching | Content identifiers on events that match catalogue items for shopping formats | The identifiers on the events no longer match the catalogue's items |
Neighbouring pages cover other parts of the same project. The website migration checklist sequences the whole move. The Google Ads guide to website migrations and the Meta Ads version of this tutorial cover those two platforms. The redirect map itself belongs to the SEO guide to site migrations.
Before you start
- Admin rights in the Business Center that holds the ad account and the pixel, in Events Manager and in the site's Tag Manager container, and access to the new shop platform and its staging copy.
- The plan for the move: whether platform, templates, checkout, domain or all of them change, the launch date and a staging copy for trial events.
- The redirect map, pairing each old address with its new one; the redirect map template shows the format.
- The setup record that the pixel tutorial finishes with (pixel code, events, parameters, triggers, consent pattern, server route, identifier field and date), kept inside the measurement plan.
- A way to place trial orders on staging and in production and find them in the order system.
- A phone with the TikTok app and a test ad whose destination can be pointed at the new site.
- A calm launch window, which as general practice should be clear of a sale or a creator push.
The steps
Inventory what the account takes from the site
As general practice, go down the table and record each item against this account, with a named owner: the pixel code and the Business Center holding it, each event with its trigger, parameters and identifier field, the server route and who runs it, the consent pattern, the landing templates and domains the ads use, the destination of each active ad, the links in owned profiles and the tracked links creators carry, the website audiences and what feeds them, and any catalogue a shopping format reads. Flag the ad groups that optimise for a pixel event or for landing page views, since a broken event teaches them the wrong lesson at full price, and anything defined by an address or by page content, because a template change can leave it sending nothing. This list is what each later step is checked against.
Keep the pixel you have and map its events
The pixel was created in Business Center and named after the website because it outlives campaigns and agencies, and a change of platform is one more thing it outlives. Keep it. Load the existing pixel code on the new pages and point every event at it; should the new platform's TikTok integration offer to create a pixel while it is being set up, connect the existing one. A new pixel starts with no history, and the Business Center tutorial shows the price: in its worked example the advertiser runs reach and video view campaigns while the purchaser audience refills and starts conversion campaigns only afterwards. The exception is a pixel held in someone's personal login, which the same tutorial's worked example replaces in one release; as general practice, a move is a good time for that. Then, as general practice, draw up an event map giving, for each event, how it triggers on the old site and on the new one, its parameters, the source of each value, its identifier and the route that sends it, and file it with the setup record.
Check the base code on every new page type
New templates are new places for the base code to go missing. Follow the whole journey in the event map and look at each page type, including those that can sit outside the container: a hosted checkout, a booking or quote tool on a subdomain, a confirmation page served by the platform and the page a payment provider sends the visitor back to. The pixel not firing diagnosis lists these cases with the check for each. The base code should load once per page, from one trigger. When the new platform's own integration installs the pixel, keep one copy and remove the other, because a pixel loaded twice doubles every event from page view to purchase. If checkout moves to another domain, find out what happens to the pixel's cookie and to anything carried in the address as the visitor crosses.
Wire the events into the new templates
Build each event from the map. The pixel tutorial describes what every event needs, and a move puts the weight on four points. Spell every event name as TikTok documents it, because any other spelling turns a standard event into a custom one. Fire each event at the moment its action happens: the purchase once, on the order-complete push the platform makes when payment confirms, never on a page view, a button click or a reload of the confirmation page. The value, the currency and the contents come from the new platform's data layerA structured object on a web page that passes values to a tag manager for tags to use. and not from text on the page, which a redesign can change; the data layer guide explains the timing. And generate one event identifier from the order or submission number and pass the same value to every route. When other platforms' tags also report the purchase, ad platform tags from one data layer feeds all of them from a single event.
Replace the server route before the old platform goes
Establish how server events reach TikTok at present. The pixel tutorial names the routes: a hosted shop platform's maintained integration, a server-side Tag Manager container fed from the data layer, or a custom backend. An integration links two accounts, so one tied to the old platform can end when the old shop does. Build the replacement on staging with the Events APIServer-side event sharing with Meta. before launch: the same pixel code, the same event names as the browser, the same identifier for each action, connected from a login the business controls, and running on the new platform before the old route is retired. Send trial events with the test event code so they reach the test view and not live reporting, then take that code out of the live configuration, because live sends that still carry it are a cause the diagnosis for missing Events API events names. TikTok counts a purchase once when both routes report it with the same name and identifier, so a mismatch on either side counts it twice.
Re-test consent on the new banner
A new site can bring a new banner, or the old banner wired to a new container, and no part of the pixel setup should run until a visitor has agreed, in the places where agreement is required. Release the base code and every event tag from the trigger that the consent tool raises once a visitor opts in, make the same decision on the server route, and follow the wiring in the consent mode guide. Then test both branches on the new templates. Refuse consent, and the pixel helper should show no pixel while the test view stays empty for that session; accept it, and the pixel should start on the same page without a reload, because the page where a visitor accepts is often the page the ad opened, and a banner that saves the choice without telling the container leaves that page silent.
Trace every address through every hop
When someone taps an ad, TikTok adds a click identifier to the address they land on, which the pixel stores so that later events can be tied to that tap; the business's own campaign parameters travel on the same address. Anything that rewrites the address can strip both. As general practice, take the redirect map and follow each address the ads use, the links in owned profiles and each creator's tracked link through every hop to the final page, whether that hop is the old address, a link shortener, a rule that cleans parameters on arrival or a change of domain or protocol. Every hop has to pass the query string through untouched and the click identifier has to be exempt from any cleaning rule, as the diagnosis for clicks without conversions sets out. Keep permanent redirectsA permanent server redirect telling browsers and search engines a URL has moved for good. from every retired address and, as general practice, try a sample with real campaign parametersURL tags identifying traffic source. appended rather than the bare address; the naming and UTM guide holds the convention the new links should follow.
Open each landing page from a phone inside TikTok
On a phone, a link tapped in TikTok opens inside the app's own browser, which treats a page differently from a desktop test. A landing page view, the optimisation goal the traffic setup recommends once the pixel is installed, is recorded only when the page has loaded and the pixel has fired on it, so a new landing template without the pixel removes the signal an ad group learns from. Open each new landing template from a test ad inside TikTok and confirm that it loads quickly, that no consent wall or pop-up covers the content on arrival, that the pixel fires and that the main action completes in the app, payment included, since some express payment buttons depend on the device's own browser. The sales setup makes the same check on a product page by buying something from a test ad.
Point ads, profile and creator links at the new addresses
List the active ads whose destination changes, using the redirect map, and prepare each new link with its campaign parameters. On launch day, swap the links. The campaign structure guide warns that changing the budget, bid, targeting or creative in a big way may start learning again, and a destination link is not among the edits it names, so, as general practice, change the link alone and leave the rest of the ad and its ad group untouched in the same edit. Change the links in owned profiles as well and, as general practice, ask any creator carrying a tracked link to switch to the new address; the guide to influencer tracking links explains how such links are built. Leave the redirects in place for whatever was missed.
Walk the journey, then check audiences, products and forms
As soon as the new pages are public, run the whole journey while watching the helper extension and Events Manager's test view: a landing page opened from a test ad with its click identifier, a product page, the basket, checkout, a test order and a form; the debugging tutorial for Tag Manager preview shows how to watch the container. For each event confirm that it arrives once by each route, under one name and one identifier, marked as deduplicatedRemoving double counts when one conversion is reported by more than one source., with value, currency and contents correct, and that nothing arrives when consent is refused. The tracking verification checklist runs the same chain across the rest of the stack, and the guide to checking conversion paths covers the journeys themselves. Then look at what the events feed. The audiences guide explains that a website audience holds only the people the pixel recorded, so, as general practice, note each audience's size on launch day and watch it: a changed event shows as an audience that stops growing, and a change in consent moves its size too. Where a shopping format reads a catalogue, the content identifiers on the events must still match its items. An instant form opens inside TikTok, so the move leaves it alone, while a website form depends on its form event; the lead generation setup weighs the two, and either test should follow a lead to wherever the business reads it.
Read the early weeks against orders and log the move
Once the site is live, set the pixel's received purchases, the server's received purchases and the deduplicated total beside the shop's orders for the same closed days, in the way the diagnosis for conversions higher than orders describes. Received purchases above orders point to a duplicate; a shortfall points to a missing event or route, though consent refusals leave some gap on both routes, and blockers leave a gap until the server route carries what the browser misses. Read cost per result with the move in mind: counted results can fall after a release for reasons of counting rather than delivery, so match any change to the launch date before blaming the creative, as the cost per result diagnosis advises. As general practice, hold the campaigns steady while the early counts are read, since changes of your own add a second possible cause to any movement. Record the move in the measurement change log: the date, what changed, each fault found and the day it was fixed. Mention it in the next monthly TikTok report so readers know which weeks ran on which setup. If the counts collapse, the tracking outage response SOP sets out how to keep the campaigns safe while the gap is repaired. Finish by bringing the setup record up to date.
A barometer shop changes platform (illustrative)
Velaemar Barometers moves platform and checkout
Velaemar Barometers, an invented online seller of brass barometers and weather instruments, changed shop platform and moved checkout to a hosted page on another domain, both on one day. Its inventory held one pixel, six events, server events sent by the old platform's integration, one consent banner, 24 active ads pointing at 11 addresses, a profile link and three website audiences: visitors, add to cart and purchasers.
| Item | Old site | New site | Action |
|---|---|---|---|
| Pixel | One pixel in the shop's Business Center | New platform offered a pixel of its own | Declined; the existing pixel code installed |
| Browser events | Six events from the old theme | New templates and a hosted checkout | Rebuilt from the data layer; base code added to the checkout |
| Server route | Old platform's integration | New platform's integration | Same pixel, order-number identifier; test code removed from live sends |
| Consent | Old banner signalled the container | New banner | Container releases the pixel when a visitor accepts, and on each later page |
| Links | Old addresses with campaign parameters | New addresses | 24 ads changed; one redirect rule corrected to keep the query string |
| Audiences | Visitors, add to cart, purchasers | Same events | Sizes recorded on launch day and read weekly |
A test from a phone, opened from a test ad inside TikTok, caught two faults that a desktop test had missed. The hosted checkout's express payment button did not complete inside the app, so the team asked the provider to show the card form first. And the redirect from an old address dropped the query string, so the click identifier never reached the new page; the rule was corrected and the ads' links moved to the final addresses that afternoon. The day after launch the pixel helper reported the pixel twice on checkout pages, because the platform's integration and the container had both installed it, and the integration's copy was switched off. In the first week the shop took 64 orders against 53 purchases received from the pixel and 61 from the server, which deduplicated to 63; in the second week it took 72 orders against 71 deduplicated purchases. The add to cart audience had been gaining about 40 people a day before the move, gained 6 on launch day while the consent wiring was wrong, and was back to 38 a day after the consent wiring was corrected. The team read the first week's higher cost per result against the launch date and the faults found before changing any creative, and entered the move in the change log, naming each fault and the day it was fixed.
The TikTok measurement hub explains how these events become attributed conversions and where to go when a symptom appears after the move.
Common mistakes
- A fresh pixel for the new site. It starts with no history, and everything built on the old one must be rebuilt and re-pointed.
- Duplicate pixel installs. A platform integration beside a container tag doubles every event, page views included.
- No replacement for the server route. Whatever the old platform sent from its servers can end with the old shop, and counted purchases can drop to whatever the browser alone reports.
- Checking on a desktop only. The in-app browser is where a pop-up, a consent wall or a payment button can fail.
- Redirects used instead of link updates. Live ads should point at the new addresses, with redirects covering what was missed.
- A redirect that drops the query string. The click identifier and the campaign parameters go with it, and conversions that happen are not credited.
- A test code left in live sends. Server events go to the test view and never reach reporting.
- Reading the early weeks' cost per result as creative fatigue. Set it against the launch date and the counts before changing the ads.
