ads-meta-google

Implement server-side and client-side ad tracking for Meta and Google campaigns.

1|Updated May 8, 2025
One-click install
npx skills add https://github.com/Uncodier/API --skill ads-meta-google
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ads-meta-google
Source: https://github.com/Uncodier/API/tree/main/src/skills/ads-meta-google
Command: npx skills add https://github.com/Uncodier/API --skill ads-meta-google

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill implements comprehensive ad tracking for Meta Pixel, Meta Conversions API (CAPI), and Google Tag, enabling unified attribution, conversion measurement, and campaign analysis across platforms while respecting privacy and consent.

Core Features & Use Cases

  • Server-side tracking (CAPI) for Meta to improve deduplication and reliability, including hashing user data and unique event IDs.
  • Client-side tracking with Meta Pixel and Google Tag to fire standard events with accurate parameters and consent controls.
  • Attribution and campaign analysis with UTMs, click IDs, and cross-platform reporting to support ROI/ROAS optimization.
  • Privacy and consent management using Google Consent Mode v2 and guardrails to prevent PII exposure.
  • Campaign analysis support through MCP-like data sources for performance insights.

Quick Start

Configure the server- and client-side tracking for a campaign and verify attribution across Meta and Google Analytics.

Frequently Asked Questions about ads-meta-google

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

FAQPage Schema
How do I implement server-side tracking for Meta Conversions API and Google Tag?

Unified ad tracking implements both server-side and client-side measurement for Meta and Google, improving deduplication and reliability through CAPI event formatting, pixel firing, and GA4 configuration.

How does consent mode v2 work with Meta Pixel and Google Tag firing?

Consent mode v2 integrates with Meta Pixel and Google Tag firing by applying privacy guardrails that prevent PII exposure while maintaining accurate client-side conversion tracking across advertising platforms.

What is the best way to maintain UTM and click ID persistence for accurate attribution?

Maintaining UTM and click ID persistence for accurate attribution requires cross-platform reporting configurations that track conversions and ROI across multiple campaigns and platforms simultaneously.

Can I use this approach to configure GA4 and Meta CAPI event formatting simultaneously?

Yes, you can configure GA4 and Meta CAPI event formatting simultaneously because the approach satisfies requirements for both platforms, ensuring unified attribution and conversion measurement across campaigns.

Why does Meta Conversions API require hashing user data and unique event IDs?

Meta Conversions API requires hashing user data and unique event IDs to improve deduplication and reliability when matching conversion events sent from the server with corresponding client-side pixel fires.