tracking-verify

Name: tracking-verify
Availability: InStock
Author: jtrackingai

Verifies GA4/GTM telemetry behavior via preview-driven QA on live sites.

134|39|Updated Apr 2, 2026

Search Tags:#playwright #schema validation #gtm #ga4 #event verification #tracking release #telemetry QA

Ready to run

npx skills add https://github.com/jtrackingai/analytics-tracking-automation --skill tracking-verify

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tracking-verify
Source: https://github.com/jtrackingai/analytics-tracking-automation/tree/main/skills/tracking-verify
Command: npx skills add https://github.com/jtrackingai/analytics-tracking-automation --skill tracking-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents broken GA4/GTM releases by verifying that the correct events fire and match the expected schema before publishing to production.

Core Features & Use Cases

Playwright preview QA for live event firing: Runs a real Chromium session to exercise the live site and confirm GA4/GTM behavior.
Failure interpretation and release readiness: Produces a health verdict by identifying blockers, selector mismatches, unexpected fired events, and expected failures.
Optional publish handoff with safety gating: Generates publish-ready artifacts and can stop the publish step by default when blockers exist or health is missing, supporting an explicit release workflow.

Quick Start

Tell your agent to run verification for the generated artifacts in your artifact directory, then review the produced preview report and health summary for release readiness.

Frequently Asked Questions about tracking-verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I verify GA4 and GTM events before publishing to production?▼

GA4 and GTM event verification uses Playwright to run a real Chromium session against your live site, exercising user interactions to confirm expected events fire and match the defined schema before release.

What does GTM preview failure interpretation look for during release readiness checks?▼

GTM preview failure interpretation identifies blockers, selector mismatches, and unexpected fired events by analyzing event-schema and GTM context artifacts. It generates a health verdict that gates the publish step by default when blockers exist.

Can I use Playwright to run event-tracking preview QA on my live site?▼

Yes, you can use Playwright to run event-tracking preview QA. It launches a real Chromium session to exercise your live site and confirm actual GA4 and GTM telemetry behavior against your schema artifacts.

How do I compare current tracking health to a prior baseline during a release?▼

You compare current tracking health to a prior baseline by running the event-tracking preview command with artifact inputs and optionally referencing the baseline. This generates tracking-health reports and updated workflow-state for release handoff.

Why does schema validation stop the publish step for GTM releases?▼

Schema validation stops the publish step to provide safety gating for GTM releases. It halts the publish handoff by default when health is missing or blockers exist, preventing broken telemetry from reaching production.