Understanding the Naming Changes

The rebranding of Datorama Reports is part of a larger effort by Salesforce to streamline and simplify its product offerings. However, this change can cause confusion, especially when working with Journey Builder Activities or other features that still reference the old name.

For example, Datorama Reports Advanced are now referred to as Intelligence Reports for Engagement Advanced, which can be confusing for users who are familiar with the old naming convention.

Implications for Marketing Cloud Users

The naming changes in Datorama Reports can have implications for Marketing Cloud users, particularly those who are working with Journey Builder or other features that integrate with Datorama Reports.

It is essential to understand the new naming convention and how it affects your workflows and processes. This includes updating any documentation or training materials to reflect the new names.

The root cause of the confusion is the rebranding of Datorama Reports as Intelligence Reports for Engagement, which has not been fully reflected in all areas of the Marketing Cloud platform.

Best Practices for Navigating the Changes

To navigate the changes in Datorama Reports, we recommend the following best practices:

Checklist for Navigating the Changes

• Review the official Salesforce documentation for Intelligence Reports for Engagement
• Update any documentation or training materials to reflect the new naming convention
• Verify that your workflows and processes are compatible with the new naming convention
• Test any integrations with Journey Builder or other features to ensure they are working correctly
• Reach out to Salesforce support if you have any questions or concerns about the changes

Frequently Asked Questions

What is the difference between Datorama Reports and Intelligence Reports for Engagement?

Datorama Reports have been rebranded as Intelligence Reports for Engagement, with the same functionality and features.

Will the old name still be used in the system?

Yes, the old name may still be used in some areas of the system, but the official documentation and support will reference the new name.

How do I update my workflows to reflect the new naming convention?

You can update your workflows by reviewing the official documentation and verifying that your processes are compatible with the new naming convention.

What if I have questions or concerns about the changes?

You can reach out to Salesforce support for assistance with any questions or concerns you may have.