Show Menu
TOPICS×

2016 Release Notes

Feature releases, updates, or changes to the Experience Cloud Identity Service for 2016.
These changes are also captured in the Experience Cloud Release notes . See the previous release notes for older Experience Cloud announcements.

Version 1.10

November, 2016
Fixes and Improvements
  • Added instructions on how to implement the ID service in a server-side environment.
  • Added
    Visitor.overwriteCrossDomainMCIDAndAID
    , a boolean function that lets you overwrite the Experience Cloud and Analytics IDs on other domains that you own. See Overwrite Visitor ID .
  • Added
    TS = UTC
    timestamp as a property of the
    visitor.appendVisitorIDsTo
    function. The ID service uses the timestamp to determine if it should use the IDs in the redirect URL based on a 5-minute aging interval. See Append Visitor ID Function .
  • Added
    Visitor.getLocationHint,
    a new function that returns a region ID. See Get Region IDs (Location Hint) .
  • Added
    idSyncByURL
    and
    idSyncByDataSource
    , 2 functions that let you manually implement an ID sync in the Destination Publishing iFrame. See ID Synchronization by URL or Data Source .
  • Fixed a bug that blocked the AppMeasurement tracking call if
    disableThirdPartyCalls:true
    .
  • Fixed a bug that prevented the ID service from passing the Experience Cloud ID (MID) across different domains.

Version 1.9.0

October, 2016
Fixes and Improvements
  • Fixed a bug that passed Audience Manager unique user IDs (AAMUUIDs) as Experience Cloud IDs to the ID service.
  • If time-to-live (TTL) for an AMCV cookie has expired, the ID service will still return that information to the server as long as the cookie contains a Experience Cloud ID. After this call, the ID service makes an asynchronous call to update the cookie. This helps improve performance because the ID service doesn't have to wait for a server response. It can use existing AMCV cookie values and then request an update.
  • The ID service automatically synchronizes Experience Cloud IDs (MIDs) with Adobe Media Optimizer and other internal Adobe domains directly on the page. Automatic synchronization is enabled for all existing and new accounts. This helps improve match rates for Media Optimizer. Applies to VisitorAPI.js version 1.8, or higher. See also, Understanding ID Synchronization and Match Rates .
New and Revised Documentation

Version 1.8.0

September, 2016
Fixes and Improvements
Added
disableThirdPartyCalls
as an optional, Boolean flag you can set in the
Visitor.getInstance
function. When
disableThirdPartyCalls= true
, the ID service will not make calls to other domains. By default,
disableThirdPartyCalls= false
. See disableThirdPartyCalls .

Version 1.7.0

August, 2016
Fixes and Improvements
  • Added
    idSyncAttachIframeOnWindowLoad
    as an optional boolean flag you can set in the
    Visitor.getInstance
    function. When
    idSyncAttachIframeOnWindowLoad= true
    , the ID service loads the ID synchronization iFrame on window load. By default, the ID service loads the iFrame as fast as possible. This flag
    replaces
    idSyncAttachIframeASAP
    , which is deprecated. See Visitor.getInstance Function Variables .
  • Added functionality to support tracking Experience Cloud IDs across domains, native apps and hybrid apps to web transitions. See Append Visitor ID Helper Function .
  • Added functions to visitorAPI.js code that determine if the ID service has generated the visitor Experience Cloud ID client-side or server-side or if ID calls timed out. See Timeout Tracking Functions and Tracking Client-side Visitor ID Generation .
New and Revised Documentation
Known Issues
Customers using Audience Manager DIL code and visitorAPI.js code on the same page should set the DIL variable
secureDataCollection= false
. See secureDataCollection .

Version 1.6.0

July, 2016
Version 1.6.0 of the Experience Cloud ID service
requires
AppMeasurement for JavaScript version 1.6.2. If you upgrade to ID service version 1.6.0, please make sure you are using the right AppMeasurement code version.
Feature
Description
Cross-Origin Resource Sharing (CORS)
CORS allows browsers to request resources from a domain other than the current domain. The Experience Cloud Identity Service supports CORS standards to enable client side, cross-origin resource requests. The ID service reverts to JSONP requests on browsers that do not support CORS.
See:
Fixes and Improvements
  • Added a
    d_fieldgroup
    parameter to ID synchronization calls to
    dpm.demdex.net
    . This new parameter is used for internal troubleshooting and debugging purposes.
  • Added a title attribute to the ID service iFrame. An iFrame title helps screen readers provide page information to users who require assistance when interacting with online content. The iFrame title attribute is set to
    Adobe ID Syncing iFrame
    .
  • Added
    idSyncAttachIframeASAP: true
    as an optional flag you can set in the
    Visitor.getInstance
    function. When
    true
    , the ID service loads the ID synchronization iFrame as fast as possible. This is designed to help improve ID synchronization match rates. By default, the ID service loads the iFrame on window load. See Visitor.getInstance Function Variables .
  • Fixed a bug with a callback function that caused AppMeasurement to get stuck in an infinite loop.
  • Changed the default
    loadTimeout
    interval to 30,000 milliseconds (from 500 milliseconds). See Visitor.getInstance Function Variables .
New and Revised Documentation
New
Revised

Version 1.5.7

June, 2016
Feature
Description
Changes to the
iframe.sandbox
attribute
The iFrame is now set so that
iframe.sandbox='allow-scripts allow-same-origin';
.
Allowing only these 2 tokens helps improve security and provides the ID service with the basic functionality required for ID synchronization.
The sandbox attribute is not supported in Internet Explorer version 9 or earlier. For more information, see the Attributes section in this iFrame documentation .
Encoding the Experience Cloud ID (MID)
The ID service encodes the MID value returned from the server or when it's set by the
visitor.setMarketingCloudVisitorID()
function. For more information about the MID, see Cookies and the Experience Cloud ID .
Fixes
The visitor API no longer forces an extra re-synchronization call with Audience Manager when there is no legacy Analytics visitor ID.

Version 1.5.x

Version 1.5.4

March, 2016
Feature
Description
Opt-out support
The
Experience Cloud
ID service supports visitor opt-out requests.
Change ID synchronization interval
The
Experience Cloud ID
service now makes ID synchronization calls on every call to the data collection servers. Previously, the ID service made only 1 request on the first call to get a
Experience Cloud
ID.
Documentation Updates

Version 1.5.3

January, 2016
Documentation Updates
Topic
Description
Revised text. Customer IDs must be passed in as un-encoded values only. Encoding IDs will create double-encoded identifiers.