2022 Customer Journey Analytics release notes
November 2022 nov22
mvvar1
- mvvar3
will no longer be automatically lowercased. Instead, data passed through the Analytics source connector to Adobe Experience Platform and Customer Journey Analytics will reflect the original case that was passed in from the page. Source Connector and Customer Journey Analytics columns _experience.analytics.customDimensions.lists.list1.list[]
- _experience.analytics.customDimensions.lists.list3.list[]
are impacted by this change.Fixes
- Fixed an issue where recent MacOS versions were incorrectly named as “Macintosh”. With this fix, the OS dimension will begin using “MacOS” version numbering, starting with MacOS 11. (AN-301834)
Other Fixes
AN-302367; AN-302562; AN-304036
Important notices for Customer Journey Analytics Administrators
Adobe’s vendor for IP lookups, Digital Element, is upgrading to a new improved dataset (NetAcuity Pulse) for IP-to-geolocation mapping. Adobe Analytics has postponed the adoption of this new dataset to January 11, 2023. The new database will be more accurate than previous versions. Some IP-to-geo mappings will change/improve when the new database is adopted.
Customer Journey Analytics data provided through the Analytics source connector will also automatically take advantage of the new mappings.
October 2022 oct2022
mvvar1
- mvvar3
will no longer be automatically lowercased. Instead, data passed through the Analytics source connector to Adobe Experience Platform and Customer Journey Analytics will reflect the original case that was passed in from the page.Important notices for Customer Journey Analytics Administrators
Adobe’s vendor for IP lookups, Digital Element, is upgrading to a new improved dataset (NetAcuity Pulse) for IP-to-geolocation mapping. Adobe Analytics has postponed the adoption of this new dataset to January of 2023. The new database will be more accurate than previous versions. Some IP-to-geo mappings will change/improve when the new database is adopted.
Customer Journey Analytics data provided through the Analytics source connector will also automatically take advantage of the new mappings.
September 2022 sep2022
Fixes
AN-298412
Important notices for Customer Journey Analytics Administrators
Adobe’s vendor for IP lookups, Digital Element, is upgrading to a new improved dataset (NetAcuity Pulse) for IP-to-geolocation mapping. Adobe Analytics will adopt this new dataset on October 5, 2022. The new database will be more accurate than previous versions. Some IP-to-geo mappings will change/improve when the new database is adopted.
Customer Journey Analytics data provided through the Analytics source connector will also automatically take advantage of the new mappings.
August 2022 aug22
July 2022 jul22
June 2022 jun22
May 2022 may22
April 2022 apr22
The Analytics source connector is now integrated with the Data Prep capabilities provided by Adobe Experience Platform. Adobe Real-Time Customer Data Platform (RTCDP), Customer Journey Analytics and Adobe Journey Optimizer customers can now extend the Analytics field group with additional field groups. They can also leverage 100+ Data Prep operators to enrich the Analytics data during ingestion into Adobe Experience Platform. RTCDP Customers can now enable multiple Data Prep-enabled report suites for Profile.
Customer Journey Analytics customers who ingest multiple report suites via the Analytics source connector now have a means to deconflict column differences between report suites. For example, if “Search Term” is stored in eVar1
in one report suite and in eVar2
in another report suite, using Data Prep you can extend the Analytics field group with a new column that merges the values from the two eVars.
March 2022 mar22
Fixes
- Fixed a console error when accessing Customer Journey Analytics from the Experience Cloud homepage. (AN-281468)
February 2022 feb2022
January 2022 jan2022
personID
(or customerID
, or whatever ID you are using for merging datasets in a connection) as a dimension in data views. This enhancement makes it easier for you to include the personID
as a dimension in your data view by pulling it in from the connection. Learn more