Awin
Last updated
Was this helpful?
Last updated
Was this helpful?
provides a global affiliation network connecting businesses with customers. Using this destination you can implement using the same .
The Awin destination provides the following key features:
Events structure: our covers , meaning that your data is properly bridged to the expected fields in an optimized way.
Prebuilt mappings: data mapping for event-based destinations happens automatically, which simplifies user inputs.
Smart mapping: data mapping can be readjusted using your datalayer defined fields.
Support for multi-item data: information included in the array is bridged to Awin.
Commission group: remunerate different products based on your .
The parameter is appended to the landing page URL by Awin to identify the source of the click. This value is mandatory and is retrieved by getting the value of either the Click Id (See ) or the cookie, in this priority order.
Advertiser Id
Required
Your advertiser programme ID. Consult your Awin account contact or assigned integrator for more information on this value.
Conversion Type
Required
The conversion type that is bound with your activity. This can be either Sale or Lead. If conversion type is Sale, only purchase events are sent to the partner, if it's Lead, only generate_lead events are forwarded to Awin.
Click Id
Default Commission Code
The default commission code for conversion type Sale . If this is not set, the standard commission group code DEFAULT is used.
Force parts with default commission code
and amount
For conversion type Sale, set Awin parameter parts with default commission code and total amount.
Test Mode
This field is available when flagging the Advanced Settings . It's either 0 (default value) for live production or 1 for UAT/test environment: when setting to the latter, the incoming tracking requests will not be processed by Awin.
Custom Event Properties
Map your custom event properties by setting their field names in Awin property name and adding the field name holding the value in Your event property. E.g. if you input size in the Awin property name and items.0.product.size in Your event property, you will have a custom event property in Awin called size with a value based on the content of the field items.0.product.size.
generate_lead
Lead
purchase
Sale
Advertiser Id
merchant [*]
Click Id
cks [1][*]
revenue
amount
channel
ch [2]
items.X.affiliation:items.X.product.price*items.X.quantity
Default Commission Code:revenue
parts [3]
coupon
vc
currency
cr
id
ref
Test Mode
testmode
AW:P|Advertiser Id|id|items.X.product.id|items.X.product.name|items.X.product.price|items.X.quantity|items.X.product.price|items.X.id|items.X.affiliation|items.X.product.category_1
bd[X] [4]
Awin click identifier (awc). If it's not set the cookie "awc" is used. More details are available following this .
Alternatively, you can Force parts with default commission code and amount . See for more details. Accepted characters for the commission group codes are alphanumerics and letter in upper case, underscore (_) , point (.) and minus (-).
[*] Mandatory property.
[1] See for more details.
[2] Default value "aw".
[3] Computed amounts are rounded with two decimals (E.g. "DOWNLOAD:551.18|FIX-NC:15302.67"). For Sale conversion type, when the "Smart Mapping" field Item Affiliation is not filled with a proper value, the commission group code is set with the value provided in Default Commission Code . If Force parts with default commission code and amount is flagged the values is set using the Default Commission Code and revenue . See for more details.
When you select Lead as conversion type, it's set with the static string LEAD:1 .
[4] It takes into account each product.