Common Issues

Connection issues

API key not accepted / authentication error

Double-check that you're using the correct API key from your AWIN account. AWIN generates separate API keys for different access levels — make sure you're using an API key that has advertiser data access enabled. Also verify that you've entered the correct Advertiser ID alongside the key, as both are required.

Data flow returns no data after a successful connection

This usually means the start date is set further back than your AWIN account has data, or the date range returns an empty result. Try setting the start date to a recent period (e.g., the last 30 days) and rerun the data flow to confirm the connection is working before expanding the date range.

Missing data

Recent transactions are missing or incomplete

AWIN transactions often start in a "pending" state and can take several days to be confirmed or declined. If you're only syncing forward without a lookback window, you'll miss status updates on recently created records. Set the lookback days parameter to at least 7–14 days to ensure recent transactions are re-synced with their latest status.

Campaign performance data is missing for certain date ranges

The AWIN API has a maximum window of 400 days per request for campaign performance data. If your requested date range exceeds this, some data may not load. Use the step increment parameter to break the range into smaller intervals (e.g., 30 or 90 days at a time).

Permission errors

"Unauthorized" or "403 Forbidden" error

Your API key may not have the necessary permissions to access advertiser data. Log in to AWIN and check that your API key is associated with your advertiser account and has read access to reporting data. If you manage multiple advertiser accounts, confirm you're using the API key and Advertiser ID for the correct account.

Data discrepancies

Commission totals in Coupler.io don't match the AWIN dashboard

This is most commonly caused by commission status changes. If your destination only received a snapshot of transactions when they were "pending," and some were later declined, the totals will diverge. Enable the lookback days parameter so that updated transaction statuses are pulled on each sync. Also check whether your AWIN dashboard is filtering by confirmed transactions only.

Clicks or sales counts differ from AWIN's reporting UI

AWIN's UI may apply default filters (e.g., by region or publisher type) that differ from the raw API data Coupler.io pulls. Check if your AWIN dashboard has any active filters and align your data flow configuration accordingly.

Rate limits

Sync is slow or times out for large date ranges

AWIN's API can be slow to respond when querying large date ranges, especially for the Transactions entity on high-volume accounts. Use the step increment parameter to limit each API request to a smaller time window (e.g., 30 days). This reduces response size and helps avoid timeouts.