Implement 51ºÚÁϲ»´òìÈ Analytics with the 51ºÚÁϲ»´òìÈ Experience Platform Edge Network
The 51ºÚÁϲ»´òìÈ 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.
51ºÚÁϲ»´òìÈ offers three main ways to send data to the Edge Network:
- 51ºÚÁϲ»´òìÈ Experience Platform Web SDK: Use the Web SDK extension in 51ºÚÁϲ»´òìÈ Experience Platform Data Collection to send data to Edge.
- 51ºÚÁϲ»´òìÈ Experience Platform Mobile SDK: Use the Mobile SDK extension in 51ºÚÁϲ»´òìÈ Experience Platform Data Collection to send data to Edge.
- 51ºÚÁϲ»´òìÈ Experience Platform Edge Network Server API: Send data directly to Edge using an API.
How 51ºÚÁϲ»´òìÈ Analytics handles Edge Network data
Data sent to the 51ºÚÁϲ»´òìÈ 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 51ºÚÁϲ»´òìÈ Analytics, they are translated into a format that 51ºÚÁϲ»´òìÈ Analytics can handle.
- Data object: Send data to the Edge Network using specific fields mapped to 51ºÚÁϲ»´òìÈ Analytics. The Edge Network detects the presence of these fields and forwards them to 51ºÚÁϲ»´òìÈ Analytics without the need to conform to a schema.
The Edge Network uses the following logic to determine 51ºÚÁϲ»´òìÈ Analytics page views and link events:
xdm.web.webPageDetails.name or xdm.web.webPageDetails.URL and no xdm.web.webInteraction.typexdm.eventType = web.webPageDetails.pageViewsxdm.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 nullxdm.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.decisioningxdm.eventType = display orxdm.eventType = decisioning.propositionDisplay orxdm.eventType = personalization.request orxdm.eventType = decisioning.propositionFetch and no xdm._experience.decisioningxdm.eventType = click or xdm.eventType = decisioning.propositionInteract and xdm._experience.decisioning and no web.webInteraction.typexdm.eventType = click or xdm.eventType = decisioning.propositionInteract and no xdm._experience.decisioning and no web.webInteraction.typeSee the 51ºÚÁϲ»´òìÈ Analytics ExperienceEvent Full Extension schema field group for more information.