> 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/data-overview.md).

# 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


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.coupler.io/sources/category/marketing/awin-advertiser/data-overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.