Prepare to migrate components and projects from Adobe Analytics to Customer Journey Analytics
Before anyone in your organization begins migrating projects as described in Migrate components and projects from Adobe Analytics to Customer Journey Analytics, complete the following sections.
Prerequisites
Before your projects and their associated components are ready to migrate, you first need to follow the steps in Evolution from Adobe Analytics in the Adobe Customer Journey Analytics Guide. These steps include:
-
Use either of the following methods to ingest data into Adobe Experience Platform in order to view Adobe Analytics report suite data in Customer Journey Analytics:
note note NOTE When you use the WebSDK to ingest data, all schema fields must be manually mapped. (For more information about the mapping process, see Migrate components and projects from Adobe Analytics to Customer Journey Analytics) -
To use the Adobe Analytics source connector, you need to:
-
To use the WebSDK, you need to:
-
-
Create a connection and data view with the data ingested.
-
Ensure that users in Customer Journey Analytics are provisioned to the data views where data is being mapped.
For more information, see Customer Journey Analytics permissions in the Admin Console in Customer Journey Analytics access control.
The Permissions tab is part of each product profile in Admin Console. You can add users to specific product profiles. Then you assign rights to specific data views and specify which permissions the users in a product profile have.
-
Decide as an organization how you will map components.
For more information, see the section below, Decide as an organization how you will map components.
Understand what is included in a migration
The following tables outline which elements of a project and component are included in a migration:
Component elements that are migrated
Dimensions and metrics are migrated as part of the mapping process described in Migrate Adobe Analytics projects to Customer Journey Analytics.
Segments, date ranges, and calculated metrics that don’t already exist in Customer Journey Analytics are re-created there based on the dimensions and metrics that are mapped.
Dimensions and metrics: No
Segments and date ranges:
Dimensions and metrics: No
Segments and date ranges: No
Dimensions and metrics: No
Segments and date ranges:
Dimensions and metrics: No
Segments and date ranges: No
Dimensions and metrics: No
Segments and date ranges: No
Project elements that are migrated
Understand unsupported elements that cause errors
The following visualizations and panels are not supported in Customer Journey Analytics. When these elements are included in a project prior to migration, they can either cause the migration to fail or they can result in errors after the project is migrated.
Remove these elements from the Adobe Analytics project before migrating the project to Customer Journey Analytics. If a migration fails, remove these elements before retrying the migration.
Unsupported Visualizations
Unsupported Panels
Decide as an organization how you will map components
Dimensions that must be manually mapped
- averagepagetime
- pagetimeseconds
- singlepagevisits
- visitnumber
- timeprior
- timespent
- category
- connectiontype
- customerloyalty
- customlink
- downloadlink
- exitlink
- hitdepth
- hittype
- pathlength
- daysbeforefirstpurchase
- dayssincelastpurchase
- dayssincelastvisit
- identificationstate
- optoutreason
- persistentcookie
- returnfrequency
- searchenginenatural
- searchenginenaturalkeyword
- mobilecarrier
- monitorresolution
- surveybase
- mcaudiences
- tntbase
- targetraw
Metrics that must be manually mapped
- timespentvisit
- timespentvisitor
- reloads
- bounces
- bouncerate
- pageevents
- pageviewspervisit
- orderspervisit
- averagepagedepth
- averagetimespentonsite
- exitlinkinstances
- customlinkinstances
- downloadlinkinstances
- darkvisitors
- singlepagevisits
- singlevaluevisits
- visitorhomepage
- visitorsmcvisid
- pagesnotfound
- newengagements
- time_granularity
- concurrent_viewers_visitors
- concurrent_viewers_occurrences
- devices
- estimatedpeople
- playback_time_spent_seconds
- playback_time_spent_minutes
- average_minute_audience_time_based
- average_minute_audience_media_time
- average_minute_audience_content_time
- video_length
- targetconversion
- targetimpression