Connecting Meta CAPI (Signals Gateway Setup)

Overview

Signals Gateway is LayerFive's server-side connection to Meta's Conversions API (CAPI). It sends event data directly from your website to Meta, improving the accuracy and reliability of your Meta attribution by reducing dependence on browser-based tracking.

Setup is a guided three-step flow: connect your Meta account, optionally configure a custom tracking domain, and set up your data pipeline. Most accounts can complete the full setup in under 15 minutes (longer if you choose to configure a custom domain, since DNS changes take time to verify).

Where to start: This setup flow appears the first time you connect Meta CAPI. If you've already completed it and need to make changes, use View Configuration from the Setup Complete summary screen, or check with your CSM for the direct path in your account.

Step 1: Get Started — Connect Meta CAPI

This is the first step in setup. You connect your Meta Business Account before any domain or pipeline configuration happens. Navigate to Edge and Select CAPI

What to do:

1. Click Configure META CAPI and click Connect

2. LayerFive handles the Meta authentication and connection automatically in the background

3. No manual entry of Business ID, Dataset ID, or Access Token is required at this step

4. On success, you're automatically advanced to Step 2

Only the Signals Gateway pipeline type is supported. You won't see a pipeline type selection screen — clicking Connect takes you straight into the Meta CAPI connection.

Once connected, this step appears as Meta CAPI connected on the final summary screen, with a Disconnect option available.

Step 2: Configure DNS (Optional)

This step is optional. You can skip it and move directly to Pipeline Setup, or complete it to route your data through a first-party custom domain — which generally improves measurement accuracy by making your tracking look like part of your own website rather than a third-party connection.

What you'll need if you choose to set this up

• A domain associated with your business

• Access to make changes to your DNS settings through your DNS provider

Screen 1: Optimize Data Routing (Intro)

Explains the benefit of custom domain routing. Two options:

Screen 2: Choose Your Signals Gateway Domain

You'll set up a subdomain on a domain you already own.

Requirements:

• Must be based on a domain you already own

• You need access to update DNS settings through your DNS provider

• The Signals Gateway domain can't already be in use elsewhere

Screen 3: Configure DNS to Connect Domain

You'll create two CNAME records with your DNS provider to verify domain ownership and route traffic to Signals Gateway. Here's an example:

Important timing notes:

• DNS changes typically take about 1 hour to propagate and reflect as verified

• You must complete this process within 48 hours, or you'll need to start the domain setup again

• If you need to change domains or restart, use the reset your domain link on this screen

Once verified, this step appears as Custom domain verified on the final summary screen, with a View DNS records option. If you skipped this step, it won't appear on the summary at all.

Step 3: Pipeline Setup

By this point, Meta CAPI is already connected (Step 1). This step focuses on naming your pipeline and configuring your Signals Gateway Pixel.

Screen 1: Set Up Signals Gateway Pixel

You'll be asked: Does your website have a Meta Pixel?

If Yes (recommended):

• Your existing Meta Pixel settings are applied to the new Signals Gateway Pixel

• Event data is sent to the same Meta dataset you already use

• Running both pixels together typically performs better

• Installation is faster since settings carry over

If No:

• The Signals Gateway Pixel will be set up fresh and will send first-party website data directly to Meta

• You'll configure a new pixel and its events from scratch

Both paths include a Connect Meta Pixel step — the only difference is when it happens in the sequence. On the Yes path, it comes right after Get Started. On the No path, it comes after you've added your pixel code.

Screen 2: Connect Meta Pixel

You'll manually connect your Meta business portfolio so Signals Gateway can create or link the pixel using your existing Meta Pixel settings.

The Connect button activates once all three fields are filled in.

Screen 3: Setup Method

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

Screen 4: Add Pixel Code

The instructions shown depend on the method you chose in the previous screen.

Manual:

• A base code snippet is shown for you to paste into your website's <head> section, just above </head>

• Copy instructions — share these with a developer

• Copy base code — add the pixel yourself

• The base code automatically records page views; you can select additional web events to track

Shopify:

• A custom code snippet is shown (includes your Pixel ID and Host)

• Deploy it via Shopify Admin → Settings → Customer Events

• Use the Copy custom pixel code button

Google Tag Manager:

• Your Pixel ID, Pixel Host, and Pixel Script are each shown with individual Copy buttons

• Paste these into the Tag Configuration page in your GTM account (Template Preview)

Screen 5: Connect to Meta / Finish

The final screen in pipeline setup. Confirms your Meta connection and completes the process. Clicking Continue takes you to the Setup Complete summary.

Setup Complete — Summary Screen

Once all steps are finished, you'll land on a summary screen confirming everything is connected.

Progress Tracker

Shows your completed steps in sequence:

• Get Started ✓

• Configure DNS ✓ (only shown if you completed this step; omitted if skipped)

• Pipeline Setup ✓

Summary Cards

Meta CAPI connected This account is connected to Meta CAPI. Action available: Disconnect

Disconnect is destructive. It removes your pipeline, your custom domain and DNS configuration, and unlinks your Meta account entirely. Only use this if you intend to fully remove the integration.

Custom domain verified (only shown if DNS setup was completed) Events route through your custom domain (e.g. signals.l5id.com). Action available: View DNS records

Your data pipeline is configured Your Signals Gateway pipeline is set up and provisioned. Events will appear in the CAPI dashboard once they start flowing. Actions available: Delete configuration | View Configuration

Delete configuration removes only the pipeline setup — it does not affect your Meta CAPI connection or your DNS/domain setup. This is the safer option if you just need to reconfigure your pipeline without starting over completely.

View Configuration opens your existing pipeline setup in edit mode, so you can review or update any step without starting from scratch.

Troubleshooting

My DNS records show "Waiting" after more than an hour DNS propagation can occasionally take longer than expected depending on your provider. Double-check the records were entered exactly as shown, including the full record name. If it's been several hours, use the reset your domain link to restart the process.

I ran out of time on the DNS setup (48-hour window) You'll need to restart the domain configuration from Screen 2 of Step 2. Your Meta CAPI connection from Step 1 is unaffected — you won't need to reconnect Meta.

I'm not sure whether to choose Yes or No for "Does your website have a Meta Pixel?" Check Meta Events Manager for your business. If you see an existing pixel actively receiving events, choose Yes — this lets Signals Gateway share its configuration instead of starting from scratch. If you're not sure or don't have one yet, choose No.

I accidentally clicked Disconnect on the Meta CAPI card This is destructive and removes your entire setup, including your custom domain and pipeline. You'll need to go through the full setup flow again, including reconnecting Meta and reconfiguring DNS if you had it set up.

I need to change my pipeline configuration but don't want to lose my Meta connection or domain Use Delete configuration on the pipeline card, not Disconnect on the Meta CAPI card. This removes only the pipeline, leaving your Meta connection and DNS setup intact.

Related Articles

• Tag Management

• System Settings

• Integrations

• Attribution Analytics

• Glossary of Terms