What Is AWIN?

AWIN is a global affiliate marketing network that connects advertisers with publishers to drive online sales and revenue growth. It provides a platform for businesses to create and manage affiliate partnerships, allowing publishers to earn commissions by promoting advertiser products and services. The network offers tracking, reporting, and payment solutions to ensure transparency and efficiency in affiliate campaigns. With a presence in multiple markets worldwide, AWIN serves industries such as retail, finance, travel, and technology.

Product Type: Advertising
Integration Type: Starter Kit & ID Sync
Event Source Type: Web
Event Scope: Conversion Events Only

Capabilities

Sends conversion events directly to AWIN's Conversion API.
Supports order_completed as the primary conversion event, with the option to map additional events as conversions.
Captures and forwards the AWIN Click ID (awc) and Google Click ID (gclid) for attribution.
Sends orderReference, amount, and currency to AWIN's Conversion API for processing.
Assigns transactions to AWIN commission groups for attribution.
Transmits product details including product_id, sku, name, category, price, and quantity as part of the transaction payload.
Passes applied coupon or discount codes under the voucher parameter.
Supports country-level geo-reporting by forwarding IP addresses.
Sends the last-click channel captured by the AWIN sync, defaulting to aw when no channel is available.

Considerations

The advertiser ID and API key must be provided by AWIN and are used to authenticate and route conversion events.
Transactions are assigned to the DEFAULT commission group unless additional commission groups are configured.
The isTest flag is set to false by default, indicating live transaction data.
The user's IP address is forwarded for country-level geo-reporting and is set within the connection YAML rather than mapped as an event parameter.

Limitations

View-through conversions that rely on AWIN's client-side pixel are not supported.
The integration does not access browser session data, which may affect multi-touch attribution.
By default, the integration supports country-level geo-reporting only. State, region, or city-level reporting requires additional custom parameter mapping that must be manually configured.

Identity Sync

Sync Available: Yes
Required for Starter Kit: Yes
Prerequisites: AWIN advertiser ID
Documentation: See Additional AWIN Sync Documentation

Sync Details

Captures the AWIN Click ID (awc) and Google Click ID (gclid) used for conversion attribution.
Captures the last-click channel, defaulting to aw when none is available.
Without this sync, conversions may not be accurately attributed in AWIN reporting.

Starter Kit Setup Guide

1. Deploy the AWIN Sync

To collect the sync values (e.g., awc, gclid), you must implement an AWIN ID sync. Refer to the following documentation to complete the setup: AWIN - ID Sync Guide.

2. Gather Credentials

Ask AWIN representatives for, or retrieve from your AWIN account, the following credentials:
- Advertiser ID: On the AWIN Dashboard, locate the Your Accounts section; the Advertiser ID is displayed beneath your account name.
- API Key: In AWIN, open your profile menu and select API Credentials. Your OAuth2 Token serves as your API Key.

3. Add an AWIN Integration

From the integration library, add an AWIN integration. Then, fill out the Connection Parameters:

Connection Parameter	Description
`ADVERTISER_ID`	A unique identifier assigned to an advertiser's account in AWIN, used for tracking and reporting.
`API_KEY`	A secure token used to authenticate and access AWIN's API services.

4. Configure Event Mapping

MetaRouter provides all of the event mappings that AWIN integrations typically require. You may add custom events, parameters, or mappings in accordance with AWIN's API documentation.

5. Deploy to Pipeline

In the Pipelines tab, add your AWIN integration.
Select the correct integration revision.
Click Add Integration to finalize deployment.

Event Mappings

Global

Global mappings will be applied to all events. If your parameter names do not match the Expected Inputs provided, you will need to overwrite the Inputs provided with your own.

Output Key	Description	Expected Input
`channel` Required	String: The channel identifier. Defaults to `aw` if not provided.	`context.providers.awin.channel`

Event Specific

Order Completed

Output Key	Description	Expected Input
`awc` Required	String: The AWIN click reference ID used to track the source of a transaction.	Expression – returns `awc`, or a `gclid`-derived reference, otherwise empty
`orderReference` Required	String: The reference ID for the order or booking (max 50 characters).	Expression – returns `properties.order_id` as a string
`amount` Required	Float: The total order value before additional charges like taxes and delivery fees.	Expression – sums price × quantity across `properties.products`
`currency` Required	String: The ISO currency code (e.g., `USD`).	`properties.currency` (uppercased, default `USD`)
`voucher`	String: The voucher or coupon code used in the transaction.	`properties.coupon` (default empty string)
`commissionGroups` Required	Array: Attribution breakdown for different commission groups.	Expression – builds a `DEFAULT` group with the summed order amount
`basket`	Array: List of purchased product objects, including `id`, `sku`, `name`, `price`, `quantity`, and `category`.	Expression – maps `properties.products` to product objects
`isTest`	Boolean: Indicates whether the transaction is test or live data.	Enrichment – `false`

Required & Recommended Identifiers

These identifiers must be mapped to AWIN in order for successful user matching to occur. Without these IDs, any events sent to AWIN may not be accurately reflected in reporting. For your convenience, required and recommended IDs are mapped as Global parameters to ensure they are added to every event.

Attribute	Example	Sync Injector Required?
`awc` Required	`93737_1063212554_e7cb8a25160fa9797fe60009323d47d6`	Yes
`gclid` Recommended	`Cj0KCQiA8qKfBhDdARIsAMPywCllG29hJ3r3F4Kq7mX5vQZQz7aK1h4G2XMpK8V4x5Jz9vO3H5G2O5QaAjpUEALw_wcB`	Yes
`ip` Recommended for geo reporting	`192.168.1.100`	No

Integration Validation

Coordinate with your AWIN representative to confirm that conversion events are being received and processed correctly on their backend.

Additional AWIN Documentation

AWIN Conversion API