analytics-tracking_skill

Overview

This skill creates precise, technical implementation plans for Google Tag Manager and platform pixels. It delivers step-by-step GTM architecture, data layer specs, tag/trigger configuration, and validation checks focused on accurate conversion tracking and privacy compliance.

How this skill works

I inspect the conversion points, current tag inventory, and site code to produce a deployable plan: data layer variables, GTM container structure (client + server), tag templates, triggers, and CAPI mapping. The output includes code snippets, debug steps (GTM Preview, pixel helpers), event deduplication rules, and publish/versioning instructions for a resilient rollout.

When to use it

• Setting up Google Tag Manager for a new website or funnel
• Installing or migrating Meta/Google/TikTok/LinkedIn pixels
• Implementing server-side tracking (sGTM) or Conversion API (CAPI)
• Standardizing data layer variables across multiple pages or environments
• Auditing and fixing broken or duplicate conversion events

Best practices

• Create separate GTM containers for client and server; keep consistent variable naming (user_id, transaction_id, event_name).
• Define a single source-of-truth data layer spec before building tags; include ecommerce objects and transaction fields.
• Use advanced matching with hashed PII for improved attribution while following privacy rules; hash on the server when possible.
• Implement event_id deduplication between browser events and CAPI server events to prevent double-counting.
• Use folder structure in GTM by platform and maintain version-controlled publish notes and QA checklists.

Example use cases

• Build a GTM plan to track Purchase, Lead, AddToCart, and InitiateCheckout events across a 5-page funnel.
• Migrate existing pixels into a single GTM container and add server-side forwarding for Facebook CAPI.
• Create a data layer spec and code snippet for ecommerce transaction pushes to ensure consistent order_value and currency fields.
• Implement deduplicated server-side purchase events with event_id matching and hashed email for advanced matching.
• Run a QA checklist with GTM Preview Mode and platform pixel helpers, produce a verification report and publish instructions.