OrcLink
← Help Center

Ad platforms

Amazon Ads Conversions API

Coming soon. Amazon Ads: not available yet. It needs an Amazon Ads API client approved by Amazon and a Login with Amazon sign-in, which OrcLink does not have yet, and Amazon needs the country of each conversion, which OrcLink does not store.

Coming soonComing soon: Amazon Ads: not available yet. It needs an Amazon Ads API client approved by Amazon and a Login with Amazon sign-in, which OrcLink does not have yet, and Amazon needs the country of each conversion, which OrcLink does not store.

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: upload a CSV in Conversions > Ad costs (platform column "amazon"). 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

  • Amazon matches on hashed email and phone (no click id). Amazon cost: upload a CSV in Ad costs (platform column "amazon").
  • Amazon Ads: not available yet. It needs an Amazon Ads API client approved by Amazon and a Login with Amazon sign-in, which OrcLink does not have yet, and Amazon needs the country of each conversion, which OrcLink does not store.

The adapter is built (request shape from Segment's open-source Amazon Conversions API destination; Amazon's docs pages could not be read; UNVERIFIED) but it never sends. It needs, first:

  1. An Amazon Ads API client approved by Amazon (an application OrcLink files) and a Login with Amazon sign-in per workspace.
  2. The country of each conversion (Amazon requires countryCode; OrcLink does not store one per conversion).
  3. Amazon's email normalisation (it drops characters other than a-z, 0-9, ., @, +, -) differs from OrcLink's stored hash.
  4. The PHI filter removes any key named name; Amazon's event requires eventDescription.name.

Amazon has no click id for this API: matching would be by hashed email and phone. Health, legal and financial workspaces, and every workspace in HIPAA mode: blocked (rules unclear).

Cost: CSV upload only (platform amazon), see csv-cost.md.