AWIN
Datafly Signal reports sales and leads to Awin server-to-server through the Awin Conversion API, so the publisher who referred the visitor is credited and paid.
Why route AWIN through Datafly Signal
- Commission is not lost to blocked tags. A browser conversion tag from an affiliate network is blocked for part of your traffic; Signal reports the sale from your own server, so the publisher who referred the visitor is paid.
- The click reference is captured first-party. Signal captures the network’s click ID when the visitor lands and attaches it to the later sale, without waiting for advertising consent: affiliate tracking is how a publisher is paid for a genuine referral.
- No vendor tag on the page. Removing it removes its page weight and its independent access to your visitors.
Prerequisites
Get API access
In the Awin interface open Account > API Credentials and generate an API token. Signal sends it as the x-api-key header.
Find your advertiser ID
Your advertiser ID is under Account > Account Details. It is part of the Conversion API URL.
Check your commission groups
Open Commission Management and note the commission group code sales should be paid on (upper case). Leave the setting empty to use DEFAULT.
Configure in Signal
Configuration Fields
| Field | Required | Description |
|---|---|---|
advertiser_id | Yes | Your Awin advertiser ID (Account > Account Details). It is part of the Conversion API URL. |
api_key | Yes | Your Awin API token (Account > API Credentials), sent as the x-api-key header on the Conversion API. |
test_mode | No | When enabled, orders are sent with isTest=true: Awin validates them but does not track them. Turn off before going live. |
commission_group | No | The commission group code Awin pays on when the event carries no commission_group property. Must exist in Commission Management in Awin (upper case). Leave empty for DEFAULT. |
currency | No | ISO 4217 code used when an event carries no currency. Awin requires a currency on every order, including leads. |
Management UI Setup
- Go to Integrations > Add Integration > AWIN.
- Choose a preset: Default (
default), Retail (ecommerce), Lead Generation (lead_gen), Insurance (insurance), Travel (travel). - Fill in the fields above and click Save.
Request format
POST https://api.awin.com/s2s/advertiser/{advertiser_id}/orders
x-api-key: <API token>
{"orders": [{"orderReference": "ORD-1001", "amount": 259.99, "currency": "GBP",
"channel": "aw", "awc": "1001_1758499000_abc123", "voucher": "SAVE10",
"isTest": false, "commissionGroups": [{"code": "DEFAULT", "amount": 259.99}]}]}orderReference, amount, currency, channel and commissionGroups are required on every order. Attribution needs awc (or a voucher code assigned to a publisher). Orders are batched and sent at most every 10 seconds, as Awin asks.
Event Mapping
| Signal event | Vendor event | Presets |
|---|---|---|
purchase | sale | Default, Retail, Insurance, Travel |
generate_lead | lead | Lead Generation, Insurance |
sign_up | lead | Lead Generation |
quote_completed | lead | Insurance |
For leads (Lead Generation and Insurance presets) the amount is the number of leads, 1, as Awin documents for lead transactions. channel is the event’s channel property when your site sends the last-click channel, otherwise aw, the fallback Awin documents for de-duplication.
amount is the event value (else revenue). Awin pays on the subtotal after discounts and before tax and delivery, so send a net value if your commission terms require it (#1383). Basket-level data is not sent yet (#1382).
Signal forwards properties the preset does not map unless the integration’s strict output contract is on. Turn on strict_output_contract for this integration so only the documented fields are sent.
Identity
Attribution is by the awc click reference Awin appends to your landing page; Signal captures it as click_ids.awc. No personal data is sent: the Conversion API has no field for it.
Consent
Awin is an attribution destination. It is not gated on advertising consent by default, and its click reference is captured without it, because affiliate tracking is how a publisher is paid for a referral. Set a consent category on the integration if your legal basis requires one.
Troubleshooting
| Problem | Solution |
|---|---|
401 Unauthorized | Regenerate the API token and update api_key. |
400 or 406 | An order is missing a required field; check the order reference, amount and currency on the event. |
| Sale recorded but not attributed | The visitor has no awc; confirm your Awin links land on a page running Datafly.js. |
| Test orders appearing in reports | Turn on Test Mode while validating; it sends isTest: true. |
Blueprint
The AWIN blueprint version is 0.5.0. It was last reviewed against the vendor’s documentation on 2026-09-22.