Documentation

AWIN

Suggest Edits

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.

What are the benefits of integrating MetaRouter with AWIN?

  • Enhanced Attribution Accuracy – Captures and forwards key identifiers like awc and gclid to support AWIN’s tracking and reporting.
  • Flexible Data Handling – Allows customization of event mappings and additional parameters in accordance with AWIN’s API requirements.

Capabilities and Considerations

  • AWIN Conversion API Integration – Sends conversion events directly to AWIN’s Conversion API, ensuring compliance with AWIN’s tracking requirements.
  • Flexible Conversion Tracking – Supports order_completed as the primary conversion event, with the option to map additional events as conversions based on customer needs.
  • Click ID Handling – Captures and forwards AWIN Click ID (awc) and Google Click ID (gclid) for attribution.
  • Transaction Data Transmission – Sends orderReference, amount, and currency to AWIN’s Conversion API for processing.
  • Commission Group Support – Allows transactions to be assigned to AWIN commission groups for proper attribution.
  • Product Data Mapping – Transmits product details including product_id, sku, name, category, price, and quantity as part of the transaction payload.
  • Voucher Code Inclusion – Passes applied coupon or discount codes under the voucher parameter.
  • Channel Identification – Specifies aw as the transaction source to align with AWIN tracking requirements.
  • Geo-reporting Support – Supports country-level geo-reporting by forwarding IP addresses.

Limitations

  • Post-Impression Tracking – View-through conversions that rely on AWIN’s client-side pixel are not supported.
  • Session-Based Attribution – The integration does not access browser session data, which may affect multi-touch attribution.
  • Limited Georeporting – By default, the integration supports country-level georeporting only. State, region, or city-level reporting requires additional custom parameter mapping, which must be manually configured.

Getting Started - From Your AWIN Account

Advertiser ID

  1. Log into your AWIN account.
  2. On the Dashboard, locate the Your Accounts section.
  3. Your Advertiser ID will be displayed beneath your account name.

API Key

  1. Log into your AWIN account.
  2. Click on your profile icon in the upper-right navigation bar to open the menu.
  3. Select API Credentials to navigate to the API page.
  4. Your OAuth2 Token can be accessed here—this serves as your API Key.

Getting Started - From Your MetaRouter Account

Adding an AWIN integration.

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

Connection ParameterDescription
ADVERTISER_IDA unique identifier assigned to an advertiser's account in AWIN, used for tracking and reporting.
API_KEYA secure token used to authenticate and access AWIN’s API services.

Adding an AWIN Sync

To gather the awc value and the gclid value, you must add an AWIN sync.

  1. From the Pipelines page, find the pipeline associated with the web property you’d like to add a sync to. Hover over the three dot dropdown and select “Build AJS File.”
  2. In the Identity Syncs section, select the AWIN sync.
  3. Fill out the following fields:
    1. AWIN Lifetime (in days) - Specifies the duration for which the synced identifier remains in the first-party ID graph. Once this period expires or if the sync no longer detects the identifier—whichever occurs first—a new sync will be triggered to retrieve an updated value.
    2. GCLID Lifetime (in days) - Specifies the duration for which the synced identifier remains in the first-party ID graph. Once this period expires or if the sync no longer detects the identifier—whichever occurs first—a new sync will be triggered to retrieve an updated value.
  4. Scroll down and click the Save and Build File button.
  5. Deploy your AJS file to propagate changes to your web property.

Event Mappings

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.

Event Specific

Order Completed

Output KeyDescriptionExpected Input
awc
Required		String: The Awin click reference ID used to track the source of a transaction.Expression:
return input.context.providers.awin.awc or (input.context.providers.awin.gclid and 'gclid_$$ADVERTISER_ID$$_' .. input.context.providers.awin.gclid) or ''
orderReference
Required		String: The reference ID for the order or booking (max 50 characters).Expression:
return tostring(input.properties.order_id)
amount
Required		Float: The total order value before additional charges like taxes and delivery fees.Expression:
return SUM(MAP(input.properties.products, function (p) return p.price \* (p.quantity or 1) end))
currency
Required		String: The ISO currency code (e.g., "USD").properties.currency (converted to uppercase, defaults to "USD").
voucherString: The voucher or coupon code used in the transaction.properties.coupon (defaults to an empty string if not provided).
commissionGroups
Required		Array: Attribution breakdown for different commission groups.Expression:
return {{ code = 'DEFAULT', amount = SUM(MAP(input.properties.products, function (p) return p.price \* (p.quantity or 1) end)) }}
basketArray: List of purchased product objects, including id, sku, name, price, quantity, and category.Expression:
return MAP( input.properties.products, function (p) return { id = p.product_id or '', sku = p.sku or p.product_id or '', name = p.name, price = p.price, quantity = p.quantity or 1, commissionGroupCode = 'DEFAULT', category = p.category or '' } end )
channel
Required		String: The channel identifier for Awin transactions.Enrichment - Static value "aw".
isTestBoolean: Indicates whether the transaction is a test or live data.Enrichment - Static value 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.

AttributeExampleSync Injector Required?
awc
Required		93737_1063212554_e7cb8a25160fa9797fe60009323d47d6Yes
gclid RecommendedCj0KCQiA8qKfBhDdARIsAMPywCllG29hJ3r3F4Kq7mX5vQZQz7aK1h4G2XMpK8V4x5Jz9vO3H5G2O5QaAjpUEALw_wcBYes
ip*
Recommended for geo reporting		192.168.1.100No *IP is set within the connection YAML

Additional AWIN Documentation

AWIN Conversion API

Updated about 7 hours ago