Meta Conversions API Setup Guide: Recover iOS Conversions (2026)

Meta Conversions API (CAPI) has become essential for advertisers facing iOS tracking restrictions. By sending conversion events directly from your server to Meta, you bypass browser limitations and achieve 20-30% better attribution accuracy. This guide shows you how to implement Meta CAPI using Google Tag Manager Server-Side.

Why Meta CAPI Is Critical for iOS Campaigns

Since iOS 14 and Apple's ATT framework, Meta Pixel tracking has degraded significantly. 50-60% of iOS users opt out of tracking, making your conversion data incomplete. Meta CAPI solves this by sending events server-side, where browser restrictions don't apply.

• Better Attribution: 20-30% more conversions tracked vs Pixel alone
• iOS Recovery: Track opt-out iOS users through server events
• Event Match Quality: Higher match rates with more customer data
• Ad Optimization: Meta's algorithm gets more signal for better targeting
• Reduced CPA: Better data = better targeting = lower cost per action

Prerequisites

1. Meta Business Manager account with admin access
2. Meta Pixel installed and firing events
3. Google Tag Manager Server-Side container (or willingness to set one up)
4. Access to generate Meta Conversions API token
5. Developer resources for implementation

Step 1: Generate Meta Conversions API Access Token

1. Go to Meta Events Manager and select your Pixel
2. Navigate to Settings > Conversions API
3. Click "Generate Access Token"
4. Copy the token (starts with "EAAG...") - keep this secure
5. Note your Pixel ID (16-digit number)

Step 2: Configure sGTM Meta Tag

In your Google Tag Manager Server container, add the Meta Conversions API tag. This tag forwards events from your server to Meta. Configure it with your Pixel ID and Access Token.

Step 3: Implement Event Deduplication

Critical: without deduplication, Meta counts the same conversion twice (once from Pixel, once from CAPI). Use event_id parameter to deduplicate.

Step 4: Maximize Event Match Quality

Event Match Quality (EMQ) measures how well Meta can match your events to user profiles. Higher EMQ = better attribution. Aim for 7.0+ EMQ score by sending more customer data points.

• Email (hashed): Most valuable identifier
• Phone (hashed): Second most valuable
• First & Last Name (hashed): Helps when combined
• City, State, Zip (hashed): Location data
• IP Address & User Agent: Automatically captured
• fbp & fbc cookies: Browser identifiers

Testing Your Implementation

1. Use GTM Preview Mode to fire a test event
2. Check sGTM Debug console
3. Go to Meta Events Manager > Test Events
4. Confirm event appears with green checkmark
5. Verify Event Match Quality score (7.0+ for events with email)
6. Check Deduplication shows "2 Events Received, 1 Counted"