ÃÛ¶¹ÊÓƵ

Implement ÃÛ¶¹ÊÓƵ Analytics with the ÃÛ¶¹ÊÓƵ Experience Platform Edge Network

The ÃÛ¶¹ÊÓƵ Experience Platform Edge Network allows you to send data destined to multiple products to a centralized location. The Edge Network forwards the appropriate information to the desired products. This concept allows you to consolidate implementation efforts, especially spanning multiple data solutions. ÃÛ¶¹ÊÓƵ Analytics is one of the products that you can send data to using the Edge Network.

How ÃÛ¶¹ÊÓƵ Analytics handles Edge Network data

Data sent to the ÃÛ¶¹ÊÓƵ Experience Platform Edge Network can follow three formats: XDM object, Data object, and Context data. When a datastream forwards data to ÃÛ¶¹ÊÓƵ Analytics, they are translated into a format that ÃÛ¶¹ÊÓƵ Analytics can handle.

xdm object

Conform to schemas that you create based on XDM (Experience Data Model). XDM gives you flexibility in what fields are defined as part of events. If you want to use a pre-defined schema specific to ÃÛ¶¹ÊÓƵ Analytics, you can add the ÃÛ¶¹ÊÓƵ Analytics ExperienceEvent schema field group to your schema. Once added, you can populate this schema using the xdm object in the Web SDK to send data to a report suite. When data arrives at the Edge Network, it translates the XDM object into a format that ÃÛ¶¹ÊÓƵ Analytics understands.

See XDM object variable mapping to ÃÛ¶¹ÊÓƵ Analytics for a full reference of XDM fields and how they map to Analytics variables.

data object

As an alternative to using the xdm object, you can use the data object instead. The data object is geared towards implementations that currently use AppMeasurement, making the upgrade to the Web SDK much easier. The Edge Network detects the presence of fields specific to ÃÛ¶¹ÊÓƵ Analytics without the need to conform to a schema.

See Data object variable mapping to ÃÛ¶¹ÊÓƵ Analytics for a full reference of data object fields and how they map to Analytics variables.

Context data variables

Send data to the Edge Network in any format that you’d like. Any fields that don’t automatically map to xdm or data object fields are included as Context data variables when forwarded to ÃÛ¶¹ÊÓƵ Analytics. You must then use Processing rules to map the desired fields to their respective Analytics variables.

For example, if you had a custom XDM schema that looked like the following:

{
  "xdm": {
    "key": "value",
    "animal": {
      "species": "Raven",
      "size": "13 inches"
    },
    "array": [
      "v0",
      "v1",
      "v2"
    ],
    "objectArray":[{
      "ad1": "300x200",
      "ad2": "60x240",
      "ad3": "600x50"
    }]
  }
}

Then these fields would be the context data keys available to you in the Processing rules interface:

a.x.key // value
a.x.animal.species // Raven
a.x.animal.size // 13 inches
a.x.array.0 // v0
a.x.array.1 // v1
a.x.array.2 // v2
a.x.objectarray.0.ad1 // 300x200
a.x.objectarray.1.ad2 // 60x240
a.x.objectarray.2.ad3 // 600x50