Prepare to migrate components and projects from Adobe Analytics to Customer Journey Analytics

Last update: 2024-01-26
  • Created for:
  • User
    Admin

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:

  1. 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

    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)

  2. Create a connection and data view with the data ingested.

  3. 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.

  4. 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.

Migrated
Owner Dimensions and metrics: No

Segments and date ranges: check mark

Sharing Dimensions and metrics: No

Segments and date ranges: No

Descriptions Dimensions and metrics: No

Segments and date ranges: check mark

Tags Dimensions and metrics: No

Segments and date ranges: No

Attribution (on dimensions) Dimensions and metrics: No

Segments and date ranges: No

Project elements that are migrated

Migrated
Date ranges check mark
Segments check mark
Quick segments check mark
Dimensions check mark Mapped automatically or manually
Metrics check mark Mapped automatically or manually
Panels check mark
Visualizations check mark
Owner check mark Defined by user doing the migration
Curation No
Sharing No
Annotations No
Folder structure No
Descriptions check mark
Tags No
Favorites No
Schedules No
Anomaly Detection check mark

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

IMPORTANT

The migration process identifies components in your Adobe Analytics project that can’t be automatically mapped to components in Customer Journey Analytics, and it allows you to manually map them.

Any mappings made on one project apply to all future projects across your entire IMS org, regardless of which user is performing the migration. These mappings cannot be modified or undone except by contacting Customer Care.

Because of this, it’s important that your organization decides how dimensions and metrics will be mapped before any projects are migrated. Doing so avoids individual administrators making decisions in a silo when considering only a single project.

Following is a list of dimensions and metrics that you must manually map if they exist in your project. We recommend reviewing this list before your migration. If any of these components exist in your project, decide now which Customer Journey Analytics components you will map them to.

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

On this page