Logo of TAGGRS, written in blue and with a small favicon
HomeServer-side Tracking
Start for free
Introduction
Get started
Get started with TAGGRSSet up Google Tag ManagerAdd the GTM Data LayerConfigure GTM transformationsTest the setupDebuggingAnalytics dashboard
Migrate from Google CloudMigrate from hosting
Shortcuts
GTM Copy PasteReady-made templates
GA4 Server-side Tracking
Setup in GTMCreate GA4 Event TagsGA4 tag setup in server containerE-commerce events in GTM
Google Ads Server-side Tracking
Install Conversion LinkerSet up Conversion TrackingConfigure Enhanced ConversionsDeploy Remarketing Tags
Facebook Server-side Tracking
Set Meta PixelImprove your EMQ ScoreInstall Meta CAPIMeta Events DeduplicationMeta CAPI Gateway
LinkedIn Server-side Tracking
Install LinkedIn Insight TagSet up LinkedIn CAPILinkedIn Events Deduplication
TikTok Server-side Tracking
Set up TikTok PixelInstall TikTok Events APITikTok Events Deduplication
Pinterest Server-side Tracking
Set up Pinterest TagConfigure Pinterest Conversions APIPinterest Events Deduplication
Snapchat Server-side Tracking
Set up Snap PixelSnapchat Conversions APISnapchat Events Deduplication
TAGGRS Tracking Tags and Tools
Tracking TagsGoogle Service Account integrationsGTM LogsProfit TrackingData Enricher ToolWebhooks TesterEnhanced Tracking ScriptMulti Domain ToolClick ID RecoveryConsent Tool
Configurations
Billy Grace Server-side TrackingLeadPages Server-side TrackingPiwik PRO Server-side TrackingCDN Server-side TrackingShopify Server-side TrackingActiveCampaign Server-side TrackingKlaviyo Server-side Tracking
Server-side Tracking for e-commerce
Shopify Data LayerShopware Data LayerMagento Data LayerWooCommerce Data LayerPrestashop Data LayerLightspeed Data Layer
Consent Management server-side
Activate Consent ModeConfigure TAGGRS with Axeptio

Install Meta Conversions API

In this guide, you'll find a comprehensive walkthrough for implementing Meta’s Conversions API (CAPI) using Google Tag Manager’s server container and TAGGRS. By establishing a direct server-to-server connection between your infrastructure and Meta, you ensure reliable conversion tracking, delivering accurate campaign measurement even in privacy-centric environments. With CAPI, you capture critical events (like purchases, sign-ups, and leads) directly from your server, complementing browser-based Pixel data to create a complete, deduplicated view of user actions for optimized ad targeting and attribution.

Configure server container prerequisites

  • TAGGRS Setup: Ensure your TAGGRS server container is deployed.

    You can follow our implementation guide to have it done easily.

  • Access token: Generate in Meta Events Manager under Conversions API > Settings.
  • Pixel ID: Locate in Meta Events Manager under Data Sources.

Create CAPI tag in GTM server container

  1.  In GTM server container, create a new HTTP Request tag.
  2. Configure settings:
    • URL: https://graph.facebook.com/v19.0/<PIXEL_ID>/events
    • Method: POST
    • Headers:
      Content-Type: application/json
      Authorization: Bearer <ACCESS_TOKEN>
  3. Add Request Body using JSON:

    json
    {
     "data": [
       {
         "event_name": "{{Event Name}}",
         "event_time": {{Unix Timestamp}},
         "user_data": {
           "em": ["{{Hashed Email}}"],
           "ph": ["{{Hashed Phone}}"]
         },
         "custom_data": {
           "currency": "{{Currency}}",
           "value": {{Value}}
         }
       }
     ]
    }

Map data layer variables

Create GTM variables to populate the JSON payload:

Variable Type

Example Path

Purpose

Data Layer Var

ecommerce.transaction_id

Transaction ID

Data Layer Var

ecommerce.value

Purchase value

Custom JavaScript

SHA256(email)

Hashed user email

Built-in Variable

Timestamp

Event time

Configure trigger

Use Custom Event triggers (e.g., purchase, lead) from your website’s data layer.
Apply filters to fire only for conversion events.

Test and validate

Use GTM Preview Mode to verify payload structure.
Check Meta Events Manager > Test Events for incoming server events.
Validate deduplication by comparing CAPI and Pixel events in reports.

Troubleshooting

Data hygiene:
- Hash all PII (SHA256)
- Include event_id for deduplication
- Send currency with value fields

Hybrid tracking:
Maintain Pixel for client-side events
Use CAPI for critical conversions (purchases, leads)
Combine both for 10-30% higher attribution accuracy

Monitoring:
Track EMQ scores in Events Manager

Useful resources

Facebook server-side tracking - The full manual
Find expert support
Previous
Meta Event Match Quality Score
Next
Prevent duplicate Meta events
Copyright © 2025 TAGGRS. All right reserved.
TABLE OF CONTENTS
Configure server container prerequisitesCreate CAPI tag in GTM Map data layer variablesConfigure triggerTest and validateUpdate the Conversion Event triggerTest and validateTroubleshootingUseful resources