Support

Omea Consent · Guides

Snapchat Conversions API for WordPress

Send WordPress and WooCommerce conversions to the Snapchat Conversions API – de-duplicated with the Snap Pixel and sent only with consent.

Updated · Omea Consent 1.0.2

On this page
  1. Set it up
  2. What Omea sends to Snap
  3. Consent
  4. Check it

The Snapchat Conversions API sends conversions from your server to Snap, next to the Snap Pixel. Conversions blocked in the browser still arrive, and Snap can match more of them to your ads.

Set it up

  1. Switch on the Snap Pixel Under Omea Consent › Integrations, switch on Snap Pixel and paste its Pixel ID (a UUID).
  2. Generate a token In Snap Ads Manager go to Business Details › Conversions API Tokens › Generate token and copy it.
  3. Turn on the Conversions API In the Snap Pixel card, switch on Conversions API, paste the Access token and click Save changes.
  4. Map your conversions Under Omea Consent › Conversions, choose a Snap event for each conversion – SIGN_UP, PURCHASE, SUBSCRIBE, START_TRIAL, ADD_CART, START_CHECKOUT or ADD_BILLING.

What Omea sends to Snap

What Details
Conversions Each conversion mapped to a Snap event, from the browser and the server
Server-side events WooCommerce purchases, checkouts and add-to-carts, sign-ups
Event ID The same as the pixel’s client_dedup_id, so Snap counts each once
Customer data Email, phone, first and last name, country and external ID – SHA-256 hashed
Click and browser data The ScCid click ID, the _scid cookie, IP address and user agent

Omea uses Snap’s Conversions API v3 and treats an event as sent when Snap confirms it as valid.

The Snap Pixel has no consent mode of its own, so it always waits for Marketing consent. The Conversions API follows the same rule – Omea checks Marketing consent on your server before every event.

Check it

The Snap card’s Latest server events list shows recent events as Sent or Error. If something’s missing, see Conversions API events missing.