Home AppMeasurement Web SDK · Migration Guide Created by Amit G Dusane

Migration › Add the Analytics Full Extension field group

Step 04 of 13
31% complete

Add the Analytics Full Extension field group

If the schema is the blueprint, field groups are the pre-drawn room templates you drop into it, and for an Analytics migration, one of them does almost all the work. The Adobe Analytics ExperienceEvent Full Extension adds the entire _experience.analytics structure, every eVar, prop, event, and hierarchy, and, crucially, the Edge already knows how to translate those fields straight into your Analytics variables[3][4] with no processing rules. Choose it and most of your mapping becomes drag-and-drop; skip it and you hand-wire each variable through processing rules later. It's a small step that quietly decides whether the next steps are easy or painful.
What to do
1
Where (in the schema) › Add field groups
Do Add Adobe Analytics ExperienceEvent Full Extension and AEP Web SDK ExperienceEvent. Add Commerce / productListItems too if you track purchases. Save.
FULL EXTENSIONADOBE ANALYTICS...eVars.eVar12...props.prop3...event1to100.event7.valueeVar12prop3event7no rule needed
The Edge already knows these fields, populate the Full Extension path and it lands in the matching variable, no processing rule in between.
⚠ Do not flip Profile

Leave the Profile toggle OFF. Once a schema is enabled for Profile and ingests data it locks permanently; you can't remove fields or disable it without resetting the sandbox.

⚠ Common mistake

Hand-mapping eVars through processing rules because nobody added the Full Extension. The auto-mapping it provides is the single biggest time-saver in the whole build, don't skip it.

✓ You should see

_experience.analytics.customDimensions.eVars, ...events, and web.webPageDetails.name now in the tree.