Meta's Conversions API Gateway: Simple Setup Guide

If you're running Meta ads in 2026 without Conversions API, you're losing 20-40% of your tracking signal. Apple's ATT, ad blockers, browser tracking restrictions and slow page loads all eat browser-side pixel events. CAPI fixes the gap by sending events server-side.

The problem has always been setup complexity — until Meta introduced the Conversions API Gateway. This post walks through what the Gateway does and how to set it up for UK Shopify, WooCommerce, and custom sites.

What CAPI Gateway is

The Conversions API Gateway is a Meta-managed AWS deployment that sits between your website and Meta's CAPI endpoints. It acts as a server-side relay, capturing events from your site without you needing to write custom server-side code.

The gateway handles:

Event collection from your domain
Hashing of personally identifiable information
Deduplication with browser pixel events
Forwarding to Meta's CAPI endpoints
Connection monitoring and error logging

You don't have to maintain it. AWS billing happens on Meta's account.

CAPI Gateway vs other CAPI methods

Method	Setup difficulty	Maintenance	Cost
Direct CAPI integration	High	High	Free (your servers)
CAPI via partner (Shopify, Stape)	Low	Low	Some free, some paid
CAPI Gateway (Meta-managed AWS)	Medium	None	Free for first year, then small AWS charges
Server-side GTM	High	High	Free + GTM costs

For most UK advertisers, the choice is between a partner integration (if you're on Shopify/WooCommerce) and the Gateway (if you're on a custom site).

Setting up the Gateway

Step 1: Verify prerequisites

You need:

A verified domain in Business Manager
Pixel installed and firing on your site
AWS account access (Meta handles deployment, but your team approves)

Step 2: Launch the Gateway

In Events Manager → Settings → Conversions API → Set up CAPI Gateway. Click "Get Started" and follow the AWS deployment wizard. It takes 10-15 minutes.

Step 3: Configure events

Choose which events to forward (PageView, ViewContent, AddToCart, InitiateCheckout, Purchase). Mark Purchase and Lead as priorities.

Step 4: Test events

Use the Test Events tab in Events Manager to confirm both browser and server events are received and deduplicated.

Step 5: Monitor for 7 days

Check for missing events, deduplication errors, and connection issues. The Gateway dashboard shows real-time status.

Setting up CAPI for Shopify (no Gateway needed)

Shopify includes native Meta CAPI integration. To enable:

In Shopify admin, go to Sales Channels → Facebook & Instagram
Connect your Pixel and Business Manager
Toggle on "Customer data sharing" → Maximum
Enable Conversions API

Test events in Meta Events Manager to confirm.

Setting up CAPI for WooCommerce

WooCommerce has multiple plugin options:

PixelYourSite Pro (paid)
PixelMe
Facebook for WooCommerce (official, free)

The official Facebook for WooCommerce plugin handles CAPI. Configure it in WooCommerce → Settings → Integration → Facebook.

FAQ

Is CAPI Gateway free?

Free for the first year on AWS's free tier. After that, AWS charges apply (typically £5-30/month for most sites).

Do I still need the Pixel if I have CAPI?

Yes. They work together via deduplication. Run both for the strongest signal.

Will CAPI fix all my tracking gaps?

It recovers most ad-blocker and iOS losses, but not 100%. Expect 20-30% recovery on top of pixel-only setups.

What's deduplication?

When the same event fires from both pixel (browser) and CAPI (server), Meta uses event_id to avoid double-counting. Both events should share the same event_id for deduplication to work.

Can I send custom events through CAPI?

Yes — any event you fire in the pixel can also fire via CAPI.

Does CAPI send personal data to Meta?

Yes, hashed. Meta uses email, phone, IP and cookie data (all hashed with SHA-256) to match users to ads. UK GDPR rules require user consent for this.

Is the Gateway GDPR-compliant?

Yes, when implemented with proper consent. You're still responsible for collecting and respecting user consent before firing events.

Common mistakes

Not setting event_id for deduplication. Causes double-counting.
Sending unhashed data. Meta will reject it.
Forgetting consent management. GDPR violations.
Skipping test events verification. Silent failures cost weeks of data.

Why this matters

Better tracking signal = better Estimated Action Rate = lower CPAs across the board. CAPI is the single highest-leverage technical change you can make to a Meta account in 2026.

Pix-Vu and CAPI

Pix-Vu doesn't replace tracking, but the better your tracking, the better Meta's algorithm uses the creative variety Pix-Vu provides. Strong CAPI + diverse creative = the algorithm's ideal feeding ground. Try it at pix-vu.com.