In this article you will learn which steps the Brand Configurator takes you through, what you need to have ready before you start, and what happens once you submit.
Contents
- Before you start
- Steps 1 to 4: branding
- Steps 5 and 6: store accounts and access
- Step 7: API Keys
- Steps 8 to 11: configuration and submission
- After you submit
Fast lane
- Create two developer accounts: one for the Apple Developer Program, one for the Google Play Console.
- Invite us as an administrator into both accounts: whitelabel@mysports.com for Apple, android@mysports.com for Google.
- Have six values ready for step 7: Apple Team ID, API Key Issuer ID, API Key ID, the key file for API Key, your Google Developer ID and the service account key for Google Service Account Private Key.
- You do not need an app in your store accounts. We create it after you submit.
- Work through the configurator in order. You cannot skip a step, and step 7 is checked against Apple and Google while you are in it.
Before you start
Permission: Brand management, in the roles screen under the tab Member App & Web in the group Brand Configurator
Where to find the configurator: MySports / Branded Member Platform / Brand configurator. The same page lists every brand configuration you have started with its current status.
You need two things that are not part of the configurator itself, and both take time to obtain. Start them first, because the configurator cannot be completed without them.
- An Apple Developer Program account for your company. Enrolment requires a D-U-N-S number and is verified by Apple, which can take several days.
- A Google Play Console account for your company, with a one-time registration fee.
Once both accounts exist, you invite us into them as an administrator. That access is what lets us build and publish your app in your name later on.
The configurator has eleven steps and shows your position as Step 7 of 11 at the top. You move forward one step at a time and each step is validated before you can continue, so it is worth having everything ready rather than starting and stopping.
Steps 1 to 4: branding
These four steps cover how your app looks and which languages its store entry uses. Nothing here depends on Apple or Google, so you can fill them in straight away.
- Name & Logo
- App login screen
- Slogan & Colors
- Language settings of the app store entry
Steps 5 and 6: store accounts and access
Step 5, App store information, is where you enter the texts and details that will appear on your store entry.
Step 6, App store setup, is where you confirm that you have invited us into both store accounts. You tick one checkbox per store, and each one names the address to invite:
- Apple App Store: whitelabel@mysports.com, with the Admin role
- Google Play Store: android@mysports.com, with the administrator role
Send both invitations before you reach this step. You confirm them here, but the access has to exist for the later steps to work.
Step 7: API Keys
This is the step most configurations stall on, so it is worth understanding what it wants. Step 7 collects six values, four for Apple and two for Google:
| Field | Store | What you enter |
|---|---|---|
| Apple Team ID | Apple | A ten-character string from your Apple Developer account under Membership details. It is not in App Store Connect, so do not look for it next to your keys. |
| API Key Issuer ID | Apple | Shown near the top of the Integrations page, above your key list, with a Copy link. A long identifier in UUID form. |
| API Key ID | Apple | Shown in the key list under Active. Hovering a row reveals Copy Key ID. A ten-character string. |
| API Key | Apple | The key file you downloaded when generating the key. Apple lets you download it only once. |
| Developer ID | The identifier of your Google Play developer account | |
| Google Service Account Private Key | The service account key as a .json file |
Two things about this step regularly cause confusion.
You do not select an app here, and you do not need one. The keys are created at account level, not per app, and the configurator never asks for an app. Your app is created after you submit your configuration.
The keys are checked immediately. When you continue, we contact Apple and Google to confirm the credentials work. If anything is wrong you see Api Key validation failed and cannot move on. The message is the same for every cause, so check each of the six values rather than assuming something is missing on our side.
Apple only lets the account owner create an API key, and the same key can be reused if you set up further branded apps. Store it securely and pass it to us only through the configurator, because it grants administrator access to your store account.
Apple lets you download the key file only once and keeps no copy. If you lose it, the key cannot be recovered: revoke it and generate a new one, which gives you a new API Key ID to enter here. The name and the access level of a key also cannot be changed after it has been generated.
Steps 8 to 11: configuration and submission
- Branded Website configuration: the details for your branded website.
- Test user: a facility code and a test account, so Apple and Google reviewers can log in and see your app working. Without it, store review will reject the app.
- Legal information: your imprint, privacy policy, terms and support page. These links are checked automatically, and both stores reject placeholder or unreachable pages.
- Confirmation: a summary of everything you entered. Submitting here starts the work on our side.
After you submit
Submitting ends your part of the configuration and starts ours. We validate your data, send you DNS records to add, publish your branded website once those records resolve, and then build your app and send you test links before it goes to the stores.
Until you submit, no app exists in your Apple or Google account. That is expected, and it is why there is nothing to select at step 7.