Files
our-claude-skills/.claude/commands/gtm-validator.md
Andrew Yim 6a10ce1333 docs: sync README, CLAUDE.md, AGENTS.md with latest skill changes
- Add 93-tui-designer to all doc files and directory layouts
- Remove phantom 42-jamie-journal-editor (directory never existed)
- Update GTM directory names: 61-gtm-manager → 61-gtm-editor,
  62-gtm-guardian → 62-gtm-validator in CLAUDE.md layout
- Fix skill count: README 64→62, AGENTS.md 52→62
- Add .claude/commands/ slash command definitions
- Add SEO comprehensive audit gotcha notes (JHR, SLA)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-21 12:52:59 +09:00

43 lines
1.5 KiB
Markdown

---
description: GTM QA - tag firing verification, trigger testing, naming conventions, cross-platform validation
---
# GTM Validator
Verify GTM implementations on live pages. Test triggers, validate dataLayer, check naming conventions.
## Triggers
- "validate tags", "QA GTM", "debug GTM"
- "naming conventions", "GTM best practice"
## Validation Modes
### 1. Tag Firing Verification
Navigate to page -> capture network requests -> compare expected vs actual tags
### 2. Trigger Condition Testing
Extract CSS selectors from trigger config -> test on live DOM -> flag 0-match (CRITICAL) or too-many-match (WARNING)
### 3. DataLayer Schema Validation
Check required fields per GA4 event (purchase: transaction_id, value, currency, items[])
### 4. Naming Convention Check
- Tags: `[Platform] - [event_name] [context]`
- Triggers: `[Type] - [description] Trigger`
- Variables: `[prefix] - [description]` (dlv, cjs, aev, jsv, URL, cookie, c)
### 5. Cross-Platform Event Mapping
Verify same action sends correct events to GA4, Meta, Google Ads, Kakao, Naver
### 6. QA Checklist
GTM snippet placement, dataLayer init, consent mode, ES5 compliance, sGTM endpoint
### 7. Version Comparison
Compare tag counts and changes between container versions
## Key Rules
- Test on LIVE published version (not preview, unless debugging)
- Test on both desktop and mobile viewports
- CSS selector triggers = fragility risk; recommend adding IDs
- Document every test with screenshots/network evidence