> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/activate/event-streaming/destinations/attribution-and-affiliate/awin.md).

# AWIN

AWIN (formerly ShareASale) is an affiliate marketing network that connects advertisers with publishers. This destination loads the AWIN JavaScript SDK in the browser to enable affiliate click tracking and commission attribution. Once loaded, the SDK handles all affiliate tracking by itself. Chord does not forward individual events.

## Getting started

The AWIN SDK loads automatically, so you don't install any script yourself. You need your AWIN (ShareASale) merchant ID. Find it at the top right of your AWIN account when you are logged in.

## Settings

* **Destination Name** (required): a name to tell this destination apart.
* **AWIN Merchant ID** (required): your AWIN merchant ID.
* **Consent Requirements** (optional): the consent categories a visitor must accept before Chord sends data to this destination. See [Consent](/activate/event-streaming/consent.md).

## Connect

Add **AWIN Pixel** from the destination catalog, using the settings above. See [Connect a destination](/activate/event-streaming/connect-a-destination.md) for the full steps.

## Events

This destination does not forward individual page, track or identify events. The AWIN SDK loads on the first event of any type. From then on, the SDK handles all affiliate tracking by itself.

## Initialization

On the first event of any type, Chord loads `https://www.dwin1.com/{merchantId}.js`. It does not queue or process later events. Its only job is to make sure the AWIN script loads once per page.

Chord tracks loading state (`fresh` → `loading` → `loaded`/`failed`) to prevent duplicate script loads. If the script fails to load, it does not try again.

## 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` |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.chord.co/activate/event-streaming/destinations/attribution-and-affiliate/awin.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.