Rakuten Advertising in Hi Energy AI: sync coverage and limitations

## What Hi Energy AI syncs from Rakuten

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

Supported in Hi Energy today

• Partnerships / advertisers
• Transactions via Events API
• Reporting clicks (separate setup from main Rakuten creds)
• Deals
• Commission terms

• Deeplinks

  How sync behaves

  Rakuten is a flagship integration: OAuth scopes, Events API transactions, terms import, and deeplinks. Configure reporting clicks separately when you need click analytics.

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

  Limitations and gotchas

  • Skips rows where is_event=Y
• Corrections often arrive as negative commission rather than a separate status token
• Rows are skipped when the local CID/advertiser is missing

• Clicks require rakuten reporting clicks setup in addition to core OAuth

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

  Practical guidance

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