Switching a live site from one Google Tag Manager container to another looks like a five-minute job: swap one snippet for another. In practice, the step that breaks most often is the one the business cares about most — contact-form lead tracking. The safest approach is to rebuild and test every conversion in the new container, run both containers side by side for a short, controlled window, and only then remove the old snippet. This post is the checklist we follow at Centaur Strategies when we migrate a WordPress site to a new container, and why each step is there.
Observation: form conversions are what usually fall silent
When a container migration goes wrong, pageviews rarely disappear. GA4's configuration tag is easy to recreate, so traffic reports look normal. What disappears quietly is the custom work: form-submission triggers, data-layer events pushed by a form plugin, thank-you-page conditions, and the variables those triggers depend on. Because traffic still looks healthy, nobody notices until the monthly report shows zero leads for a site that had real enquiries.
Evidence: why the old setup does not carry over cleanly
A GTM export and import copies tags, triggers and variables, but it does not copy the context those items relied on:
- Built-in variables (Form ID, Form Classes, Click URL) must be re-enabled in the new container. A trigger that references a disabled built-in variable never fires.
-
Form plugins change markup. If a form was rebuilt or updated since the original trigger was written, a selector such as
form#wpforms-form-123may no longer match. - Thank-you-page triggers depend on URLs that may have changed after a redesign or a staging-to-live move.
- Consent settings in the new container may block tags that the old container fired by default.
Analysis: what to rebuild, not just import
Treat the import as a starting draft. For each conversion, confirm three things in Preview mode on a staging copy of the site:
- The trigger fires once per genuine submission — not on page load, not on a failed validation, not twice.
- The event reaches GA4 with the expected event name and parameters (check DebugView).
- The event is marked as a key event in GA4, so it counts as a lead in reports.
A submission listener based on the form plugin's own success event (or a data-layer push on success) is more reliable than a generic "Form Submission" trigger, which can fire before server-side validation finishes.
Implications: the overlap window matters
Running both containers at the same time can double-count events. Removing the old container before the new one is verified creates a gap in lead data. The practical compromise is a short overlap where the old container's GA4 tags are paused, but the container itself stays installed so it can be restored quickly.
Options
- Hard cutover: swap snippets in one deploy. Fast, but any missed trigger means lost data until someone notices.
- Staged cutover: install the new container on staging, verify every conversion, then deploy to live with the old container's conversion tags paused for a few days before removing it.
- Rebuild from scratch: skip the import and recreate only the tags still in use. Slower, but it clears out years of unused tags.
Recommendation
Use the staged cutover. Verify every form conversion on staging in Preview mode and GA4 DebugView, deploy the new container with the old container's conversion tags paused, compare lead counts against the form plugin's own entry log for a few days, and remove the old snippet only when the two numbers agree. For sites with a long tag history, combine this with a selective rebuild rather than a blind import.
We document setups like this as part of our analytics and website work at Centaur Strategies, a full-service digital agency in San Diego.

Top comments (0)