What a website migration can break in an affiliate programme
The SEO migration guide treats any change of domain, protocol, address structure, platform, framework or templates as a migration, alone or several at once, and plans the organic side: the URL inventory, a one-to-one redirect map, staging checks, launch day and monitoring. The Google Ads migration guide and the Meta Ads migration tutorial carry the paid accounts. None of the three plans for the partners who link to the site and are paid on what they send.
The programme depends on the site in ways those plans do not look at. The tracking guide lays out the chain: a partner's link holds two identifiers, one for the partner and one for the click, as URL parametersA key and value appended to a URL after a question mark, such as a filter, sort order, session or tracking tag, that may or may not change the page.; any hop from the partner's page to the landing page can lose them; on arrival the identifier is read, kept on the advertiser's own domain and handed to the order at checkout; and a PostbackA server-to-server message reporting a conversion, install or in-app event back to the ad network or affiliate platform that should receive credit. reports the conversion from the server with the order reference, while a browser pixel stands by as a backup. A migration can touch every link in that chain on the same day.
| What the programme depends on | Where it lives | What a migration can do to it |
|---|---|---|
| Partner links and deep links | Partners' pages, emails, posts and feeds, outside the business's control | Send readers to a removed page, a redirect chain or the home page |
| Click identifier | The query string of each landing address | Strip it in a redirect, a domain change or a server rule that drops query parameters |
| Stored identifier | The advertiser's domain and the order record | Leave it unread by the new site or never passed to the new order |
| Postback and pixel | The confirmation step or the order event | Leave them listening to a page or event that no longer exists |
| Consent handling | The banner and the tags that follow its choices | Reset it on new templates, so tags fire too early or never |
| Codes | The shop's discount rules and the register of who holds each code | Lose them in the move, or apply them differently on the new platform |
| Partner feed | The product data partners build their pages from | Change addresses, identifiers or prices partners have not received |
When a link in that chain breaks, a partner may be the first to see it, which is the moment the tutorial on tracing missing affiliate conversions starts from: it works from what the partner can show to a repaired chain. This tutorial is meant to stop the gap opening. Changing affiliate platform is a different job, which the platform move tutorial runs while the website stays where it is; the two belong in separate releases.
Before you start
- The migration plan and its date. What is changing (domain, addresses, platform, templates, checkout), what is not, and who owns the project. The affiliate items go into that plan, not onto a separate list.
- The project's redirect map. The redirect map template lists the fields for each row, from the old address and the signals that rank it to the test result and the owner; partner destinations go into the same map, with partner sales among their signals.
- Partner traffic records. The links, deep links and feed the programme has issued; the landing pages of partner-tagged visits in analytics and in the server logs; clicks and conversions by partner from the platform, with order references and statuses; all over a period long enough to include partners' older pages as well as recent promotions.
- The integration record. The entry for every connection the migration will cut and remake, from the postback and the pixel to the feed and any order exports, kept as the tutorial on documenting marketing integrations describes.
- The terms and the partner list. The change-notice rule, the consent wording and the agreed process for adjusting commission after the fact, and the partners ranked by validated sales and new customers.
- Owners. A RACI matrix row for each affiliate item: who maps partner destinations, who tests the identifier, who rebuilds the postback, who tells partners and who reads the comparison afterwards.
- The peak calendar. Set the launch clear of the trading peaks, which the tutorial on planning a change freeze protects from risky changes, and once a Change FreezeA set period around a peak when changes that are hard to reverse are stopped while routine, reversible work continues through an agreed route. has started, a tracking fix goes through its exceptions route.
The steps
List everything the programme depends on
Start from the launch date and work back, as the backward planning framework describes, so the map, the staging tests and the partner notice each get a latest start. Then build the inventory from the programme's own records rather than from the new site's navigation: the destination addresses in the links, deep links and feed the programme has issued and in the onboarding pack; the landing pages of partner-tagged visits in analytics; the server logs, which the SEO guide's inventory also reads; and the platform's click records where they hold the destination. Rank each address by the sales its partner visits produced. Add the codes partners hold, the confirmation step or order event the postback fires on, the pixel and the consent hooks the tracking relies on. Include addresses that only old or dormant partners use. Old partner pages stay in front of readers: the content check tutorial warns that ranking pages go on displaying codes and prices that have expired, and the same pages go on sending clicks to addresses the new site may not have.
Add partner destinations to the redirect map
Give every partner landing address its own row in the project's Redirect MapThe table of every old URL and its new destination, one row per address, from which a site migration or URL change is built and then checked.. Each row gets the one-to-one destination the SEO guide asks for: the new page that serves the same purpose, reached in a single hop by a permanent redirect. The SEO guide treats old pages sent in bulk to the home page or to a category as soft not-found errors wherever they do not match; for a partner's reader, who clicked for one product, a loose destination can lose the sale as well. Where a product or range has gone, apply the SEO guide's rule for removed pages, the closest equivalent if one exists and otherwise removal, record the decision on the row, and send the partner a suggested replacement link with the notice. Rank the rows by the sales behind them, so the testing starts where the commission is.
Keep the click identifier through every redirect
For each redirect pattern on the new site, take a tracking link a partner really uses, not one you built, and follow it on staging from the partner's page to the landing page, watching the query string at every hop: the old domain to the new one, the old address pattern to the new, any regional or protocol redirect, any rule that adds or removes a trailing slash, and any server rule that drops query parameters. Where a rule drops the identifier, change the rule before launch instead of asking partners to relink. Read the affiliate identifier and the analytics tags separately: analytics can show the visit with its campaign tags intact while the identifier the network pays on has already gone.
Move storage and the postback to the new checkout
On the new templates, confirm that the identifier is read from the landing address, kept on the business's own domain and carried onto the order record, as the tracking guide describes. Rebuild the postback on the new platform's order event rather than on a page, as the tracing tutorial's fix does, and check that it carries the order's reference, value and status. Decide which event counts: an order created before payment and abandoned when payment fails is not the outcome a sale-based programme pays for. Keep the pixel as a backup with duplicates removed. Where the conversion fires through Tag Manager, Google's preview and debug documentation, as the debugging and preview tutorial walks through it, shows which tags fired on each event and which trigger condition failed; start it from the workspace that holds the rebuilt tags, because preview shows that draft rather than the version visitors receive. Last, test a click made on the old site that turns into an order on the new one: if the new site cannot see an identifier stored before the switch, write down which period is affected so those orders can be handled under the terms.
Test codes, consent and every payment route on staging
Replay a purchase from a partner's link on each route a customer can take: every payment method, guest and account checkout, phone and desktop, and an order that uses a partner's code. Codes that do not carry over have to be recreated on the new platform with the same owners, end times and eligibility; the discount code request SOP tests each code at the checkout, including a basket that should be refused, and the same test belongs here. Then repeat the doubtful routes with each choice the consent banner offers. Consent mode, which Google documents and the privacy and consent guide explains, starts tags from a default state and changes it when the visitor chooses on the banner; new templates can load tags before the default is set or never pass the choice on. The consent banner QA checklist is the gate for the banner itself. Losing a conversion after a refusal is the banner doing its job; losing one after the customer agreed is a fault to fix before launch.
Update the feed and the pack, and tell partners before launch
Partners who build pages from product data need the new Product FeedA structured file of a store's products, prices and availability used to build shopping and catalogue ads.: new addresses, new product identifiers if the platform changes them, and prices that match the new pages. Rewrite the links and creative in the onboarding pack, which the onboarding tutorial for new affiliates keeps in one place, and the instructions for building a Deep LinkA link that opens a specific screen inside a mobile app rather than its home screen. under the new address pattern. Then tell partners the date, what changes for them, that existing links keep working through redirects, which links are worth updating after launch, when the new feed goes live and whom to contact. The needs table in the key partners guide counts advance notice of range and price changes among what those partners need, so the highest-value partners hear first, from their named contact. Everyone else gets the notice the terms promise under the change-notice rule that the terms tutorial sets out.
Test real partner links on launch day
Once the site is live and the redirects are deployed, click through from a sample of real partner pages, beginning with the partners whose links carry the largest share of validated sales. Is the link live, does it land on the right new page, is the identifier still in the address bar on arrival, and does it reach the order? Place test orders through a few of them and confirm each records against the right partner, with the order reference, and appears in that partner's own report. Check that the feed has refreshed and the codes work at the live checkout. Keep the old domain and its redirects running for as long as the SEO guide advises from Google's documentation on site moves, because partners' pages, like every other site's links to the old addresses, never update themselves. For the rest of the project's launch-day sequence, use the website migration checklist.
Compare clicks, orders and conversions, partner by partner
For the weeks after launch, set three daily series side by side for each partner: the clicks the platform logged, the orders that carry a stored partner identifier and the conversions the platform recorded. Flag any partner whose conversion count drops suddenly, as the tracking guide advises, and read which series moved. Clicks holding while identified orders and conversions both fall points at that partner's links, the redirects they pass through or storage; identified orders holding while conversions fall points at the postback or consent handling; a fall on one payment route points at the order event. Comparing conversions with identified orders alone would miss the first case, because an order whose identifier was stripped drops out of both. The same pattern at every partner points at a rule or event the whole site shares rather than at one set of links. Reconcile the platform, the order system and analytics for the period, as the tracking guide asks each period, and write down anything not yet explained. The test click-to-sale journey the affiliate programme launch checklist asks for before a programme opens is the test to repeat while any gap remains unexplained.
Re-credit lost orders and record the move
For each fault the comparison found, record the date it started and the date it was fixed. Between those dates, find the orders that carry evidence of a partner's click, either the stored identifier or a matching click in the platform's logs where the identifier was lost, run them through the same validation as every other conversion, and submit the ones that pass through the adjustment process agreed with the network or platform, as the tracing tutorial does for a gap a partner reports. Tell each affected partner what happened, which orders were credited and what changed. Carry the adjustments into the month's close, which the month-end commission tutorial matches to the invoice. Then update the integration record with the new postback and feed, keep the old redirect rules on file with their reasons, and put the launch date in the programme's reporting history, so that a later comparison does not read the migration as a change in how partners performed.
Affiliate items in the migration plan
| Item | Before launch | Launch day | After launch |
|---|---|---|---|
| Partner destinations | One-to-one rows in the redirect map, ranked by partner sales; replacement links for removed pages sent with the notice | A sample of partner pages clicked through | Rows added for any partner link found on the wrong page |
| Click identifier | Every redirect pattern tested from real partner links | Identifier checked in the address bar on arrival | Alerts on per-partner drops |
| Stored identifier and postback | Rebuilt on the paid-order event, with the order reference | Test orders record against the right partner | Clicks, identified orders and conversions compared each day |
| Consent | Each banner choice tested on the new templates | Banner and tags checked on the live site | Loss after agreement treated as a fault |
| Codes | Carried over or recreated with owners, end times and eligibility, then tested | Codes checked at the live checkout | Codes on partner orders matched to the register |
| Feed and pack | New addresses and identifiers; pack links rewritten | Feed refresh confirmed | Partners' questions about the feed answered |
| Partners | Key partners called; everyone else given notice | A contact available all day | Adjustments explained to each partner affected |
| Records | Owners named; integration record updated | Launch time noted | Launch date in the reporting history; old rules kept on file |
A single page that changes address between migrations does not need this project shape: the SOP for changing a page URL already lists partner pages among the places an old address is used. The fundamentals hub sets tracking beside the other foundations the programme rests on.
A musical instrument retailer changes platform (illustrative)
Gostrevick Music moves to a new shop platform
Gostrevick Music, an invented online musical instrument retailer, moves to a new shop platform in late January, clear of its December peak. Every product and category address changes, and the checkout is new. Its affiliate programme, with 260 active partners, is hosted on a network; a server-side postback carries the order reference and a pixel stands behind it.
Working back from the launch date, the programme manager builds the inventory from the links and feed the programme has issued, the landing pages of partner-tagged visits in analytics and the server logs. Over the past 12 months partner visits arrived at 2,140 landing addresses, and 180 of them carried 83% of the sales those visits produced. Nine are pages for a discontinued keyboard range that a large review site still links to. The feed holds 3,600 product links, and 14 partners hold exclusive codes. The other 2,131 partner addresses go into the project's redirect map, each with a one-to-one destination; the 9 range pages are left, by mistake, to the project's catch-all rule for retired products.
On staging, a real tracking link from a guitar review site is followed through each redirect pattern. The new platform tidies addresses by removing parameters it does not recognise; it keeps the analytics tags but strips the network's click identifier. The rule is changed to keep it and every pattern is tested again. The first draft of the new postback fires when an order is created, before payment; moved to the paid-order event, it stops reporting 6 test orders whose payment failed. The 14 codes are recreated and tested, including an expired one that correctly fails.
Three weeks before launch the manager calls the 12 partners who produce the largest share of sales; the rest receive notice by email as the terms promise, with the date, the new feed address and a contact. On launch day 30 partner pages are clicked through. The review site's keyboard links land on the home page, because the catch-all rule sent the range pages there. Within the hour each of the 9 gets its own row pointing at the page for the range that replaced it, the closest equivalent, and the review site is sent the new links.
For the first fortnight the manager sets each partner's three daily series side by side. Across the programme they move together, except at 6 partners that link to old buying guides:
| Week, for the 6 buying-guide partners | Clicks logged by the network | Orders carrying a stored partner identifier | Conversions recorded by the network |
|---|---|---|---|
| Week before launch | 2,310 | 61 | 60 |
| Launch week | 2,280 | 27 | 26 |
| Second week after launch | 2,350 | 63 | 62 |
Their clicks held while both other series fell, which points at links, redirects or storage rather than the postback. Following one of their real links finds the cause: another team moved the buying guides late, under a redirect rule of its own that bypassed their rows in the map, and that rule dropped the query string. The rule is fixed on day 4. Matching the network's click logs for the 6 partners against orders placed between the fault and the fix, as the tracing tutorial allows, finds 33 orders with a matching click; 2 are returned, and the other 31 go through the network's adjustment process and into February's close. Each partner is told which orders were credited, and the launch date goes into the programme's reporting history.
Common mistakes
- Treating the migration as the web team's project alone. Organic addresses and paid destinations get mapped, and nobody maps the pages partners link to.
- Sending partner links to the home page or a loose category. A reader who clicked for one product has no reason to search the front of the shop or a whole range for it. Map one to one, and decide each removed page on its row.
- Testing from a link of your own. A partner's real link goes through the network's redirect and carries its identifier; a clean test link never meets the rule that strips it.
- Firing the postback on a page, or before payment. Fire it from the paid-order event on the new checkout, with the order reference.
- Forgetting codes and the feed. Codes that were lost in the move fail at the checkout, and a feed with old addresses keeps partners' pages pointing at redirects.
- Telling partners after launch. Partners who learn of the move from their own reports have only the missing sales to go on.
- Comparing conversions only with identified orders. A redirect that strips the identifier removes the order from both counts, so no gap shows. Keep the partner's logged clicks beside them.
- Moving the affiliate platform in the same release. Two changes to one tracking chain leave no way to tell which of them lost the sales.
- Reading partner results across the launch without a note. Put the launch date in the reporting history, so a gap is not mistaken for a partner's decline.
