Glossary
The terms used across Voidhash, Studio and these docs, each linked to where it is explained.
These are the terms Voidhash uses in Studio, the SDKs and these docs. Each links to the page that explains it.
A–C
A/B test: An experiment that splits the people reaching a paywall location between two or more paywalls and compares their results. See Feature flags and A/B tests.
API key: A credential that identifies your project to Voidhash, either publishable or secret. See API keys.
Attributes: Properties you store on a person, such as a plan name or a survey answer. See People and identity.
Automation: A no-code flow in Studio that reacts to what people do, for example by sending a push notification. See Automations.
Billing retry: The period after a subscription renewal fails, while the store keeps trying to charge the person. See Subscription lifecycle.
Bot: An AI assistant inside Studio that answers from your project's data and acts through tools. See Bots.
Build: A compiled version of a paywall, made from its design in Studio. A build reaches your app only once you deploy it. See Build and deploy.
Churn: Paid subscriptions that end. The churn rate is the share of paid subscriptions active at the start of a period that ended during it. See Metric definitions.
CLI: The voidhash command-line tool for managing projects, paywalls, keys and data from a
terminal or script. See CLI.
Custom component: A paywall component you write in code and publish to a registry for your project or team. See Custom components.
D–F
Deploy: Making a paywall build the live one, so apps receive it. You can roll back to an earlier build. See Build and deploy.
Development mode: An SDK option that lets debug builds buy from a simulated store with the test publishable key. See Development mode.
Distinct ID: The ID Voidhash knows a person by. It is anonymous until your app calls identify
with your own user ID. See People and identity.
Entitlement: A person's current access to a perk, and the subscription or purchase that gave it. See Products and perks.
Environment: Where a purchase or event belongs: production, sandbox (store sandbox) or
test (simulated purchases and test modes). See
Environments.
Event: Anything recorded for analytics, such as a screen view or a purchase. Built-in event
names start with $. See Events.
Feature flag: A switch or variant your app reads at runtime to turn features on for some people. See Feature flags and A/B tests.
Flow: The SDKs' term for anything designed in Studio that they present: a paywall or an onboarding flow. See Paywalls in your app.
Flow result: What presentFlow returns when a flow ends: purchased, restored, finished (with
the name of its finish action), closed or failed. See Paywalls in your app.
G–O
Grace period: Time after a failed renewal during which the person keeps access while the store retries the charge. See Subscription lifecycle.
Location: Short for paywall location: a stable slug in your app, such as onboarding, where a
paywall appears. See Paywalls in your app.
MCP server: Voidhash's Model Context Protocol endpoint, which lets AI agents work with your projects. See MCP server.
MRR: Monthly recurring revenue: what your active subscriptions bring in per month. See Metric definitions.
Notice: A message to your team members, in Studio's inbox and by email, such as a fired analytics alert. See Notices.
Observer mode: Running Voidhash alongside your existing purchase code: the SDK reports purchases without making them. See Observer mode.
Offer: A discounted way to buy a product, such as an App Store promotional offer or a Google Play developer offer. See Products and perks.
Onboarding flow: A multi-screen flow designed in Studio that continues after a purchase. See Onboarding flows.
Organization: The API's name for a team.
P–R
Paid access sharing: The project setting that decides who keeps access when someone restores a purchase another account made. See Project settings.
Payment provider: Anything that takes payments and reports them to Voidhash: the App Store, Google Play, Stripe or a payment source. Set them up under Settings → Payment providers. See Payment providers (Help center).
Payment source: A billing system other than the stores and Stripe that reports payments to Voidhash. A provider endpoint is the handler on your server that Voidhash calls for it. See Payment sources.
Paywall: A screen, or a series of screens, designed in Studio that sells your products. See Paywalls in your app.
Perk: A capability a product unlocks, such as premium, checked by its slug in your app and on
your server. See Products and perks.
Person: An end user of your app or website, as Studio's People page lists them. See People and identity.
Placement: A paywall assigned to a location. Changing a location's placement changes what apps show there without a release. See Paywall locations.
Product: Something a person buys: a subscription, a one-time purchase or a consumable. See Products and perks.
Project: One app or product inside a team. It owns its keys, products, perks, paywalls, people and data. See Teams, projects and environments.
Publishable key: The key you ship in apps and websites (vh_pk_…, or vh_pk_test_… for
test). It only reaches the SDK endpoints, for one person at a time. See
API keys.
RTDN: Real-time developer notifications: the messages Google Play sends Voidhash when a purchase changes. See Connect Google Play (Help center).
S–Z
Scope: One permission a secret key holds, such as project:analytics:read. Studio groups
scopes into None, Read and Write per resource. See Access levels.
Secret key: A key for your servers (vh_sk_…, or vh_sk_test_… for test), with the access
you choose. Never ship it in an app. See API keys.
Server notification: A message the App Store sends Voidhash when a purchase changes, such as a renewal or refund. See Connect the App Store (Help center).
Simulated purchase: A free purchase made in development mode, recorded in the test
environment. See Development mode.
Store product: The App Store, Google Play, Stripe or payment-source item that a Voidhash product is mapped to. See Products and perks.
Studio: The Voidhash web dashboard. See How Voidhash works.
Subscriber: A person with an active subscription.
Subscription status: Whether a subscription is active or canceled. The SDKs and Studio's
People page show more detailed statuses derived from it. See
Statuses.
Team: Your company's account in Voidhash. It holds projects and members. See Teams, projects and environments and Members and roles.
VoidQL: Voidhash's read-only query language for project analytics, run from the API, an AI agent or Studio's Query page. See Query analytics with VoidQL.
Webhook: An HTTP request Voidhash sends to your server when something changes, such as a renewal. See Webhook delivery.
Next steps
Something wrong or missing on this page? Tell us by email or on Discord.