- Implement Adobe Analytics
- Analytics Release Notes
- AppMeasurement release notes
- Analytics variables, functions, and methods
- Overview
- Configuration variables
- Configuration variables overview
- abort
- account
- charSet
- collectHighEntropyUserAgentHints
- cookieDomain
- cookieDomainPeriods
- cookieLifetime
- currencyCode
- decodeLinkParameters
- dynamicVariablePrefix
- fpCookieDomainPeriods
- linkDownloadFileTypes
- linkExternalFilters
- linkInternalFilters
- linkLeaveQueryString
- linkTrackEvents
- linkTrackVars
- linkURL
- offlineHitLimit
- offlineThrottleDelay
- trackDownloadLinks
- trackExternalLinks
- trackingServer
- trackingServerSecure
- trackInlineStats
- trackOffline
- useBeacon
- useLinkTrackSessionStorage
- usePlugins
- visitorID
- visitorNamespace
- writeSecureCookies
- Page variables
- Functions and methods
- Plug-ins
- Plug-ins overview
- addProductEvar
- addProductEvent
- apl
- cleanStr
- formatTime
- getAndPersistValue
- getGeoCoordinates
- getNewRepeat
- getPageLoadTime
- getPageName
- getPercentPageViewed
- getPreviousValue
- getQueryParam
- getResponsiveLayout
- getTimeBetweenEvents
- getTimeParting
- getTimeSinceLastVisit
- getTimeToComplete
- getValOnce
- getVisitDuration
- getVisitNum
- inList
- manageVars
- Numbers suite
- p_fo
- pt
- removeFromList
- websiteBot
- Integrate module
- Prepare to implement Adobe Analytics
- Implement Analytics using Experience Platform Edge
- Implement Analytics using the Adobe Analytics extension
- Implement Analytics using JavaScript
- Implement Analytics on other platforms
- Implement Analytics on mobile devices
- Implementation use cases
- Validate your implementation
- Frequently asked questions
- Review your implementation
Implement Adobe Analytics with Adobe Experience Platform Edge
Adobe Experience Platform Edge allows you to send data destined to multiple products to a centralized location. Experience Edge forwards the appropriate information to the desired products. This concept allows you to consolidate implementation efforts, especially spanning multiple data solutions.
Adobe offers three main ways to send data to Experience Edge:
- Adobe Experience Platform Web SDK: Use the Web SDK extension in Adobe Experience Platform Data Collection to send data to Edge.
- Adobe Experience Platform Mobile SDK: Use the Mobile SDK extension in Adobe Experience Platform Data Collection to send data to Edge.
- Adobe Experience Platform Edge Network Server API: Send data directly to Edge using an API.
How Adobe Analytics handles Experience Edge data
Data send to Experience Edge has to 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 Adobe Analytics, these events are translated into more structured data that Adobe Analytics can handle: page views or link events.
XDM does not itself prescribe how to define page views or link events, nor does it instruct Adobe Analytics how to treat its payload. For example, certain out of the box XDM fields that appear to be related to page views or link events, like eventType, web.webPageDetails.pageViews, or web.webInteraction.linkEvents are completely implementation agnostic and have no relevance for Adobe Analytics.
To properly handle page views and link events, the following logic is applied to data send to the Adobe Experience Edge network and forwarded to Adobe Analytics.
| XDM payload contains… | Adobe Analytics… |
|---|---|
web.webPageDetails.name or web.webPageDetails.URL and no web.webInteraction.type |
considers payload a page view |
web.webInteraction.type and (web.webInteraction.name or web.webInteraction.url) |
considers payload a link event |
web.webInteraction.type and (web.webPageDetails.name or web.webPageDetails.url) |
considers payload a link event web.webPageDetails.name and web.webPageDetails.URL are set to null |
no web.webInteraction.type and (no webPageDetails.name and no web.webPageDetails.URL) |
drops the payload and ignores the data |
Business.Adobe.com resources
Resources
Adobe Account
