6 GTM Web Container

GSS creates and updates the web container’s required variables, triggers, and tags in your selected GTM workspace. Approve each row’s proposed change.

Note: This step content was written for the original dual-run architecture and is being updated for the current setup workflow. The guide overview reflects the current approach.

This step is being finalized. Content is accurate but will be updated and expanded before full release.

Deliverable

Web container sends equivalent event traffic to both GA4 properties.

Validation

This step covers the web container and the browser page itself. Configure creates or updates the required GTM variables, triggers, and tags in the GSS workspace, then detection re-runs. The required GTM items panel above shows which items are Ready, Missing, Changed, or ambiguous so you can audit the result without leaving the page.

The page-level checks below still need to pass: the GTM snippet must be present in the page <head> with a noscript fallback immediately after the opening body tag. Open your live or test page and inspect the HTML — this part isn’t something GSS can write into your site, only verify against it.

After that, use GTM Preview and the browser network panel together to confirm both config tags fire and that browser-side and server-routed collect requests return successful responses. If the site uses the first-party loader profile, also verify the first-party loader path and its network behavior.

Step Values

Field Current value
GTM Web Container Pending
Workspace Pending

6.1 Validate Web Container Configuration

Click Create on each Missing item, Reset on each Changed item, and Pick on each Multiple-matches item, then Re-check. The item cards show what is Ready, Missing, Changed, or has multiple matches.

Checks

  • HTTP GTM snippet is present in the page <head> section.
  • HTTP GTM noscript iframe is placed immediately after the opening <body> tag.
  • HTTP GTM snippet references the correct web container ID.
  • API GTM variable for browser measurement ID exists in workspace.
  • API GTM variable for server measurement ID exists in workspace.
  • API GTM variable for server container URL exists in workspace.
  • API Google Tag referencing browser measurement ID exists and fires on Initialization.

6.2 Verify Browser Tag Fires via GTM Preview

Click the Preview button to connect Tag Assistant to your site. On your Tag Assistant page, validate the checks below:

Checks

  • Browser GA4 config tag fires on page load.
  • Browser GA4 collect request returns HTTP 200.

Documentation

Fields recorded during this step.

Field Description
GTM Web Container GTM web container and its public ID.
Workspace GTM web workspace used for edits.
← Step 5 Step 7 →

Use the app to validate this step automatically.

Request access