Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From GTM Skills
Set up first-party tracking and analytics — website pixels, conversion tracking, UTM architecture, cookie consent, server-side vs client-side tagging, 1P vs 3P data strategy, and identity resolution.
How this skill is triggered — by the user, by Claude, or both
Slash command
/gtm-skills:1p-tagging-pixelsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Third-party cookies are dead. Apple ITP, Firefox ETP, and Chrome's phase-out
Third-party cookies are dead. Apple ITP, Firefox ETP, and Chrome's phase-out have made browser-based tracking unreliable. The future is first-party data and server-side measurement — data your customers intentionally share with you that survives ad blockers, cookie restrictions, and platform changes.
This skill covers the complete measurement stack: 1P vs 3P strategy, pixel implementation, UTM architecture, server-side tagging, consent management, and identity resolution. The output is a privacy-resilient analytics infrastructure that works when cookies don't.
Data you collect directly from your customers — they know they're sharing it. Examples: email signups, form fills, product usage, purchase history, support tickets, survey responses, account registration.
Advantages: Privacy-compliant by default. Survives browser changes. Higher data quality. You own it. No intermediary. Can be enriched with identity resolution.
Disadvantages: Requires customer action (signup, login, form fill). Smaller volume than 3P. Needs infrastructure to collect, store, and activate.
Data collected by entities that don't have a direct relationship with the user. Examples: browser cookies, ad network tracking, data brokers, device graphs, cross-site tracking.
Advantages: Large scale. Doesn't require user action. Useful for prospecting and lookalike audiences. Historical data for benchmarking.
Disadvantages: Dying. Browser restrictions block 30-40% of 3P tracking. Regulatory pressure (GDPR, CCPA). Lower data quality. You don't own it. Expensive (data broker fees).
Now: Run both 1P and 3P in parallel. 3P for scale, 1P for accuracy. Next 12 months: Shift budget from 3P data to 1P infrastructure. End state: 1P is the foundation. 3P is supplementary where still available.
Collect → Enrich → Activate:
Install these four pixels on every page:
LinkedIn Insight Tag: Base code in <head>, event tracking on conversions.
Identifies company visitors for ABM retargeting even without form fills.
Meta Pixel (Facebook): Base code + conversion events. Required for Meta ads optimization, retargeting, and lookalike audience building.
Google Ads Conversion Tag: Via Google Tag Manager or gtag.js. Tracks ad-driven conversions for bidding optimization.
TikTok Pixel: Base code + events. Required for TikTok ads optimization.
Plus: Google Analytics 4 (GA4) — your analytics foundation. Event-based model (not pageview-based). Free, unlimited for most use cases.
Standardize UTM parameters across all campaigns:
| Parameter | Purpose | Example |
|---|---|---|
utm_source | Traffic origin | linkedin, google, meta, email, direct |
utm_medium | Channel type | cpc, organic, email, social, referral |
utm_campaign | Specific campaign | product_demo_q1, webinar_feb |
utm_content | Ad/creative variant | variant_a, video_testimonial |
utm_term | Keyword (search only) | cold+email+software |
Enforcement: Single source of truth spreadsheet. Consistent naming. Never
mix linkedin and LinkedIn and li. Pre-built UTM templates for common
campaign types.
Move from browser tags to server-side dispatch:
Benefits:
Setup: Google Tag Manager Server-Side (free, Google-hosted or self-hosted), Segment Protocols, or custom server endpoint. One server-side container receives events, dispatches to all platforms.
Architecture:
Website/App → Server-Side GTM → LinkedIn Conversion API
→ Meta Conversions API
→ Google Ads Offline Conversions
→ TikTok Events API
→ Your Data Warehouse
GDPR (EU): explicit opt-in before tracking. CCPA (California): right to opt-out. Growing state laws.
Implementation: Consent Management Platform (Cookiebot, OneTrust, Termly). Load tracking scripts only after consent. Block all cookies and pixels until user accepts. Document data flows for compliance.
Consent banner best practices: Clear "Accept All" / "Customize" options. Don't make rejecting harder than accepting. Don't use dark patterns.
Connect anonymous visitors to known contacts:
website-visitor-identification before deploying.
Canonical playbook:
website-visitor-identification/references/visitor-identification-playbook.md.Use identity resolution for: ABM retargeting, sales alerts on target account visits, content personalization, pipeline attribution.
Measurement plan with: 1P vs 3P strategy, pixel inventory, UTM taxonomy, server-side architecture diagram, consent implementation, identity resolution setup, and conversion event map.
Client-side only. 30-40% of browser events are lost to ad blockers. Server-side captures 100%. Implement server-side tagging before scaling ad spend.
No UTM standardization. "linkedin", "LinkedIn", "li", "lnkd" are four different sources in analytics. One naming convention, enforced.
Tracking without consent. GDPR fines up to 4% of global revenue. Implement consent before tracking EU visitors.
Pixel duplication. Same pixel fired twice = double-counted conversions. Audit quarterly with browser dev tools.
3P dependency without 1P transition. 3P data is dying. 1P data is the future. Run both now, actively build 1P infrastructure.
references/framework-notes.md — named frameworks, citation anchors, and operating assumptionstemplates/output-template.md — copy-paste deliverable structure for the userscripts/check-output.py — local checklist validator for required sections
This skill includes lightweight artifacts the agent can load on demand:
Use the artifacts when the user asks for an implementation-ready deliverable, a repeatable workflow, or a quality check rather than generic advice.npx claudepluginhub leadmagic/gtm-skillsGenerates a complete, platform-specific ad conversion tracking setup (Meta Pixel/CAPI, TikTok Events API, Google Ads, GTM) from a single chat message. Auto-detects industry, maps standard events, and outputs a developer-ready implementation doc.
Master analytics tracking plan for PLG/B2B SaaS: event taxonomy, pixel strategy, attribution architecture, CDP (Segment, Rudderstack), product analytics (Amplitude, Mixpanel, PostHog), CRM tracking (HubSpot, Salesforce).
Sets up, improves, or audits analytics tracking and measurement including GA4, GTM, event tracking, UTM parameters, and conversion tracking.