gtm-pixels

GTM & Pixels Implementation

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "gtm-pixels" with this command: npx skills add mikefilsaime-groove/clickcampaigns-for-claude-code-in-cursor/mikefilsaime-groove-clickcampaigns-for-claude-code-in-cursor-gtm-pixels

GTM & Pixels Implementation

Implement precise, resilient, and privacy-compliant tracking tags using Google Tag Manager (GTM) and platform-specific pixels. This skill focuses on the technical "how-to" of tag deployment, trigger logic, and data layer integration.

Core Objectives

  • Deploy a robust Google Tag Manager container (Client & Server)

  • Implement platform pixels (Meta, Google, TikTok, LinkedIn) with 100% accuracy

  • Configure custom events and triggers for key conversion actions

  • Ensure data layer consistency across the entire funnel

  • Validate tracking health using debugging tools

Mandatory Elements

  1. GTM Architecture
  • Container Setup: Client-side for browser tracking, Server-side for privacy and performance.

  • Variable Governance: Consistent naming for User IDs, Transaction IDs, and Event Names.

  • Folder Structure: Organized by platform (e.g., [Meta], [GA4], [Ads]).

  1. Pixel Implementation
  • Base Code: Installation on every page via GTM.

  • Standard Events: PageView, Lead, Purchase, AddToCart, InitiateCheckout.

  • Advanced Matching: Securely passing hashed user data (Email, Phone) for better attribution.

Structure & Frameworks

Tag Deployment Workflow

  • Audit: Identify all current tags and conversion points.

  • Data Layer Spec: Define variables needed from the website code (e.g., order_value ).

  • Configuration: Build Tags, Triggers, and Variables in GTM.

  • Debug & QA: Use GTM Preview Mode and Platform Pixel Helpers.

  • Publish: Version-controlled release with descriptive notes.

Conversion API (CAPI) Strategy

Purpose: Bypass browser restrictions (iOS14+) by sending events directly from the server. Key Elements:

  • Event deduplication (Event ID matching)

  • Server-side GTM (sGTM) configuration

  • Direct API integrations where possible

Voice & Tone Guidelines

  • Technical Precision: Use exact terminology (Data Layer, Trigger, Variable).

  • Instructional: Clear, step-by-step guidance.

  • Authoritative: Confident in technical requirements and privacy compliance.

  • Formatting: Code blocks for data layer snippets and tag configurations.

Concrete Examples

Data Layer Push for Purchase

window.dataLayer = window.dataLayer || []; window.dataLayer.push({ 'event': 'purchase', 'ecommerce': { 'transaction_id': 'T12345', 'affiliation': 'Online Store', 'value': 59.99, 'currency': 'USD', 'items': [{ 'item_name': 'Marketing Masterclass', 'item_id': 'MM-01', 'price': 59.99, 'quantity': 1 }] } });

Meta Pixel Lead Event (via GTM Custom HTML)

<script> fbq('track', 'Lead', { content_name: '{{Page Path}}', content_category: 'Funnel Step 1', value: 10.00, currency: 'USD' }); </script>

Quality Checklist

For every implementation, ask:

  • Is the GTM container loading on all pages?

  • Are events deduplicated between browser and server (CAPI)?

  • Is hashed PII (Email/Phone) being sent correctly for Advanced Matching?

  • Does the Data Layer match the technical specification?

  • Have all tags been verified in GTM Preview Mode?

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Coding

crm-setup

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

legal-policy

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

saas-dev-marketing

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

book-writing

No summary provided by upstream source.

Repository SourceNeeds Review