.png)
.png)
.png)
How to Stop Website Changes Breaking PPC Conversion Tracking
By Blackbird Marketing
Website changes can break PPC conversion tracking without making the site look broken. A new contact form, changed thank-you page, consent banner, tag manager setting or domain migration may stop Google Ads recording enquiries while the adverts continue spending.
The safest approach is to treat tracking as part of the website change, not as something to check weeks afterwards. Record what currently counts as a conversion, protect the tracking setup, test the live journey and compare the results after the change.
In short: Before changing a trade website, document every PPC conversion, preserve the relevant tags and settings, test calls and forms on the live site, and keep a rollback option. If tracking is not tested as part of the release, you cannot assume the numbers are still reliable.
What website changes commonly break PPC tracking?
Tracking usually fails when a change removes the event, tag or page condition that tells Google Ads an enquiry has happened. The advert may still receive clicks, but the action taken afterwards is no longer passed back correctly.
Common risk areas include:
Contact forms: A form may change from a thank-you page to an on-page message, or its submission event may use a different name.
Phone numbers: A new number, altered link or different mobile call button can remove the click event used to measure calls from the website.
Landing pages: A new URL, page template or redirect can leave tags behind or send paid visitors to a page where the expected conversion action does not exist.
Cookie consent: A new consent platform or altered settings may prevent advertising and analytics tags from firing until permission is given.
Tag Manager and analytics: Container changes, deleted triggers, renamed events or altered measurement settings can affect several campaigns at once.
Domain and hosting changes: Moving the site, changing subdomains or altering security settings can affect scripts, redirects, cross-domain measurement or form handling.
Website platform changes: Rebuilding a site in a different system may remove manually installed tags or replace code added to the previous template.
The important distinction is between a visual change and a measurement change. A new colour or heading may have little tracking impact, while a small change to the form confirmation or consent behaviour can affect the conversion data that informs bidding and budget decisions.
Start with a conversion map, not the website code
Before anyone edits the site, write down what a PPC conversion means for the business. For a trade company, this might include a completed enquiry form, a click-to-call action, a tracked phone call or a request for a quotation. Do not assume that every event in Analytics should be imported into Google Ads.
A simple conversion map should record:
The action being measured, such as a form submission or phone link click.
The page, button or event that confirms the action.
Where the conversion is configured: Google Ads, Google Analytics, Google Tag Manager or the website platform.
Whether it is a primary conversion used for bidding or a secondary action used for observation.
Which campaigns, landing pages or services depend on it.
Who owns access to the relevant accounts and website settings.
This inventory gives the web developer and PPC manager something specific to protect. It also exposes gaps. If a business cannot explain how a form submission is counted, it should not rebuild the form and hope the existing tracking survives.
Separate leads from weaker interactions
Not every measurable action has the same commercial value. A page view, button click, time on page and completed enquiry may all appear in reports, but they should not automatically be treated as equivalent PPC conversions.
Keep the primary conversion set focused on actions that represent a genuine sales opportunity. Other events can still be useful for diagnosis, but treating low-value interactions as completed leads can make campaign performance appear stronger than it is.
Create a pre-change tracking record
Take a baseline before the work begins. This is not about predicting an exact number of leads; it is about recording how the current setup behaves so that a post-launch problem can be identified.
Capture the following for each important conversion:
The conversion name and platform where it is configured.
The URL or interaction that completes it.
The tag, trigger or event involved, where that information is available.
The current form confirmation behaviour.
The phone numbers and call buttons shown on paid landing pages.
Any consent conditions that control whether tracking can run.
Test evidence, such as screenshots, browser checks or recorded test submissions.
Also save the current page URLs and note any redirects. A landing page may still load after a rebuild but redirect through several addresses, lose campaign parameters or display a different form. Those changes should be reviewed rather than treated as harmless technical details.
Keep the record with the project brief. A spreadsheet, ticket or release document is sufficient if it is clear and accessible. The aim is to stop the tracking setup becoming knowledge held only by one developer or agency account.
Agree a safe website change process
Tracking is most easily damaged when design, development, analytics and PPC work happen separately. The person changing the form may not know which event Google Ads relies on, while the person managing adverts may not know that the thank-you page has been removed.
Before the change goes live, confirm:
What is changing? List new pages, deleted pages, altered forms, phone number changes, consent changes, templates, domains and integrations.
What must remain? Identify the conversion actions, landing page URLs, campaign parameters and analytics relationships that are not meant to change.
Where will the work be tested? A staging site can reveal layout and form issues, but it may not reproduce every consent, redirect or advertising condition on the live domain.
Who approves the release? Assign responsibility for checking the site, tags and PPC account before launch.
How can the change be reversed? Keep a backup of the previous site or form configuration and know who can restore it if tracking fails.
A published process for Blackbird Marketing's website design service describes work in terms of review, plan, build and launch or improve. That is a useful way to think about tracking too: review the existing measurement, plan what must be retained, build with those requirements included, then test and improve after launch.
For a wider check of whether the website and paid activity are working towards the same commercial goal, see How to Tell Whether Your Trade Website Supports Your Digital Marketing Strategy.
Test the complete customer journey
Do not test only whether the tag appears in the page source. Test the journey a potential customer takes from landing page to completed enquiry, because tracking can fail at several points between the advert click and the reported conversion.
Test form submissions
Submit every important form using a controlled test. Check that the form validates correctly, the confirmation is clear, the submission reaches the intended recipient or system, and the expected conversion event is recorded in the relevant testing tools.
If the new site shows a message without changing the URL, confirm that the event fires once when the submission succeeds. If it uses a thank-you page, check that the page cannot be reached simply by refreshing or browsing directly, otherwise visits may be counted as conversions without a completed form.
Test phone actions
Check phone numbers on desktop and mobile, including header buttons, landing page buttons and contact sections. A visible number is not necessarily a tracked interaction, and a tracked click does not necessarily confirm that a call was answered or became a qualified enquiry.
Be precise about what the measurement represents. A website phone click, a call generated through an advertising feature and a genuine received call may be separate measurements. Record the distinction rather than reporting them as identical leads.
Test consent behaviour
Test the site both before and after the relevant consent choice. Confirm which tags are expected to run in each state and whether the consent platform has changed the event or delayed it.
Do not simply disable the consent mechanism to make testing easier and then assume the result reflects normal visitor behaviour. The test should reflect the setup that real visitors encounter, within the site's legal and privacy requirements.
Test paid landing pages and redirects
Open the exact landing page URLs used by campaigns and follow the journey from there. Check redirects, page loading, form visibility, mobile layout, phone links and campaign parameters. A page that works from the main navigation may behave differently when reached through an old advert URL or a tracking template.
Check the data after launch
A successful test immediately after launch is necessary but not sufficient. Check the account again after the site has received real visits, because live consent choices, browser differences, redirects and form integrations may expose issues that a single controlled test misses.
Compare:
Whether the expected conversion actions are still being received.
Whether the volume has dropped unexpectedly after the release.
Whether duplicate conversions have appeared.
Whether one landing page, device type or campaign is affected more than others.
Whether forms and calls are arriving in the business's normal enquiry channels.
Allow for reporting delays and normal changes in traffic before declaring a problem, but do not ignore a sudden loss of all tracked enquiries immediately after a release. Check the website journey and tag setup first, then review campaign and account settings.
It is also worth comparing platform data with real business records. This will not produce identical totals: some visitors refuse consent, some calls are missed, and one person may submit more than one form. The comparison is still useful for identifying a complete tracking failure or a sudden change in lead quality.
What to do when tracking has already broken
First, identify the date and scope of the change. Ask which pages, forms, phone numbers, templates, consent settings or containers were edited, and whether the problem affects all campaigns or only one landing page.
Reproduce the journey: Test the live page on relevant devices and record where the expected action stops being measured.
Check the release: Compare the current website and tag configuration with the last known working version.
Check the conversion definition: Make sure the event or imported action has not been renamed, removed, duplicated or changed from primary to secondary.
Check consent and scripts: Confirm that the relevant tags can load under the current consent settings and that scripts are not blocked by the new platform.
Restore carefully: If the change is clearly responsible and a safe backup exists, consider reverting while the cause is investigated.
Record the fix: Update the conversion map and release notes so the same issue is not recreated in the next update.
Avoid creating a brand-new conversion action simply because the original appears empty. That can produce duplicate reporting and break historical comparisons. Establish whether the existing action can be repaired before replacing it.
When should a trade business involve its web and PPC provider?
Bring in the people responsible for the website and paid advertising before a change if the work affects forms, phone numbers, landing pages, consent, domains, templates or analytics. Early involvement is usually more useful than asking someone to diagnose missing data after the site has changed.
Ask practical questions:
Which conversion actions will this change affect?
Will the current Google Ads, Analytics or Tag Manager setup be retained?
How will forms and phone actions be tested before and after launch?
Will old paid landing page URLs continue to work?
Who will check the live site and PPC account after release?
What is the rollback option if conversions stop recording?
Blackbird Marketing lists PPC for trades, digital marketing for tradespeople and website design among its services. Its published website information also describes websites as mobile-friendly and built to support enquiries, while its website design page sets out a review, plan, build and launch or improve approach. If a rebuild or landing-page change is being considered, you can review the business website service information and ask whether the proposed work suits the tracking requirements of the job.
Make tracking part of every future website update
The best protection is a repeatable release checklist. It should be used for large rebuilds and smaller changes that affect forms, buttons, URLs or consent behaviour.
List the current PPC conversion actions before work starts.
Back up the relevant website, tag and analytics configurations.
Record landing page URLs, redirects and phone actions.
Tell the developer which events and pages must remain intact.
Test form submissions, calls, consent states and mobile journeys.
Check live conversion reporting after launch.
Compare platform activity with real enquiries.
Document the change and retain a rollback route.
This turns conversion tracking from an afterthought into a release requirement. It also gives a trade business a clearer basis for deciding whether a website change has improved the enquiry journey or merely changed the appearance of the site.
Need a safer website and PPC handover? If a website change could affect forms, calls or paid landing pages, discuss the requirements before the build or update begins. Ask Blackbird Marketing about its business website service.
