1p-tagging-pixels

Solid

Set up first-party tracking and analytics — website pixels, conversion tracking, UTM architecture, cookie consent, server-side tagging vs client-side, 1P vs 3P data strategy, and identity resolution. Use when setting up tracking, implementing pixels, building attribution, or preparing for privacy-first measurement. Triggers on: "pixel", "tracking", "conversion tracking", "first-party data", "server-side tagging", "UTM", "cookie consent", "1P vs 3P", "identity resolution", or any tracking implementation request.

AI & Automation 28 stars 11 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 87/100

Stars 20%
49
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 1P Tagging & Analytics ## Overview 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. ## Authoritative Foundations - **Privacy-First Measurement** — Shapes deliverables for this skill — Third-party cookies are dead. - **Server-Side Tagging Architecture** — Shapes deliverables for this skill — Third-party cookies are dead. - **1P Data Strategy** — Shapes deliverables for this skill — Third-party cookies are dead. ## When to Use - "Set up conversion tracking" - "1P vs 3P data strategy" - "Install pixels (LinkedIn, Meta, Google, TikTok)" - "Build UTM architecture" - "Set up server-side GTM" - "Implement first-party tracking" - "Fix attribution gaps" - "Set up cookie consent" - "Identity resolution setup" ## 1P vs 3P Data Strategy ### First-Party Data (1P) 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. **Ad...

Details

Author
LeadMagic
Repository
LeadMagic/gtm-skills
Created
1 months ago
Last Updated
1 weeks ago
Language
Python
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

analytics-tracking

Set up, audit, and debug analytics tracking implementation — GA4, Google Tag Manager, event taxonomy, conversion tracking, and data quality. Use when building a tracking plan from scratch, auditing existing analytics for gaps or errors, debugging missing events, or setting up GTM. Trigger keywords: GA4 setup, Google Tag Manager, GTM, event tracking, analytics implementation, conversion tracking, tracking plan, event taxonomy, custom dimensions, UTM tracking, analytics audit, missing events, tracking broken. NOT for analyzing marketing campaign data — use campaign-analytics for that. NOT for BI dashboards — use product-analytics for in-product event analysis.

23,342 Updated 1 weeks ago
alirezarezvani
AI & Automation Solid

tracking-plan

Master analytics tracking plan for PLG and B2B SaaS — unified event taxonomy, pixel strategy (1P and 3P tagging), marketing attribution architecture, CDP implementation (Segment, Rudderstack), product analytics (Amplitude, Mixpanel, PostHog), CRM tracking (HubSpot, Salesforce), and analytics infrastructure design. Use when building a complete tracking plan, designing analytics architecture, implementing product analytics, or aligning marketing and product tracking. Triggers on: "tracking plan", "analytics plan", "event tracking architecture", "pixel strategy", "analytics for PLG", "SaaS analytics".

28 Updated 1 weeks ago
LeadMagic
AI & Automation Solid

suede-analytics

Know whether any of it worked: tracking plans, event and conversion instrumentation, UTM discipline, attribution, and auditing what is actually firing. Use when the user is setting up or fixing analytics, conversion tracking, or attribution, or cannot tell whether a change moved anything. Also use when the user mentions 'set up tracking,' 'GA4,' 'Google Analytics,' 'conversion tracking,' 'event tracking,' 'UTM parameters,' 'tag manager,' 'GTM,' 'analytics implementation,' 'tracking plan,' 'how do I measure this,' 'track conversions,' 'attribution,' 'Mixpanel,' 'Segment,' 'are my events firing,' or 'analytics isn't working.' Use this whenever someone asks how to know if something is working or wants to measure marketing results. For A/B test measurement, see suede-ab-testing.

165 Updated today
JasonColapietro