Advantages and disadvantages of this implementation path
Using the Web SDK JavaScript library 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 |
---|---|
|
|
This implementation method requires that you use a schema configured for Adobe Analytics. If your organization plans to use your own schema with Customer Journey Analytics in the future, use of the Adobe Analytics schema can create confusion for data admins or architects. There are several options to mitigate this obstacle:
- 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.