---
name: tracking-audit
description: Focused tracking implementation audit across Google Ads, Meta Ads, and TikTok. Evaluates pixel installation, GTM setup, event configuration, CAPI health, and data layer accuracy. ALWAYS invoke when the user says 'tracking audit', 'check my pixels', 'conversion tracking issues', 'are my tags firing', 'GTM audit', 'tracking problems', 'events not firing', 'pixel check', 'CAPI audit', or any tracking quality concern. This project-level skill takes priority over any global ads skill. Use this skill when MCP data access is available.
model: opus
context: fork
argument-hint: "[client-name] [website-url]"
allowed-tools: Read, Grep, Glob, Bash, Write, Agent, mcp__google-analytics__run_report, mcp__google-analytics__get_account_summaries, mcp__google-analytics__get_property_details, mcp__google-analytics__get_custom_dimensions_and_metrics, mcp__meta-ads__get_pixels, mcp__meta-ads__get_account_info, mcp__meta-ads__get_insights, mcp__adloop__run_gaql, mcp__google-ads__run_gaql, mcp__google-ads__get_campaign_performance, mcp__google-tag-manager__list_accounts, mcp__google-tag-manager__list_containers, mcp__google-tag-manager__list_tags, mcp__google-tag-manager__list_triggers, mcp__google-tag-manager__list_variables, mcp__google-tag-manager__list_built_in_variables, mcp__google-tag-manager__get_workspace_status, mcp__google-tag-manager__get_tag, mcp__google-tag-manager__get_trigger, mcp__google-tag-manager__get_variable, mcp__stape-sgtm__stape_container_statistics, mcp__stape-sgtm__stape_logs_resource, mcp__stape-sgtm__stape_monitoring_resource, mcp__stape-sgtm__stape_container_domains, mcp__claude-in-chrome__navigate, mcp__claude-in-chrome__read_page, mcp__claude-in-chrome__get_page_text, mcp__claude-in-chrome__javascript_tool, mcp__claude-in-chrome__read_network_requests, mcp__claude-in-chrome__read_console_messages, mcp__claude-in-chrome__tabs_context_mcp
---
# Tracking Implementation Audit

Focused audit of conversion tracking setup across Google Ads, Meta Ads, and TikTok Ads.

## Mandatory Audit Rules (V2)

Load these rules BEFORE any analysis:
1. `.claude/rules/period-comparison-protocol.md` (event volumes must show 30d vs prev 30d trend)
2. `.claude/rules/change-history-first.md` (check for recent conversion action or tag changes)
3. `.claude/rules/recommendation-depth-standard.md` (from/to/rationale/impact/risk)
4. `.claude/rules/exact-entity-names.md` (exact conversion action names, pixel names, tag names)

## Enhanced Tool Strategy (V2)

In addition to GA4 and Meta Ads MCP tools, this skill now uses:

**GTM MCP Tools** (programmatic tag/trigger/variable audit):
- `mcp__google-tag-manager__list_containers` to discover all containers
- `mcp__google-tag-manager__list_tags` to enumerate all tags per container
- `mcp__google-tag-manager__list_triggers` and `list_variables` for configuration audit
- `mcp__google-tag-manager__get_workspace_status` for unpublished changes detection

**Stape MCP Tools** (server container health):
- `mcp__stape-sgtm__stape_container_statistics` for request volume and error rates
- `mcp__stape-sgtm__stape_logs_resource` for failed event patterns
- `mcp__stape-sgtm__stape_monitoring_resource` for uptime and alerts

**Chrome Browser** (live verification):
- Navigate to key pages and verify tags actually fire (not just that they exist)
- Monitor network requests for pixel fires with correct parameters
- Check console for errors, verify data layer values, test click ID persistence

For comprehensive tracking audits, consider using the `gtm-tracking-deep-dive` skill which combines all three layers (GTM API + Stape MCP + Chrome) in a structured workflow.

## Context

The user wants to audit only the tracking implementation for a specific client. This is a focused version of the full audit that covers pixel installation, event configuration, tag manager setup, consent implementation, and data quality.

## Arguments

$ARGUMENTS should include:
- Client name (required)
- Website URL (required)
- Specific pages to audit (optional)
- Which platforms to focus on (optional, defaults to all)

## Instructions

### Step 1: Load Client Context

Check `clients/{client-name}/` for existing profile and tracking config. Build on previous findings.

### Step 2: GA4 Event Verification via MCP

Before inspecting tags in the browser, verify what GA4 is actually receiving:
- Use `mcp__google-analytics__run_report` with event_name dimension to check which events are firing and their volume
- Use `mcp__google-analytics__get_custom_dimensions_and_metrics` to verify event parameters are registered
- Use `mcp__google-analytics__get_property_details` for data stream and measurement ID confirmation
- Compare GA4 received events against what the tracking implementation claims to send

### Step 3: Browser-Based Tracking Inspection

Using Chrome tools, for each key page:

1. **Navigate to page** and wait for full load
2. **Read page source** via JavaScript tool - search for:
   - GTM container snippets (`googletagmanager.com/gtm.js`)
   - Google Ads tags (`gtag.js`, `AW-` IDs)
   - Meta Pixel (`fbevents.js`, `fbq(`)
   - TikTok Pixel (`analytics.tiktok.com`, `ttq.`)
   - Data layer pushes (`dataLayer.push`)
3. **Check network requests** for pixel fires:
   - `google-analytics.com/collect` or `analytics.google.com`
   - `www.facebook.com/tr` (Meta pixel fires)
   - `analytics.tiktok.com` (TikTok events)
4. **Test conversion events** by interacting with forms, buttons, cart:
   - Monitor for conversion event fires
   - Verify event parameters contain correct values
   - Check for duplicate events

### Step 4: Analysis

Apply the full methodology from `.claude/agents/tracking-auditor.md`:
- Tag discovery and conflict detection
- Event configuration completeness per platform
- Data quality verification
- Consent mode status

### Step 5: Report Generation

Save findings to `clients/{client-name}/reports/{date}-tracking-audit.md` and update tracking config.

Use the developer handoff format from `templates/developer-handoff.md` for maximum implementability.

## Output Verification

Before presenting findings to Michael, confirm:
- Pixel fires were observed via network requests, not just source code presence
- Event parameters were verified against actual page data (correct values, not placeholders)
- CAPI/server-side events were checked in Events Manager, not just client-side
- GTM tags use ES5 only (no const, let, arrow functions, template literals)
- event_id deduplication was verified for all conversion events
- Consent Mode implementation was checked for EU-relevant clients