Conversions API Gateway: common mistakes and frequently asked questions

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.

• Meta pixel is tracking that event. The easiest way to check is by using the Meta Pixel Helper tool for the Chrome browser. Install it, then do actions on your site that should cause the event to happen. If the tool doesn't show the event, that means it's not being tracked. The first step to fix this is to set up Meta pixel tracking. Once that's done, CAPIG will start picking up the event automatically.

• Additional CAPI integration through a third-party vendor. It can be, for example, a Shopify plugin or WordPress app. Ensure no additional integration is configured to send data to Facebook CAPI.
• A domain that sends events is blocked inside the CAPIG hub. To troubleshoot this reason, log in to the CAPIG hub, open the website tab, and check the list of blocked websites. 

This error can have multiple causes. To address it, kindly contact our support team at Stape, and we'll assist you.

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, which you can find 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: 

• Pay-as-you-go costs $10/month per pixel and includes 10 million events per month per pixel.
• Unlimited costs $100/month plan and includes 200 million events per month. 

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:

• easy setup.
• the ability to add multiple pixels and domains in one CAPIG hub.
• in most situations, the setup and ongoing costs for CAPIG are lower than for CAPI.

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). 

Please keep in mind that event deduplication does not work for test events, since there is no option to add the test event code to Meta CAPI Gateway for server-side testing. You will only see browser-side events when performing tests in Facebook Events Manager.

• Enable Advanced matching inside the CAPIG hub interface. 

• Activate Automatic Advanced Matching when linking your pixel to the CAPIG hub. To specify the user parameters you wish to share with Meta, select "Show customer information parameters" and enable the ones you'd like to share.

• The United States
• Europe 
• South America 
• Asia Pacific
• Japan

• Use one CAPIG hub account for all of your clients. In this case, you must connect all pixels to one CAPIG hub and use one custom domain.
• You can use an agency account to create accounts for each client with its own CAPIG with their email. This way, you will have a custom domain for each website or pixel.

We also offer an option of private multi-user Meta Conversions API Gateway hub, which has the following benefits:

• Ensure optimal data routing for each website, enable advanced matching, attribute more conversions, and improve ad relevance.
• Predictable price. Pay a flat fee of $500 monthly for up to 1 billion requests.
• Select from up to 25 server locations.
• Connect an unlimited number of pixels in the different Facebook Business Managers.
• Manage access for each account/website individually.

Please contact our support team for a private multi-user Meta 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 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 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.

If you have further questions, please check the Stape knowledgebase or contact our support team.