Prerequisites
You need admin access to your Meta Business Manager, your Pixel ID from Events Manager, and a Datahash Signals account. Your Meta Pixel should already be firing on the site; CAPI runs alongside it and deduplicates against it. No developer time is required.
Step 1: Connect Meta as a destination
In Signals, choose Meta Conversions API from the destination catalog. Sign in with your Meta Business account and grant access to the ad account and pixel you want to feed. Signals generates and stores the access token; you never handle it manually.
Step 2: Connect your website as a source
Pick your source from the catalog. For Shopify, Salla, Zid, WooCommerce, and similar platforms this is a one-click app or plugin install. For custom sites, add the lightweight Signals tag through your tag manager.
Step 3: Map your events
Signals proposes a standard mapping out of the box: PageView, ViewContent, AddToCart, InitiateCheckout, and Purchase, each carrying value, currency, and SHA-256 hashed customer identifiers. Review the mapping, adjust names if your taxonomy differs, and confirm. Deduplication against the pixel via event_id is on by default.
Step 4: Go live
Enable the connection. Events start flowing server-side immediately, in parallel with your existing pixel.
Verify
Open Meta Events Manager and check the pixel’s overview. Within a few minutes you should see events arriving from both Browser and Server, with a Deduplicated label where both fired. Check Event Match Quality per event; purchase events with email and phone hashed typically score noticeably higher than pixel-only. Use Test Events with your test code for a real-time trace.
Troubleshooting
If server events do not appear, reconfirm the pixel selection on the destination and that the connection is enabled. If events show as duplicates instead of deduplicated, confirm your pixel sends the same event_id as the server event; Signals surfaces mismatches on the connection health screen. If EMQ is lower than expected, check that email and phone fields are being captured at checkout so they can be hashed and attached.