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

# 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](/sources/category/marketing/awin-advertiser/data-overview.md) article. For help with syncing errors or missing data, check [Common Issues](/sources/category/marketing/awin-advertiser/common-issues.md).
{% 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 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/faq.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.