Migration › Create the schema
Step 03 of 13
23% complete
Create the schema
A schema is the blueprint of your data. Like an architect's drawing of a house, it holds nothing itself; there's no furniture in a blueprint, yet it decides where every room and doorway goes, and once the house is built you live inside those decisions every day. In Experience Platform the schema defines the exact shape every event must take before the Edge will accept it: which fields exist, what type each one is, and where every value belongs. Get it right and everything downstream, Analytics today, CJA tomorrow, reads your data effortlessly. Get it wrong and you're knocking down load-bearing walls after move-in, which is exactly why the Profile lock in the next step is treated with such caution.
What to do
1
Where Data Collection › Schemas › Create schema › Experience Event
Do Pick the Experience Event class (time-series behaviour, page views, clicks), not Individual Profile. Name it
Web SDK ExperienceEvent, [site].⚠ Common mistake
Choosing the Individual Profile class out of habit, then finding it can't model page views or clicks, and rebuilding. Web events are events: pick Experience Event.
Reality check
Confirm your sandbox at the top of the screen before creating anything, a schema built in the wrong sandbox isn't movable, you recreate it. Dev sandbox if you have AEP; standalone-Analytics orgs may only see production, which is fine.
✓ You should see
The new schema opens with an empty structure tree, class shown as Experience Event. Field groups come next.