Introduction
Awin is an affiliate marketing network. The Awin connector pulls publisher performance and transaction-level data from the Awin REST API for the connected advertiser account. Two report shapes are supported: a publisher report that aggregates impressions, clicks, and commission-status totals per publisher per day, and a transaction report that exposes one row per individual transaction. As a marketing connector, metrics, breakdowns, and currencies are standardized so widgets can aggregate across sources without additional configuration. To connect this data source, see How to connect Awin to Adriel.Data refresh strategy
Architecture data
Account structure — the advertiser account and its associated publishers — is resolved at connection time by calling the Awin accounts endpoint withtype=advertiser, and is refreshed alongside reports data.
Reports data
Awin is a daily-cache connector. After initial connection, historic daily data from the last 180 days is retrieved. The latest 30 days are then refreshed every 3 hours at minute 0 (UTC). Each fetch covers a single calendar day, so a first-time backfill issues one request per day of history.Architecture levels
Advertiser account → Publisher → Campaign → Transaction Publisher reports aggregate at the publisher-per-day grain; transaction reports expose individual transactions.Metrics
How to read the columns
Data type uses this vocabulary: Number, Currency, Percentage, Ratio, Duration, Date, Text, URL, Array, Boolean.
API Key in code style like
clicks is the literal Awin API field name. Italic text describes how a value is produced when it doesn’t map cleanly to a single API field.Awin exposes two report shapes. Publisher-report metrics aggregate per publisher per day across commission statuses; transaction-report metrics describe a single transaction. The report type should match the analytical question being asked.
Clicks & traffic
Conversions & sales
Commission & cost
Breakdowns
Publisher & advertiser
Transaction attributes
Device
Geography
Time grouping
These date groupings are produced by Adriel from the underlying daily cache, not returned as Awin fields.
Limitations
- 180-day history window — after initial connection, only the last 180 days of daily data are retrieved; earlier history is not backfilled. Rolling refreshes cover the most recent 30 days.
- Generic data source — Awin data appears in generic tables and does not natively combine with other connector types unless they share identical breakdowns; blending requires separate configuration.
- Commission status is not final — pending commissions can later move to confirmed or declined, so recent totals may change as statuses are validated upstream (Awin API documentation).
- Rate limiting — when the Awin API returns HTTP 429, the connector surfaces the retry-after window so the connection check can be retried after the indicated wait.
API references
See also
- How to connect Awin to Adriel (paired how-to)
