Glossary
The following list explains common features and terms found within MonetizationOS.
| What it's called | What it does |
|---|---|
| Actions | Workflows that execute in response to trigger events, enabling automated processes and integrations with external systems. |
| Brands | Brands let you tailor access, environments and features across different entities within your organization, such as different mastheads, regional editions, or product lines. |
| Command + K | A quick command menu accessible via keyboard shortcut that enables fast navigation and actions throughout the platform. Allows users to quickly create new plans, features, versions, and other resources without navigating through multiple screens or menus. |
| Components | Specific content elements or functional parts within a surface that can have individual access control applied (article content, banner ads, ad slots, subscription prompts). Each component can have custom access rules and behaviors defined independently of other components on the same surface. |
| Component Workflows | Custom rules for component-level access control, enabling usage meters, dynamic paywalls, and personalized experiences for individual elements. These workflows provide granular control over specific content pieces within a surface. |
| Dashboard | Your application homepage showing version overview, API keys, and usage metrics. |
| Endpoints | Custom HTTP routes that external systems can call to interact with MonetizationOS, enabling two-way integration between applications and the platform. |
| Environments | Isolated workspaces for safe development and testing. Default Preview and Live environments can be expanded with custom staging setups. |
| Features | The core capabilities you want to monetize or gate (articles, videos, AI tools). The fundamental building blocks of access control. |
| Feature Properties | Configurable attributes of features that vary by access level (e.g., video resolution, ad frequency, download permissions). |
| Feature Workflows | Custom logic for dynamically setting feature property values from external sources like JWT claims or third-party systems. These workflows allow you to pull configurable attributes (like ad frequency or video resolution) from authentication tokens rather than using static provisioned values. |
| Integrations | Connections to your existing stack - authentication providers via JWT and payment processing via Stripe. |
| Identity Link | A relationship between a source and a target user identity that enables data sharing to represent a unified user journey. The source is the original user, and the target is the user receiving the link and any associated data. Supports custom relationships with additional metadata. |
| JWT | JSON Web Tokens for secure, cryptographically verified data exchange between your systems and MonetizationOS. |
| Meters | Usage tracking that resets on a schedule. Implemented as numeric properties on features or plans. |
| Observability | Complete logging and monitoring of decisions and events processed through the platform. |
| Offers | Present purchase opportunities to users with configurable pricing, messaging, and redemption flows. Each offer packages a product or action with presentation details and targeting rules. |
| Offer Groups | Offers must be added to an Offer Group to be displayed. The group determines the UI layout and contains slots where individual offers appear. |
| Orchestration Workflows | Automated business logic that coordinates multiple systems and processes through triggers, actions, and endpoints. |
| Plans | Collections of features defining user access levels. Can be auto-assigned based on identity or linked to Stripe products for paid subscriptions. |
| Provisioning Workflows | Automated plan assignment based on user attributes like location, referrer, device, or behavior patterns. |
| Surfaces | The different interfaces or touchpoints where users interact with your product or content. For example, web browsers, mobile apps, MCPs, or APIs. Surfaces contain multiple components and handle broad-level access decisions for the entire interface context. |
| Surface Workflows | Configure access decisions at the surface level, such as setting cookies, adding headers, or blocking access entirely to a web, app, or MCP interface. These workflows determine if a user can access the surface at all before any component-level decisions are made. |
| Triggers | Asynchronous events that initiate workflow execution, either fired automatically by MonetizationOS or called programmatically from within workflows. |
| Variables & Secrets | Key-value pairs that separate configuration from workflow logic, enabling different values across environments and brands. |
| Versions | Snapshots of your configuration packaged for deployment across environments, enabling safe testing and rollbacks. |
| Workflows | Automated business logic for dynamic plan assignment and custom access rules using code-based configuration. |