description | keywords | seo-description | seo-title | solution | title | uuid |
---|---|---|---|---|---|---|
New features and fixes in the Adobe Experience Cloud. |
release notes |
New features and fixes in the Adobe Experience Cloud. |
Release Notes - January 2018 |
Experience Cloud,Release Notes |
Release Notes - January 2018 |
8140299f-e530-40bf-bcc0-ba6a08b20f36 |
New features and fixes in the Adobe Experience Cloud.
Note
To be notified about the early release notes, subscribe to the Adobe Priority Product Update. The Priority Product Update is sent three to five business days prior to the release. Please check back at release time for updates. New information published after the release will be marked with the publication date.
Use Case | Date Published | Description |
---|---|---|
First-time Setup | October 18, 2017 | The first-time setup recipe walks you through the steps to get started using Experience Cloud solutions. |
Email Optimization | August 15, 2017 | The email marketing use case shows you how to implement an integrated email strategy with analytics, optimization, and campaign management. |
[!UICONTROL Mobile App Engagement] | June 1, 2017 | The mobile app engagement use case shows you how to integrate your mobile apps with the Adobe Experience Cloud to measure user engagement and deliver personalized experiences to your audiences. |
Digital Foundation | May 2017 | The Digital Foundation use case helps you implement a digital marketing platform with Analytics, optimization, and campaign management. |
Customer Intelligence | April 2017 | The Customer Intelligence use case shows you how to create a unified customer profile using multiple data sources, and how to use this profile to build actionable audiences. |
Release notes for the core services interface, including [!UICONTROL Assets], [!UICONTROL Feed], [!UICONTROL Notifications], [!UICONTROL People] core service, [!UICONTROL Mobile] Services, Launch, and Dynamic Tag Management. Also includes release information for Experience Cloud ID Service (Visitor API).
Improvements and fixes for the Experience Cloud ID service.
Release date: January 18, 2018
Item | Description |
---|---|
Update: January 17, 2018 Thread yielding for multiple ID sync requests |
Iframe For customers performing multiple ID syncs, due to continuous CPU computations happening, the UI gets blocked in some cases. We are introducing thread yielding to separate the ID sync requests by 100msec each. This change will improve performance for customers using Visitor 2.3.0+ and DIL 6.10+. |
Added the ability to disable third-party calls |
JavaScript - 3.0.0 Adobe renamed the following configurations to allow for disabling third-party sync calls.
|
Internet Explorer support |
The ID service no longer supports Internet Explorer 6, 7, 8, and 9. |
Update to getInstance documentation |
Added a warning to the Visitor function about not instantiating this function with var visitor = new Visitor . |
New features, updates, and fixes to [!UICONTROL Mobile] Services.
Release date: January 18, 2018
Fixes
- Beginning March 2018, Adobe [!DNL Target] workflows will not be available in Adobe [!UICONTROL Mobile] Services.
- Fixed a few issues with the PDF and CSV download of the reports.
See Adobe Mobile Services for product documentation. To see the release notes for previous releases, expand Previous Release Notes in the left pane.
Release date: January 18, 2018
Enhancements and new features released in Adobe [!DNL Analytics].
Product | Feature Name | Description |
---|---|---|
[!UICONTROL Analysis Workspace] |
||
More Freeform table filtering options |
These dimension filtering options have been added:
|
|
Copy & paste visualizations/panels across panels & projects |
You can now right-click and copy a visualization or panel, and then paste (insert) that copied element into another place within the project, or into a different project. You can use this capability to create building blocks (predefined visualizations/panels) that can be copied into other projects to get started more quickly, with data specific to your business. |
|
New Mobile templates for Messaging and Location |
Two new project templates have been added:
|
|
Column Resizing Improvement |
When resizing the left-most column, Workspace now maintains the width percentages of the rest of the columns (not simply adjust the next column width on the right). This change speeds up table creation for both analysis and sharing.
|
|
Display 400 rows in a table |
You can now display 400 rows in a table (up from 200), to allow for 365-day trends. |
|
Map Visualization support in PDF |
The Map visualization, introduced in October 2017, can now be rendered in PDF. |
|
Relative Intra-links when copying/saving-as project |
Previously, when you copied a project or used save as, all the intra-links saved in the project pointed to the original project, not the copied project. The intra-links are now relative to the project they live within, after you copy or save-as. |
|
Contribution Analysis: Token Notification |
If your company has a limited number of Contribution Analysis tokens, the Analysis Workspace UI now shows a notification when you consume a token. It lets you know how many tokens you have left. (Admin users: you can restrict who can use these tokens by editing your group permissions.) |
|
CSV files with multi-byte characters |
Emailed CSV files containing multi-byte characters can now be opened in MS Excel. | |
Changes to event#, eVar#, and prop# |
Event#, eVar#, and prop#, which were added to dimension names in the left rail (in 2017), will only appear when you search for the component. (Also applies to Virtual Report Suite builder.) |
|
Changes to None/Unspecified |
Changed how None/Unspecified works in Analysis Workspace so that it is consistent with [!UICONTROL Reports & Analytics], the Segment Builder, and the dimension values menu in [!UICONTROL Analysis Workspace]. This means that the value will show up as "Unspecified" instead of "None" in most projects in [!UICONTROL Analysis Workspace]. (AN-146879) |
|
Other Analytics |
||
Virtual Report Suites: Changes to Component Curation |
There is no longer a need to share curated components (segments, calculated metrics, date ranges). They will always be visible in Workspace if they are curated for the virtual report suite, even if they are not shared. |
|
Contribution Analysis: Increase in number of results |
We now display up to 50 results in Contribution Analysis (up from 10). |
|
Segment Builder: Added an Analysis Workspace product compatibility type |
In the Segment Builder , we added an Analysis Workspace product compatibility type. Segments with embedded date ranges will continue to operate differently in [!UICONTROL Analysis Workspace] versus [!UICONTROL Reports & Analytics]: In Workspace, a segment with an embedded date range overrides the panel date range. By contrast, [!UICONTROL Reports & Analytics] gives you the intersection of the report date range and the segment's embedded date range. |
Fixes and minor updates applied to Adobe Analytics interface tools and components ([!UICONTROL Analysis Workspace], [!UICONTROL Reports & Analytics], [!UICONTROL Report Builder], and so on).
Product | Fix or Update |
---|---|
Analysis Workspace |
|
Other Analytics |
|
Data Workbench |
Fixes and updates applied to [!DNL Analytics] administration tools, including implementation and developer (Web Services and SDKs).
Product / Feature | Update |
---|---|
Data Warehouse |
|
AppMeasurement (Legacy and Mobile SDKs) |
AppMeasurement for JavaScript JavaScript 2.7.0
AppMeasurement for Other Platforms See AppMeasurement Release History the following for a release history of AppMeasurement on the following platforms:
|
Important
Review the following table for important [!DNL Analytics] notices that may affect data collection, processing, APIs, product end-of-life, and so on.
Notice | Date Added or Updated | Description |
---|---|---|
User account linking |
October 26, 2017 |
Analytics users no longer need to manually link their accounts between the Experience Cloud and Analytics. Users can contact their Admin Console administrator to request Analytics access. |
User ID Migration to the Admin Console |
September 21, 2017 |
The Analytics user ID migration enables administrators to easily migrate user accounts from Analytics User Management to the Adobe Admin Console. After your users are migrated, they will have access to the solutions and core services available in the Experience Cloud. The migration is being rolled out to customers in phases beginning later this month. |
Notice for API Methods affected by the migration to the Admin Console. |
September 21, 2017 |
Adobe will phase out the Permissions and Company.GetLoginKey API methods as part of our effort to migrate user access and management to the Admin Console. All Analytics companies that currently use these methods will receive a pre-migration notification beginning March 31, 2018. After receiving this notification, administrators will have 30 days before their migration starts, and these methods will cease to work for your company. To prepare for this event, view the list of affected APIs, and learn what Adobe recommends, see Analytics Administration API 1.4 . |
Ad Hoc Analysis |
September 21, 2017 |
As of May 2018, Ad Hoc Analysis will support only Java 8 or higher. If you choose to run Ad Hoc Analysis on Java 7 after the May 2018 Maintenance Release, Adobe will no longer support your Ad Hoc Analysis implementation. Our .jar files are signed with a secure 256-bit encryption that is not supported by Java versions less than 1.7.0_76. This 256-bit certificate allows us to serve you with enhanced security. |
Bot Rules |
Sept. 21, 2017 |
We recommend defining no more than 500 bot rules per report suite. The user interface allows for 500 rules to be manually defined. After this limit is reached, rules need to be managed in bulk through the Import File and Export Bot Rules options. |
Calendar Events: Displaying top 20 most recent events |
September 21, 2017 |
To ensure optimal reporting performance, the 20 most recent calendar events will be displayed on trended and overtime graphs. |
geo_zip |
August 23, 2017 |
As of August 22, Adobe Analytics started determining geo_zip on all hits received during data collection. This update increases data accuracy, particularly for mobile devices. Previously, the geo_zip was set once per visit. Now, geo_zip can correctly change during the course of a visitor's visit. The geo_zip field is not used in reporting, but surfaces in Data Feeds. |
Geo Segmentation |
August 21, 2017 |
On August 22, Adobe Analytics enabled Geo Segmentation reports for all customers. This change is in anticipation of the upcoming removal of the geo segmentation settings in the Admin Console. |
Fixes, Enhancements, and Deprecations
- We added a limit of 50,000 on the number of Derived Signals you can use. Read more about Usage Limits.
- Fixed a bug in the Create / Edit Destinations page, where, on Safari browsers, the Segment Mappings buttons wouldn't respond. (AAM-33558)
- Fixed a bug in the Derived Signals page where, on Firefox browsers, the action buttons (Edit, Delete) wouldn't respond. (AAM-33573)
- Fixed a bug on Internet Explorer browsers. When trying to edit a destination from the view page, the Edit button wouldn't trigger an event. (AAM-33625)
- Fixed a bug in Profile Merge Rules on Internet Explorer 11 browsers, where the Authenticated Profile options would display incorrectly. (AAM-33628)
- Fixed a bug in Addressable Audiences on Internet Explorer 11 browsers, where the help modal would display incorrectly. (AAM-33631)
- Fixed an issue in Audience Lab where some customers would receive a 500 Error when attempting to download the CSV file with for conversion traits. (AAM-33775)
- Fixed an issue encountered when deleting segments using the Remove Selected button, where the segments weren't actually deleted. (AAM-33815)
- Fixed an issue reported by customers receiving an error when attempting to remove a segment mapping from the Google DBM destination. (AAM-34056)
- Fixed an issue where customers were unable to modify the operator in a trait rule without deleting the condition or using code view. (AAM-34112)
DIL Bug Fixes, Enhancements, and Deprecated Code
DIL is the API data collection code for [!DNL Audience Manager]. The January release increments DIL to version 7.
Important
DIL support for all Internet Explorer versions below 10 is deprecated and will be discontinued.
Refer to the Adobe Target Release Notes for the latest release information about the following products:
- [!DNL Target] Standard and Premium
- [!DNL Target] Classic
- [!DNL Recommendations] Classic
Adobe [!DNL Primetime] is a multiscreen TV platform that helps media companies create and monetize engaging, personalized viewing experiences.
[!DNL Adobe Campaign] provides an intuitive, automated way to deliver one-to-one messages across online and offline marketing channels. You can now anticipate what your clients want using experiences determined by their habits and preferences.
[!DNL Adobe Campaign] Standard 18.1 - Release date: Jan, 15 2018
Feature | Description |
---|---|
Reporting for Fatigue Management |
Reporting for Fatigue Management is a dedicated, configurable report displaying the impact fatigue rules have on deliveries across the Email, Push, SMS, and Direct Mail channels within a specified date range before send. With the added insight of being able to quickly see all conflicting campaigns in a single view, marketers are able to plan marketing campaigns according to set the fatigue rules more effectively, and prioritize communications. For more information, refer to the detailed documentation . |
Report sharing |
Report Sharing allows you to share your reports with Adobe Campaign users as an email attachment, and on an automated recurring basis. Users who receive recurring reports have the ability to unsubscribe from these communications via a dedicated link in each email. For more information, refer to the detailed documentation . |
Push improvements |
Push Message Preview - Preview push notifications on iOS and Android devices from within the push notification content editor to see exactly what your recipients will see before testing or executing the delivery. For more information, refer to the detailed documentation . Content Available - When apps are not opened over longer periods of time, their data can become outdated. This results in the data having to be updated or replaced at the moment a user finally opens the app, which can cause delays in using the app. With the added support of Content Available, Adobe Campaign users can wake up their app to refresh its data in the background when delivering a push notification, enabling greater consistency and control over a user's in-app experience. Mutable Content - With the added support of Mutable Content, Adobe Campaign users can now leverage their mobile app extensions to further modify the content or presentation of arriving push notifications sent from Adobe Campaign. For example, users can leverage Mutable Content to:
For more information on Content Available and Mutable Content, refer to the detailed documentation . |
Time-zone optimized deliveries |
Schedule recurring Email, SMS, and Push notifications to be delivered at a specific day and time in every recipients' time zone, ensuring that your messages are delivered at the right time without setting up multiple deliveries. For more information, refer to the detailed documentation . |
API Signal activity triggering |
It is now possible to trigger a signal activity for your workflows directly from Adobe Campaign Standard API. For more information, refer to the detailed documentation . |
For product documentation, see:
- Adobe Campaign Classic Release Notes
- Adobe Campaign Classic Documentation
- Adobe Campaign Standard Documentation
Adobe recommends customers with on-premise deployments to deploy the latest patches to ensure higher stability, security, and performance.
Title | Description | |
---|---|---|
Product releases |
AEM Assets Brand Portal 6.3.1 |
Brand Portal 6.3.1 delivers improved user experience, performance, new enhancements in metadata, search, reporting, and digital rights management.
|
AEM 6.3 Dynamic Media Feature Pack |
The AEM 6.3 Dynamic Media Feature Pack is now compatible with AEM 6.3.1.0.
|
|
AEM Desktop App 1.7 |
AEM Desktop App 1.7 focuses on improvements in stability and caching logic, better support for network proxy, and ability to clean up internal files after uninstallation.
|
|
Product maintenance |
AEM 6.3 Service Pack 1- Cumulative Fix Pack 2 |
AEM 6.3 SP1-CFP2 (6.3.1.2), released January 8, 2018, is an important update that includes key customer fixes and enhancements released since the general availability of AEM 6.3 in April, 2017.
|
Self-Help |
AEM upgrade documentation |
The AEM upgrade documentation has been improved and is available here: https://helpx.adobe.com/experience-manager/6-3/sites/deploying/user-guide.html . |
AEM Performance Guidelines |
You can find general guidelines on how to optimize the performance of your AEM deployment here: https://helpx.adobe.com/experience-manager/6-3/sites/deploying/using/performance-guidelines.html . |
|
AEM Oak Documentation and Best Practices |
See https://helpx.adobe.com/support/experience-manager/6-3/oak.html . |
|
KB: AEM 6.3 repository maintenance |
New KB article for an AEM 6.3 repository maintenance issue. |
|
KB: AEM replication |
New KB article for a replication loop issue. |
|
KB: AEM-Campaign |
New KB article for an AEM - Campaign synchronization issue. |
|
KB: AEM Cumulative Fix Pack |
New KB article for an AEM Cumulative Fix Pack deployment issue. |
|
KB: AEM asset renditions |
New KB article for generating asset renditions. |
- AEM 6.3 Learn & Support Home
- AEM 6.2 Learn & Support Home
- AEM 6.1 Documentation Home
- Older versions of AEM documentation
- Scene7 Publishing System Release Notes
- Livefyre release notes
New features, fixes, and updates to [!DNL Adobe Livefyre]. [!DNL Livefyre] offers a complete user-generated content offering, including social curation capabilities and on-site engagement applications.
See Livefyre Release Notes for the latest information. Updated: January 22, 2018, for January 20 release
Feature | Description |
---|---|
Portfolios |
For all advertisers, Google AdWords data for "Impression Share Lost due to Budget" is now used to auto-adjust campaign budgets in portfolios when the portfolio uses the "Auto adjust campaign budget limits" option and also to adjust bids. |
Bid Rules |
Bid rules have been migrated to the label classification architecture. You'll still create and edit bid rules from Optimization > Bid Rules. What has changed:
|
Search Advanced Campaign Management (ACM) |
Standard text ad fields are no longer editable in Bing Ads, Google AdWords, and Yahoo Japan inventory feed templates. In text ad templates, you now can add label classifications to the templates for individual ad variations. Add the classifications below the ad variation template on the Ads tab. In shopping ad templates, you can add label classifications to the product groups generated. Add the classifications from the Label Classifications tab. Label classifications for product groups are applied to the unit (most granular) level. |
Search Bulksheets and Search Campaigns Beta |
You can now assign label classifications to product groups from bulksheets. You also can assign them from the Product Groups view. |
Search Campaigns Beta |
You can now create and manage Bing shared sitelinks and assign them at the campaign levels. Both Bing and Google shared ad sitelinks are available under the "Extensions" section of the Campaigns Beta menu. The section includes a Sitelinks view, from which you can create sitelink text and settings, and an Associations view, which allows you to assign your sitelinks to the (Google only) accounts, campaigns, and (Google only) ad groups in whose ads you want them to appear. You can now assign your existing Bing Ads remarketing list targets as targets (but not exclusions) for Bing ad groups from the Audiences > Targets view. You can set bid adjustments and status for targets by editing the value in the Bid Adjustment and Status columns within the Audiences > Targets view. Impression, click, and cost data are available for Bing Ads dynamic search ad (DSA) targets at the target, ad group, and campaign levels. It's not available yet at the ad level. Caution: Revenue data is not yet available, and revenue data will be orphaned until attribution is available. Don't add campaigns with Bing DSA targets to optimized portfolios yet. Additional improvements include:
|
Reports |
A new basic report, the Bid Rule Report, is available. It includes cost, click, and (optionally) conversion data for one or more bid rules. By default, the data includes one row for each applicable bid rule for each time unit in the specified date range, and the rows are in ascending order first by bid rule and then by the bid rule start date. You can view data beginning with 13 December 2017. |