Skip to content
Any platform

Conversion tracking stopped after a website redesign

Conversions in Google Ads, GA4 or Meta dropped sharply or stopped on the day a new site, theme or platform went live, while enquiries and sales carried on as normal.

Steps checked against the platforms' documentation on November 20, 2026.

Quick answer

Redesigns usually break tracking in predictable places: the tag container was not carried over, the thank-you page moved, the form plugin changed, or the CSS selectors your triggers relied on no longer exist. Start by opening the new site with GTM Preview or Tag Assistant, submitting a test lead, and checking whether the container loads once and the conversion tags fire.

1. The GTM container or Google tag is missing, or installed twice

New themes and platforms do not inherit code pasted into the old theme. Equally common is the opposite: the developer adds the container in the theme and through a plugin or platform integration, so every tag fires twice.

How to check

  1. 1Open the new site in Tag Assistant and check which GTM containers and G- or AW- tag IDs load, and how many times.
  2. 2Check several page templates, not just the home page: service pages, landing pages, blog, thank-you page and checkout.
  3. 3In GTM Preview, check whether the same tag fires twice on one event.

How to fix

  1. 1Install the container once, as high in the <head> as possible, on every page. On a CMS, use one method only: a platform integration or a manual snippet, not both.
  2. 2Remove hard-coded gtag or pixel snippets that duplicate tags already in GTM.
  3. 3Re-test with Preview on each template until each tag fires once.

2. The thank-you page URL changed

Many conversion tags and GA4 key events are based on a page path such as /thank-you. A redesign often renames it, removes it in favour of an on-page message, or adds a trailing slash or query string that no longer matches the condition.

How to check

  1. 1Submit a test lead on the new site and note the exact URL you land on, or whether you stay on the same page.
  2. 2Compare it with the Page Path or Page URL conditions on your GTM triggers and with any destination-based conversion actions.
  3. 3Check GA4 Realtime for the page view and the conversion event during your test.

How to fix

  1. 1Update trigger conditions to the new path, or better, move to a dataLayer success event that does not depend on URLs.
  2. 2If the old URL still exists, make sure it cannot be reached without submitting a form, or it will inflate conversions.
  3. 3Publish the container and repeat the test lead.

3. The form plugin or booking tool changed

Switching from one form builder to another changes how submissions happen. A form that used to reload the page may now submit in the background, sit in an iframe, or push a different dataLayer event, so the old trigger never fires.

How to check

  1. 1In GTM Preview, submit the new form and look at which events appear in the left-hand list.
  2. 2Inspect the form to see whether it sits in an iframe from another domain.
  3. 3Check the plugin docs for a success event or callback.

How to fix

  1. 1Rebuild the trigger around the new form's success signal: a dataLayer event, a thank-you redirect, or an Element Visibility trigger on the confirmation message.
  2. 2For embedded third-party forms, use the vendor's GA4 or Ads integration, or a parent-page message from the developer.
  3. 3Turn on Check Validation on any remaining Form Submission trigger so failed submissions are not counted.

4. New CSS classes, IDs or button text break click and form triggers

Triggers often filter on Form ID, Form Classes, Click ID, Click Classes or button text. A redesign usually renames all of them, so triggers stop matching without any error.

How to check

  1. 1In GTM Preview, click the button or submit the form and open the Variables tab for that event.
  2. 2Compare the current ID, classes and text values with your trigger conditions.
  3. 3Look for tags that now show under tags not fired for events where they should fire.

How to fix

  1. 1Update conditions to the new values, and ask the developer for stable id or data- attributes that will not change with styling.
  2. 2Prefer dataLayer events over CSS-based triggers for anything that counts as a conversion.
  3. 3Document the attributes tracking depends on, so the developer knows not to rename them.

5. The consent banner changed

A new cookie banner or consent platform may not send consent mode signals, may default everything to denied without updating on acceptance, or may block GTM entirely until consent, which changes what Google and Meta tags can record.

How to check

  1. 1Accept all cookies on the new banner, then check in Tag Assistant that consent updates to granted and the tags fire.
  2. 2Decline cookies and confirm what still fires matches your intended basic or advanced consent mode setup.
  3. 3In GA4 go to Admin > Consent settings, select the data stream and check for warnings about missing consent signals.

How to fix

  1. 1Configure the banner to set default consent and update it on the user's choice for analytics_storage, ad_storage, ad_user_data and ad_personalization.
  2. 2Make sure the banner integration loads before your tags read consent.
  3. 3Google notes consent signal notifications in GA4 can take 48 to 72 hours to update after a fix.

6. A domain change or redirects broke cookies, cross-domain and click IDs

Moving to a new domain or subdomain, adding a separate booking domain, or putting redirects in front of landing pages can split sessions and strip gclid, fbclid, _gl and UTM parameters, so conversions lose their source or fail to attribute.

How to check

  1. 1Click one of your own Google ads and confirm gclid is still on the final landing page URL after redirects. Do the same with a UTM-tagged link.
  2. 2Check that cross-domain domains in GA4 under Configure tag settings > Configure your domains include any new domains.
  3. 3Look in GA4 traffic reports for your own domain appearing as a referral, or for a jump in direct traffic after launch.

How to fix

  1. 1Have redirects pass query parameters through to the final URL.
  2. 2Update GA4 cross-domain settings and ad final URLs to the new domain, and make sure every domain uses the same tag ID.
  3. 3Re-check landing pages in Google Ads and Meta for old URLs that now redirect.

Stop it happening again

  • Add tracking to the launch checklist: a test conversion for every form, call link and checkout before and after go-live.
  • Export the GTM container and keep a list of the pages, selectors and events tracking relies on, and share it with the developer before the build.
  • Test the new site on a staging URL with GTM Preview before launch, not after.
  • Watch daily conversion counts for the first two weeks after launch and compare them with CRM leads.

Questions

4 questions

Open the site with GTM Preview, submit a real test lead through each form, and check that the container loads once and each conversion tag fires once. Then confirm the event in GA4 Realtime and, a day or two later, in the Google Ads conversion action status.

Usually, yes. A sudden doubling is most often a container or tag installed twice, or both a plugin and GTM sending the same event. Check in Tag Assistant how many times each tag fires.

Tracking starts recording again from the fix onward; missed conversions are not recovered. Smart bidding may need time to adjust after a period of missing data, so fix it quickly and note the dates for reporting.

Agree it upfront. The developer controls the code, but the agency usually knows what tracking depends on. Share the list of selectors, URLs and events before the build and test together on staging.

Got an account that doesn't add up?

Send us one account. We review it for free and send a short video of what's working and what isn't.