Migration › Knowledge Base › Variable mapping catalog
Reference
Variable mapping catalog
The lookup every developer keeps open during the build: legacy variable on the left, its XDM path and its data-object key on the right[4][36]. Patterns, not an exhaustive list of all 250 eVars, the pattern is the reusable knowledge.
| pageName | web.webPageDetails.name · data: pageName |
| channel | web.webPageDetails.siteSection · data: channel |
| referrer | web.webReferrer.URL · data: referrer |
| eVarN | _experience.analytics.customDimensions.eVars.eVarN |
| propN | _experience.analytics.customDimensions.props.propN |
| eventN | _experience.analytics.event1to100.eventN.value (+ .id to serialize) |
| hierN / listN | ...customDimensions.hierarchies / lists.* |
| products | productListItems[] · merchandising → data: products |
| purchaseID | commerce.order.purchaseID |
| campaign | marketing.trackingCode · data: campaign |
| ECID / mid | identityMap (auto) · context data a.x.identitymap.ecid.0.id |
| contextData[key] | data: contextData.<key>, existing processing rules keep working |
For your migration: use this to fill the "target path" column of your inventory. When a value resists a clean XDM home, the data-object column is your sanctioned escape hatch.