Connect stores, Firebase and AdMob
Credential profiles connect SmartLinks to external services. Each app must be mapped to the right store or reporting identity.
Before you start
Use an account authorized to access the provider's app and the SmartLinks workspace. Enter credentials only in the private settings forms. Never put service-account JSON, private keys, client secrets or tokens in public documentation or screenshots.
Step by step: store connections
- Open Settings & Integrations from your profile settings.
- Find App Store Connect or Google Play. Complete the fields shown for that provider using credentials from your own provider account.
- Use Save All Changes. Resolve validation errors before leaving.
- Open your app's Edit App page. Under Credentials, choose the matching App Store Connect and Play Store Console profiles.
- Verify the Android package name, Apple app identity and store links, then Save Changes.
- Open a read-only reporting feature such as Reviews and sync one platform. Check its result before attempting a publish action.
Step by step: AdMob and Firebase reporting
- In settings, open AdMob or Firebase.
- Use the connection flow shown and choose the Google account with access to the intended reporting resources. Review its consent screen.
- If Firebase asks for OAuth configuration, complete the required configuration in the private form; Save and enable saves it.
- In app mapping, choose the correct SmartLinks app for each provider app. Suggest mappings or Suggest matches prepares suggestions; inspect each before Confirm all.
- Use the available sync control and wait for its result. Check Revenue for AdMob and the relevant analytics/crash panels for Firebase.
- Compare the mapped app IDs if data appears under the wrong app. A connected account alone does not prove the mapping is correct.
Confirm it worked
The connection and app mapping persist after reload, and the expected app's report receives data. A successful credential save is not proof of store publishing or SDK event delivery.
Troubleshooting
Expired consent, insufficient provider permissions, incorrect app IDs and report delays can all cause empty results. Reauthorize only the intended account. Do not disconnect a working shared profile without checking which other apps depend on it.