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: Affiliate Marketing

Integration Type: Starter Kit & ID Sync


Capabilities

  • Captures awc from URL parameters to support AWIN affiliate conversion tracking.
  • Optionally captures gclid from URL parameters as an accepted identifier for use in the AWIN starter kit.
  • Stores each identifier in first-party storage based on the configured lifetime.
  • Refreshes stored values whenever the corresponding parameter is detected again.
  • Adds identifiers to server-side events for affiliate and paid media attribution.

Considerations

  • This sync only activates when awc or gclid parameters are present in the URL.
  • If you do not intend to use gclid as an identifier, remove the parameter from your AWIN starter kit configuration.

Sync Details

  • IDs:
    • awc – A click reference ID used by AWIN for tracking conversions across its affiliate network.
    • gclid – Google Click Identifier used to associate sessions with paid ad campaigns from Google Ads. AWIN accepts this as an optional identifier to improve user matching.
  • Description:
    • Captures awc and gclid from the URL on page load.
    • Stores the values in cookie and IndexedDB storage for the duration specified in the UI.
    • Each time the parameter appears in a URL, the stored value is refreshed and its expiration reset.
    • The values are included in server-side event payloads to support tracking and attribution with AWIN.
  • Server-side Event Payload: Upon completion of all vendor's sync, the server-side events will incorporate all resolved identifiers as described above. The following object will be appended to the context.providers property within the event's JSON payload.
    {
       "awin": {
         "awc": "URL parameter value from awc",
         "gclid": "URL parameter value from gclid"
       }
    }
    
  • Cookie Name:
    • Cookie: _meta_awin_awc, _meta_awin_gclid
    • IndexedDB: [your storage prefix]_awin_awc, [your storage prefix]_awin_gclid
    • For a general guide on ID Sync validation, see here.

Sync Setup Guide

Add an AWIN Sync in MetaRouter

To gather the awc and gclid values, 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) – Duration to store the awc identifier. Example: 365
    2. GCLID Lifetime (in days) – Duration to store the gclid identifier. Example: 90
  4. Scroll down and click the Save and Build File button.
  5. Deploy your AJS file to propagate changes to your web property.

What’s Next

If applicable, proceed with setting up your AWIN Starter Kit.