Publishable keys

Publishable keys

Events are sent with a per-app publishable key, prefix bpk_, created on the app's page in the console under Events. It can do only what a shipped app needs, for that one app: write its events, fetch the onboarding funnel it should show (GET /v1/experiments) and check or report its purchases (/v1/purchases/entitlement, /v1/purchases/verify).

• It is expected to be extracted from the binary. Being extracted costs nothing, which is why it can ship in an app at all.
• It cannot read your revenue, your events or anything about the organization. The only things it can read are the app's own onboarding funnel and whether one person is entitled to what they bought.
• An organization API key (brk_) must never ship in an app. It reads and changes the whole organization and belongs on a server.
• Revoking a publishable key stops everything sent with it immediately — events, funnel fetches and purchase checks; data already received is kept. A shipped app falls back to the funnel it was built with and the entitlement the device already knows, so rotate to a new key in a release before revoking the old one.