> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Google Tag Manager on Vortex IQ > Monitor traffic, conversion and tracking integrity from Google Tag Manager, and catch instrumentation breaks before decisions are made on bad data. Monitor traffic, conversion and tracking integrity from Google Tag Manager, and catch instrumentation breaks before decisions are made on bad data. No changes are made without the configured approval policy. Read-only operations do not modify the connected system; schedules, access scopes, API usage and data handling remain governed by Vortex IQ controls. [Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) ยท [How connecting works](/integrations/connector-catalogue) | **21** | **7** | **Build your own** | **Ready to build yours** | **106** | | ------------------- | ---------------- | ------------------ | ------------------------ | -------------- | | performance signals | automated checks | automated fixes | workflows | API operations | ## Monitor performance 21 performance signals. Signals with an alert band can raise Nerve Centre alerts; every signal supports a merchant-configured watcher. | Signal | Outcome | Alert behaviour | What it tracks | | ---------------------------------------------------------- | ----------------------- | --------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | | **Consent Coverage Gap (pixel firing pre-consent)** | Run operations | Merchant rule | Alerts for Consent Coverage Gap (pixel firing pre-consent). | | **Consent Coverage vs Marketing Pixels Live** | Protect revenue | Merchant rule | Consent Coverage vs Marketing Pixels Live, broken down by row. | | **Consent Mode Coverage %** | Protect revenue | Merchant rule | GTM-distinctive - share of ad / analytics tags correctly gated behind Consent Mode. Gaps = compliance + data-quality risk. | | **Container Version Status** | Run operations | Merchant rule | GTM-distinctive - whether the live version is the latest. Unpublished changes = the site isn't measured the way the team thinks. | | **Conversion-Tag Fire Count vs Ad-Platform Conversions** | Protect revenue | Merchant rule | If the GTM conversion tag under-fires vs what the ad platform expects, the merchant is mis-measuring ROAS. | | **Pixel Parity - GTM Tags vs Ad-Platform Pixels Expected** | Protect revenue | Merchant rule | Pixel Parity - GTM Tags vs Ad-Platform Pixels Expected, broken down by row. | | **Tag Manager Health Score** | Run operations | Merchant rule | Composite penalising paused tags, unpublished workspace changes, consent gaps, and unused-trigger clutter. | | **Tags Missing Consent Gating** | Control risk and change | Merchant rule | Tags with consent\_status = needed\_not\_set - fire before consent. Names exactly which to fix. | | **Unpublished Workspace Changes** | Run operations | Merchant rule | Workspace edits not yet published - stale workspaces drift from the live container. | | **GA4 Config Tag Fires vs GA4 Pageviews** | Protect revenue | Merchant rule | Description pending editorial review; the signal is live. | | **Tag Consent-State Distribution** | Control risk and change | Watch only | Tag Consent-State Distribution, shown by share. | | **Tags by Type** | Run operations | Watch only | Configured tags grouped by GTM tag type (GTM API exposes no per-tag fire counts, so this is a live inventory breakdown, not fire volume). | | **Unused Triggers (0 attached tags)** | Run operations | Merchant rule | Triggers attached to no tag - container clutter / cleanup candidates. | | **Container Version Count** | Run operations | Watch only | Description pending editorial review; the signal is live. | | **Days Since Last Publish** | Run operations | Watch only | Description pending editorial review; the signal is live. | | **Open Workspaces** | Run operations | Merchant rule | Description pending editorial review; the signal is live. | | **Paused Tags** | Run operations | Watch only | Description pending editorial review; the signal is live. | | **Total Tags in Container** | Run operations | Watch only | Description pending editorial review; the signal is live. | | **Total Triggers** | Run operations | Watch only | Description pending editorial review; the signal is live. | | **Unused Variables (0 references)** | Run operations | Merchant rule | Description pending editorial review; the signal is live. | | **dataLayer Variables** | Run operations | Watch only | Description pending editorial review; the signal is live. | ## Audit risks and opportunities A fix status appears only where the action, inputs, approval, verification and recovery controls are mapped. Candidate remediations are never executable. | Check | Severity | Outcome | Why it matters | Fix status | | ------------------------------------------------------------------------------ | -------- | ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------- | | **Core Web Vitals failing on mobile (LCP > 2.5s OR CLS > 0.1 OR INP > 200ms)** | critical | Grow revenue | Failing Core Web Vitals on mobile suppresses rankings sitewide and correlates directly with conversion loss; this is the field data Google actually uses. | Report only | | **CWV pass rate below 75% on mobile** | high | Customer experience | When fewer than three quarters of sampled pages pass Core Web Vitals, slow experiences are the norm rather than the exception for real visitors. | Report only | | **Lighthouse performance score below 50 on mobile** | high | Grow revenue | A mobile performance score below 50 means most shoppers meet a visibly slow store; speed is a ranking factor and a conversion factor at once. | Report only | | **Lighthouse SEO score below 90** | medium | Grow revenue | Lighthouse SEO failures are basic crawlability and metadata problems that suppress pages regardless of how good the content is. | Report only | | **Lighthouse accessibility score below 90** | medium | Customer experience | An accessibility score below 90 means common assistive-technology journeys are breaking; lost customers and legal exposure in several markets. | Report only | | **Render-blocking resources blocking > 500ms** | medium | Run operations | Render-blocking resources delay the first paint beyond half a second; the store feels slower than it needs to be on every single visit. | Report only | | **Total page weight above 3 MiB** | medium | Catalogue quality | Pages heavier than 3 MiB punish mobile and slow-connection shoppers hardest, exactly the visitors with the least patience for it. | Candidate remediation | ### Build your own automated fixes 7 checks report findings on Google Tag Manager today. Turn any finding into an automated fix with a Vortex IQ workflow: **13,885 read and write operations across 229 connectors** are available as building blocks, with approval, verification and rollback on every change. ## Automate approved work Vortex IQ is integrated with **38 read** and **68 write** operations across account s.containers.workspaces, account s.containers, account s.containers.workspaces.folders, account s.containers.versions, account s.containers.workspaces.templates, account s.containers.environments on Google Tag Manager. Combine them with anything from the **13,885 operations across 229 connectors** to automate the work in your own words. Changes follow the merchant's configured approval policy: the target, proposed change, affected records, risk, reversibility and verification plan are shown before execution. Read-only operations do not modify the connected system. [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=google-tag-manager) | Resource | Read operations | Write operations | | ----------------------------------------- | --------------- | ---------------- | | account s.containers.workspaces | 3 | 8 | | account s.containers | 4 | 5 | | account s.containers.workspaces.folders | 2 | 6 | | account s.containers.versions | 2 | 5 | | account s.containers.workspaces.templates | 2 | 5 | | account s.containers.environments | 2 | 4 | | account s.containers.workspaces.clients | 2 | 4 | | account s.containers.workspaces.tags | 2 | 4 | Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected. ### Ready to build your first Google Tag Manager workflow Pick a trigger, add the operations above as steps, and every step that changes data pauses for your approval. Monitoring and audits are live now and can start any workflow you build. *** *Generated from the connector capability graph. Counts reflect the servable registry after alias normalisation and de-duplication, and refresh automatically when the registry changes.*