How to Test Google Tag Manager Before You Publish

To test Google Tag Manager before you publish, build the change in its own workspace, click Preview to run that draft on your real site through Tag Assistant, and send a real test lead while Chrome's Network panel records what the conversion tag sends. Publish only when that request carries the right conversion ID and label, with version notes that let you put the previous version back in one step.

Start here

Before you click Preview

Check 1: Is the change in a workspace of its own?

WhereGoogle Tag ManagerOverviewManage Workspaces

Do: In the Pending changes section, open the three-dot menu, select Manage Workspaces, then Add, and name the workspace after this change (Google: workspaces).

You should see: Only this change's tags, triggers and variables in the workspace. Its name and description may later become the version name and description, so make them say what changed.

If not: If someone else's unfinished edits share your workspace, publishing it ships them too. Create a new one: regular accounts allow 2 custom workspaces besides the default.

Check 2: Does a staging site need its own environment?

WhereGoogle Tag ManagerAdminEnvironments

Do: If you have a staging server, click New, enter a Name, click Create, then copy the code from the environment's Actions menu > Get Snippet into the staging site only (Google: environments).

You should see: Your environment under Custom Environments. A version published to it stays off the live site, which the default Live environment serves.

If not: No staging server? Skip this check. Preview in check 3 runs your draft on the live site in your browser only, and each environment's Share Link preview needs no snippet.

Careful: Keep the standard container snippet on the production site; Google designed environment snippets for non-production sites.

Run the draft for real

Check 3: Does Preview connect to the page your ads land on?

WhereGoogle Tag ManagerWorkspacePreview

Do: Enter the landing page URL, click Connect, then go back to the Tag Assistant tab and click Continue (Google: preview and debug).

You should see: Connected in the bottom right of your site. Preview shows the site as if the current draft were deployed, and only your browser, or people you share the session with, sees it.

If not: If the page breaks, uncheck Include debug signal in the URL and connect again. Other connection fixes are in checking conversion tags with Tag Assistant.

Check 4: Do the page-load tags fire, and only those?

WhereTag AssistantSummaryTags

Do: Select the landing page's events in the left column and open the Tags tab.

You should see: Your Google tag and Conversion Linker under Tags Fired, and the lead conversion tag under Tags Not Fired, since no lead has been sent yet (Google: Summary > Tags).

If not: A conversion tag that fires on page load has a trigger that is too broad. Narrow it, save and preview again.

Careful: A tag under Tags Not Fired with rows under Required Additional Consent is blocked by a consent check, not by its trigger.

Check 5: Does only a successful submit fire the conversion?

WhereYour siteLead form

Do: Send the form for real with an obvious test name and an inbox you own, then click the new event in Tag Assistant. Send it once more with a required field left empty.

You should see: The conversion tag under Tags Fired once, on the successful submit only. On a Form Submission trigger, Check Validation makes it fire only if the form is successfully sent.

If not: If the failed attempt fired the tag, turn on Check Validation. If no submit fires it, the form may override the browser's submit event: read the Data Layer tab for what the form pushes (Tag Assistant) and trigger on it with a Custom Event trigger.

Careful: Tell whoever follows up leads that a test is coming, and delete the test record afterwards.

Check 6: Does the conversion request leave the browser?

WhereChromeDevToolsNetwork

Do: Before you submit, open the Network panel and check Preserve log, which keeps requests across page loads (Chrome DevTools). Submit, then type /conversion in the filter box, or collect for the GA4 hit (Google Ads help).

You should see: A request to googleadservices.com/pagead/conversion/, or google.com/pagead/1p-conversion/ on some browsers, where the number after /conversion/ is your conversion ID and the characters after label= are your conversion label (Google Ads help). The request's Payload tab shows its query string parameters.

If not: Another ID or label means the tag is most likely tied to a different conversion action; copy both again (where to find them). No request while Preview shows the tag fired: turn off ad blockers, which can stop Google tags.

Check 7: Does consent start and update as your visitors see it?

WhereTag AssistantOutputConsent

Do: Accept your cookie banner, select the earliest Consent event in the Summary, open the Consent tab of your tag's output, then repeat with the most recent one (Google: consent debugging).

You should see: Values in the On-page Default column at the earliest event, set before any tag fired, and in On-page Update at the most recent one, after you accepted.

If not: An empty tab means consent mode is not implemented on the page; consent mode v2 in Tag Manager covers the setup.

Careful: Defaults can differ by region, so a test from another country can show a state your visitors never get; Google says to repeat these checks with different simulated locations.

Publish so you can undo it

Check 8: Does the version say what changed?

WhereGoogle Tag ManagerSubmit

Do: Keep Publish and Create Version, read Workspace Changes, enter a Version Name and Version Description, and click Publish (Google: publishing). In the description, note what you tested: the form, the page and the test lead's date.

You should see: Only your changes under Workspace Changes. Its More Actions menu shows each element's differences between versions.

If not: From the same menu, abandon any change you did not mean to ship, then publish.

Careful: With custom environments, pick the target under Publish to Environment; publishing to a custom environment does not change the live container.

Check 9: Does live match Preview, and can you roll back?

WhereGoogle Tag ManagerVersions

Do: Connect Tag Assistant to the live landing page and send one more test lead. With Tag Manager you may first need to select Debug live version in the Tag Assistant window (Google Ads help).

You should see: The same tags fire as in Preview, and your version shows a date in the Published column, Tag Manager's publish history.

If not: If live behaves differently, open Versions, click the last good version and select Publish from its actions. To repair from that state, select Set as Latest Version, which replaces your draft with it (Google: versions).

Can an agent run these checks?

Lauren Tan, an engineer at Cursor, said in a recorded talk that verification is the most important skill to have when you work with agents: it should run the thing "for real" instead of guessing, or you stay the verifier and the bottleneck. A container is the same: Preview and a real submit settle what reading tag settings cannot. My own agents load the public pages of practices I research in headless Chrome and capture the network requests (gtm.js, the gtag config, any conversion request), always read-only and never submitting a form. That shows which tags load and what a page sends; the real submit in check 5 stays with a person. One of their findings, consent denied with no banner, held only because the check ran from Bulgaria; Wix's help says that on a site without a banner, visitors from countries that require consent send no data to Google Analytics, so I withdrew it.

After the container is live

Passing all nine checks shows that the browser sends a lead to Google Ads with the right ID and label. It cannot tell you which leads became a booked appointment or a customer, because that answer lives in your CRM or phone system. Sending it back to Google Ads is the marketing analytics work I do.

Frequently asked questions

Does Google Tag Manager preview mode send data to Google Ads and GA4?

Yes. Preview lets you browse your site as if the draft were published, so a tag that fires sends its request, and each time a Google Ads conversion tag runs it calls Google's conversion URL. Give test leads an obvious test name and delete them from your CRM afterwards.

How do I preview an older version of a GTM container?

Click Versions in the top navigation of your workspace, find the version, click More Actions and select Preview. The same menu has Share Preview, which gives you a link that lets a colleague open that version in preview mode on your site.

How do I roll back Google Tag Manager to a previous version?

Open Versions, click the version that worked and select Publish from its actions. To keep fixing from that state, select Set as Latest Version, which replaces your current draft with it. Versions keeps the publish history: when each version was live and who published it.

Can I test GTM changes on a staging site without changing the live container?

Yes, with environments. Create one under Admin > Environments, install its snippet on the staging site and publish versions to it; changes published to a custom environment do not reach the live container. Without a staging server, Preview tests the draft in your browser only.