What a website move can break in LinkedIn Ads
The Insight Tag and conversions tutorial installs the tag and builds conversions on a site that stays still; this page is for the moment the site changes under an account that is already running. By then the account holds conversions with a history, retargeting audiences that fill slowly and campaigns that keep spending, so the job is to keep one tag from one ad account recording the same outcomes from new pages. The LinkedIn Ads hub describes the three jobs the tag does, and a move can interrupt any of them. The Insight Tag is LinkedIn's tracking tagAn ad platform's browser code that reports page views and events on a site back to the platform., and the steps below keep it, and everything that reads it, in place.
| What depends on the site | What LinkedIn reads or holds | What a move can do to it |
|---|---|---|
| The base tag | One tag from the business's own ad account, on every page, fired from one trigger | New templates, a new subdomain or a new form provider carry no container; a retired theme keeps its tag, or the new platform adds a tag of its own |
| URL conversions | A rule that matches the address the browser shows after the action | A new address structure, a language folder or a provider's own thank-you address can leave the rule matching nothing |
| Event conversions | An event the page fires on the confirmed outcome | The new form fires a different event, fires on the click or fires nothing |
| Consent wiring | The tag released when consent is given | A new banner records a choice but never tells the container |
| Website retargeting audiences | URL rules over the visits the tag records | Rules written for old paths describe pages that no longer exist, and these pools fill slowly even once the rules are right |
| Ad and message destinations | Every ad's link with its tracking parameters, including button and call-to-action links | Links point at addresses that redirect, drop their parameters or no longer exist |
| Lead Gen Form links | The required privacy policy link and the link in the confirmation message | Links go to pages or files that moved |
| Pages for named accounts | Company-list campaigns that send members to pages written for those accounts | The pages are merged or removed in the rebuild |
| Page and profile links | The page's website field and custom button, people's website and Featured links, event and newsletter links | Links go dead or arrive untagged |
| Reporting | A conversion register and a weekly comparison with the CRM | The starting position is lost, or definitions change on the same day as the site |
The site as a whole has owners elsewhere. The SEO guide to site migrations and the website migration checklist own the redirect map and the launch-day sequence, and the Google Ads and Meta Ads migration pages carry the same job for their platforms. This page covers the LinkedIn side only. It says nothing about LinkedIn that the guides on this site do not already say: where screens, limits or reporting delays matter, LinkedIn's help centre is the reference, and the page says so. The order of work below, from the sheet and the starting position through the freeze and the change windows to the launch-day order, together with treating a server route as a dependency, reading retargeting pools as slow to refill and leaving published items to the redirect map, is general practice and not a LinkedIn rule; what the steps say about LinkedIn's own behaviour comes from the guides this page links. A symptom that appears after a move has its own diagnosis page, listed after the steps.
Before you start
- The ad account, the tag and the company page, all under business logins. Read the Campaign Manager setup tutorial if they are not.
- Publish access to the tag manager containers of the old and the new site, or the developer who holds it.
- The migration plan: the launch window, which hostnames and address patterns change, which templates, form providers and booking tools are new, who owns the redirect map and how a rollback would work. The site project writes it; this page feeds it.
- Access to Campaign Manager for the person doing the work, granted by job as the setup tutorial describes, admin access to the company page, and the names of the people whose profiles, newsletter or events carry links to the site.
- A list of every campaign, live, paused and drafted, because a campaign switched on after the move carries its old addresses with it.
- The conversion register and the change log, if the account has them. If not, the second step starts the register and the last step opens the change log.
- A written plan of what counts. The measurement plan framework is where the actions worth counting are listed, and the move should leave that list as it is unless a change to it is made on purpose and dated separately.
- A browser with no content blockers, and its network view, for the tests.
The steps
List every address LinkedIn holds in one sheet
Make one sheet with a row for each place that holds an address or depends on one: where it lives, what it is, the address or rule it holds today, who can change it, what it becomes and when it was changed. Walk the account in this order. Start with the conversions, listing each URL rule and each event-specific conversion with the trigger that fires it, then the website retargetingAdvertising to previous visitors or engagers. audiences and the URL rules that define them, as covered by the targeting and Lead Gen Forms guide. Next take every campaign, including paused and drafted ones, and list each ad's destination, its tracking parameters and the button links of any message or conversation ad, as set out in the objectives and formats guide. Then take each Lead Gen Form: its privacy policy link and the link in its confirmation message. Finish with the website itself: where the tag lives today (a container, a theme, a plugin or all three), every thank-you address, every form provider and booking tool, every subdomain, and any server route that sends conversions.
Fill the sheet from the account rather than from the site's crawl. The addresses that ads and forms hold can be campaign landing pages, which, as the website migration checklist notes, a pattern-based map misses. Record why each rule and tag exists as you list it, and leave anything whose purpose nobody can state in place until it is understood; the Chesterton's fence framework makes that rule explicit for the clean-up at the end. One written definition per result, with each platform's event mapped to it, is what the guide to conversion events across platforms asks for, and the sheet is where any departure from it first shows up.
Record the starting position before anything changes
The sheet says what the account depends on; this step records how it performs while the dependencies still work, because after the move you can only say a count fell if you know what it was. For each conversion, note the count by campaign for the last full weeks, the rule or event that produces it, its type, value and attribution settings, and the date each was set, and keep these in the conversion register. For the LinkedIn-sourced leads in the CRM, record the same weeks, and note the gap between the two, since the platform's count and the CRM's differ for reasons that the conversions-higher-than-CRM diagnosis, listed after the steps, explains. Note the forecast size of each campaign audience that includes a website retargeting audience, list the roles and companies the website demographics view shows, and record each campaign's objective, budget and audience. Read all of it as ranges against the account's own history, not as single weeks; reading small numbers explains why a figure built on small counts can jump around by chance and needs that care.
Freeze everything that is not the move
From the first change to the end of the reading period, hold still what the move does not require: budgets, objectives, targeting facets, creative, attribution settings and values, and what each Conversion ActionA Google Ads definition of one action to count, such as a purchase or lead, with its source, category, counting method, value and conversion window. means. Then a change in results can be read as the move rather than as one of several things changed alongside it, which is the same one-change-at-a-time discipline the creative testing guide applies to ads. A redesign can arrive with a new offer or a shorter form, and those are decisions of their own: if the move changes what counts as a result, gate that change with the conversion goal change checklist and date it separately from the migration.
Give every address a destination in the redirect map
Hand the sheet's website addresses to whoever owns the 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., so that every address LinkedIn still points at has one new equivalent and none is mapped to the homepage. The redirect map template holds the table, and the page URL change SOP covers a single address changing. Redirects are the safety net for ads, posts, documents and saved links that are already out in the world, not the plan for ads you control: those should carry the new addresses once the pages exist. A redirect also needs testing with a tagged link, because one that drops the query string strips the campaign values that analytics reads, and the visit then looks like it came from somewhere else.
Prepare the tag, the consent wiring and the success events on the new site
Decide that there is exactly one tag, the business's own, and that one trigger covering every page fires it in the new container. If the retired theme carries a LinkedIn tag, or the new platform adds one, find out which ad account each reports to before launch and plan to keep one. If the old tag was hard-coded and the new site moves into a container, the tutorial on moving hard-coded tags gives the order. Walk every template and subdomain on the sheet using the template and subdomain step of the tag tutorial; a new form provider's thank-you pages and any booking tool are the first places to look.
Check consent next. A new banner is new wiring, so the question is whether its state still reaches the container, through consent modeA Google tag feature that adjusts what tags collect according to the visitor's consent choices. or whatever signals the banner exposes. The consent step of the tag tutorial is the reference for how the tag waits; the guide to wiring consent into the container sets out the wiring and the consent banner QA checklist tests the banner itself. Then agree the success events with the developers: each new form pushes the success event as the tag tutorial's event step sets out, under a name the container's trigger expects. Where other platforms already read that event, the one-data-layer tutorial shows how to feed each platform's tags from that one event. If the account also sends conversions from a server, treat that route as one more dependency: find who owns it, check it against the new site and test that one submission still counts once. How a server route is integrated and matched is left to LinkedIn's help centre, as the tag tutorial leaves it. Staging addresses differ from live ones, so the checks here prove that the tag loads and the events fire, while a rule is checked on the live site.
Change the rules and links in a fixed order on launch day
Change each item in the same window as the page it describes goes live: a rule written for an address that does not exist yet matches nothing, and a rule left on an address that has gone matches nothing either. A staged launch means a staged change. Within a window, work in this order and write each change into the sheet as it is made.
First confirm the tag loads on the live site. Then bring each URL conversion up to the address the browser displays after a real journey, using the existing conversion where the help centre allows its rule to be edited and otherwise detaching the old one in the same window, so that no outcome has two conversions attached, and re-point each event conversion's trigger at the new success event. Then bring the website retargeting rules up to the new addresses, including any rule that matches every page, and record the date each changed audience started; whether an existing audience's rule can be edited in place or the audience must be rebuilt is a question for the help centre, and either is recorded in the sheet. Then give the ads their new destinations, keeping the tracking parameters and leaving the creative as it was, so that any change in results can still be read as the move; whether a live ad's link can be edited or the ad must be replaced is a question for the help centre, and either is recorded in the sheet. Include the paused and drafted campaigns, the button links of message and conversation ads, and the pages written for named accounts that the traffic setup describes. Finally bring each form's privacy policy link and confirmation link up to date; whether an existing form's links can be edited in place or the form must be rebuilt is again a question for the help centre, and either is recorded in the sheet.
Run the destination, tag and conversion lines of the LinkedIn Ads launch QA checklist over every campaign that was edited; the checklist itself asks for another run whenever an audience is swapped or a form changes.
Test each conversion end to end with consent accepted and refused
Run the test step of the Insight Tag tutorial, linked at the start of this page, on the live site for every conversion on the sheet. That step holds the mechanics, and a move adds checks to it. Run each journey twice, once with consent accepted and once with it refused, because the new banner is new wiring, and confirm that nothing reaches LinkedIn when consent is refused. Count what one submission produces: it should show as one conversion, because two is the double count that the diagnosis of Campaign Manager running ahead of the CRM traces. Submit a live test lead through each Lead Gen Form and follow its confirmation link, since the tag does not count those submissions and the form's links are on the sheet. Record each pass in the register with its date.
Then widen the pass. The tracking verification checklist covers the other platforms' tags in the same sitting, and conversion paths after a release walks the paths themselves on the devices visitors use.
Update the links LinkedIn shows without a campaign
Not every link sits in Campaign Manager, and the same-window rule of the previous steps applies to these too. On the company page, check the website field and the custom button, which the company pages guide says should point at a page matching the action the button names; the guide also names a dead website link as a fault that weakens what the company's people post. Each person who posts for the business owns their own profile, so ask them to change the website, contact and Featured links, as set out in the personal branding guide, and give them the new addresses and the tagged versions. Upcoming events that use an external link, covered in the LinkedIn Events tutorial, and the next newsletter edition, covered in the newsletters guide, need the new addresses too; whether an existing event's link can be edited is a question for LinkedIn's help centre. Reissue each tagged link by way of the UTM link request SOP so that UTMURL tags identifying traffic source. values stay consistent.
Leave links already published in posts, documents and past newsletter editions to the redirect map. Whether and how a published item can be edited is LinkedIn's rule, and the plan should not depend on editing it.
Read the first weeks against the starting position
Each week, compare the conversions Campaign Manager reports with the LinkedIn-sourced leads in the CRM and set the gap beside the one recorded at the start. A gap that holds steady is a counting difference, a sudden fall is a break, and a count that jumps ahead is checked for a second conversion for the same outcome or an event that now fires on the click. Check the forecast size of each campaign audience that includes a website retargeting audience against its recorded size. These pools fill slowly, so a small pool while it is still filling is not a fault by itself, while a pool that has not moved at all once the tag is proven is the cue to check its rule against the new addresses. Open the website demographics view and confirm that the roles and companies arriving are the ones the campaigns aim at, which the tag tutorial offers as the quickest check on whether a campaign reached its roles.
Do not read the new pages' conversion rate as a tracking result. New templates can change how many visitors act whatever the tag does, and click counts will still differ from analytics sessions, which is covered in why platforms and analytics disagree. Compare campaigns with each other and the account with its own history. Hold budget, audience and creative changes until the reading is clean.
Retire the old tag and rules and write the change down
When the new tests have passed and the first weeks read cleanly, remove any copy of the tag that the release did not already remove, detach or archive any conversion that still counts the same outcome as another, and stop using any audience whose rule matches only addresses that no longer exist. Act on each only once its purpose is known, following the fence rule from the first step. Bring the conversion register up to date: each rule or event, the campaigns that carry it, and the attribution settings with their dates. Then write the move into the change logA dated record of changes made to tracking, accounts, reports, lists or rules, with who made each and why, so later movements in the figures can be traced. as one entry that lists everything it touched, using the habit set out in keeping a measurement change log, so a later break can be placed against it. Keep the sheet: it is the account's record of where addresses live, and the next move starts from it.
What a break looks like and where it is fixed
A move can produce several faults at once. Use the table to route each symptom to the page that diagnoses it. The end-to-end test from the testing step, run again, splits the problem into a site half and a campaign half; the table gives the first check for each symptom.
| Symptom after launch | First check | Where it is fixed |
|---|---|---|
| A conversion column reads zero while the site records the action | The test journey: does a LinkedIn request leave the confirmation page? | Insight Tag not tracking conversions |
| Campaign Manager runs far ahead of the CRM | One test submission: how many conversions does it produce? | Conversions higher than the CRM |
| Clicks arrive but the site records no sign-ups either | The landing pages on a phone, and whether each repeats the ad's promise | Clicks but no conversions |
| A retargeting campaign stops spending after the move | The audience's forecast size against its recorded size | The launch-day step of this tutorial for the rule; Campaign not spending for the other delivery causes |
| The tag is proven but fewer visitors convert on the new templates | The paths, forms and pages, not the tag | Conversion rate dropped after a redesign |
A hydropower controls maker moves its site (illustrative)
Tuhopril Controls moves to a new platform and a new address structure
Tuhopril Controls, an invented maker of control gear for small hydropower plants, moves its website to a new platform with a new address structure, a new form provider and a new consent banner. Its LinkedIn account has 3 live campaigns: a Lead Gen Form campaign offering an operator's guide, a website conversions campaign for demo requests and a company-list campaign that sends plant engineers at named operators to pages written for them. The marketing manager builds the sheet in the first week and finds 41 places that hold an address or depend on one: 6 conversion and audience rules, 6 form links (a privacy policy link and a confirmation link on each of 3 forms), 20 ad destinations (7 of them in paused or drafted campaigns), 2 links on the company page, 4 on profiles, 2 on events and 1 in the next newsletter edition.
| Where | What the sheet showed | What the team did |
|---|---|---|
| Demo request conversion | The URL rule matched the old thank-you address; the new form provider lands on its own address on a subdomain with no container | Added the container to the subdomain and had the conversion count the live address on launch day |
| Pricing-page audience | The rule matched the old pricing path, which is now at a new path | Had the audience match the new path at launch and wrote the date beside its recorded size |
| The tag | The retired theme still carried a hard-coded tag, and the new container carried the same one | Removed the old tag in the same release |
| Lead Gen Forms | The privacy policy link and the confirmation link of each form pointed at old paths | Had all 6 links lead to the new addresses; submitted a test lead per form and followed the link |
| Page, profiles, events and newsletter | The custom button and website field, 4 profile links (two of them founders' Featured links), 2 event links and 1 newsletter link | Had all 9 lead to the new addresses; reissued the tagged links |
The redirect test shows that a tagged link to the old contact page loses its parameters, so the developer corrects the redirect rule, and the ads carry the new addresses regardless. The launch-day tests pass with consent accepted and nothing leaves with it refused, but one test submission produces 2 conversions: a second conversion created during the project still sits beside the old one. The team keeps one, and the next test produces 1. In the weeks before the move Campaign Manager reported 8 demo-request conversions a week against 10 LinkedIn-sourced demo requests a week in the CRM; across the first 2 full weeks after it averaged 9 against 11, the same gap of 2. The pricing-page pool is still filling, so the team leaves the results that depend on it unread until it has grown, and it writes the whole move into the change log as a single entry.
Common mistakes
- Building the inventory from the site's crawl. The addresses that ads and forms hold can be campaign landing pages, which a pattern-based map misses, so list them from the account.
- Treating the redirect map as the plan for ads. Redirects are a net for links already out; the ads you control should carry the new addresses.
- Leaving two conversions for one outcome. If a replacement is created for the new thank-you page, detach the old one in the same window, or the outcome is counted twice.
- Changing a rule before its page goes live, or long after. An early change describes a page that does not exist yet; a late one describes a page that has gone.
- Testing one consent branch, or a single page. The tag has to be present on the page where each conversion happens, and has to stay quiet when consent is refused.
- Forgetting paused and drafted campaigns. They carry the old addresses into the day they are switched on.
- Letting the new platform add its own LinkedIn tag. Two tags from two accounts leave counts and audiences harder to read.
- Skipping the form links. The privacy policy link and the confirmation link can point at the website even though the form does not live there.
- Changing audience, creative or budget while the move is being read. The result can no longer be read as the move.
- Judging retargeting pools before they have had time to fill. They fill slowly; read them once they have grown.
- Closing the project at launch. The weekly comparison with the CRM is where a quiet break is caught.
