OrcLink
← Help Center

Ad platforms

StackAdapt conversions

Coming soon. StackAdapt: not available yet. StackAdapt matches server conversions on its own click id, which OrcLink cannot store yet, and StackAdapt's postback format is not published.

Coming soonComing soon: StackAdapt: not available yet. StackAdapt matches server conversions on its own click id, which OrcLink cannot store yet, and StackAdapt's postback format is not published.

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

  • Not available yet: the destination cannot be switched on and no test can be sent.

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).

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

  • StackAdapt cost can already be imported in Ad costs.
  • StackAdapt: not available yet. StackAdapt matches server conversions on its own click id, which OrcLink cannot store yet, and StackAdapt's postback format is not published.

Conversions: the adapter is built behind "coming soon" and never sends. StackAdapt matches server conversions on its own click id (the {SA_POSTBACK_ID} click-URL macro, read as sapid), which OrcLink cannot store yet (needs a database column), and StackAdapt's postback format is only described by third parties. OrcLink would send the click id and the event id only (StackAdapt's other server API needs the visitor's raw IP address, user agent and email, which OrcLink never sends). Health, legal and financial workspaces, and every workspace in HIPAA mode: blocked.

Cost: the StackAdapt importer already exists (Ad costs > Connect StackAdapt).