What's new in Acoustic Journey Analytics

Learn what's new in Acoustic Journey Analytics.

January 2020

View completed journey stages reports in the Journey stages report manager.

You can now view completed journey stages reports that are generated with the current configuration and past configurations. To view completed reports, open the Journey stages report manager by clicking Journey stages > Manage. The All tab shows all completed reports for the current configuration and past configurations, and the Current tab shows all completed reports for the current configuration. To see details about a report's duration period (and other configuration details), click the report info icon. To view a journey stages report, click the Report ID.

In earlier releases, you could see only the current day report. In this release, you can see past reports, including the most interesting reports when the duration is met.

Reconfigure the journey stages report after the report duration period expires.

Starting in this release, if you want a new journey stages report after the report duration period expires, you must reconfigure the report. For example, you might reconfigure the baseline or target metrics for the journey stages reports.

In earlier releases, the journey stages report continued processing after the duration period expired.

October 2019

The IBM Watson Customer Experience Analytics name is changing to Acoustic Analytics!

Journey analytics, which was also called IBM Watson Customer Experience Analytics, is changing to Acoustic Journey Analytics. Additional name changes include IBM Digital Analytics to Acoustic Digital Analytics, IBM Tealeaf on Cloud to Acoustic Experience Analytics (Tealeaf), and IBM Universal Behavior Exchange to Acoustic Exchange.

We are updating the UI to reflect the name changes.

In the Analytics navigation menu, you'll see Experience Analytics, Digital Analytics, and Exchange. Additionally, we renamed the Reports menu to Journey Analytics.

We even changed the loading IBM bee to an Acoustic blue spinner!

We made additional UI changes.

Here are some more UI changes:
  • In response to client feedback, we removed the Web and Mobile dashboards and are redesigning them for better style and usability. You'll see the improvements soon in a future release. In the meanwhile, you can access the same data by using Digital Analytics and Acoustic Experience Analytics (Tealeaf).

  • The Most traveled metric is temporarily removed from the Channel summary report. The paths in the Channel summary report are now sorted by unique customers in descending order. Also, when you create Journey reports, the Unique customers metric is the default for top journeys.

Holiday Readiness Program 2019

Bring it on, holidays! Be prepared for the upcoming holiday season with Acoustic’s new 2019 Holiday Readiness Program. Download our product-specific guidelines for recommendations to optimize peak program activity. To learn more and access our Holiday Readiness webinars, check out this blog post.

Our Support and Services team is available to help make your peak season successful. If you should need any assistance, please let us know how we can help.

For information on contacting Support and related processes, and links to sign up for outage notifications, check out our Acoustic Support Handbook.

Set time zones to be the same for your organization across the Acoustic Journey Analytics, Acoustic Digital Analytics, and Acoustic Experience Analytics (Tealeaf) applications.

You can configure time zones in Acoustic Journey Analytics and thus ensure consistent time zone reporting across your Acoustic Journey Analytics, Acoustic Digital Analytics, and Acoustic Experience Analytics (Tealeaf) applications. Neither the Digital Analytics application nor the Tealeaf application is set to GMT by default. Journey Analytics shows time zone information in the Administration page, which you can access by clicking Settings > Administration.

To configure time zones, contact Support.

We changed the name of the Mindset changed event icon to Stage migration.

In the previous release, journey stages replaced mindsets. In this release, we are renaming the Mindset changed event to Stage migration, the Original mindset attribute to Original stage, and the New mindset attribute Ito New stage.

Exclude specific journeys from journey reports.

Now, when you specify starting and ending touch points as part of creating a journey report, you can exclude journeys from reports by excluding events that the journeys contain.

For example, you might find that a journey report with a Add to Cart start touch point and an Cart Abandon end touch point is including users who made purchases in earlier sessions. In this case, you can exclude the Cart Purchase event to set up a journey report with the Cart Abandonment AND do NOT include Cart Purchase rule.

In a different example, you might define a journey report that targets cart abandoners who do NOT purchase in-store or online. In earlier releases, you set up this scenario by creating a report with a Cart Abandon start touch point, reviewing the report, and then saving audiences for journeys where no offline purchase occurred. Starting in this release, you can create a report with a Cart Abandon and NOT In-store Purchase rule.

Report building panel now shows report descriptions.

For example, if you add a description when creating a journey report, you can view the description later in the Journey report manager and in the Description field of the report building panel. You cannot edit the description.

Switch client IDs in flexible reports - in beta!

Users can now utilize multiple Digital Analytics client IDs when creating flexible reports. Simply select Flexible reporting in the navigation menu, click Switch Client ID, and then select a client ID. If you're in the Create window for flexible reporting, you can select Menu > Switch Client ID.

Now you're ready to drag and drop dimensions, metrics, and segments and see results on the fly! If you don't have access to flexible reports but want access, open a support ticket and request to participate in the beta.