Advantages and disadvantages of this implementation path
Using the Web SDK extension to send data to Adobe Analytics has both advantages and disadvantages. Carefully weigh each option to decide which approach is best for your organization.
Advantages | Disadvantages |
---|---|
|
|
- You can use the Adobe Analytics schema in CJA. Note that CJA does not have a concept of props or eVars; they are treated as any other schema field. Also note that the use of the Adobe Analytics schema in CJA can make it more difficult to use other platform services, such as Adobe Journey Optimizer or Real-Time Customer Data Platform.
- You can use the data object, similar to a migration workflow. Note that the use of the data object requires that you map each data object field to an XDM schema field.
- You can skip the Adobe Analytics implementation entirely, and send data to Adobe Experience Platform using your own schema. This approach is ideal long-term, and allows your organization to start using Customer Journey Analytics.
Steps required to implement the Web SDK tag extension
A high-level overview of the implementation tasks:
Analytics
- Implement Adobe Analytics
- Analytics Release Notes
- AppMeasurement release notes
- Analytics variables, functions, and methods
- 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