53-tracking-setup-global

Configures and verifies conversion tracking across Meta, Google, GA4, and TikTok before ad launch.

569|224|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/minhnv0807/ai-business-skills --skill 53-tracking-setup-global
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 53-tracking-setup-global
Source: https://github.com/minhnv0807/ai-business-skills/tree/main/skills/en/53-tracking-setup-global
Command: npx skills add https://github.com/minhnv0807/ai-business-skills --skill 53-tracking-setup-global

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Launching paid campaigns without verified conversion tracking means every dollar spent is unmeasurable, and fixing events mid-campaign destroys historical comparability. This Skill ensures pixels, server-side APIs, consent mode, and UTMs are correctly installed and verified before any ad spend begins.

Core Features & Use Cases

  • Multi-platform setup checklists: Covers Meta Pixel plus Conversions API, Google Ads with Enhanced Conversions, GA4 key events, TikTok Pixel plus Events API, and LinkedIn Insight Tag, with deduplication via shared event IDs.
  • Consent and privacy compliance: Implements Google consent mode v2 for GDPR/ePrivacy in the EU/UK, Limited Data Use for California under CCPA/CPRA, and consent logging requirements.
  • UTM conventions and event mapping: Defines a lowercase UTM naming standard aligned with ad names, plus a GA4-to-platform event mapping table from page_view through purchase with value and currency.
  • Use Case: A marketer about to launch Meta and Google campaigns for a Shopify store uses this Skill to install CAPI with deduplication, configure consent mode v2 for EU traffic, standardize UTMs, and run the pre-launch verification checklist before spending anything.

Quick Start

Set up and verify conversion tracking for my Meta and Google Ads campaigns on Shopify, including server-side events, consent mode, and UTM conventions, before I launch.

Frequently Asked Questions about 53-tracking-setup-global

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

FAQPage Schema
How do I set up Meta Pixel and Conversions API together?

Install the Meta Pixel via GTM or a native integration using exactly one method, then set up the Conversions API through a platform integration or server-side GTM. Send the same event_id from both browser and server so events deduplicate, and include hashed customer parameters to reach Event Match Quality of 6.0 or higher.

What is Google consent mode v2 and when is it required?

Google consent mode v2 sends four signals (ad_storage, analytics_storage, ad_user_data, ad_personalization) that control how Google tags behave based on user consent. It is required for EEA/UK traffic via a Google-certified CMP; without it, remarketing audiences stop populating and conversion modeling degrades.

Why do Meta Ads and GA4 conversion numbers not match?

Meta and GA4 use different attribution windows and modeling methods, so their conversion counts naturally differ. Meta defaults to 7-day click and 1-day view post-ATT, while GA4 uses its own attribution; pick one source as decision-grade and treat the other as directional.

How do I track offline sales from ad campaigns?

Capture source, campaign, and click IDs (GCLID or fbclid) in CRM fields on every lead, then import closed conversions weekly via Meta offline conversions or Google Enhanced Conversions for Leads. This trains bidding on actual revenue instead of raw lead counts.

Why is my pixel firing duplicate conversion events?

Duplicate events usually occur when both GTM and a hardcoded tag are installed on the same site. Remove one installation method and verify that browser and server events share the same event_id so the platform can deduplicate them.

When should I use server-side GTM instead of client-side tags?

Use server-side GTM when the account has real revenue at stake, heavy iOS or EU traffic, or significant event loss from ad blockers and ITP. It centralizes event forwarding to Meta CAPI, Google Ads, GA4, and TikTok while preserving first-party cookie lifetimes, but it does not bypass consent requirements.