The easy way to implement Meta Conversions API with no manual tagging. No need to hire a tracking specialist or use a third-party integration tool.
Start 7-day free trialCheck how much you can save
or
if you want something bigger
If you run an agency or a large business, сontact our sales to discuss your needs and we’ll pick a perfect custom plan for you.
Average cost per action improvement
Increase in the number of conversions measured after the implementation of Conversions API Gateway
Create your Stape account if you don’t have one.
Connect your Facebook Pixel to Meta CAPI Gateway.
Actually, there’s no step 3. All done!
If you plan to transfer the CAPI Gateway to your clients, it's better to create separate CAPIGs for each client. If you plan to manage each Pixel yourself (or as an agency) and do not plan to transfer them to other clients in the near future, you can add them to the same CAPI Gateway hub. Receiving data through a first-party domain (DNS routing) can enhance measurement performance. If you plan to add Pixels that are used on different websites to the Gateway hub, it's better to separate them into different hubs to fully utilize this feature (i.e., create separate CAPI Gateways in your Stape account).
Meta Conversions API Gateway is an easy-to-use technical solution designed specifically for implementing the Meta Conversions API. With server Google Tag Manager and the Meta Conversions API tag, you can enable server-side tagging for multiple platforms, including the Meta Conversions API. However, setting up the Conversions API through server Google Tag Manager is more time-consuming and requires additional knowledge of GTM and Meta CAPI documentation. Despite this, it allows you to create a more flexible tracking system and gain greater control over how server events function.
For now, we offer the following zones: North America (US), Europe (Belgium), South America (Brazil), Asia Pacific (Singapore), Asia Northeast (Japan). It is mandatory to use the European zone for all companies in Europe.