Awin
Awin
About Awin Connector
The Awin connector allows you to ingest affiliate-network performance data from Awin into your data warehouse via Daton. You can extract advertiser-level, publisher-level, transaction and commission data and unify it with other marketing or sales data to build richer analytics pipelines.
This connector supports pulling raw transaction records, publisher metadata, and aggregated advertiser performance metrics. Use it to streamline your affiliate channel reporting in BigQuery, Snowflake, Redshift or any supported destination.
Prerequisites & Authentication
Before configuring the connector, ensure you have:
- A valid Awin account with Accelerate and Advanced plan.
- Your Advertiser ID from Awin.
- Your API Key from Awin.
How to obtain the Advertiser ID & API Key
Step 1 – Locate the Advertiser ID
- Log in to your Awin Advertiser (or Agency) account.
- Navigate to Advertisers → Advertiser List (or similar menu).
- Find your advertiser; note the numeric ID shown (or visible in the URL when clicking into that advertiser).
- Record this value for use in the connector’s Advertiser ID field.
Step 2 – Create or retrieve your API Key
Before you create your token, ensure you have Admin access to the Awin account you want to retrieve data from
- Click the “API Credentials” link from your User Menu in the top-right corner of your Awin dashboard.
- On the credentials page, enter the password you use to log in to Awin.
- Click “Show my API token.”
- Copy the API Token and paste in connector's API Key.
Integration Setup
Follow these steps to configure the connector in Daton:
- In Daton, navigate to Add Integration → Awin.
- Begin Setup – Enter Source Configuration Details
- Integration Name: provide a descriptive name.
- Description (optional): e.g., “Awin – UK advertiser affiliate data”.
- Replication Frequency: select how often to pull data (1h, 2h, 6h, 24h, etc.).
- Replication Start Date: choose when to begin historical extraction.
- Lookback Window: pick the number of days to look back for late-arriving data.
- Advanced Configuration Options: set Loading Mode (Append/Upsert), Nested Object behavior (inherit, no unnest, one level, two levels).
-
Authenticate the Source
- Advertiser ID: enter the numeric Advertiser ID from Awin.
- API Key: paste the alphanumeric API Key.
- Click Authenticate (Daton will validate credentials).
-
Select Tables for Replication
- Choose which tables you wish to replicate (transactions, publishers, advertiser performance, etc.).
-
Configure Schema / Columns
- Optionally select which columns you wish to load into the destination or
- Choose “Select All” option to select all columns across all tables.
- Click Submit and Connect your warehouse: Daton will begin the initial historical load, and then schedule incremental loads at the selected frequency.
Supported Tables / APIs & Schema Information
Below is an overview of the tables/APIs supported by this connector, along with field definitions.
Tables/APIs
Table Name |
Purpose |
Replication Strategy |
|---|---|---|
transactions |
Detailed transaction-level affiliate data (sales, commissions, clicks) |
Key-based incremental (transaction date) |
publishers |
Metadata on publishers (affiliates) generating traffic |
Full load / incremental |
publisher_performance_report |
Aggregated advertiser-level performance metrics (by date, region) |
Incremental |
transactions
Purpose: Provides detailed transaction records from Awin, including sale amount, commission status, click & transaction dates, etc.
Fields:
Field Name |
Data Type |
Description |
|---|---|---|
id |
STRING |
Unique transaction identifier |
advertiserId |
STRING |
Advertiser ID for this record |
publisherId |
STRING |
Publisher (affiliate) ID |
siteName |
STRING |
Name of publisher site |
commissionStatus |
STRING |
Status of commission (Confirmed, Pending, Declined) |
commissionAmount |
NUMERIC |
Commission amount paid to publisher |
saleAmount |
NUMERIC |
Sale amount that triggered commission |
ipHash |
STRING |
Hashed IP address of customer |
customerCountry |
STRING |
Country code of customer |
clickRefs |
STRING |
Click reference IDs |
clickDate |
TIMESTAMP |
Date/time when click occurred |
transactionDate |
TIMESTAMP |
Date/time when transaction occurred |
validationDate |
TIMESTAMP |
Date/time when transaction was validated |
type |
STRING |
Type of transaction |
voucherCodeUsed |
BOOLEAN |
Whether a voucher code was used |
oldSaleAmount |
NUMERIC |
Previous sale amount in case of amendment |
oldCommissionAmount |
NUMERIC |
Previous commission amount in case of amendment |
clickDevice |
STRING |
Device used for the click |
transactionDevice |
STRING |
Device used for the transaction |
customerAcquisition |
STRING |
Flag to indicate new/acquired customer |
publisherUrl |
STRING |
URL of the publisher’s site |
advertiserCountry |
STRING |
Country code of the advertiser |
orderRef |
STRING |
Order reference |
customParameters |
RECORD |
Custom parameter key/values passed in transaction |
transactionParts |
RECORD |
Breakdown if transaction has multiple parts |
paidToPublisher |
STRING |
Date when the publisher was paid |
paymentId |
STRING |
Payment identifier |
transactionQueryId |
STRING |
Internal query ID for transaction |
networkFee |
NUMERIC |
Network fee applied |
voucherCode |
STRING |
Voucher code applied |
publishers
Purpose: Contains metadata about affiliate publishers in your Awin account.
Fields:
Field Name |
Data Type |
Description |
|---|---|---|
id |
STRING |
Publisher ID |
name |
STRING |
Publisher name |
primaryRegion |
STRING |
Primary region of publisher |
salesRegions |
STRING |
Regions that the publisher sells into |
primaryType |
STRING |
Type of publisher (Content, Influencer) |
publisher_performance_report
Purpose: Aggregated performance metrics for an advertiser (clicks, impressions, confirmed/declined commission) by date/region.
Fields:
Field Name |
Data Type |
Description |
|---|---|---|
advertiserId |
STRING |
Advertiser ID |
advertiserName |
STRING |
Name of advertiser |
region |
STRING |
Region code |
currency |
STRING |
Currency of transactions |
impressions |
NUMERIC |
Number of impressions (if available) |
clicks |
NUMERIC |
Number of clicks |
pendingNo |
NUMERIC |
Number of pending commissions |
pendingValue |
NUMERIC |
Value of pending transactions |
pendingComm |
NUMERIC |
Value of pending commission |
confirmedNo |
NUMERIC |
Number of confirmed transactions |
confirmedValue |
NUMERIC |
Value of confirmed transactions |
confirmedComm |
NUMERIC |
Commission value confirmed |
bonusNo |
NUMERIC |
Number of bonus transactions |
bonusValue |
NUMERIC |
Value of bonus transactions |
bonusComm |
NUMERIC |
Commission value for bonus |
totalNo |
NUMERIC |
Total number of transactions |
totalValue |
NUMERIC |
Total value of transactions |
totalComm |
NUMERIC |
Total commission value |
declinedNo |
NUMERIC |
Number of declined transactions |
declinedValue |
NUMERIC |
Value of declined transactions |
declinedComm |
NUMERIC |
Commission value declined |
report_date |
DATE |
Date for the report row |
tags |
STRING |
Any tags or metadata |
Additional Notes & Tips
Lookback Window ensures any delayed/late-arriving transactions (e.g., validated days after click) are captured. Choose a window (7/15/30 days) appropriate to your business.
Be mindful of replication frequency vs warehouse cost: more frequent loads (e.g., hourly) may incur higher usage/cost. Choose based on how fresh you need the data.