tracking-audit

Name: tracking-audit
Availability: InStock
Author: ceekay1901

Validate campaign and website tracking setups for missing, duplicated, or inconsistent analytics tags.

Updated Jul 8, 2026

Search Tags:#utm #tracking #consent #ga4 #campaign audit #pixels

Ready to run

npx skills add https://github.com/CeeKay1901/pilot-skillmarkt --skill tracking-audit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tracking-audit
Source: https://github.com/CeeKay1901/pilot-skillmarkt/tree/main/skills/tracking-audit
Command: npx skills add https://github.com/CeeKay1901/pilot-skillmarkt --skill tracking-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you verify whether a campaign or website is tracking data correctly before launch, so you can avoid missing, duplicated, or misleading analytics.

Core Features & Use Cases

UTM Validation: Checks whether source, medium, and campaign parameters follow a consistent naming convention.
Event Verification: Confirms that GA4 and pixel events exist, fire once, and are named consistently.
Consent Review: Flags cases where tracking may start before user consent or where consent is not propagated properly.
Use Case: Use it when a campaign report looks wrong, conversions are missing, or you want a pre-launch sanity check for analytics setup.

Quick Start

Ask the skill to audit your campaign tracking setup and return a clear pass, warning, or blocker report with concrete fixes.

Frequently Asked Questions about tracking-audit

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

FAQPage Schema

How do I audit my website tracking setup before a campaign launch?▼

To audit website tracking before a campaign launch, you need to validate UTMs, verify GA4 and pixel events fire once, and check consent-gated activation. This process checks tag configuration and event naming to return a pass, warning, or blocker report with concrete fixes.

Why does my GA4 event fire twice or not at all during campaign tracking?▼

GA4 events fire incorrectly due to duplicated or missing analytics tags. An audit verifies event firing logic and naming consistency to pinpoint configuration errors, ensuring your tracking tags execute exactly once per intended user action.

What is the best way to check if Meta and LinkedIn pixels respect user consent?▼

Checking Meta and LinkedIn pixel consent behavior requires reviewing consent-gated activation logic. An audit flags cases where tracking starts before user consent or where consent parameters are not properly propagated to your pixels.

Can I validate UTM parameter naming conventions for an existing analytics setup?▼

You can validate UTM parameters by checking whether source, medium, and campaign values follow a consistent naming convention. This structured review prevents misleading analytics data caused by inconsistent or malformed UTM tags across your campaigns.

Does this tracking audit work for troubleshooting missing conversions in GA4?▼

Yes, troubleshooting missing GA4 conversions is a primary use case. It validates whether your event tracking tags exist and fire correctly, helping you identify and resolve configuration gaps when a campaign report looks wrong.

What do I need to check before launching a campaign to avoid misleading analytics?▼

Before launching a campaign, you need to check tag configuration, event naming, firing logic, and consent behavior. This structured pre-launch sanity check identifies missing, duplicated, or inconsistent analytics tags to prevent misleading data.