Connexity in Hi Energy AI: sync coverage and limitations

## What Hi Energy AI syncs from Connexity

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

Supported in Hi Energy today

• Advertisers
• Transactions via a configured performance report CSV

• Deeplinks

  How sync behaves

  Connexity aggregates performance by merchant and FROM_DATE from the report (often GCS). Poll attempts are capped. This is a different shape from networks that accept start/end date ranges.

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

  Limitations and gotchas

  • Not date-windowed—polls a fixed performance report id rather than a historical range API
• Wizard runs Connexity once (not per-month history)
• Date-range transaction backfill is unsupported
• No clicks or deals in the all-refresh deal/click jobs
• Status map defaults to pending; lifecycle detail is limited by the aggregate feed

• Needs both Connexity credentials and a performance report id for transactions

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

  Practical guidance

  Connect Connexity 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.