> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/marketing/awin-advertiser.md).

# AWIN Advertiser

Connect AWIN Advertiser to pull campaign performance, transactions, and commission data into Google Sheets or BigQuery via Coupler.io.

AWIN is an affiliate marketing platform that connects advertisers with publishers to drive sales and conversions. As an advertiser on AWIN, you generate data around campaign performance, transactions, and commissions that's essential for understanding your affiliate program's ROI.

Connecting AWIN Advertiser to Coupler.io lets you pull that data into your preferred destination automatically — no manual exports needed.

## Why connect AWIN Advertiser to Coupler.io?

* **Centralize affiliate data** alongside other marketing channels in one dashboard
* **Track transactions and commissions** without logging into AWIN every time
* **Combine AWIN data with other sources** using Join or Append transformations — for example, merging campaign performance with spend data from your ad platforms
* **Send data to AI tools** like ChatGPT, Claude, or Gemini to surface insights from your affiliate program

## Prerequisites

* An active AWIN advertiser account
* Your AWIN API key (found in your AWIN account under **API credentials**)
* Your AWIN Advertiser ID

## Quick start

{% hint style="success" %}
Start with the **Campaign performances** entity to get a high-level view of your affiliate program before drilling into individual transactions.
{% endhint %}

## How to connect

{% stepper %}
{% step %}
**Create a new data flow in Coupler.io.** Log in to Coupler.io, go to the Data Flows section, and click **Add data flow**. Search for and select **AWIN Advertiser** as your source.
{% endstep %}

{% step %}
**Enter your API credentials.** Paste your AWIN API key into the API key field. Then enter your AWIN Advertiser ID. You can find both in your AWIN account under the API section of your profile settings.
{% endstep %}

{% step %}
**Select an entity.** Choose either **Campaign performances** or **Transactions** depending on what data you need. You can add more entities to the same data flow later.
{% endstep %}

{% step %}
**Set your start date.** Use the date picker to specify how far back you want to pull data. For first-time connections, start with 30–90 days to validate the data before going further back.
{% endstep %}

{% step %}
**Choose a destination.** Select where you want your data to land — Google Sheets, Excel, BigQuery, Looker Studio, or an AI destination like ChatGPT, Claude, Gemini, Cursor, Perplexity, or OpenClaw.
{% endstep %}

{% step %}
**Run your data flow.** Click **Run** to execute a manual sync. Once it completes successfully, your AWIN data will appear in your chosen destination.
{% endstep %}
{% endstepper %}

## AWIN Advertiser data overview

AWIN Advertiser exposes two core entities through Coupler.io: campaign-level performance summaries and individual transaction records. Together, these give you a complete picture of your affiliate program — from top-line channel metrics down to individual order details.

## Entities

| Entity                | What it contains                                                                                          |
| --------------------- | --------------------------------------------------------------------------------------------------------- |
| Campaign performances | Aggregated clicks, sales, commissions, and revenue grouped by campaign and time period                    |
| Transactions          | Individual transaction records including order value, commission earned, publisher info, and product data |

## Available data

#### Campaign performance metrics

| Field                    | Description                                             |
| ------------------------ | ------------------------------------------------------- |
| Clicks                   | Number of clicks tracked through AWIN for the campaign  |
| Impressions              | Ad impressions recorded for the campaign                |
| Sales                    | Number of confirmed sales attributed to the campaign    |
| Revenue                  | Total order value generated through the campaign        |
| Commission               | Total commission payable to publishers for the campaign |
| Commission rate          | Commission as a percentage of revenue                   |
| EPC (Earnings per click) | Revenue divided by clicks — a key efficiency metric     |

#### Campaign performance dimensions

| Field         | Description                                    |
| ------------- | ---------------------------------------------- |
| Campaign ID   | Unique identifier for the campaign             |
| Campaign name | Human-readable campaign label                  |
| Date          | The date or date range the row covers          |
| Region        | Geographic region associated with the campaign |

#### Transaction fields

| Field             | Description                                         |
| ----------------- | --------------------------------------------------- |
| Transaction ID    | Unique identifier for the transaction               |
| Order reference   | Advertiser-side order reference number              |
| Transaction date  | Date and time the transaction was recorded          |
| Order value       | Gross value of the order                            |
| Commission value  | Commission amount payable to the publisher          |
| Commission status | Current status (e.g., pending, confirmed, declined) |
| Publisher ID      | ID of the publisher that drove the transaction      |
| Publisher name    | Name of the publisher                               |
| Product name      | Name of the product purchased (if available)        |
| Voucher code      | Discount or promo code used, if any                 |
| Customer country  | Country of the customer                             |
| Click date        | Date of the click that led to the transaction       |

## Common metric combinations

* **Revenue + Commission** — calculate your effective affiliate margin across campaigns
* **Clicks + Sales** — derive conversion rate to evaluate publisher quality
* **Transaction date + Commission status** — monitor pending commissions and track confirmation timelines
* **Publisher name + Order value** — identify top-performing publishers by revenue contribution

## Use cases by role

{% tabs %}
{% tab title="Marketers" %}

* Monitor campaign-level EPC and conversion rates to identify which affiliate partnerships are delivering real value
* Compare revenue and commission trends over time to report on affiliate channel ROI
* Use Append transformation to combine AWIN data with other paid channel data (e.g., Google Ads, Meta) in a single performance dashboard
  {% endtab %}

{% tab title="Finance teams" %}

* Pull transaction-level commission data to reconcile payable amounts with AWIN statements
* Filter by commission status to track confirmed vs. pending vs. declined commissions
* Export order values and commission amounts to BigQuery or Excel for monthly accrual reporting
  {% endtab %}

{% tab title="Affiliate managers" %}

* Track publisher-level transaction volume and revenue to manage partner relationships
* Identify voucher code usage patterns across transactions
* Use the Aggregate transformation to roll up transaction data by publisher or product category for performance reviews
  {% endtab %}
  {% endtabs %}

## Platform-specific notes

* The Campaign performances entity supports a maximum lookback window of 400 days per API request — use the step increment setting to break large date ranges into smaller chunks
* Transaction statuses in AWIN can change over time (pending → confirmed or declined), so use the **lookback days** parameter to re-sync recent transactions and capture status updates
* AWIN data is scoped to your advertiser account — publisher-side data (like publisher earnings breakdowns) is not available through the advertiser API
* Commission values reflect what's payable to publishers and do not include AWIN's platform fee

## AWIN Advertiser common issues

### Connection issues

<details>

<summary>API key not accepted / authentication error</summary>

Double-check that you're using the correct API key from your AWIN account. AWIN generates separate API keys for different access levels — make sure you're using an API key that has advertiser data access enabled. Also verify that you've entered the correct Advertiser ID alongside the key, as both are required.

</details>

<details>

<summary>Data flow returns no data after a successful connection</summary>

This usually means the start date is set further back than your AWIN account has data, or the date range returns an empty result. Try setting the start date to a recent period (e.g., the last 30 days) and rerun the data flow to confirm the connection is working before expanding the date range.

</details>

### Missing data

<details>

<summary>Recent transactions are missing or incomplete</summary>

AWIN transactions often start in a "pending" state and can take several days to be confirmed or declined. If you're only syncing forward without a lookback window, you'll miss status updates on recently created records. Set the **lookback days** parameter to at least 7–14 days to ensure recent transactions are re-synced with their latest status.

</details>

<details>

<summary>Campaign performance data is missing for certain date ranges</summary>

The AWIN API has a maximum window of 400 days per request for campaign performance data. If your requested date range exceeds this, some data may not load. Use the **step increment** parameter to break the range into smaller intervals (e.g., 30 or 90 days at a time).

</details>

### Permission errors

<details>

<summary>"Unauthorized" or "403 Forbidden" error</summary>

Your API key may not have the necessary permissions to access advertiser data. Log in to AWIN and check that your API key is associated with your advertiser account and has read access to reporting data. If you manage multiple advertiser accounts, confirm you're using the API key and Advertiser ID for the correct account.

</details>

### Data discrepancies

<details>

<summary>Commission totals in Coupler.io don't match the AWIN dashboard</summary>

This is most commonly caused by commission status changes. If your destination only received a snapshot of transactions when they were "pending," and some were later declined, the totals will diverge. Enable the **lookback days** parameter so that updated transaction statuses are pulled on each sync. Also check whether your AWIN dashboard is filtering by confirmed transactions only.

</details>

<details>

<summary>Clicks or sales counts differ from AWIN's reporting UI</summary>

AWIN's UI may apply default filters (e.g., by region or publisher type) that differ from the raw API data Coupler.io pulls. Check if your AWIN dashboard has any active filters and align your data flow configuration accordingly.

</details>

### Rate limits

<details>

<summary>Sync is slow or times out for large date ranges</summary>

AWIN's API can be slow to respond when querying large date ranges, especially for the Transactions entity on high-volume accounts. Use the **step increment** parameter to limit each API request to a smaller time window (e.g., 30 days). This reduces response size and helps avoid timeouts.

</details>

## AWIN Advertiser FAQ

<details>

<summary>Where do I find my AWIN API key and Advertiser ID?</summary>

Log in to your AWIN account and navigate to **Account > API credentials** (sometimes listed under your profile or settings menu). Your Advertiser ID is typically shown in the top navigation or account summary page once you're logged in. Both are required to authenticate the connection in Coupler.io.

</details>

<details>

<summary>Can I pull data from multiple AWIN advertiser accounts into one destination?</summary>

Yes. Create one data flow source per advertiser account, each with its own API key and Advertiser ID. Then use the **Append** transformation in Coupler.io to combine the data from all accounts into a single table in your destination.

</details>

<details>

<summary>What does the step increment parameter do, and what should I set it to?</summary>

Step increment controls the size of each time window Coupler.io uses when making API requests to AWIN. For example, setting it to `P30D` means data is fetched in 30-day chunks. This is useful for large date ranges where a single request would be too large or slow. For Campaign performances, the maximum window is 400 days — for safety, stick to 30–90 day increments.

</details>

<details>

<summary>Why do my transaction commission totals keep changing between syncs?</summary>

AWIN transactions move through statuses — typically pending, then confirmed or declined. If transactions are declined after your last sync, the totals in your destination will be out of date. Set the **lookback days** parameter (14 days is a good starting point) so Coupler.io re-syncs recently updated transactions on every run.

</details>

<details>

<summary>What's the difference between Campaign performances and Transactions?</summary>

Campaign performances gives you aggregated metrics (clicks, sales, commissions, revenue) rolled up at the campaign level — good for reporting and trend analysis. Transactions gives you a row for every individual sale, including order reference, publisher, voucher code, and commission status — better for reconciliation and publisher-level analysis. For most use cases, you'll want both.

</details>

<details>

<summary>Can I send AWIN data to AI tools for analysis?</summary>

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Cursor, Perplexity, and OpenClaw. You can route your AWIN campaign or transaction data directly to these tools to generate summaries, identify anomalies, or draft affiliate performance reports.

</details>

<details>

<summary>How far back can I pull historical data?</summary>

This depends on your AWIN account history. Coupler.io doesn't impose a hard limit, but the AWIN API limits Campaign performances requests to a maximum 400-day window per call. Use the step increment parameter to handle longer historical ranges. Set your start date using the date picker in the data flow configuration.

</details>

{% hint style="info" %}
For details on what fields are available in each entity, see the [Data Overview](#awin-advertiser-data-overview) article. For help with syncing errors or missing data, check [Common Issues](#awin-advertiser-common-issues).
{% endhint %}


---

# 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.coupler.io/sources/category/marketing/awin-advertiser.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.
