Connect Rakuten Advertising
Rakuten uses OAuth2 client credentials — a Client ID and Client Secret you create in the Developer Portal — together with your Account SID (your publisher Site ID), which scopes the data ChaffChing reads. Keys stay in your device Keychain; access is read-only.
- Client ID
- Client Secret
- Account SID
Use OAuth2, not the legacy token. The Client ID / Client Secret are Rakuten's current credentials. They're not the older "Web Services Token / Security Token" found in the Publisher Dashboard — that's a separate, legacy mechanism. If your portal only shows the legacy tokens, ask Rakuten support about Developer Portal / OAuth2 access.
Before you start
- You need a working Rakuten Advertising Publisher Dashboard login.
- Access tokens are scoped per SID — if you manage multiple accounts, you'll connect each one with its own SID.
Step 1 — Create an OAuth2 application
- Go to the Developer Portal at developers.rakutenadvertising.com (also reachable from the nine-dot apps menu in the Publisher Dashboard).
- Open the Applications dashboard → Add Application.
- Name it (e.g. "ChaffChing") and choose Create.
- The app then displays your Client ID and Client Secret — copy both into the matching ChaffChing fields.
Step 2 — Find your Account SID
- Sign in to the Rakuten Publisher Dashboard.
- Your SID (Site ID) is shown in the top-right corner. The dropdown arrow beside it switches between accounts if you have more than one.
- Paste it into ChaffChing's Account SID field.
The dashboard labels this value simply "SID" — it's the same thing ChaffChing calls the Account SID.
Troubleshooting
"Could not authenticate"
Re-check the Client ID and Client Secret for typos, and confirm you copied the OAuth2 credentials (Step 1) rather than a legacy Web Services / Security Token.
Connected, but no sales
Make sure the Account SID matches the account those sales belong to (multi-account users must pick the right SID), then run Re-sync history from the ⋯ menu.