Server-Side Tracking
- 26 Feb 2025
- DarkLight
Server-Side Tracking
- Updated on 26 Feb 2025
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
The Awin Conversions Connector can be used to setup server-side tracking in Tealium. The Awin Conversions Connector makes use of the Awin Conversion API, and please see more information on our API documentation.
Step 1 - Tag Configuration
Go to the Connector Marketplace and add a new connector. For general instructions on how to add a connector, see Tealium’s documentation About Connectors.
After adding the connector, the following settings will need to be configured:
Token
The required API token. This token is linked to the Awin account and please see the Authentication guide for more information on how to access your token.
Merchant (Advertiser ID)
If you’re unsure, you should have received this ID from your assigned integrator or you can find it in the Awin UI > Account > Overview .
Click Done when you are finished configuring the connector.
Deduplication
If required, deduplication setup can be achieved and please see our Channel Parameter article for full information.
Step 2 - Actions
Action Name | AudienceStream | EventStream |
|---|---|---|
Send Conversion | ||
Product Level Conversion |
Click Continue to configure the connector actions. Enter in a name for the action and then select the action type from the drop-down menu.
The following section describes how to set up parameters and options for each action.
Send Conversions
Server to Server Tracking is now a mandatory element of tracking. The requirement is that conversion data is sent (via a HTTPS request through the Tealium Connector) directly from the Tealium Customer Data Hub to Awin’s servers. This is to ensure a Hybrid Tracking Solution.
Parameters
Parameter | Description |
|---|---|
Total Amount | (Required) The order subtotal amount after any relevant discounts are applied, but prior to any additional fees such as taxes, delivery charges, or relevant service charges. The value must be a float data type, no thousand separator is allowed, and the decimal place must be a standard dot (.) character. |
Order Reference | (Required) The unique booking or order ID. |
Merchant (Advertiser ID) (override) | The advertiser program ID. |
Commission Group Code | (Recommended) The Commission Group Code should receive the desired Commission Group code for the transaction’s attribution. These codes are defined and configured within the Awin UI. For guidance on this parameter, please see our article on Commission Groups. |
Commission Group Amount | The commission amounts that you want to assign to each commission group. This parameter can be a string for a single group or an array for multiple groups. Array values must appear in the same order as the commission group array. If not mapped, the default value is the mapped total amount. |
Channel | The channel name of the last click referrer. Always use aw for Awin, which is the default value. For guidance on this parameter, please see our article on the Channel Parameter. |
AWC parameter | The AWC value is a parameter that is appended to the landing page URL by Awin to identify the source of a click. You must configure your site to record the AWC’s value when a customer lands on your site. For more information on capturing the AWC value, please find the information on our server-to-server guide. |
Voucher Code | A URL-encoded voucher code for the transaction. You must supply a value for either the AWC parameter or the Voucher Code. |
Currency Code | The ISO currency code of the currency that was used in the transaction, for example GBP or USD. Note: This parameter is highly recommended to maintain accurate tracking. |
Custom Parameters | The input data for single or multiple custom tracking parameters. For more information, please see Custom Parameters. |
Test Mode | Should be populated with “0” at all times unless otherwise instructed, especially in a Live program. When set to “1”, conversions will not be processed. |
Product Level Conversion Parameters
For full guidance, please find the information on the Product Level Tracking guide.
Parameter | Description |
|---|---|
Product Name | (Required) An array of product names in the transaction. |
Product ID | (Required) An array of unique product IDs in the transaction. |
Product Quantity | (Required) An array of the quantity of each of the products in the transaction. |
Product SKU | (Required) An array of the SKU of each of the products in the transaction. |
Product Item Price | (Required) An array of the prices for a single quantity of each of the products in the transaction. This single unit price must reflect the price after any relevant discount is applied, but prior to any taxes or additional charges are applied. The value must be a float, no thousand separator is allowed, and the decimal place must to be a standard dot character. |
Product Category | (Required) An array of each product’s category in the transaction. |
Testing your Tracking
Please see our article on testing your Integration for further instruction.
Consent
As an Advertiser, it is your responsibility to obtain cookie consent for Awin’s tracking and inform us of the consent status. We strongly recommend making use of Awin Consent Signals. Further information regarding consent can be found on Consent Framework.
Was this article helpful?