Skip to content

Conversions API Gateway and Signals Gateway: Domain Setup in GCP

Updated: Apr 30, 2026

When you set up your Conversions API Gateway or Signals Gateway, a data routing domain will be automatically generated during your setup process. Creating a custom domain for your Gateway Product will let you route event data to your account directly from a server, which may help improve measurement performance.

Follow the steps below to set up a custom domain for a Gateway Product setup that hosts multiple accounts.

Domain Setup Option Selection

After connecting a Meta business portfolio, you will be directed to the Domain management page, or you can navigate to the page using the left sidebar under Settings.

Domain management page showing the choice between GCP Load Balancer and Cloudflare custom domain providers

On this page, you can choose whether to use GCP Load Balancer or Cloudflare.

If you anticipate fewer than 13 domains will be set up on your Gateway Product account, we recommend GCP Load Balancer.

If you anticipate supporting more domains, Cloudflare has the capacity to support more domains.

If you are unsure, we recommended that you select GCP Load Balancer. Once you choose GCP Load Balancer, you will not be able to select Cloudflare as a provider.

Option A: Set Up Domain Using GCP Load Balancer

Choose the GCP Load Balancer method. Then enter a domain.

Choose domain step with prefix and root domain fields to enter your custom Conversions API Gateway domain

Click Continue. Make sure you have control of the domains, then Confirm the domain.

Confirm Conversions API Gateway dialog listing domain requirements with Edit domain and Confirm buttons

Follow the instructions on the next page to set up your DNS records:

Configure DNS step showing A and AAAA records to create for verifying ownership and routing, both with Waiting status

Set DNS records in your DNS service (for example, Amazon route 53), and wait for the status to change to Complete.

When the domain becomes active, you will see the below screen.

Domain management Active products view showing GCP Load Balancer with an active Data routing domain

Option B: Set Up Domain Using Cloudflare

Choose the Cloudflare method

Navigate to the Domain Management page. Review the instructions and requirements, then click the Get started button at the bottom of the page. In order to complete the setup process, you'll need:

  • A Cloudflare account with admin access.
  • Admin access for your cloud platform account.
  • 30 minutes to complete the process.

Cloudflare setup intro page describing the data routing flow, prerequisites, and benefits with a Get Started button

Choose a Cloudflare setup method. We recommended that you select the option to register a new domain and use it with Cloudflare. Choose the option you'd like to select.

Choose a Cloudflare setup method screen with three options: register a new domain, use an existing Cloudflare account, or use a domain from another provider

Option 1: Register a new domain and use it with Cloudflare

Select this method if you need to set up a new Cloudflare account and a new domain for custom data routing.

Register a new domain with Cloudflare instructions: create an account, add a payment method, and add a domain to Cloudflare

Option 2: Use an existing Cloudflare account

Use an existing Cloudflare account instructions: log in, add a payment method, and add a domain to Cloudflare

Option 3: Use an existing domain

Use an existing Cloudflare account steps: log in with administrator access, select a domain, and enable Cloudflare for SaaS

Use a domain from another provider with Cloudflare.

Select this method if you have a domain registered with another provider (such as Godaddy or AWS Route 53) and want to use it with Cloudflare.

Use a domain from another provider on Cloudflare instructions: create an account, add a payment method, and add a domain with another registrar

On the next page, you'll find instructions for how to proceed on Cloudflare, depending on your selected setup method.

Next you will start the Cloudflare setup process.

Cloudflare setup steps for an existing account: log in, add a payment method, and add a domain via the Register a new domain with Cloudflare banner

Continued Cloudflare setup steps: select a domain, enable Cloudflare for SaaS, enable additional settings, and generate an API token with the listed permissions

Follow the instructions in the Gateway Product UI to set up Cloudflare.

The admin can now add host users to the Gateway instance or create advertiser accounts.

Host Manage Accounts page with an empty accounts table showing No Data and an Add account button

First Party Domain Setup

Step 1: Go to Data Routing Section under Gateway Product

Data routing section under Conversions API Gateway showing the Optimize data routing to improve performance panel with an Optimize button

Step 2: Click on Optimize. (Note: This button is only available if you have set up your agency domain)

Data routing Choose domain step with empty prefix and root domain fields for setting up a first-party Conversions API Gateway domain

Step 3: Enter the domain name and click Continue:

Choose domain step with prefix testprefix and root domain mybusiness.com entered, showing the resulting Conversions API Gateway domain and a Continue button

Step 4: Click Confirm

Confirm Conversions API Gateway dialog showing the web address testprefix.mybusiness.com with Edit domain and Confirm buttons

Step 5: Setup CNAME record from the first-party domain to the agency domain

Configure DNS step showing one CNAME record for testprefix.mybusiness.com with a Waiting status to verify ownership and route traffic

Step 6: Once the CNAME record is verified, domain setup is complete

Data routing page showing an Optimized status confirming the first-party Conversions API Gateway domain is set up, with a Change button

See Also

Unofficial mirror for reference/search purposes. All content originates from developers.facebook.com — see the source link at the top of each page. Machine-readable indexes: llms.txt · llms-full.txt · About