Data, Catalog, and Forms

Define project data, reusable catalog data, live controls, and form-submission handling

Personalization in Platform depends on structured data. The project data schema defines the viewer parameters used by the MP5 experience, live controls define operational values that can change without changing each viewer record, catalog data stores reusable grouped records, and form data captures viewer submissions when forms are enabled.

Dynamic Data

Dynamic Data defines the fields used to personalize the MP5 experience. Each field has a type and a default value, such as numbers, text, images, links, and grouped fields.

Common actions include:

• Add Field to define a new project parameter.

• Add Group to organize related parameters.

• Add Internal to add fields used internally by the project.

• Add Catalog Item to connect a parameter to reusable catalog data.

• Code mode to inspect or edit the data schema in a structured format.

Live Control

Catalog

Form Data

Data Model Checklist

1

Define Viewer Parameters

Create the Dynamic Data fields that arrive from the CRM, spreadsheet, SDK, URL, or API integration.

2

Add Shared Live Controls

Create Live Control fields for values that should be managed centrally, such as brand colors, logos, or campaign settings.

3

Use Catalogs for Reusable Records

Create Catalog groups when the project needs reusable rows like products, offers, plans, or collections.

4

Collect Viewer Input When Needed

Enable Form Data when the MP5 player needs to capture submitted values from interactive forms.

Catalog, Form Data, and optimization-related features can depend on project and account configuration. Platform shows setup or enablement guidance in the feature area when additional configuration is required.

Integration and SimulationCatalog