Home/Services/Server-Side Tracking/Meta CAPI
Meta CAPI Through Server-Side GTM
We run your Meta Conversions API from a server-side GTM container you own. Events reach your first-party endpoint, the Meta CAPI tag builds each request, and you control exactly which fields leave your server. For teams that already use sGTM or want Meta on the same infrastructure.
Advertisers who want Meta server events on their own sGTM infrastructure, not a plugin
- Meta CAPI tag in the server container
- Events via your first-party endpoint
- Field-level control of user data
- Shared hosting with GA4 and Ads
Free 30-minute tracking audit • No obligation
Why Plugin-Based CAPI Leaves You Without Control
Many sites send Conversions API events through a platform plugin or partner integration. It works, but the data path is opaque and hard to extend.
No Visibility Into Payloads
Built-in integrations decide which fields go to Meta, and you cannot easily inspect or change the request before it is sent.
Separate Pipelines per Vendor
Meta runs through one integration and Google through another, so each platform receives slightly different event data.
Limited Routing Rules
There is no single place to drop a parameter, block an event for a region or enrich a purchase before Meta sees it.
What We Build for Meta Inside sGTM
The Meta side runs as one more tag in your server container. It reuses the same incoming event stream as GA4 and Google Ads, with rules specific to Meta.
Meta CAPI Server Tag
A Conversions API tag template configured with your pixel ID and a system user access token stored in the container.
Shared Event Stream
Meta events built from the same GA4-format stream the server already receives, with event names mapped to Meta standard events.
First-Party Endpoint
Browser data arrives at your own subdomain, so _fbp and _fbc values can be read and kept as first-party cookies.
User Data Routing
Rules that choose which hashed fields, such as em and ph, are sent to Meta and which are held back.
Event ID for Deduplication
A shared event_id passed from the web container so Meta can match server events to any remaining Pixel events.
Consent and Region Filters
Triggers that block or limit Meta requests based on consent state or visitor region before any call is made.
How Meta Events Travel Through Your Server
One browser event reaches your endpoint, and the server container decides what version of it Meta receives.
Purchase or lead captured by web GTM
Sent to sGTM on your subdomain
Consent, region and field filters
Builds the Conversions API request
Server event received and deduplicated
What's Included in Meta CAPI
Clear deliverables, documented and validated before handover.
Meta Tag Configuration
Conversions API tag, triggers and event mapping set up and published in your server container.
Hosting Review
Your existing sGTM hosting checked, or a new Cloud Run or Stape setup planned if none exists yet.
Data Routing Map
A diagram of which fields flow to Meta, which are hashed and which are removed before sending.
Events Manager QA
Test events checked in Meta's Test Events tool, with deduplication and parameter coverage reviewed.
Token and Access Setup
Access token generated under a system user and stored in the container, not in page code.
Setup Documentation
Written notes on the tag template, variables, triggers and how to add new Meta events later.
From Audit to Validated Data
How a Meta CAPI project runs, step by step.
Audit
Audit current Meta integrations, sGTM setup and which events reach Events Manager
Strategy
Plan event mapping, user data fields and which requests move off plugins
Implementation
Install the Meta CAPI tag in sGTM and wire it to the shared event stream
Testing
Test payloads in server preview and Meta's Test Events tool
Validation
Validate deduplication and event coverage, then document the routing rules
Platforms and Tools We Work With
The tools involved in a typical Meta CAPI implementation.
Server events and testing
Meta CAPI tag
Event and ID capture
Managed sGTM hosting
Self-managed hosting
Meta CAPI FAQ
Straight answers before you book. Still have a question? Talk to us directly.
How is this different from your Meta Conversions API service?
Our Meta Conversions API service covers CAPI in general, including partner and platform integrations. This page is specifically about running CAPI as a tag inside your own server-side GTM container, sharing infrastructure and data with GA4 and Google Ads.
Do I need an existing sGTM container?
No. If you do not have one, we set it up as part of the project. If you already run sGTM for GA4 or Google Ads, the Meta tag is added to that container and reuses its hosting and endpoint.
Should I remove the Meta Pixel after adding CAPI?
Usually not. Meta recommends running Pixel and Conversions API together with a shared event_id for deduplication. We keep the Pixel where it adds value and make sure both sources are matched correctly.
Which tag template do you use for Meta in sGTM?
We use a maintained Conversions API template from the GTM community gallery or the one provided by your hosting partner, reviewed before install. The choice is documented so your team knows what to update later.
Can I control which customer data Meta receives?
Yes. That is one of the main reasons to route CAPI through your own server. Every user data field is an explicit choice in the tag, so you can send hashed email only, add phone, or send no personal data at all.
Services That Work Well Together
Tracking is a system. These services are often delivered alongside this one.
Server events sent to Meta with event IDs, deduplication and customer data for stronger event match quality.
Server container setup, hosting, custom subdomain and routing, ready for every platform.
Hashed customer data added to Meta events so more conversions match to the people who saw your ads.
Stop Guessing. Start Measuring.
Get a professional review of your tracking setup and discover where your marketing data may be leaking.
Free 30-minute review • No obligation