Core concepts
Workspace, project, and app
Section titled “Workspace, project, and app”A workspace is your organization. Its members use the Admin dashboard; they are separate from the customers who use your apps.
A project groups apps with shared entitlements. For example, a mobile app and its desktop companion can belong to the same project. An app represents one product integration, with its own keys, customers, catalog products, paywalls, and events.
Choose the project and app before editing configuration. Reports may support one app, a project, or multiple apps; check the current selection before comparing results.
Test and Live
Section titled “Test and Live”Test and Live are separate project environments. Their app records, keys, customers, and configuration are distinct. Public Test keys begin with pk_test_; public Live keys begin with pk_ without the Test marker.
Apple Sandbox is a provider environment, while One Test/Live identifies your selected One project. A TestFlight or App Review purchase does not by itself prove a production purchase or switch your One environment.
Customers and accounts
Section titled “Customers and accounts”An anonymous installation can have a customer record before anyone signs in. Authentication upgrades or links identity through the SDK. Do not create your own customer identity from an email address or copy customer IDs between apps.
Cross-app linking is explicit or established through verified shared authentication. It does not require creating a customer in every app in a workspace.
Products, prices, and entitlements
Section titled “Products, prices, and entitlements”A product is something your app sells. A price connects it to a provider and purchasing terms. An entitlement names the benefit, such as premium access. A grant records access to that benefit for its eligible owner.
Products belong to apps; entitlements belong to projects. Multiple products can unlock the same entitlement. Use the SDK’s effective access state to gate a feature rather than checking whether any historical purchase exists.
Paywalls, surfaces, placements, and campaigns
Section titled “Paywalls, surfaces, placements, and campaigns”A paywall presents an offer. An in-app surface presents other content, such as a message. A placement names an app moment. A campaign decides what to show at a placement based on its audience, schedule, and variants.
Apps can also present a known paywall or surface directly. Direct presentation and campaign targeting are different workflows; use the one your feature needs.
Events and usage
Section titled “Events and usage”Events record actions and outcomes. Usage records measurements such as counts, bytes, duration, or credits. Define a measurement’s meaning before sending it; changing its label is different from changing what is measured.