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.
ÃÛ¶¹ÊÓƵ offers three main ways to send data to the Edge Network:
- ÃÛ¶¹ÊÓƵ Experience Platform Web SDK: Use the Web SDK extension in ÃÛ¶¹ÊÓƵ Experience Platform Data Collection to send data to Edge.
- ÃÛ¶¹ÊÓƵ Experience Platform Mobile SDK: Use the Mobile SDK extension in ÃÛ¶¹ÊÓƵ Experience Platform Data Collection to send data to Edge.
- ÃÛ¶¹ÊÓƵ Experience Platform Edge Network Server API: Send data directly to Edge using an API.
How ÃÛ¶¹ÊÓƵ Analytics handles Edge Network data
Data sent to the ÃÛ¶¹ÊÓƵ Experience Platform Edge Network can follow two formats:
- XDM object: Conform to schemas based on XDM (Experience Data Model). XDM gives you flexibility in what fields are defined as part of events. At the time events reach ÃÛ¶¹ÊÓƵ Analytics, they are translated into a format that ÃÛ¶¹ÊÓƵ Analytics can handle.
- Data object: Send data to the Edge Network using specific fields mapped to ÃÛ¶¹ÊÓƵ Analytics. The Edge Network detects the presence of these fields and forwards them to ÃÛ¶¹ÊÓƵ Analytics without the need to conform to a schema.
The Edge Network uses the following logic to determine ÃÛ¶¹ÊÓƵ Analytics page views and link events:
xdm.web.webPageDetails.name
or xdm.web.webPageDetails.URL
and no xdm.web.webInteraction.type
xdm.eventType = web.webPageDetails.pageViews
xdm.web.webInteraction.type
and (xdm.web.webInteraction.name
or xdm.web.webInteraction.url
)xdm.web.webInteraction.type
and (xdm.web.webPageDetails.name
or xdm.web.webPageDetails.url
)Also sets
xdm.web.webPageDetails.name
and xdm.web.webPageDetails.URL
to null
xdm.web.webInteraction.type
and (no xdm.webPageDetails.name
and no xdm.web.webPageDetails.URL
)In addition to differentiating page views and link clicks, the following logic is in place that determines if certain events are categorized as A4T or are discarded.
xdm.eventType = display
orxdm.eventType = decisioning.propositionDisplay
orxdm.eventType = personalization.request
orxdm.eventType = decisioning.propositionFetch
and xdm._experience.decisioning
xdm.eventType = display
orxdm.eventType = decisioning.propositionDisplay
orxdm.eventType = personalization.request
orxdm.eventType = decisioning.propositionFetch
and no xdm._experience.decisioning
xdm.eventType = click
or xdm.eventType = decisioning.propositionInteract
and xdm._experience.decisioning
and no web.webInteraction.type
xdm.eventType = click
or xdm.eventType = decisioning.propositionInteract
and no xdm._experience.decisioning
and no web.webInteraction.type
See the ÃÛ¶¹ÊÓƵ Analytics ExperienceEvent Full Extension schema field group for more information.