Awin in Hi Energy AI: sync coverage and limitations

## What Hi Energy AI syncs from Awin

Hi Energy AI connects publisher credentials for Awin and normalizes what the network can return into the shared advertiser, transaction, deal, and (where supported) click models.

Supported in Hi Energy today

• Advertisers / programs
• Transactions (transaction + validation + amendment date types)
• Clicks
• Promotions / deals
• Commission terms
• Deeplinks

• Relationship-status advertiser feeds (applied / rejected / stopped)

  How sync behaves

  Default orchestration lookback is about 26 weeks. Each window is requested three times (transaction, validation, amendment) and merged by transaction id so late declines inside the lookback are not missed.

  Across every network, negative commission amounts map to corrected status after normalization, even when the raw network token differs.

  Limitations and gotchas

  • API date windows max out at 31 days; Hi Energy walks them in 7-day chunks
• Status changes older than the lookback window are not re-fetched
• Transaction rows are skipped when the advertiser is not already in Hi Energy

• Keep lookback large enough for your validation lag

  Contacts are not pulled from Awin’s affiliate API—people data comes from Hi Energy’s contact graph / CRM paths, not the network ledger.

  Practical guidance

  Connect Awin on the publisher, run credential validation, then refresh advertisers before you expect transactions or deals to resolve cleanly. Many adapters skip rows when the local advertiser is missing.

  If you are comparing networks for coverage, start from this page’s checklist and the companion guides for Impact, Awin, and Rakuten when you need terms + deeplinks + deep transaction tooling in one place.