What a website move can break in a Meta account
The pixel setup tutorial installs the pixel on a site for the first time; this tutorial keeps what it built working when the site underneath changes. The difference matters, because a migration is not a fresh install. The dataset already holds the events delivery learns from, audiences already depend on them, and campaigns are running while the switch happens. The aim is continuity: the same dataset receiving the same events with the same parameters from new pages.
| Dependency | What the account relies on | How a move breaks it |
|---|---|---|
| Dataset and base code | One dataset for the website, owned by the business portfolio | A new platform installs its own pixel, or a second dataset is created |
| Standard events | Purchase, add to cart and the rest, with value, currency, content identifiers and an event ID | New templates fire nothing, fire twice, or read values from page text |
| Conversions API route | Server events from the platform or your own server, deduplicated with the browser | The old platform's integration stops when the shop moves |
| Custom conversions | Rules on URLs or event parameters | URL rules stop matching new addresses |
| Website custom audiences | Events and URL rules within retention windows | Rules for old paths stop adding people |
| Catalog | Item identifiers that match the events' content identifiers | The new platform uses different identifiers |
| Domain | The root domain verified in the owning portfolio | A new domain is not verified, or is verified elsewhere |
| Ad destinations | Each ad's link and its URL parameters | Links point at redirects that drop parameters or at removed pages |
Two neighbouring pages cover other parts of the job. The troubleshooting guide for performance drops diagnoses a drop after a site change has already happened, starting with measurement breaks; this tutorial is the plan that prevents one. The Google Ads website migration guide covers the Google side of the same move, and the SEO plan owns the redirect map.
Before you start
- Admin access to the business portfolio that owns the ad account and the dataset, to Events Manager, to Commerce Manager if the account runs catalog ads, and to the site's Tag Manager container.
- The migration plan: what is changing (platform, templates, domain or all three), the launch date and a staging site where events can be tested.
- The redirect map from the developers or the SEO lead, listing old addresses and their new equivalents.
- The measurement plan, which the measurement plan framework describes, with the event map this tutorial adds to it.
- A way to place test orders on staging and on the live site, and to identify them in the order system.
- The new platform's options for sending browser and server events, as its own documentation describes them.
- A quiet launch window, away from a sale or peak, agreed with whoever runs the campaigns.
The steps
List everything in the account that depends on the site
Work through the table above for this account and write down each item: the dataset identifier and who owns it, every event with its trigger and parameters, the Conversions API route and who runs it, each custom conversion with its rule, each website custom audience with its rules and window, any lookalikes and exclusions built on those audiences, the catalog and its feed source, the verified domain, and the destinations of every active ad. Note which items are written as URL rules, because those are the ones a move breaks without any error message. This inventory is the checklist for every step that follows.
Keep the same dataset and map the events
The pixel setup tutorial creates one dataset for the website, named after the site rather than a campaign or agency, in the business portfolio that owns the ad accounts, because it will outlive both. A migration keeps that dataset. Install the same identifier on the new site and send every event to it; if the new platform offers to create a pixel during setup, connect the existing one instead. Then write an event map: for each event, its trigger on the old site, its trigger on the new templates, the parameters it carries, the source of each value and whether the browser, the server or both send it. Add the map to the measurement plan so that the next person to touch the site can find it.
Rebuild the events on the new templates
Build every event on the new templates from the map. The pixel setup tutorial sets out what each needs: standard events where one fits, value and currency on purchase, content identifiers, content type and the contents array on the commerce events, and an event ID variable on every event tag. Read values from the new platform's data layer, never from page text, since the redesign is exactly when page text changes. If a partner integration on the new platform installs the base code and commerce events itself, do not add a second install on top, or every event will be duplicated. Where the move also brings tags into Tag Manager, the tutorial on moving hard-coded tags covers the cut-over without a gap or a double count.
Move the Conversions API route and check deduplication
Find out how server events reach Meta today. The Conversions API guide, citing Meta's documentation on the Conversions API, lists partner integrations, the Gateway, direct integrations and server-side tag managers as routes. A partner integration belongs to the platform that runs it, so moving off that platform ends its server events on the day the old shop closes. Set up the new route on staging before launch, sending the same event names as the browser and the same event ID for each action, generated once from the order or lead record. Meta treats a browser and a server event with matching event name and event ID as one, so a mismatch on either side doubles every purchase. Make sure only one server route is live after the switch.
Rewrite custom conversions and URL-rule audiences
Custom conversions and website custom audiences built on URL rules are only as stable as the URLs, as the pixel setup tutorial warns. Go through each rule in the inventory. A rule that matches a path fragment which survives the move, such as a checkout step with the same name, may need nothing. A rule that matches an old path, an old domain or a full address needs rewriting. The custom audiences guide, citing Meta's documentation on Custom Audiences, describes website audiences refreshing continuously as events arrive and people age out of the retention window, so an audience whose rule no longer matches stops adding people while its members keep leaving. For the transition, write rules that match both old and new patterns; where a rule can be replaced by an event or an event parameter, replace it, since events survive the next redesign too.
Check the catalog feed and its content identifiers
If the account runs catalog ads, the catalog ads guide explains that dynamic retargeting connects a person to a product through the content identifiers on their events, which must match the item identifiers in the catalog. A new platform can change those identifiers, for example sending variant identifiers where the feed holds parent ones, or the reverse. Generate the new feed on staging, compare its identifiers with what the new events send, and decide which side changes before launch. Check that each item's link in the product feedA structured file of a store's products, prices and availability used to build shopping and catalogue ads. points at the new product page, and that the feed source in Commerce Manager, whether a scheduled fetch from a hosted feed address or a platform connection, now reads from the new platform.
Verify a new domain in the owning portfolio
A move to a new domain needs that domain verified. The pixel setup tutorial notes that verification proves the business portfolio controls the site, that Meta documents a meta tag, an uploaded file or a DNS record as methods, and that the registered root domain should be verified in the portfolio that owns the dataset, not in an agency's. Verify the new domain before launch, while the old one is still live. Afterwards, Events Manager may ask you to configure the events the new domain will use; follow the prompts the interface shows, as the tutorial advises, with the optimisation event first.
Update ad destinations and keep redirects
Using the redirect map, list every active ad whose destination changes and prepare the new links with their URL parameters. On launch day, change the links. The learning phase guide lists editing an ad's image, video or text and adding a new ad among the significant edits that can restart learning; a link change is not among the edits it lists, so change only the link and leave the creative alone in the same edit. Keep permanent redirectsA permanent server redirect telling browsers and search engines a URL has moved for good. from every old address for ads that were missed, for saved and shared posts and for catalog links that have not yet refreshed, and test that each redirect passes URL parameters through to the final page.
Test every event on launch day
As soon as the new site is live, walk the full journey with the test events tool in Events Manager: landing, product view, add to cart, checkout, a test order and any lead form. For each event, check that it appears once, with the intended name, value, currency, content identifiers and event ID, and that the server copy arrives beside the browser copy. Check Commerce Manager's diagnostics for the event-to-catalog match, preview a sample of ads to confirm their destinations, and run the tracking verification checklist across the rest of the stack. The next day, read the dataset overview for events from real traffic and the diagnostics tab for new warnings. If events are missing, the diagnosis page for pixel events not showing works through the causes in order.
Compare counts with orders for two weeks and record the move
For the first weeks after launch, compare received purchase events with the shop's order count each week. The Conversions API guide notes that server purchase events over a week should be close to the order count before attribution is applied, and it recommends noting a measurement launch date so that later analysis does not mistake it for a change in performance. Check the deduplicated share in the purchase event's detail, the size of each rewritten audience and the catalog match. Record the move in the account's change log and the measurement plan: the date, what changed, the faults found and when each was fixed. Leave campaigns alone while delivery settles on the restored signal, rather than adding edits of your own.
A kitchenware shop changes platform (illustrative)
Ivyclatter Kitchenware moves platform and domain
Ivyclatter Kitchenware, an invented online kitchenware shop, moved to a new shop platform and a new domain on the same day. Its inventory listed one dataset, nine events, server events from the old platform's partner integration, four custom conversions (two on URL rules), seven website audiences (five on URL rules), a catalog of 1,800 items and 46 active ads.
| Item | Old site | New site | Action |
|---|---|---|---|
| Dataset | Owned by the shop's portfolio | Same identifier installed | Declined the new platform's offer to create a pixel |
| Server events | Old platform's integration | New platform's integration on the same dataset | Event names and order-based event IDs matched before launch |
| Custom conversions on URLs | Thank-you path on the old domain | New confirmation path | Replaced one with a purchase-event rule, rewrote the other |
| URL-rule audiences | Old collection paths | New collection paths | Rules matching both patterns for the transition |
| Catalog | Parent product identifiers | Platform sends variant identifiers | Feed switched to variant identifiers |
| Ads | Old product URLs | New product URLs | 46 links changed, creative untouched |
The launch-day test events walk-through showed purchase, add to cart and view content arriving once each with values and event IDs, but Commerce Manager's diagnostics showed only 12% of events matching catalog items: the new platform sent variant identifiers while the feed still held parent ones. The team had planned the feed switch for the following week and brought it forward; by the next morning the match had recovered to 94%. Over the first two weeks, server purchase events ran at 97% and 99% of website orders, the deduplicated share held steady, and two URL-rule audiences that had stopped growing on launch day were growing again after a rule fix. The move went into the change log with each fault and its fix date.
Common mistakes
- Creating a new dataset for the new site. Everything built on the old one then has to be rebuilt and re-pointed.
- Installing the pixel twice. A partner integration plus a manual install duplicates every event.
- Forgetting the server route. The old platform's integration stops when the old shop closes, and purchases fall to whatever the browser alone reports.
- Leaving URL rules for the old paths. Audiences quietly stop growing and custom conversions stop counting.
- Changing catalog identifiers on one side only. Dynamic ads show the wrong products, or none.
- Verifying the new domain in an agency's portfolio. Ownership and event configuration end up in the wrong place.
- Relying on redirects for live ads. Update the links; keep redirects for everything else.
- Editing creative while changing links. Change the destination alone, so the edit is no bigger than it needs to be.
- Launching during a sale. A migration needs a quiet period in which a fault costs little and is easy to see.
