AWIN

Send conversion and sale data to AWIN for affiliate tracking, commission attribution, and publisher performance reporting.

Prerequisites

Complete these steps in the AWIN dashboard before configuring Signal.

Create an AWIN advertiser account

Sign up as an advertiser at awin.com or log in to your existing AWIN account. You must have an active advertiser account to use the server-to-server integration.

Find your Advertiser ID

Navigate to Account > Overview in the AWIN dashboard. Your Advertiser ID is displayed prominently on the account overview page and also appears in the URL.

Generate an API key

Go to Account > API Credentials (or contact your AWIN account manager to enable API access). Generate or copy your API Key. This key authenticates server-to-server conversion tracking calls.

Configure your conversion feed

Navigate to Tracking > Conversion Tag and set up your conversion parameters. Note the Feed ID associated with your product or conversion feed. This links tracked conversions to the correct publisher commissions.

Configure commission groups

Ensure your commission groups are set up in Finance > Commission Groups so that server-tracked conversions are correctly attributed and paid out to publishers.

Configuration

Field	Type	Required	Description
`advertiser_id`	string	Yes	Your AWIN advertiser ID from Account Overview.
`api_key`	secret	Yes	Your AWIN API key for authenticating server-to-server calls.
`feed_id`	string	Yes	The feed ID associated with your product or conversion feed.

Signal Setup

Quick Setup

Navigate to Integrations in the sidebar.
Open the Integration Library tab.
Find AWIN or filter by Attribution.
Click Install, select a variant if available, and fill in the required fields.
Click Install Integration to create the integration with a ready-to-use default blueprint.

API Setup

curl -X POST http://localhost:8084/v1/admin/integration-catalog/awin/install \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "AWIN",
    "variant": "default",
    "config": {
      "advertiser_id": "12345",
      "api_key": "your_api_key",
      "feed_id": "67890"
    },
    "delivery_mode": "server_side"
  }'

Event Mapping

Signal events are mapped to AWIN server-to-server conversions via your blueprint. Common mappings include:

Signal Event	AWIN Mapping	Notes
`purchase`	Conversion with order value	Requires `orderRef`, `amount`, `currency`, and `commissionGroup`
`lead`	Lead conversion	Map to appropriate commission group for lead-based payouts
`sign_up`	Registration conversion	Useful for pay-per-registration affiliate programmes

AWIN requires the click reference (awc parameter) to attribute conversions to the correct publisher. Ensure your site captures and forwards the awc click cookie through Signal events.

Testing

Generate a test click through an AWIN tracking link to create a valid awc reference.
Complete a test conversion on your site that triggers a Signal event.
Send a test event through Signal using the Test Event button on the integration detail page.
In the AWIN dashboard, navigate to Reports > Transactions and look for your test conversion (it may take a few minutes to appear).
Check Live Logs in Signal to confirm delivery returned 200 OK.

Troubleshooting

Symptom	Cause	Resolution
`401 Unauthorized`	Invalid API key	Verify `api_key` in AWIN API Credentials and update Signal.
`400 Bad Request`	Missing required conversion fields	Ensure `orderRef`, `amount`, and `commissionGroup` are mapped in the blueprint.
Conversions not appearing	Missing `awc` click reference	The AWIN click ID must be captured from the landing page URL and included in the event.
Commission not attributed	Wrong commission group	Verify commission group codes in AWIN match the values in your blueprint.
Duplicate conversions	Same `orderRef` sent twice	AWIN deduplicates by order reference; ensure each order has a unique ref.

Visit AWIN documentation for full API reference and credential setup instructions.

AppsFlyer iOS Button