ÃÛ¶¹ÊÓƵ

XDM object variable mapping to ÃÛ¶¹ÊÓƵ Analytics

The following table shows the XDM variables that the ÃÛ¶¹ÊÓƵ Experience Platform Edge Network automatically maps into ÃÛ¶¹ÊÓƵ Analytics. If you use these XDM field paths, no additional configuration is necessary to send data to ÃÛ¶¹ÊÓƵ Analytics. These fields are included in the ÃÛ¶¹ÊÓƵ Analytics ExperienceEvent Template field group. Use of these fields are recommended if you intend to send data to both ÃÛ¶¹ÊÓƵ Analytics and ÃÛ¶¹ÊÓƵ Experience Platform.

If your organization plans to move to Customer Journey Analytics, ÃÛ¶¹ÊÓƵ recommends instead using the data object to send data directly to ÃÛ¶¹ÊÓƵ Analytics without conforming to a schema. This strategy allows your organization to use your own schema, instead of using the ÃÛ¶¹ÊÓƵ Analytics ExperienceEvent Template (which is less applicable to Customer Journey Analytics). See Data object variable mapping to ÃÛ¶¹ÊÓƵ Analytics for a similar mapping table.

Value priorities

Most XDM object fields in this table coincide with a data object field. If you set both a given XDM object field and its respective data object field, the data object field takes priority. If you use both the XDM object field and the data object field, ÃÛ¶¹ÊÓƵ recommends setting custom events using the data object field. If the field data.__adobe.analytics.events is present, it overwrites all XDM object fields related commerce and custom events.

XDM object field mapping

Previous updates to this table can be found on this page’s .

Mapping other XDM fields to Analytics variables

If there are any dimensions or metrics that you want to add to ÃÛ¶¹ÊÓƵ Analytics, you can do so through Context Data variables.

Implicit mapping

Any XDM field elements that are not automatically mapped are sent to ÃÛ¶¹ÊÓƵ Analytics as Context Data with the prefix a.x. You can then map this context data variable to the desired Analytics variable using Processing rules. For example, if you send the following event:

alloy("event",{
    "xdm":{
        "_atag":{
            "search":{
                "term":"Example search term"
            }
        }
    }
})

The Web SDK sends that data to ÃÛ¶¹ÊÓƵ Analytics as the context data variable a.x._atag.search.term. You can then use a processing rule to assign that context data variable value to the desired Analytics variable, such as an eVar:

Explicit mapping

You can also explicitly map XDM field elements as context data. Any XDM field element that is explicitly mapped, using the contextData element, is sent to ÃÛ¶¹ÊÓƵ Analytics as Context Data without a prefix. You can then map this context data variable to the desired Analytics variable using Processing rules. For example, if you send the following event:

alloy("event",{
    "xdm":{
        "_atag":{
            "analytics": {
                "contextData" : {
                    "someValue" : "1"
                }
            }
        }
    }
})

The Web SDK sends that data to ÃÛ¶¹ÊÓƵ Analytics as the context data variable somevalue with value 1. You can then use a processing rule to assign that context data variable value to the desired Analytics variable, such as an eVar: