Meta offers several ways to send server events through the Conversions API. Two of them are easy to confuse with a standard integration: the Conversions API Gateway, a Meta-built server you host in your own cloud account, and the Parameter Builder library, a set of open-source SDKs that help a direct integration send cleaner customer information. This guide covers setup, hosting, documented costs, maintenance and how both relate to Event Match Quality. For the basics of a direct setup, see our Conversions API setup guide. Each rule here comes from Meta's Help Center or developer documentation.
What the Conversions API Gateway is
Meta's Help Center describes the Conversions API Gateway as a codeless, self-serve setup option that you select in Events Manager, without a third-party partner integration or your own developers. Its developer documentation describes it as a standalone Meta product that sends events through both the Meta Pixel and the Conversions API in a redundant setup.
It runs as a server instance that you provision in a cloud account your business owns. Meta lists three cloud services it can run on: AWS EKS, AWS ECS Express and Google Cloud Platform. The instance has two parts: middleware that receives events from browsers, turns them into Conversions API events and sends them to Meta, and an admin web interface at /hub/capig on your Gateway endpoint, which shows connected pixels, event volume, success rate and update notices.
The flow starts in the browser. A Meta Pixel configured with the Gateway endpoint sends each event to Meta and to your Gateway, and the Gateway forwards it server to server. Meta says the event_id deduplication key is generated automatically and passed along, and the Help Center lists automatic deduplication between browser and server events as a Gateway feature. Our deduplication guide covers how event_id matching works.
Meta also notes that if you have a Meta Pixel and only need to send website events, a Meta-run option can do it with nothing for you to host. The Gateway documentation calls it Conversions API with Meta; the Help Center comparison calls it the Meta-enabled Conversions API and lists it as web-only, free and set up in one click.
Setup paths: your own AWS or GCP account, or a partner host
Before you start, Meta's prerequisites are admin access to a cloud provider account and admin access to the Meta Pixel. You can deploy on an existing cloud account or on a new one kept apart from your other assets. Meta's AWS ECS Express page says that during setup you choose either your own cloud account or to have your account hosted by a partner service.
- AWS from Events Manager: open the Settings tab, find Set up with Conversions API Gateway and click Get started. Choose preferences (enhanced events and health monitoring), a cloud setup and one hosting region, then open the pre-filled AWS stack. Meta says not to change the ProvisioningData field and that the stack takes about 30 to 40 minutes to create.
- First login: the stack's Outputs tab gives a CapigSetupURL, also shown in Events Manager. You create an admin account there. Meta says data can take 5 minutes to 2 hours to appear, and to contact Meta if nothing shows after 2 hours.
- Custom domain (recommended by Meta): set it up under Domain management in the admin interface, using AWS Certificate Manager or Cloudflare. Meta says a custom domain may help data routing and may reduce costs.
- GCP: the instance runs in your own GCP project on Cloud Run, Cloud Storage and Cloud Build. You install it by running Meta's install command in Cloud Shell with Owner access, and Meta says this usually takes less than 10 minutes.
- Partner-hosted: an agency or partner that runs a Gateway for multiple accounts can invite your business to onboard, so you connect your data sources without running the infrastructure yourself.
Several pixels, domains and businesses on one Gateway
Meta's developer documentation says one Gateway instance supports multiple Meta Pixels and multiple domains, for example domain.com, domain.co.uk and anotherdomain.com. In Events Manager you can add another Gateway connection with a different pixel, or connect another pixel to an existing Gateway from the Existing Conversions API Gateways section of the Settings tab.
For agencies, partners and resellers, Meta offers the Conversions API Gateway for multiple accounts. A host sets up the Gateway once and invites other businesses, which then connect their own website data sources through their own accounts. Meta says that because more than one pixel can share the same configuration, computing resources are shared and costs may be lower. It's available to hosts with an AWS or GCP account.
Hosts can also use the control plane API, a set of GraphQL APIs on the Gateway instance for managing accounts, data sources and configuration from their own tools. For full integration, Meta says the partner needs the advertiser's authorization through Meta Business Extension or a manually generated token.
Costs, capacity and maintenance
Meta's developer documentation says the only cost of the Gateway is the associated cloud resource or partner fees. Its Help Center adds that cloud fees start at $30 per month and may vary by region, usage and Meta Pixel traffic volume. Meta publishes no fixed price beyond that, so check your cloud provider's bill.
The admin interface includes a Cost management page where you can see current cost, last month's cost and a six-month average, set a maximum budget in US dollars, and set up to two alerts by percentage of budget used. Meta's GCP onboarding includes a step to set minimum and maximum instance counts to manage resource use and cost.
On maintenance, Meta says automatic software updates exist from version 1.0.8, are on by default and can be turned off in the Updates menu under Settings. With them off, your business must update the Gateway manually. Meta also states that advertisers remain responsible for the hardware and operating system infrastructure of the cloud provider they host on. The default TLS certificate lasts one year and renews as long as the two DNS records created during installation stay unchanged.
The Parameter Builder library
Parameter Builder is not a hosting option. Meta describes it as open-source SDKs that help you create, manage and send customer information parameters in your own Conversions API integration. There is a client-side version in browser JavaScript and server-side versions in PHP, Java, Python, Node.js and Ruby, published at github.com/meta/capi-param-builder. Meta notes the server-side SDK can't write cookies, while the client-side SDK can save them automatically.
- fbc and fbp: read from the _fbc and _fbp cookies on your domain, or generated (fbc from an fbclid query parameter). Supported in client-side JavaScript and every server-side language.
- client_ip_address: supported in client-side JavaScript, PHP and Node.js, with Java, Python and Ruby marked coming soon. Meta says the IP must never be hashed and that IPv6 is preferred over IPv4. It recommends capturing the IP with the client-side library, saving it to a cookie, then letting the server-side library pick the best available IP from the cookie and the request.
- referrer_url and event_source_url: server-side only. event_source_url is rebuilt from the incoming request and needs the processRequestFromContext method; Meta says the older processRequest is deprecated.
- Customer details: email, phone, name, date of birth, gender, city, state, zip, country and external_id are normalized and hashed by the library in client-side JavaScript, PHP and Node.js. Meta says to normalize and hash only once and to send the returned values as they are.
- Appendix: values the library produces carry an extra suffix (8 characters in current versions) recording the SDK version, incrementality and language, so they won't look exactly like a raw cookie value. Don't strip it, and don't change the case of _fbc.
How Gateway and Parameter Builder affect Event Match Quality
Event Match Quality is a 0 to 10 score Meta calculates for website server events, based on the customer information sent and the share of events matched to Meta accounts, using the last 48 hours of data. Meta lists email and click ID as high-priority parameters and browser ID as medium. Our Event Match Quality guide covers the full score.
Meta's Gateway documentation doesn't promise a match quality change. What it documents is an optional Enhance events with advanced matching data setting, off by default, which lets the Gateway set and send a browser cookie with fuller user data from your Meta Pixel. If available, it can add email, name, phone number, city, state, gender and zip code.
For Parameter Builder, Meta says the library may lead to higher match quality scores by increasing coverage of fbc, fbp, client IP and URL parameters and by formatting customer data. It also recommends saving _fbp and _fbc as early as possible, ideally on the landing page rather than only on later events.
Choosing an option, and common mistakes
Meta's Help Center says the Gateway suits businesses that already use the Meta Pixel, don't yet send web events through the Conversions API, spend more than $300 a month on campaigns optimized for web events and don't work with an ecommerce partner. If you're on Shopify, WooCommerce, BigCommerce or a similar platform that supports the Conversions API, Meta recommends using that partner. For app or physical-store events, Meta says direct integration is currently the only option.
Practitioner advice (our view, not Meta's): if you only need web events and have no developer, look at the Meta-run option first and consider Gateway when you want your own server, a custom domain or several pixels managed in one place. If you already have a developer-built integration, Parameter Builder is usually the smaller step, because it improves the parameters you already send without adding infrastructure. Gateway's main flow relays what the pixel sees in the browser, so events that only happen in your back office, such as offline sales, still call for a direct integration. Power Ads supplies Meta agency ad accounts; the tracking setup works the same on any ad account.
- Running Gateway alongside another server integration for the same pixel without checking deduplication, so one purchase can arrive twice from the server side.
- Changing the ProvisioningData field in the AWS stack, or letting browser autofill change it, which Meta lists as a cause of expired provisioning data errors.
- Deleting or editing the two DNS records from installation, which stops the default certificate from renewing.
- Turning off automatic updates and then never updating manually.
- Hashing client_ip_address, hashing customer data twice, or lowercasing _fbc.
- Leaving cloud budgets and alerts unset. Meta says cloud fees vary with region, usage and traffic.
Key takeaways
- Conversions API Gateway is a Meta product you host in your own AWS or GCP account, or through a partner, that relays pixel events server to server with event_id deduplication built in.
- Meta says the only Gateway cost is cloud or partner fees; its Help Center puts cloud fees from $30 a month, varying with region, usage and traffic.
- One Gateway can serve several pixels and domains, and Gateway for multiple accounts lets an agency or partner host other businesses.
- Automatic updates are on by default, but you still own the cloud infrastructure and its DNS records.
- Parameter Builder is a set of open-source SDKs for your own integration that build fbc, fbp, client IP and customer parameters, which Meta says may raise Event Match Quality.
FAQ
Does Meta charge for the Conversions API Gateway?
Meta's developer documentation says the only cost is the cloud resources or partner fees. Its Help Center says cloud fees start at $30 per month and vary by region, usage and pixel traffic. The admin interface has a Cost management page where you can set a budget and alerts.
Can one Conversions API Gateway handle several pixels?
Yes. Meta's documentation says one Gateway instance supports multiple Meta Pixels and multiple domains. Agencies, partners and resellers can also use the Conversions API Gateway for multiple accounts to onboard other businesses onto a single configuration.
Do I have to update the Gateway myself?
Not by default. Meta says automatic software updates are on by default from version 1.0.8 and can be turned off in the Updates menu under Settings. If you turn them off, you must update manually. You remain responsible for the cloud provider's hardware and operating system infrastructure.
Is Parameter Builder an alternative to the Gateway?
No. Parameter Builder is a set of open-source SDKs you add to your own website or server code to build fbc, fbp, client IP, URL and hashed customer parameters. Gateway is a hosted server that relays pixel events. They solve different problems.
Will the Gateway or Parameter Builder improve my Event Match Quality?
Meta doesn't promise it. It says Parameter Builder may lead to higher match quality scores, and the Gateway's optional enhanced events setting adds user data from the pixel to help match events. Check the score in Events Manager after any change.
Can the Gateway send offline or app events?
Meta's comparison page says direct integration is currently the only option for mobile app or physical store events through the Conversions API. The Gateway's main flow is built around web events sent by the Meta Pixel.
Sources
- facebook.com/business/help/387152639648383
- facebook.com/business/help/746511563926080
- facebook.com/business/help/433493041367251
- facebook.com/business/help/765081237991954
- developers.facebook.com/documentation/ads-commerce/gateway-products/conversions-api-gateway
- developers.facebook.com/documentation/ads-commerce/gateway-products/configuration
- developers.facebook.com/documentation/ads-commerce/gateway-products/conversions-api-gateway/setup
- developers.facebook.com/documentation/ads-commerce/gateway-products/host-management/post-setup-management
- developers.facebook.com/documentation/ads-commerce/gateway-products/gateway-aws-ecs-express
- developers.facebook.com/documentation/ads-commerce/gateway-products/gateway-aws-ecs-express/ecs-express-cost-monitoring
- developers.facebook.com/documentation/ads-commerce/gateway-products/gateway-gcp/host-onboarding
- developers.facebook.com/documentation/ads-commerce/gateway-products/gateway-gcp/create-instance-agencies-partners
- developers.facebook.com/documentation/ads-commerce/gateway-products/gateway-control-plane-api
- developers.facebook.com/documentation/ads-commerce/gateway-products/conversions-api-gateway/enhance-events-advanced-matching
- developers.facebook.com/documentation/ads-commerce/conversions-api/parameter-builder-library
- developers.facebook.com/documentation/ads-commerce/conversions-api/parameter-builder-library/get-started
- developers.facebook.com/documentation/ads-commerce/conversions-api/parameters/fbp-and-fbc
