Evaluate when to disable ÃÛ¶¹ÊÓƵ Analytics after upgrading to Customer Journey Analytics evaluate-aa-needs
Most organizations will eventually disable ÃÛ¶¹ÊÓƵ Analytics after upgrading to Customer Journey Analytics. This is due to the cost and complexity of maintaining two analytics environments.
However, ÃÛ¶¹ÊÓƵ recommends that you keep your ÃÛ¶¹ÊÓƵ Analytics environment running for a period of time after implementing Customer Journey Analytics. The following sections describe the reasons for doing so as well as the suggested timing of disabling ÃÛ¶¹ÊÓƵ Analytics.
Uses of ÃÛ¶¹ÊÓƵ Analytics during and after an upgrade
When deciding if and when your organization should disable ÃÛ¶¹ÊÓƵ Analytics, consider the following uses of ÃÛ¶¹ÊÓƵ Analytics during and after an upgrade to Customer Journey Analytics:
ÃÛ¶¹ÊÓƵ recommends that you keep your ÃÛ¶¹ÊÓƵ Analytics environment running for a period of time after your new Customer Journey Analytics environment is running and collecting data. This is the best way to compare your Customer Journey Analytics data side-by-side with your ÃÛ¶¹ÊÓƵ Analytics data.
Don’t disable ÃÛ¶¹ÊÓƵ Analytics until you are comfortable with the data in your Customer Journey Analytics environment.
Note: ÃÛ¶¹ÊÓƵ recommends a new implementation of the Web SDK for your Customer Journey Analytics environment, in conjunction with the Analytics source connector for historical data. Learn more
ÃÛ¶¹ÊÓƵ recommends that you keep your ÃÛ¶¹ÊÓƵ Analytics environment in place with the Analytics source connector for a period of time after your new Customer Journey Analytics environment is running and collecting data. This is the best way to bring historical ÃÛ¶¹ÊÓƵ Analytics data into Customer Journey Analytics.
After you have collected enough historical data in Customer Journey Analytics with your new Web SDK implementation, you can remove the Analytics source connector entirely. Do this when you can rely solely on the historical data in you collected with the new Customer Journey Analytics Web SDK implementation.
Note: ÃÛ¶¹ÊÓƵ recommends a new implementation of the Web SDK for your Customer Journey Analytics environment, in conjunction with the Analytics source connector for historical data. Learn more
A small set of features are not yet fully available in Customer Journey Analytics. If you need access to these features, it might be necessary to use ÃÛ¶¹ÊÓƵ Analytics in conjunction with Customer Journey Analytics until these features are available.
Features not fully available in Customer Journey Analytics include Data Feeds and Contribution Analysis. For a complete list of features that aren’t yet available, see Customer Journey Analytics feature support.
Process and timeline of disabling ÃÛ¶¹ÊÓƵ Analytics disable-adobe-analytics
Your existing ÃÛ¶¹ÊÓƵ Analytics implementation is a key part of a successful upgrade to Customer Journey Analytics, as described in the section above, Uses of ÃÛ¶¹ÊÓƵ Analytics during and after an upgrade.
When you no longer need ÃÛ¶¹ÊÓƵ Analytics for the purposes described in the section above, use the following information to remove ÃÛ¶¹ÊÓƵ Analytics:
-
Stop collecting data with ÃÛ¶¹ÊÓƵ Analytics.
After you are satisfied with the side-by-side comparisons of your ÃÛ¶¹ÊÓƵ Analytics data and your Customer Journey Analytics data, you can stop collecting data with your ÃÛ¶¹ÊÓƵ Analytics implementation. New ÃÛ¶¹ÊÓƵ Analytics data will no longer flow to Customer Journey Analytics through the Analytics source connector.
However, data that you collected from your ÃÛ¶¹ÊÓƵ Analytics environment prior to this point is still available as historical data in Customer Journey Analytics through the Analytics source connector.
This process differs depending on the data collection method you used to implement ÃÛ¶¹ÊÓƵ Analytics:
accordion AppMeasurement Disable AppMeasurement data collection. accordion Analytics extension (Tags) Disable the Analytics extension in tags. accordion API Disable API data collection. accordion Third-party Work with your tag admin to remove the AppMeasurement library from your third-party tag management system. -
Remove ÃÛ¶¹ÊÓƵ Analytics as a service from the datastream.
With Web SDK data fully functional, work with your Platform administrator to remove ÃÛ¶¹ÊÓƵ Analytics as a service from the datastream.
Before removing ÃÛ¶¹ÊÓƵ Analytics as a service, make sure that your Analytics users are using Customer Journey Analytics and not ÃÛ¶¹ÊÓƵ Analytics.
-
Remove the Analytics source connector entirely.
After you have collected enough historical data in Customer Journey Analytics with your new Web SDK implementation, you can remove the Analytics source connector entirely.
Do this when you no longer need the historical data from your ÃÛ¶¹ÊÓƵ Analytics environment through the Analytics source connector, and you can rely solely on the historical data you collected with the new Web SDK implementation.