Create an app
An app is the unit everything else is scoped to: keys, events, paywalls, connections, and team access.
Dashboard → app switcher → Add new app. Paste the app's store link and press Add.
- One link, either store. An App Store link or a Google Play link, whichever you have to hand; the page works out which store it is. The listing supplies the name, icon and category, and the bundle id / package name and store page are saved with the app, so creator links, Universal Links and artwork work from the first minute. A bare bundle id or package name works too.
- Not in a store yet? Choose Add it manually: a name is all it needs, and a logo is optional.
- The commission and tax live on Setup, the other store in Settings. New apps are saved at the 30% headline rate; if the account is on Apple's Small Business Program or Google's equivalent (15%, under $1M a year), switch it on Dashboard → Setup → Revenue. The other store's link goes in Settings → App identity. Every ROAS figure on the dashboard is net of it, so it's worth setting honestly. Apps created through the API without a commission default to the 30% rate too.
Adding the app takes you straight to Setup and its six steps. The app has two credentials, and both stay retrievable on Dashboard → Setup → Keys & webhook — they are not shown-once secrets:
- SDK app key (
gk_…) — passed toGrowth.initand sent asx-api-keyon every SDK and ingest call. - RevenueCat webhook URL — paste it into RevenueCat (Project → Integrations → Webhooks → + New) and store billing events start flowing; that feed is the billing spine for entitlements, cohorts, and revenue. See RevenueCat webhooks.
Step 1 of Setup is a ready-made prompt for Claude Code, Cursor or any coding agent: it carries the API base and the app key, and asks the agent to install @fictura/sdk and call Growth.init exactly as the SDK quickstart does.
A new app's free trial starts when you connect a coding agent in step 2, with no card, and lasts 30 days. Until it starts, Setup and Tools work in full and every other tab shows the activate screen. Once a trial ends, the same screen comes back until you activate. Your app can already send data, and nothing it reports while unpaid is lost.
Team access is by membership: teammates see an app when their email is on it, and the dashboard's current app follows you as a cookie. There is no separate staging concept — billing events carry an environment (PRODUCTION or SANDBOX), and a user's entitlement verdict follows their most recent granting event's environment, so always check environment before trusting a verdict in production.
SDK Quickstart
Install one package and call Growth.init. Events, error tracking, entitlements and experiment assignment all start on that one call — paywalls are one of the things you can do next.
Deep links in your app
Save your app's identity, create a tracking link, and let a tap on it open your app and credit the install.