Skip to main content

Supported data types

Marketing cost

Affiliate commission spend and conversions

Prerequisites

  • Access to your Awin account
  • An Awin API access token
  • The Awin advertiser ID(s) you want to import data from

Step-by-step integration guide

Multiple storefronts

Awin records are stored per storefront, so each storefront needs its own Awin connection with its own API token and advertiser IDs.
  • On merchants with a single storefront, the connection is attached to that storefront automatically and the storefront picker is not shown.
  • On merchants with multiple storefronts, the connect form asks you to pick which storefront the connection belongs to. Only storefronts that don’t already have Awin connected appear in the dropdown.
  • To connect Awin to an additional storefront later, open Settings → Integrations, click Awin, then use Add in the connector dialog to run the connect flow again for another storefront. Storefronts you already connected keep their existing API token and advertiser IDs.
Reconnecting an existing Awin connection updates the credentials on that storefront’s record and does not prompt for a storefront.

How we calculate spend

Awin splits every transaction’s commission into four states as it moves through the validation process. We report a projected spend view by summing the payable states, so recent days are populated immediately instead of waiting for advertisers to validate each transaction. Declined commission is deliberately excluded because it will never be paid. As transactions move from pending to confirmed or declined, historical figures may adjust slightly to reflect the final validated amounts.
If you prefer to report only strictly validated (confirmed) spend instead of projected spend, let your Customer Success Manager know — this can be configured per merchant.

Processing

  • Date attribution: Costs are dated by the transaction (sale) date, so they align with your orders and attribution rather than the later approval date.
  • Timezone handling: Awin supports a limited set of timezones. Your merchant timezone is mapped to the nearest supported one, falling back to UTC when no match is available.

Data refresh

Initial import

On the first fetch, we import historical data going back to 2023-01-01. If you have costs before that date, let us know — we recommend at least two years of data.

Ongoing updates

Subsequent updates re-fetch the last 90 days. Awin’s validation window is typically 30 days but can extend to 60–90 days, so the wide lookback keeps projected spend accurate as transactions are validated.

Finalizing integration

Once your token and advertiser IDs are set up, our system automatically begins fetching your Awin cost data. You can then view and analyze this data on our platform to understand your affiliate marketing performance.

Troubleshooting and support

If you encounter any issues during the integration process or have questions regarding your data, please contact our support team for assistance.

Additional resources

For more information on managing your Awin account and understanding transaction validation, visit the Awin Help Center and the Validating transactions guide.