Setting Up Meta Conversions API (Signals Gateway)

Overview

Meta's Conversions API (CAPI) sends conversion data to Meta directly from your server rather than relying only on browser-based pixel tracking. This improves measurement accuracy, especially as browser privacy restrictions continue to limit cookie-based tracking.

LayerFive's Signals Gateway sets this up for you through a guided onboarding flow. This guide walks through the three stages:

1. Account Setup — name your managed account

2. Data Routing — route data through a first-party custom domain for better measurement

3. Data Pipeline — connect your website data to Meta

Before you begin, you'll need: a domain associated with your business, access to update DNS settings with your domain provider, and access to your Meta Business Account.

Step 1: Account Setup

The first screen asks you to name your managed account.

Tip: Use a name that matches your related Meta Business Account. This makes accounts easier to identify later when you're managing multiple connections.

Click Continue to proceed.

Step 2: Data Routing

Data routing sends your tracking data through a first-party custom domain that you own, rather than a third-party domain. This improves measurement performance and data reliability.

This step has three parts.

2a — Optimize Data Routing

This intro screen explains what you'll need:

• A domain associated with your business

• Access to make changes to your DNS settings

If someone else on your team manages your DNS, you can share the setup instructions with them from this screen.

Click Optimize to begin domain setup.

2b — Choose Your Signals Gateway Domain

Here you'll create your custom Signals Gateway domain, built from two parts:

This would create a domain like routing.mybusiness.com.

Requirements:

• The domain must be based on a domain you already own

• You must have access to update DNS settings through your DNS provider

• The domain you choose cannot already be in use elsewhere

Click Continue to proceed to DNS configuration.

2c — Configure DNS

To connect your domain, you'll add two CNAME records in your DNS provider's account. These verify that you own the domain and direct traffic correctly.

You'll create:

1. A routing record that directs traffic to Signals Gateway

2. A domain ownership validation record that confirms you own the domain

Each record shows a status indicator that updates once the record is detected.

Important timing notes:

• DNS changes typically take about 1 hour to take effect

• The process must be completed within 48 hours, or you'll need to start again

• If you need to change your domain or restart, use the reset your domain link

Tip: Adding DNS records varies by provider (GoDaddy, Cloudflare, Namecheap, etc.). If you're not sure how to add a CNAME record, your DNS provider's help documentation will have provider-specific steps, or your CSM can guide you.

Step 3: Data Pipeline Setup

A data pipeline connects your website data to a destination — in most cases, Meta.

Choosing Your Pipeline Type

You'll choose between two pipeline types:

The setup flow branches based on which you choose. The most common path is the Signals Gateway Pipeline, covered below.

Signals Gateway Pipeline Setup

Name Your Pipeline and Choose Data Sources

Data source options:

• Signals Gateway Pixel — shares activity from your website such as content views, add-to-cart events, and purchases

• File Upload — adds data from files, automatically or manually

Your data destination is Meta by default. (Other destinations like Google BigQuery and custom connectors are available but handled in the background.)

Set Up Your Signals Gateway Pixel

Name your pixel, then indicate whether your website already has a Meta Pixel installed.

Connect Your Meta Pixel (if you have one)

If you indicated you have a Meta Pixel, you'll connect your Meta Business Account using one of two methods:

Recommendation: Use Facebook Login unless you have a specific reason to connect manually. It's faster and avoids copy-paste errors with IDs and tokens.

Choose Your Setup Method

Select how you'll add the Signals Gateway Pixel to your website:

Add the Pixel Code

For Shopify: Copy the displayed code snippet and paste it into your Shopify Customer Events admin page. Use the Copy custom pixel code button to copy it exactly.

For manual installation: Paste the base pixel code into your website's HTML.

Configure Your Pixel

Finally, configure how your pixel gathers and processes data.

Data Enhancement (enabled by default) lets you send additional customer data to improve matching accuracy. When enabled, you can choose to include details such as email, name, phone number, location, and other identifiers.

Contact Data Treatment:

Privacy note: If you're sending customer contact data, consider using the Hashed option to protect that information in transit. Confirm your data sharing complies with your privacy policy and applicable regulations.

Click Continue to complete setup.

Conversions API Gateway Pipeline (Alternative Path)

If you chose the Conversions API Gateway Pipeline instead, you'll connect your existing Meta Pixel directly.

In the current version, connection is done manually. Enter the following from your Meta Events Manager dataset:

• Meta Business ID

• Dataset ID (Pixel ID)

• Access Token

Click Connect to finish.

Facebook Login for this pipeline type is planned for a future release. For now, manual connection is the available method.

After Setup

Once your pipeline is live, conversion data begins flowing to Meta through the Conversions API. It may take some time for events to appear in your Meta Events Manager.

To verify everything is working:

• Check that your DNS records show a verified/connected status

• Confirm events are appearing in Meta Events Manager

• Watch your Coverage % in LayerFive's Attribution Analytics — improved server-side tracking should support stronger coverage over time

If events aren't appearing after a few hours, confirm your DNS records are verified and your pixel code is correctly placed. Your CSM can help troubleshoot.

Related Articles

• Setting Up Google Conversions API

• Configuring DNS for Signals Gateway

• Tag Management

• Attribution Analytics