tracking-discover

Name: tracking-discover
Availability: InStock
Author: jtrackingai

Analyze crawl coverage, platform type, dataLayer events, and live GTM container IDs for a target URL.

134|39|Updated Apr 2, 2026

Search Tags:#web crawling #shopify #gtm #ga4 #datalayer #tracking plan #artifact bootstrap

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves the problem of not knowing what analytics tracking should be built before GA4 and GTM planning starts, including missing crawl coverage, unknown page grouping, and undetected dataLayer or live GTM configuration.

Core Features & Use Cases

Crawl coverage and platform detection: Analyzes a target site to detect the platform and how widely pages can be fetched, producing a reviewable baseline before schema work.
dataLayer and GTM container discovery: Detects dataLayer events and live GTM container IDs so you can design GA4 event plans that match reality.
Fresh artifact bootstrap for later phases: Generates an output root directory with site-analysis.json and workflow-state.json to resume grouping and schema work safely.

Quick Start

Run tracking-discover by analyzing your site and generating a new artifact directory for the next tracking-planning steps.

Frequently Asked Questions about tracking-discover

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

FAQPage Schema

How do I discover dataLayer events and live GTM container IDs on a website?▼

You can discover dataLayer events and live GTM containers by crawling a target URL with Playwright-based HTTP access, which detects active tracking configurations and outputs a site-analysis.json file for review.

What is the best way to detect Shopify platform tracking coverage before building a GA4 schema?▼

Detecting Shopify platform tracking coverage requires analyzing crawl coverage and platform type for a target site, producing a reviewable baseline artifact directory before starting your GA4 event schema work.

How do I bootstrap a tracking plan artifact directory for GTM and GA4 workflows?▼

You bootstrap a tracking plan artifact directory by running an analysis-only crawl of your target URL, which writes site-analysis.json and workflow-state.json files to a specified output root to safely resume grouping and schema work.

Does this web crawling tracking discovery require outbound network access?▼

Yes, this tracking discovery requires Playwright-based HTTP crawling with outbound network access to fetch site pages, and it will pause to ask for telemetry consent when it encounters unanswered consent prompts.

Can I use this to analyze crawl coverage and page grouping for analytics planning?▼

Yes, you can analyze crawl coverage and page grouping for analytics planning by detecting how widely pages can be fetched and generating a fresh baseline artifact directory before proceeding to detailed schema work.

Why does the tracking discovery crawl stop before detecting my dataLayer events?▼

The crawl stops when it encounters an unanswered telemetry consent prompt, requiring you to address the site's consent mechanism before it can proceed to detect dataLayer events and live GTM containers.