Getting started
Sign up, create an organization, add an app, connect App Store Connect, send events, and read the numbers.
The shape of it
Broctic answers two questions about an iOS app that no single source can answer alone. What did it earn, and who arrived? comes from Apple, through App Store Connect. Where did people stop before they paid? comes from the app itself, through product events. The two are joined into one funnel.
You can do the first without writing a line of code, and it is the right place to start — the store data alone already gives you download-to-trial, trial-to-paid and refund rate.
Step by step
1. Sign up
Create an account at /sign-up with GitHub, Google or an email address and password.
2. Name your organization
Signing up creates an organization and makes you its owner — there are no personal accounts, because every app, key and connected Apple account belongs to a company rather than a person. Onboarding asks you to name it (the field is prefilled) and you can invite people later from People: owners, admins and members, where members can create apps but only admins and above manage people or rename the organization.
3. Add an app
There are three doors, and they land on the same object with a different origin:
- Build a new app — nothing exists yet, so the builder asks about the shape, the funnel and the theme.
- Improve one you shipped — the import path. Broctic reads the live listing and your App Store figures and proposes changes instead of asking. See importing an app.
- Market a website — no build and no store listing, the marketing half only.
4. Connect App Store Connect
This is the step that turns names in a list into measurements. You need a Team API key with Sales access, its Issuer ID and Key ID, the .p8 file, and your Vendor Number — the full walkthrough is in connect App Store Connect.
One key covers every app in the account, so this is done once for the organization, not once per app. Within a minute you have the last three weeks; within a few hours, up to a year.
5. Read the numbers
Home gives the organization at a glance; Analytics has the overview, funnel, revenue, acquisition, places and data views, with a time range and a display currency at the top that scope everything below them. Every figure is defined in the analytics reference — worth ten minutes before you draw conclusions, because Apple's "units" is four different things and only one of them is a download.
6. Add product events
Apple can tell you 4,000 people downloaded the app and 60 started a trial. It cannot tell you that 2,300 of them never finished onboarding. Product events fill that gap. An app built in the Studio already sends them. For an app you imported or wrote yourself, copy one dependency-free file into the app, create a publishable key on the app's Events page, and send the standard event names as things happen. See events, or hand the AI instructions to your coding assistant.
Two things worth knowing up front
Nothing here is live, and that is Apple's design
Apple publishes each day's sales report by 08:00 Pacific the next morning. The freshest possible figure is yesterday's. Broctic shows how current the data is next to the numbers rather than implying they are real time, and draws a day it has never successfully fetched as a gap rather than a zero.Two keys, two jobs
An organization API key (brk_) is a secret: it reads and changes your organization through the API and belongs on a server. An app's publishable key (bpk_) can only do what a shipped app needs for that one app — write its events, fetch its onboarding funnel and check its purchases — and is meant to ship inside the binary. Never put a brk_ key in an app.