Two behaviours
Record
Attributes of an entity — a customer, product or store. Example class: XDM Individual Profile.
Time-series
Events that happen at a point in time — page views, purchases, app opens. Example class: XDM ExperienceEvent.
Reusing fields across classes
Field groups are tied to a class, so a custom field group built for a profile schema will not appear when editing an event schema. To reuse the same structure, create a data type and add it inside class-specific field groups.
Standard ExperienceEvent fields
ExperienceEvent schemas already include _id, timestamp, eventType and identityMap. Map your data to them instead of creating custom duplicates. Each record needs a unique _id; generate a UUID during mapping if the source has none.
Before you enable Profile
Enabling a schema for Profile cannot be undone. Review the schema first; fixing a mistake later can mean recreating the schema and dataset and re-ingesting.
Frequently asked questions
Can I edit a field group used by several schemas?
You can add fields, which affects every schema using it, so treat shared field groups as governed assets.
What causes 'Cannot merge incompatible data types'?
A field path was already defined elsewhere in the tenant with a different type. Rename the new path or align the types.
Last updated: