Setup

Dashboard → Platform → Setup. The account menu item Get apps and SDKs opens it too.

Setup holds everything the selected app needs to start reporting. It has ten sections. A list on the left picks which one you see. On a small screen the list turns into a row of chips across the top.

Each section has its own address, like /dashboard/setup?section=keys. You can bookmark it or send it to a teammate.

The top of the page

X of Y essentials at the top right shows how many of the must-do steps are done. Click it to open Getting started.

When you open Setup with no section picked, it opens on Getting started until every essential is done. After that it opens on Keys & webhook.

The marks in the list

Each row in the list has a small mark on the right:

• A green tick means that step is really working. For example, the tick on Keys & webhook only shows once RevenueCat has actually sent data.
• An amber dot means it is not reporting yet.
• Short text gives a quick status, like 3/5 done, 15%, no keys, optional, on, off, or rejected.

Essentials

Getting started

A checklist. Each tick is worked out from real data, so a step you finished shows as finished.

Each open step has a title, a Go link to where you do it, what to do, and why it matters. Finished steps are crossed out. Steps you can skip are folded under Optional.

Keys & webhook

The two values that connect your app to Fictura. Both are always here to copy.

Press Copy next to either one.

SDK & errors

The code that starts the SDK. One start call turns on events, crashes and error reports. Your key is already filled in.

Pick React Native, Python or Node, then press Copy. See How error tracking works.

Revenue

What the stores keep before you are paid. Net revenue and every ROAS on Attribution use these settings.

• Store commission. Pick 15%, small business, 30%, standard, or Custom. Custom shows a Commission rate box.
• Sales tax or VAT (optional). Leave it at 0 unless you know your rate. When RevenueCat sends its own tax for a sale, that is used instead.
• List prices include tax. Turn it on if your store prices already include tax.

Press Save. The new rates apply to sales from now on. Revenue you already have keeps the rate it came in with, so past reports do not change.

AI

Your own Anthropic key. Hawkings and the paywall, onboarding and ad copy generators run on it. Anthropic bills you for it directly. Your Fictura plan does not include it.

Nothing AI works until you add a key.

1. Make a key at console.anthropic.com/settings/keys.
2. Paste it and press Save key. It is checked with Anthropic before it is saved.

Once saved, the section says AI features are on, with the start and end of your key. From there you can:

• Replace it with a new key.
• Remove it. This turns off Hawkings and every generator. Fictura never cancels anything at Anthropic.

If Anthropic later turns the key down, the section says Anthropic rejected this key and the list shows rejected. Most often the key was revoked, changed, or the account ran out of credit. Paste a working key to fix it.

Platform

Coding agents

Keys that let Claude Code, Cursor, VS Code or Claude Desktop read this app's live setup while they write your code. They can only read. They can never change anything.

1. Give the key a name if you want, then press Create key.
2. Copy the key right away. It is shown once and cannot be shown again. A lost key is replaced, not recovered.
3. Pick your tool: Claude Code, Cursor, VS Code or Claude Desktop. Press Copy snippet. The snippet has your new key in it.

Each key in the list shows when it was last used. Revoke stops it at once and cannot be undone. See MCP server for everything an agent can read.

App backend

Optional. Connect your own Supabase organization so the apps you build get their own database and sign-in, in projects you own.

Fill in your organization slug or ID, a Supabase access token (make one at supabase.com/dashboard/account/tokens), and a region. Press Connect Supabase.

Disconnect does not touch app backends that already exist. They stay in your organization and keep running. See Supabase.

Web checkout

Send iPhone users to your own Stripe checkout instead of Apple's payment sheet. If Web checkout is missing from the list, it is not available for your app yet.

• On / Off at the top turns it on or off. It stays off until Stripe is connected and you have picked a plan or added a link.
• Checkout page. Fictura hosts it, or I have my own.
• What are you selling? Your Stripe plan, when Fictura hosts the page. Connect Stripe in Connections first.
• Free trial (days). Leave blank for none.
• Purchase link. Your own checkout page, when you have your own.
• Countries. Two-letter codes, with commas between them. A device whose country cannot be read gets Apple's sheet.
• Return deep link. Where buyers go back to in your app when they are done.

Press Save. Devices pick up the change on their next config refresh.

Below the form you see whether purchases report back to Fictura, the Checkout URL to test, and Fee avoided so far, counted from real payments. See How web checkout works.

Services

Connections

Alerts and read-only data. Each one is checked with the provider before it is saved. Keys are stored encrypted and never shown again.

Under Data sources · read-only are the sources that pull numbers in from outside:

Ad platforms are not here. They connect on Paid Ads.

The list mark shows how many of these cards are connected.

Import data

Your webhook only reports what happens from now on. Import data brings in everything from before. It only shows when there is a source to import from.

If a source is already imported, the main button only pulls what is new since the last run. Importing everything again is a separate button that asks you to confirm. See Migrate in and Leave AppsFlyer.