3. Define a MeData

A MeData Definition describes one data point you want the SDK to collect on-device — its name, source, value type and constraints. The SDK fetches every Definition you publish on the Orchestrator and uses it to know how to collect and store values.

We'll create a Question-sourced MeData called favorite_color. Question-sourced MeData is the simplest source: when the SDK needs to collect it, it shows the question you authored and stores the user's answer.

1. From the Orchestrator's left navigation, open MeData Definitions.
2. Click the + button on the top-right of the MeData Definitions table.
3. Fill in the editor:
   • Source: Question
   • Programmatic name: favorite_color
   • Display name: Favourite colour
   • Description: The user's favourite colour, asked once.
   • Sharable: true (you'll be able to request it as Zero-Party Data later)
   • Value Type: string
   • Provide the question text shown to the user, e.g. "What is your favourite colour?"
4. Save the Definition.

[#02] The MeData Definition editor with favorite_color

The new Definition appears in the table. The SDK will pick it up on its next sync.

Other sources

A MeData Definition's Source can also be Native (device/OS data), Script (logic you author) or VC (Verifiable Credentials). We're keeping it simple here.

---