Docs
Documentation
Everything needed to connect an App Store account, read the numbers honestly, and measure the funnel Apple cannot see.
Get the SDK (legacy)
For an imported or hand-written app. One file, zero dependencies, no package to add — Swift for native iOS, TypeScript for Expo, React Native, web and Node. An app built in the Studio is already instrumented by its kit and needs neither.
Use it from your coding agent
The MCP server puts your own numbers — and the whole reference an agent needs to instrument an app correctly — inside Claude Code, Cursor or any MCP client.
Where to start
If you have already shipped an app, start with connecting App Store Connect. It takes about five minutes, needs no code, and gives you a year of daily sales history. If you want to see where people drop off before they pay, add product events afterwards — the store data and the event data are joined in the same funnel.
Get started
Sign up, create an organization, add an app, connect App Store Connect, send events, and read the numbers.
Build apps
Describe an app, watch it run on a phone in your browser, then build a signed iOS and Android release from the same screen.
Connect Claude Code, Codex, Cursor or any MCP client to Broctic: build and ship apps, read your numbers, and give the agent the reference it needs.
App Store data
Generate a Team API key with Sales and Finance access, find your Issuer ID, Key ID and Vendor Number, and connect them to Broctic.
Connect the In-App Purchase key, point Apple's server notifications at Broctic, and ask whether a person is entitled — with no third party in between.
Bring a live App Store app into Broctic so its store figures, funnels and recommendations attach to it.
What every figure on Home and Analytics means: proceeds versus customer spend, first-time downloads versus updates, trials versus paid, currency conversion and freshness.
Measure
A Studio app is instrumented by its kit with nothing to install. For an imported app: the legacy drop-in client and how to send events.
How Broctic builds a funnel from events, how onboarding A/B tests are assigned and read, which templates fit which app, and where the benchmarks behind each verdict come from.
A single prompt you can paste into Claude Code, Cursor or any coding agent to instrument your app correctly the first time.
Playbook
What published data says about how iOS subscription apps convert, edge by edge — install to first open to onboarding to paywall to trial to paid to retained — and which levers have the largest documented effect.
How many screens, what to ask, where the permission prompts go, and whether sign-up belongs before or after the first moment of value.
Hard gate versus soft gate, what a converting paywall contains, what Apple's review guidelines require it to say, and the published conversion figures for each choice.
Published price medians by duration and region, the weekly-versus-annual trade-off, trial length evidence, introductory offers and price anchoring.
Trial-to-paid medians, day-0 cancellations, first-month churn on annual plans, refunds, renewal reminders and what win-back is actually worth.
The whole playbook as numbered, terse lines — each with the metric it moves and the Broctic event or report that measures it. Written to be read in one pass by a person or an agent.
Every study, report and Apple document cited in the playbook, with its publisher, year, sample and the claims that rely on it.
Reference
Legacy, for imported and hand-written apps: the Swift and TypeScript analytics clients as single files. A Studio app is instrumented by its kit and needs neither.
The OpenAPI contract, Swagger UI, and the analytics, events, experiment and purchase routes with the permission each one requires.