ga4-debugging-validation

ga4-debugging-validation is a skill for Claude Code from Ad-Superpowers/ad-superpowers-plugin. It costs 81 tokens per session (5,133 once invoked), scanned A, original, MIT.

A guide to finding and checking problems in Google Analytics 4 tracking. It explains DebugView, a GA4 screen that shows recent events and their details while you test a site.

In plain words
What is it for?
Use it to test tags in Google Tag Manager Preview, inspect events in GA4 DebugView, and investigate tracking that is not working.
Why use it?
It helps reveal missing events, incorrect parameters, and tags that do not fire before bad data reaches reports. It also supports checking tracking quality during development and audits.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the ad-superpowers plugin — 120 skills, 35 commands, 5 agents, 1 MCP server shipped together

Good fit Use it to test tags in Google Tag Manager Preview, inspect events in GA4 DebugView, and investigate tracking that is not working.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ad-superpowers/ad-superpowers-plugin/ga4-debugging-validation
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add Ad-Superpowers/ad-superpowers-plugin --skill ga4-debugging-validation
Clone the repo
git clone --depth 1 https://github.com/Ad-Superpowers/ad-superpowers-plugin

Made for: Claude Code.

Or install ad-superpowers, the plugin that ships this one along with the rest of its 120 skills, 35 commands, 5 agents, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for ga4-debugging-validation

README.md
[![agentmods](https://agentmods.dev/badge/skills/ad-superpowers/ad-superpowers-plugin/ga4-debugging-validation/github.svg)](https://agentmods.dev/skills/ad-superpowers/ad-superpowers-plugin/ga4-debugging-validation)
Your own site
<a href="https://agentmods.dev/skills/ad-superpowers/ad-superpowers-plugin/ga4-debugging-validation"><img src="https://agentmods.dev/badge/skills/ad-superpowers/ad-superpowers-plugin/ga4-debugging-validation/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for ga4-debugging-validation

Your own site · 80×15
<a href="https://agentmods.dev/skills/ad-superpowers/ad-superpowers-plugin/ga4-debugging-validation"><img src="https://agentmods.dev/badge/skills/ad-superpowers/ad-superpowers-plugin/ga4-debugging-validation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 81 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,133 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00081 $0.05133
Opus 5.5 $0.00032 $0.02053
Sonnet 5.5 $0.00016 $0.01027
Haiku 4.5 $0.00008 $0.00513

Measured 1mo ago against content hash 1a6242a5103c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ga4-debugging-validation scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugin/skills/ga4-debugging-validation/SKILL.md · 744 lines

How it starts

The opening of the file, as written. The whole thing — 744 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GA4 Debugging & Validation Guide

Complete guide for debugging GA4 implementations and ensuring data quality.

GA4 DebugView Setup

CONFIGURING DEBUGVIEW
======================

WHAT IS DEBUGVIEW:
├── Real-time event monitoring in GA4
├── Shows events within 1 minute
├── Including parameters and user properties
├── Perfect for development and QA
└── No impact on production data

LOCATION: GA4 Admin → Property → DebugView

METHOD 1: CHROME EXTENSION
───────────────────────────
1. Install "Google Analytics Debugger" extension
   └── Chrome Web Store → search "GA Debugger"

2. Activate extension (icon in toolbar)

3. Refresh page where GA4 is active

4. Open GA4 → Admin → DebugView

5. Select your device in dropdown

NOTE:
├── Extension must be ON
├── Can take 1-2 minutes for device to appear
└── Multiple devices may be visible

METHOD 2: GTM PREVIEW MODE
───────────────────────────
1. Open GTM → Preview

2. Enter website URL

3. Debug session starts automatically

4. Events are visible in:
   ├── GTM Preview panel
   └── GA4 DebugView

ADVANTAGE: See GTM tag firing + GA4 simultaneously

METHOD 3: DEBUG PARAMETER
──────────────────────────
Add parameter to URL:
https://example.com?debug_mode=true

OR in GTM tag configuration:
├── GA4 Configuration tag
├── Fields to Set
├── Field name: debug_mode
└── Value: true

OR via dataLayer:
gtag('config', 'G-XXXXXXXXXX', { 'debug_mode': true });

METHOD 4: MOBILE APP DEBUGGING
───────────────────────────────
iOS:
├── Xcode → Product → Scheme → Edit Scheme
├── Arguments Passed On Launch
└── Add: -FIRAnalyticsDebugEnabled

Android:
adb shell setprop debug.firebase.analytics.app [package_name]

Stop debugging:
adb shell setprop debug.firebase.analytics.app .none.

Interpreting DebugView

DEBUGVIEW INTERFACE EXPLAINED
==============================

MAIN SECTIONS:
┌─────────────────────────┬──────────────────────────────────────────┐
│ Section                 │ Shows                                    │
├─────────────────────────┼──────────────────────────────────────────┤
│ Device selector         │ Debug devices (choose correct device)    │
├─────────────────────────┼──────────────────────────────────────────┤
│ Timeline (left)         │ Chronological event stream               │
├─────────────────────────┼──────────────────────────────────────────┤
│ Event details (right)   │ Parameters of selected event             │
├─────────────────────────┼──────────────────────────────────────────┤
│ Top events (above)      │ Most recent events (quick overview)      │
└─────────────────────────┴──────────────────────────────────────────┘

EVENT COLOR CODES:
──────────────────
Green     → Automatically collected events (first_visit, session_start)
Blue      → Enhanced Measurement events (scroll, click, etc.)
Purple    → Custom events (your implementation)
Yellow    → Key Events (marked as conversions)
Red       → Errors or issues

CHECKING EVENT PARAMETERS:
──────────────────────────
1. Click on event in timeline
2. View "Parameters" section on right
3. Verify:
   ├── All expected parameters present
   ├── Values correct (types: string/int/double)
   ├── No empty values where data expected
   └── Parameter names exactly right (case sensitive!)

USER PROPERTIES:
────────────────
├── Scroll down in event details
├── "User properties" section
├── Check that custom user properties are correctly set
└── Persistent across sessions

COMMON ISSUES TO SPOT:
──────────────────────
├── Event not visible → Tag not fired
├── Parameters missing → DataLayer issue
├── Wrong values → Mapping/transformation error
├── Duplicate events → Multiple tags for same event
└── Events too fast → Possible bot/automation

Read the full file on GitHub · 744 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 744 lines · 81 tokens per session scan A 1a6242a5103c

Subscribe to this mod's changes

ga4-debugging-validation is a skill published in the GitHub repository Ad-Superpowers/ad-superpowers-plugin (5 stars, last pushed 29d ago), licensed MIT. It adds 81 tokens to every session and 5,133 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-11.

Related

Other skills, from other repositories

traffic-diagnosis

Systematically diagnose why traffic changed — spike, drop, or shift in mix. Follow these steps in order. Each step narrows the hypothesis.

surendranb/google-analytics-mcp · 34 tokens

incident-postmortem

Close the learning loop after a rescue or incident — reconstruct the timeline from actionlog, run root-cause analysis (platform / site / measurement / external), produce a structured postmortem document, distill reusable insights via /learn, and propose preventive guardrails. Use after a /rescue, a CPA spike, a…

logly/mureo · 150 tokens

ai-hive-a2a-cancel-handoff-check

A verification workflow for tasks handed from one AI agent to another using A2A, a protocol for agent-to-agent communication. It checks remote status, task identifiers, handoff outputs, and cancellation results.

wubin1836/ai-hive-agent-skills · 166 tokens

ai-hive-agents-api-session-recovery

A design guide for recovering long-running hosted-agent sessions, their execution events, and result files after interruptions.

wubin1836/ai-hive-agent-skills · 143 tokens

sealeap-amazon-featured-offer-loss-triage

Triage loss of the Amazon Featured Offer by checking account health, order defect signals, price competitiveness, offer and fulfillment state, listing classification, unauthorized sellers, and external price evidence before escalating. Use when the Buy Box or purchase button disappears or repeatedly returns. Do not…

xjli360/sealeap-amazon-ad-skills · 80 tokens

self-healing-agents

Self-Healing Agents are autonomous systems that detect their own failure modes and self-correct without human intervention.

itallstartedwithaidea/agent-skills · 27 tokens