Getting started
This guide takes you from workspace access to a verified Test integration. You need access to a One workspace, your app’s source code, and the SDK distribution supplied for your workspace. Provider credentials are needed only for the services you use.
1. Choose your app and environment
Section titled “1. Choose your app and environment”Open One Admin and select your project and app. A project groups apps that share entitlements; each app has its own customers and configuration. Switch to Test before experimenting. Test and Live have separate app records and keys.
If the workspace has no project or app yet, have its owner create the project and app first. Record the bundle identifier for iOS or the browser origin for web. Do not reuse a key from another app.
2. Connect the SDK
Section titled “2. Connect the SDK”Open Configure → Developer Access and copy the selected Test app’s public key. Client keys begin with pk_test_ in Test. A secret key belongs on a trusted server, never inside a mobile app or browser bundle.
Follow iOS setup or web and desktop setup. Create one SDK instance at startup and share it with the rest of the app. Let the SDK manage customer identity, retries, and cached entitlements.
Open the app, then use Insights → Customers to find the resulting customer in the same environment. This checks connection and identity; it does not yet verify purchases or authentication.
3. Choose one feature to test
Section titled “3. Choose one feature to test”| Your first goal | Configure | Verify |
|---|---|---|
| Customer sign-in | Auth; provider credentials in Integrations where needed | Sign in, relaunch, sign out, and recover the account |
| Paid access | Catalog products, prices, entitlements, and provider connection | Make a test purchase, restore it, and check access in the app |
| A paywall | Catalog, Paywalls, then a placement and campaign when targeting is needed | Show it at the intended app moment and complete a test purchase |
| Contact Support | Auth support requirements and your app’s Support integration | Open a thread and verify the reply in the app |
| Usage reporting | Define measurements and instrument the app | Produce a known activity and inspect that customer’s usage |
| Customer feedback | Create a Survey and connect it to a campaign placement | Preview the saved design, then test delivery and response handling in the app |
You do not need to configure every feature. Read Surveys when collecting feedback. Outbound webhooks, campaigns, and messaging are optional unless your integration depends on them.
4. Verify a complete journey
Section titled “4. Verify a complete journey”Test from the customer’s point of view. A configured product or an active server grant does not prove that a device unlocks the correct feature. For billing, check the transaction, the entitlement, and the app’s visible result. For email, check delivery and the destination link.
Use Troubleshooting if configuration and the app disagree. Keep Test and Live evidence separate.
5. Prepare Live
Section titled “5. Prepare Live”Configure the corresponding Live app explicitly. Recheck its keys, provider mappings, products, callback URLs, and access policy. Do not assume that a Test edit also changed Live.
Work through the release checklist. For an iOS submission, inspect the exact SDK version and generate bundled paywall fallbacks from the current One configuration.