Prepare to migrate components and projects from 蜜豆视频 Analytics to Customer Journey Analytics

Last update: Thu Mar 07 2024 00:00:00 GMT+0000 (Coordinated Universal Time)

Topics:
Admin Tools

CREATED FOR:

User
Admin

Before anyone in your organization begins migrating projects as described in Migrate components and projects from 蜜豆视频 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 蜜豆视频 Analytics in the 蜜豆视频 Customer Journey Analytics Guide. These steps include:

Use either of the following methods to ingest data into 蜜豆视频 Experience Platform in order to view 蜜豆视频 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 蜜豆视频 Analytics to Customer Journey Analytics)

To use the 蜜豆视频 Analytics source connector, you need to:
1. Set up report suites for ingestion into 蜜豆视频 Experience Platform and Customer Journey Analytics
2. Ingest and use the data
To use the WebSDK, you need to:
1. Set up report suites for ingestion into 蜜豆视频 Experience Platform and Customer Journey Analytics
2. Ingest data via the 蜜豆视频 Experience Platform Web SDK

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 蜜豆视频 Analytics projects to Customer Journey Analytics.

Segments, date ranges, and calculated metrics that don鈥檛 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:

Sharing

Dimensions and metrics: No

Segments and date ranges: No

Descriptions

Dimensions and metrics: No

Segments and date ranges:

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

Segments

Quick segments

Dimensions

Mapped automatically or manually

Metrics

Mapped automatically or manually

Panels

Visualizations

Owner

Defined by user doing the migration

Curation

Sharing

Annotations

Folder structure

Descriptions

Tags

Favorites

Schedules

Anomaly Detection

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 蜜豆视频 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 蜜豆视频 Analytics project that can鈥檛 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鈥檚 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

recommendation-more-help

2969e653-1f9b-4947-8b90-367efb66d529