In today's digital landscape, data is a crucial part of understanding user behavior, tracking conversions, and optimizing digital experiences, especially for businesses aiming to stay ahead of the curve. Adobe Analytics stands as a reliable solution in this realm, offering robust tools to dissect and leverage data effectively.
Adobe Analytics’ Component Migration Tool offers efficiency within the scope of data migration and management. This powerful tool serves as a catalyst for seamless transitions to Customer Journey analytics (CJA), empowering businesses to evolve their analytics ecosystem without the headache of manually reconstructing their traditional Analytics reports.
In this blog, we embark on a journey through the nuances of Adobe Analytics' Component Migration Tool from its general functionalities to best practices for leveraging the tool. We'll equip you with the knowledge needed to streamline your analytics migration process while unlocking newfound efficiencies and insights to kickstart your analytics endeavors forward.
Adobe Analytics administrators can migrate Adobe Analytics projects and their components to Customer Journey Analytics. Prior to beginning the migration process of any Adobe Analytics projects, carefully review Adobe’s Migration Preparation documentation.
The migration process includes re-creating Adobe Analytics projects in Customer Journey Analytics and mapping dimensions and metrics from Adobe Analytics report suites to Customer Journey Analytics data views. Some dimensions and metrics are automatically mapped; others must be mapped manually. Additionally, you cannot make any mapping changes to automatically mapped dimensions and metrics (for example, the Visits metric in Adobe Analytics will automatically be mapped to the Sessions metric in Customer Journey Analytics).
When a dimension or metric cannot be automatically mapped, an orange symbol displays next to the Dimensions or Metrics section header with the number of Metrics or Dimensions that need to be manually mapped. In addition, the Status column will display as “not mapped”.
Note that all dimensions and metrics under your map schema are required to be mapped before you can finalize your migration. Components that cannot be mapped should be removed from your report during migration prep.
It’s important to note that any dimension or metric that you map are permanent, both for the project you are migratingand for all future projects you’d like to migrate. Any mappings that you make cannot be altered once the migration is complete. For example, if the Revenue Booked metric is accidentally mapped to Orders Placed, the migration tool will make the same incorrect mapping to all other projects in future conversions. Because of this, always ensure that the correct components are being selected before finalizing a migration. Note that any incorrect mappings will need to be resolved with Adobe’s support team.
It’s important to note that any dimension or metric that you map are permanent, both for the project you are migrating and for all future projects you’d like to migrate. Any mappings that you make cannot be altered once the migration is complete. For example, if the Revenue Booked metric is accidentally mapped to Orders Placed, the migration tool will make the same incorrect mapping to all other projects in future conversions. Because of this, always ensure that the correct components are being selected before finalizing a migration. Note that any incorrect mappings will need to be resolved with Adobe’s support team.
Not all components and features are supported in CJA, and in-turn will not be supported as part of the migration. Prior to beginning a project migration remove all unsupported dimensions, metrics, panels, and visualizations from your workspace. We recommend making a copy of the Adobe Analytics report you’d like to migrate and making all necessary changes to the copy.
The following visualizations and panels are not supported in CJA and therefore must be removed from Adobe Analytics reports prior to using the component migration tool:
When the above elements are included in a project prior to migration, they can cause the migration to fail or result in errors after the project is migrated. It is best practice to remove these elements before beginning a migration. If a migration fails, remove these elements before retrying the migration.
Decide as an organization how components will be mapped. This will mitigate any errors in the component mapping process. Also, as best practice, have someone familiar with your analytics data be responsible for performing report migrations. This will help ensure that only necessary reports and components are transitioned to CJA and help avoid mapping errors.
Segments, date ranges, and calculated metrics that don’t already exist in Customer Journey Analytics are re-created and based on the dimensions and metrics they are mapped to during the migration process.
Component Elements:
Project Elements:
Develop a thorough plan and process for validating traditional Adobe Analytics reports against new CJA reports including how they will be delivered to respective report users. Validation should include documentation of any reporting differences found between platforms. Often these differences are due to enhancements like cross-channel analytics. Discuss as an organization how reporting differences will be communicated to key stakeholders to ensure clear understanding of analytics reporting and what these differences mean for the business.
Below is a step-by-step guide for the component migration tool, but there is more that goes into streamlining your journey to CJA. Our team can work with you on building a strategy and roadmap that factors in all endpoints, timelines, and maintenance to ensure a seamless transition.
1. In Adobe Analytics, select the Admin tab, then select All admin.
2. Under Data configuration & collection, select Component migration.
3. Locate the project that you want to migrate.
4. Mouse over the project that you want to migrate, then select the Migrate icon Or, select the project that you want to migrate, then select Migrate to Customer Journey Analytics.
5. Now the Migrate project_name to Customer Journey Analytics dialog box should be displayed. Select the project name under the Project owner field and begin typing the name of the user who you want to be the owner of the project in Customer Journey Analytics, then select their name in the drop-down menu.
6. Select the report suite name listed under the Map schema for report suites section and use the dropdown to select a report suite.
7. Next, in the Data view drop-down menu, select the Customer Journey Analytics data view where you want the project and components to be migrated.
8. Select Map schema.
9. In the Map schema section, expand the Dimensions and Metrics sections.
10. To manually map dimensions and metrics, select a dimension or metric that has a “not mapped” status. Next, in the Mapped Customer Journey Analytics metric field (or the Mapped Customer Journey Analytics dimension field if you are mapping a dimension), select the dimension or metric in Customer Journey Analytics that you want to map to the dimension or metric you selected.
11. Repeat this process for each dimension or metric that contains a status of “not mapped”.
12. (Conditional) If the project you are migrating contains more than one report suite, select another report suite in the Map schema for report suites section, then repeat step 6 through Step 10.
13. Select Migrate.
If a migration fails, you can retry the migration. Before retrying a failed migration, make sure you remove any unsupported elements from the project.
1. In Adobe Analytics, select the Admin tab, then select All admin.
2. Under Data configuration & collection, select Component migration.
3. Select Failed in the Migration status column next to the project that you want to retry.
4. Select Retry migration.
Not sure on your next step? We'd love to hear about your business challenges. No pitch. No strings attached.
