← Help Center
Marketing tools
Awin
Visits with Awin's awc click id (or utm_source=awin) are put in the Affiliate (Awin) channel, so affiliate leads and sales show in your reports.
Built, not yet tested liveBuilt: OrcLink reads Awin's awc click id and files the visit in the Affiliate (Awin) channel. Not yet tested on live Awin clicks. Nothing is sent to Awin.
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
- No connection needed: tag your Awin links (see "Tagging Awin links"); OrcLink reads awc on its own.
What OrcLink reads
- Awin's awc click id on the landing page, read by the OrcLink script; it is kept on the visit.
What OrcLink writes back
- Nothing. Conversions are not sent to Awin: its server-to-server tracking needs your own order feed (your store's Awin plugin or Awin's MasterTag).
Never stored
- Raw email addresses and phone numbers: hashed (SHA-256) the moment they arrive.
- The raw payload: only its SHA-256, for provenance.
- Your credentials and webhook secrets in clear: they are stored encrypted (AES-256-GCM).
Known limits
- Visits with awc, or utm_source=awin, are in the Affiliate (Awin) channel. awc is kept on the visit only, not as an ad click.