Networks
Rakuten Advertising
Program and transaction sync via the Rakuten Advertising API using your application token-key scoped to your publisher SID, with deep links from the official deep_links endpoint.
Credentials
Enter these once in the dashboard at https://app.affiliateos.dev/onboarding?network=rakuten. They are verified against the network on submit.
| Field | Where to find it | Secret |
|---|---|---|
clientId | Rakuten Advertising Developer Portal, under Application | no |
clientSecret | Rakuten Advertising Developer Portal, under Application | yes |
sid | Your Rakuten publisher site ID | no |
What syncs
| Programs | Transactions | Payments | Product search |
|---|---|---|---|
| yes | yes | no | no |
Attribution tags travel as u1 on every link minted through this network.
Good to know
- Access tokens from the token-key exchange are cached in memory only and never stored.
- Programs come from the Partnerships API (your own roster with statuses), not the network-wide advertiser catalog.
- The Events API limits ranges to 30 days and history to about 100 days, so backfills are chunked automatically; Rakuten exposes no payments API, so payment records are unsupported.
- Deep links require the advertiser ID, so create_link needs a program match (resolve_url or program_id) on Rakuten.
- Your attribution tag travels as u1 and comes back on each event.
Raw network payloads are stored for audit in your account only and are never exposed through webhooks or pooled across users.