Documentation changes
This page lists significant changes made to the Adobe Target product documentation.
Updates
Date
Topic
Changes
December 3
Added prerelease notes for the upcoming Offers Library user interface update.
November 19
Added following important note to the “Adobe Experience Platform Web SDK __view__
scope optimization (October 22, 2024)” section:
- IMPORTANT: If you cannot complete your implementation review and resolve any issues by February 3, 2025, you can request a one-time, six-month extension. Ensure that your request is submitted by January 31, 2025. Adobe will review and decide on your request.
October 22
Added the following important information:
- Adobe Experience Platform Web SDK
__view__
scope optimization
October 14
Added release notes for the Target Standard/Premium 24.10.2 release.
Added important information about using the extension with Private Chrome Web Stores.
Added important information about using the extension with Private Chrome Web Stores.
September 11
Added following note under Specify roles and permissions:
To view activities in Target, users must be directly assigned to a workspace with at least the Observer role. Assignment through user groups alone is insufficient. It is generally recommended to grant users access to the default workspace.
August 1
Added following FAQ: “Can I manage Target UI-created visual offers using the Target APIs?”
June 3
Updated entire topic, including indicating that content from multiple Form-Based Experience Composer and VEC activities can deliver. Previously, only one activity from the form-based workflow could deliver. There is no longer a limit to the number of form-based activities that can deliver.
May 17
Added additional IP addresses that you can allowlist when using the Enhanced Experience Composer.
May 8
New article: Added information about the Target integration with Adobe Customer Journey Analytics.
April 30
Updated the list of IP addresses for Adobe’s server used for the EEC proxy to allowlist.
April 23
Added information explaining Google’s plan to start disabling extensions created using Manifest V2. Adobe recommends that customers move to the new Visual Editing Helper extension as soon as possible.
April 23
Updated the Important note at the top of the page explaining Google’s plan to start disabling extensions created using Manifest V2, which includes the extension documented in this article. Adobe recommends that customers move to the new Visual Editing Helper extension as soon as possible.
April 9
Updated the following section: “My page does not display in the VEC (VEC only).”
Added the following section: “Issues caused by CSS conflicts in the Visual Experience Composer.”
Updated the Considerations section.
March 22
Removed references to edge nodes 31 through 38 because this nodes no longer exist. Ensure that your allowlist is up to date.
New blog post describing what Google’s planned deprecation of third-party cookies means for your Adobe Target at.js implementation.
recommendation-more-help
3d9ad939-5908-4b30-aac1-a4ad253cd654