---
title: AWIN Pixel
slug: awin-pixel
docTags: 
createdAt: 2025-10-17T13:39:54.566Z
---

# Introduction

The AWIN Pixel (formerly the ShareASale Pixel) is a piece of tracking code used to record conversions and attribute sales or leads generated through affiliate marketing campaigns on the AWIN network. It enables advertisers to measure which publishers or partners drove each transaction, track performance metrics like order value and commission, and optimize affiliate payouts accordingly.

# Getting started

You will need the AWIN Merchant ID in order to connect this destination. You can find this ID in your AWIN Account under the drop-down menu when you click on the tab labeled "Overview". Your Merchant ID (MID) will be shown underneath your account name.

# Connecting to the AWIN Pixel CDP destination

:::hint{type="danger"}
Before connecting destinations in the Chord CDP, please verify with all Destination owners that all **non-Chord CDP** configured destinations are *disabled.*
**
Running external destinations alongside configured Chord CDP destinations ***can result in duplicate events downstream.&#x20;***
:::

1. Log into the Chord data platform.
2. Navigate to the CDP.
3. Click the **"Add"&#x20;**&#x62;utton next to Destinations.
4. Select **AWIN Pixel&#x20;**&#x66;rom the destination catalog.
5. Enter in the destination name and the AWIN Merchant ID.&#x20;
6. Click **"Create"&#x20;**&#x74;o connect.

# Events

This destination does not forward individual page, track, or identify events. The Awin SDK is loaded on the first event received from any type, and from that point the SDK handles all affiliate tracking autonomously.

## Initialization

The plugin loads the SDK on the first event it receives, regardless of event type. It does not queue or process subsequent events — its sole purpose is to ensure the Awin script is loaded once.

The plugin manages SDK loading state (`fresh` → `loading` → `loaded`/`failed`) to prevent duplicate script loads. If the script fails to load, no further load attempts are made.

## CSP requirements

If your site uses a Content Security Policy, allow the following domains:

| Directive     | Domain                  |
| ------------- | ----------------------- |
| `script-src`  | `https://www.dwin1.com` |
| `connect-src` | `https://www.dwin1.com` |

