Broctic

Import an app you already shipped

Bring a live App Store app into Broctic so its store figures, funnels and recommendations attach to it.

Why import rather than create

An app you have already shipped arrives with something a new app cannot have: history. Connecting App Store Connect is therefore also the import mechanism — the same credentials that fetch yesterday's sales are the ones that list which apps exist in your account.

Importing links a Broctic app to an App Store record. Until that link exists, an app in your portfolio is a name; after it, it has proceeds, first-time downloads, trials, paid subscriptions and refunds behind it, and everything that reads those — store-side conversion rates, funnel verdicts, recommendations — starts working.

Step by step

  1. 1. Connect App Store Connect first

    Nothing can be imported before Broctic can see your account. Follow connect App Store Connect — Issuer ID, Key ID, .p8 and Vendor Number, once for the whole organization.

    As soon as the key verifies, Broctic asks Apple which apps it can see and lists them, with each app's name, bundle id and Apple ID.

  2. 2. Apps → Add an app → “Improve one you shipped”

    In the console, open Apps and choose Add an app. Pick Improve one you shipped, then select the app from the list Apple returned.

    The three doors — build, improve, market a website — all create the same kind of object. They differ only in how much is already known, which is recorded on the app as its source: an imported app carries source: imported.

  3. 3. Check the link

    Under Settings → Integrations → App Store Connect every app Apple exposes is listed with the Broctic app it is linked to, if any. An app can be linked, re-linked, or left unlinked — an unlinked Apple app is still ingested, so nothing is lost by deciding later.

  4. 4. Wait for the backfill

    The newest 21 days arrive first, so the current week is on the page immediately. History then fills in over the following hours, up to Apple's one-year limit — that is Apple's horizon, not ours.

What gets attached, and what does not

  • Daily proceeds and customer spend, per currency, from Apple's Sales and Trends reports.
  • First-time downloads, re-downloads and updates, separated — never one 'units' number.
  • In-app purchase and subscription transactions, including free trials and introductory offers, by product.
  • Refunds.
  • Country, device and product breakdowns for all of the above.
  • Not attached: impressions, product page views, retention and crashes. Those come from Apple's App Store Analytics reports, which are produced asynchronously on a different API and are not ingested yet.
  • Not attached: what people did inside the app. Nothing at the store can see that — add product events for it.

An in-app purchase row does not name its app

Apple identifies an IAP row by the purchase product's own id, with the app named by SKU in a separate column. Broctic learns SKU-to-app from your app list and from every parsed row, and an unresolvable purchase keeps its own identifier rather than being dropped — an unattributed sale is a reporting problem, a discarded one is a wrong total.