Setting up the Meta Conversions API Gateway might seem easy, but it can be tricky sometimes. Since it's a crucial source for gathering data on how people use your website and follow through the conversion funnel, getting CAPIG set up correctly and using it properly is very important. This is why we created this article to assist you.
Here, we'll discuss common mistakes and answer questions people often have. This will help you solve problems faster and keep CAPIG working smoothly.
The Meta Conversions API Gateway relies on data received by the Meta pixel. Whenever the Meta Pixel is triggered, it securely sends events to the Meta Pixel and the Conversions API.
This error can have multiple causes. To address it, kindly contact our support team at Stape, and we'll assist you.
First, log in to your DNS provider and ensure you’ve set up DNS records correctly. You should configure the CNAME record that points to your CAPIG hub URL. You can find the CAPIG hub URL inside your stape.io account.
The setup inside the DNS provider should look like the screenshot below. Ensure that the Proxy is set to off. This is an example from Cloudflare.
The last step is to use a tool like this to verify DNS settings. Add your CAPIG hub subdomain, select CNAME, and check if a record matches the CAPIG hub URL.
When you click 'Add data source' in the CAPIG hub, the last thing to do is let the CAPIG hub access your Facebook access token. Ensure you've checked the box that says 'I agree to share my token with this site' and then click 'Confirm'.
If you do not see the pop-up, ensure that pop-ups are not blocked in your browser. To enable pop-ups in Chrome, go to Settings -> Privacy and Security -> Site settings -> Pop-ups and redirects. Select "Sites can send pop-ups and use redirects" or add CAPIG URL to exceptions.
Next, log into your Gateway Hub and try adding the pixel again.
If enabling pop-ups doesn't work, try changing the browser or using incognito mode.
If your Gateway Hub has not stopped receiving events after you created a subdomain for your Gateway Hub and you see the following error in the console. Please add a CAA record to your main domain - 0 issue “pki.goog”.
We offer two subscription plans that have the following limits:
With a pay-as-you-go subscription, you can add an unlimited number of pixels. A 7-day free trial is possible only for the first pixel. If you add more pixels, a prorated charge for additional pixels is applied at the end of the billing cycle. You can check the number of pixels and billing cycle inside stape admin.
The Conversion API Gateway is one way to connect the Conversion API. It has some benefits over other FB CAPI implementations, which are:
You do not need to set up event deduplication for CAPIG. Event deduplication is set up automatically. Event_id deduplication key is automatically generated and propagated to help ensure deduplication between both channels (web and server).
We also offer an option of private multi-user Meta's Conversions API Gateway hub, which has the following benefits:
Please contact our support team for a private multi-user Meta's Conversions API Gateway hub.
You can use the same CAPI gateway instance for all your clients and connect all pixel IDs. All you have to do is click on Add data source. In this case, you can add and use only one subdomain to Gateway Hub.
Go to Accounts, click on three dots on the left, and choose Edit name.
Yes, if the event is configured through an FB pixel, you can capture any value associated with a purchase.
Meta's Conversions API Gateway automatically identifies events set up with an FB pixel and transmits them via the server. Deduplication is also configured automatically.
This documentation explains how to set up and install Meta Pixel.
To see which domains send data to the CAPIG hub, go to the CAPIG hub, open the websites sections, and you should see the list of all domains that send data to CAPIG. Below, you can add websites that you want to block.
Meta's Conversions API Gateway monitors server-side events based on the data captured by the Meta pixel. Any event the Meta pixel detects will be automatically tracked via the Meta Conversions API Gateway. Through the gateway's hub, you can control which events get sent using an on-off toggle for each event.
To track new events, standard or custom, through CAPIG, you must set up a pixel to track this event.
Getting CAPIG set up the right way is really important. It helps you understand how people use your site, make your sales process better, and improve your Facebook ads.
We hope this article has shed light on the common pitfalls and FAQs surrounding CAPIG. With this knowledge, you are better equipped to navigate the setup process, troubleshoot issues efficiently, and ensure that your CAPIG operates seamlessly.
Meta’s Conversions API Gateway is the newest approach in setting up Conversions API and it looks like it’s the easiest one. Meta’s Conversions API Gateway receives events from the browser and sends them to the Conversions API. With Meta’s Conversions API Gateway, you won’t need to set up event deduplication, send user parameters and events from the server. Another huge advantage is having multiple domains/pixels within a single instance of Meta’s Conversions API Gateway.Edited Oct 20, 2023
Read this blog post and find out the main differences and benefits of Meta Conversions API Gateway and Conversion API with their use cases.Edited Oct 20, 2023
Learn how to configure the Meta Conversions API Gateway using Stape in this step-by-step guide.