Integrations: connect your existing accounts
Connect your existing accounts so that Appwin reads your data and sends on your behalf.
No integration is mandatory: the SDK, the community and support all work without them. Each one unlocks a specific product or piece of data, listed below.
Where it is configured
Settings → Projects → your app → Integrations tab.
Integrations are set per project, not per organisation. Two apps from the same studio have two App Store listings, two Android packages, two sets of keys: mixing them would make no sense.
From any product, a "Connect" button opens the right configuration popup directly and brings you back where you were once the key is saved.
What each integration unlocks
| Integration | Product served | What it brings |
|---|---|---|
| App Store Connect | ASO, Finance | App Store listing, reviews and ratings, sales reports |
| Google Play Console | ASO | Play listing, Android reviews and ratings |
| RevenueCat | Finance | MRR, ARR, revenue, churn, active subscribers, trials |
| Adjust | Finance | Marketing spend and attributed installs |
| APNs | Notifications | Sending iOS push |
| FCM | Notifications | Sending Android and web push |
How keys are stored
Every value marked "secret" is encrypted at rest in the database, with the environment's key.
They are never sent back in clear to the dashboard: once saved, a key is shown masked and can only be replaced. Nobody, on the Appwin side or on your team's, reads a key back from the interface.
A key encrypted in one environment does not decrypt in another. If you import a staging database locally, the integrations have to be entered again - the API says so explicitly rather than failing with a 500.
If you suspect a leak, revoke the key at the provider: revocation is immediate there, independently of what is stored at Appwin.
The principle behind the keys
Appwin never uses its own keys on your behalf. Push notifications go out under your publisher identity, App Store calls are made with your role, revenue is read from your RevenueCat account.
Two direct consequences:
- You keep control. Revoking a key cuts access immediately, without going through us.
- The role you grant is the role we have. Grant the minimum needed for what you intend to use; each page says which one that is.
When a key is missing
The product concerned says so and offers to connect the account, rather than showing zeros. One deliberate exception: with no push key configured, the API simulates the send and logs it instead of failing, so the rest of the product can be developed with no keys at hand. See APNs to recognise it.