Schemas
This guide introduces schemas and explains how they are used in MonetizationOS.
Schemas define the structure and data model behind your experiences and offers. They tell MonetizationOS what fields exist, what type of data each field holds, and how that information connects to the rest of your configuration. Before you can build an experience or attach offer presentation or redemption logic, you need a schema to describe the shape of that data.
Schema Types
There are three schema types, each serving a distinct purpose in your monetization setup.
App Experience
Used for schema-driven components rendered by your own frontend library. Use this when your frontend team has built a component and needs a form-driven way to populate it with content. You can optionally enable offer support, allowing offers to be attached and displayed within the experience.
Offer Presentation
Defines how an individual offer is displayed within an experience. For example, fields like name, price, and description. When an experience has offers enabled, it references an Offer Presentation schema to determine how each offer is rendered to the user.
Offer Redemption
Defines the information required to redeem an offer. For example, what subscription terms to create in your subscription service. Attached at offer level to control what happens when a user redeems an offer.
Viewing Your Schemas
Navigate to the Schemas section from the left-hand navigation menu. You will see a list of all schemas in your organization. For each schema, you will see:
- Name: The name and description of the schema
- Purpose: The schema type — App Experience, Offer Presentation, or Offer Redemption
- Brands: The brands this schema is linked to
- Last Updated: The date and time the schema was last modified, and the avatar of the admin user who made the update
- Actions: A three-dot menu with the option to delete the schema
Add a Schema
For information on creating a new schema, see our Add a Schema guide.
Manage a Schema
For information on editing or deleting a schema, see our Manage a Schema guide.