OrcLink
← Help Center

Ad platforms

Snapchat Conversions API

Send outcomes to Snapchat Conversions API through the approval gate, matched by click id or hashed email and phone.

Built, not yet tested liveBuilt. Not yet tested against a live Snapchat Conversions API account.

Live: shipped in OrcLink's production release before this one. Built, not yet tested live: built and tested with sample data, not yet run against a live account of the vendor. Coming soon: listed, not available to connect yet.

How to connect

  • Conversions > Destinations > Snapchat Conversions API: Snap Pixel ID; Conversions API token (Events Manager) (stored encrypted).
  • Then send a test event and check Conversions > Audit log.

What OrcLink reads

  • Ad cost: imported by API in Conversions > Ad costs (campaign, ad group and keyword, with impressions and clicks), once a day while the scheduled jobs ad-spend and jobs run (your OrcLink operator schedules them). Cost days are the ad account's calendar days (in the ad account's time zone); conversion and outcome days are UTC days. Near midnight, a cost and its conversions can be on different days.

What OrcLink writes back

  • Conversions for the stages you set to relay (Outcomes > Stages), each with its click id and the hashed email and phone the platform matches on. Each batch waits for approval when approval is on (the default).
  • The browser user agent, when "send user agent" is on in the Compliance tab (never in strict consent mode).

Never stored

  • Raw email or phone: only hashes leave OrcLink.
  • Page paths, page titles, referrers and IP addresses: never sent to an ad platform.

Known limits

  • Snapchat matches on the hashed email or phone number; the Snapchat click id (ScCid) is added when the click had one. A conversion with only a click id is skipped. Snapchat takes a fixed list of event names: a purchase is PURCHASE, a booked appointment RESERVE, a lead SIGN_UP. A generic label (event_1 to event_5, under a neutral-name rule) goes as CUSTOM_EVENT_1 to CUSTOM_EVENT_5; other labels are not sent. In HIPAA mode and for health workspaces nothing is sent to Snapchat. The test button uses Snapchat's validate endpoint: nothing is recorded.

Status: built from Snap's docs (read 2026-10-05). Not yet checked against a live account.

Conversions (Snapchat Conversions API v3)

What OrcLink sends, per conversion: the Snapchat event (PURCHASE, RESERVE for a booked appointment, SIGN_UP for a lead, PAGE_VIEW), the event time, the event id (dedupe with the Snap Pixel), the hashed email and the hashed phone number (only a number given with its country code), the hashed customer id, the Snapchat click id (ScCid) when the click had one, the user agent when the workspace allows it, the site origin (never a path), and the value with its currency.

  • Matching: Snapchat needs the hashed email or phone. A conversion with only a click id is skipped ("needs an email or phone hash").
  • A purchase needs a value with a currency; without both it is skipped.
  • HIPAA mode: nothing is sent, whatever the ad category (a workspace in HIPAA mode is treated as a health workspace for this platform). The destination cannot be connected or switched on while HIPAA mode is on; one connected before shows "Blocked: HIPAA mode" and sends nothing. Withheld events show as Blocked in the Audit log with the reason hipaa_mode.
  • Health workspaces: nothing is sent (not even page views). To open this platform for health workspaces, the owner must first confirm its terms on health data in writing.
  • Not captured or sent: the _scid Snap Pixel cookie.
  • Consent: OrcLink sends no Limited Data Use / opt-out flag. A visitor who refused advertising consent sends OrcLink no click id and no conversion at all (the capture script stays silent, and orc.trackConversion resolves false), so nothing of that visit can reach Snapchat. Conversions your server sends through the API, or that come from a CRM, carry no consent state: send OrcLink only conversions of people who agreed to advertising use, or turn on strict consent mode.

Setup:

  1. In Snapchat Ads Manager, open Events Manager and create (or pick) the Snap Pixel. Copy the Pixel ID.
  2. Generate a Conversions API token for that pixel.
  3. In OrcLink, Conversions > Destinations > Snapchat: paste the Pixel ID and the token. Approval is on by default.

Smoke test (owner): click Send test event. It goes to Snap's /events/validate endpoint, which checks the request and records nothing. A good answer reads "Snapchat validated the test event (validate endpoint): nothing was recorded." (Snap answers status: VALID). Then send one real conversion with an email through the Approvals tab and check Events Manager.

Ad cost (Snapchat Marketing API)

Ad costs > Connect Snapchat Ads, with:

  • the ad account ID (a UUID),
  • a Snap app's client ID and secret, and a refresh token with the snapchat-marketing-api scope (Business Manager > Business Details > OAuth app),
  • the ad account currency and time zone (Ads Manager > ad account settings; for example USD, America/Los_Angeles). Days start at midnight in that zone.

OrcLink reads spend, impressions and swipes (as clicks) per campaign and day, the last 3 days every day while the scheduled jobs ad-spend and jobs run (your OrcLink operator schedules them), up to 90 days back on the first pull.