How to configure Meta CAPI Gateway

Since Meta Conversions API Gateway routes the events your site already sends, you’ll need to set up Meta web tracking on your site. 

1. 1.
   Log in to your Stape account and click Gateways in the dashboard.

2. Click Create gateway → Create Meta CAPI Gateway.

3. Fill in:

• Gateway name – a descriptive label.
• Admin email – the account you'll use to log in to Meta CAPI Gateway. It can be different from your Stape login.
• Server location – pick the region closest to the majority of your traffic.

4. Click Create gateway.

5. Select a subscription plan and click Continue.

6. Wait for the gateway status to change to Running.

1. 1.
   Go to your email and click the invitation link.

2. Create an account.

3. In the gateway hub, click Add data source.

4. Add your data source. You can either:

• Connect with Meta (recommended) – CAPIG pulls your Business Account, datasets, and tokens for you.
• Manual connection – use this option if you can't use Facebook Login for security/policy reasons, or you want to control exactly which system user the token belongs to. Enter the following:

  •  Meta Business ID - the unique ID of the Business that owns the dataset.
  •  Dataset ID - the Meta dataset / pixel ID from Events Manager.
  •  Access Token - a permanent CAPI token generated in Events Manager.

Click Connect.

4.1. Select your business portfolio.

4.2. Select your dataset.

4.3. Click Confirm and continue.

5. You will see the pixel on your dashboard.

Routing Meta Conversions API Gateway through a custom domain on your own site measurably improves match quality and reduces ad-blocker loss.

1. 1.
   Go to Data routing → click Optimize.

2. Enter your subdomain, which consists of a prefix (for example, data, events, or gateway) and the root domain of your website (for example, example.com)

3. In your DNS provider (in our case Cloudflare), add a new record:

• Type - CNAME
• Name - the New managed domain from step 2.
• Target - the Conversion API Gateway domain from step 2.
• Proxy status - off. If you keep it on, the Stape support team might not see the record and help with debugging.

Click Save.

4. Back in CAPI, click Continue. You should see the Optimized status.

Domain verification can take up to 72 hours, but it usually happens within 30-60 minutes if your DNS records are correct. If it takes more time for you, there may be a problem with your configurations.

There are the main reasons why a subdomain may not verified:

• Typo in the Name/Host field – some DNS managers automatically append your root domain. If you enter data.yourdomain.com instead of just data, the record might resolve to data.yourdomain.com.yourdomain.com. In some DNS providers, only the prefix (for example, data) should be entered in the Host/Name field.
• Proxy status enabled – if you use Cloudflare, ensure the proxy status for the CNAME record is set to DNS only, not Proxied.
• Target mismatch – ensure the CNAME points to the exact gateway target provided by Stape, with no spaces or typos.
• Conflicting DNS records – ensure there are no existing A, AAAA, or conflicting CNAME records for the exact same subdomain name in your DNS settings.
• Missing SSL – if you configured the custom domain using an Own CDN setup, Stape cannot verify the domain until an active SSL certificate is in place on your side.

You can check your DNS records with the Google Admin Toolbox Dig tool.

1. 1.
   Enter your custom subdomain (for example, data.yourdomain.com, without https:// or trailing slashes).
2. 2.
   Select the CNAME tab.
3. 3.
   Verify that the returned target matches the exact value provided in your Snapchat Conversions API Gateway dashboard.

Check the following:

• Events in the Meta Conversions API Gateway. Open Overview, in 30 minutes after triggering the events, you should see them in the dashboard.

• Events in Meta Events Manager. Open the connected dataset → Overview. You should see events arriving with the server parameter populated.

• Event Match Quality. In the Events Manager, check EMQ for each key event. Expect ≥ 6.0 once advanced matching data is flowing. If the score is <6.0, you can read the Facebook Event Match Quality – what it is and how to increase it article for more information.