GTM container monitoring

Where global monitoring watches requests leaving the page, container monitoring works inside Google Tag Manager itself: Monita deploys its approved tag template into your workspace and reports on every tag it sees fire — tag name, type, execution time, firing status, triggers and consent state.

Use it when GTM is your system of record and you want tag-level answers: did this tag fire, on which trigger, how long did it take, with what consent?

Before you start

• Connect the GTM integration with an account that has edit access to the container.
• Monita deploys changes to a workspace but never publishes — you always review and publish yourself.

Set up

1. Create a property in the app with source type GTM container.

2. Select the account and container, and the hostnames the container is deployed on.

3. Choose which tags to monitor — or monitor the whole container.

   Caution

   Make sure nobody is editing the container while Monita deploys its template — the deployment creates a new workspace revision.

4. Monita deploys its tag template, monitoring tag and variables into the workspace and reports what was created, updated or left unmodified.

5. Open GTM, review the workspace changes, then preview or submit as you would any release. Previewed tags fire normally, but preview traffic is kept out of your production data so it doesn’t skew detectors.

Adding or changing monitored tags

Rerun the deploy from the property’s manage view whenever you add tags you want covered — Monita updates its assets in a fresh workspace revision and you publish again. The GTM integration page covers reconnecting and permissions.

Verify

1. After publishing, browse the site and check the Network tab for POST requests to collect.monita.ai returning 204 — see Verifying network requests.
2. Tag fires appear in the property’s dashboards within a minute or two.
3. Nothing arriving? The usual cause is an unpublished container — walk through Deployment troubleshooting.