2015 Release Notes
Release notes and updates for 2015.
Version 1.5.3
November, 2015
The Children’s Online Privacy Protection Act (COPPA) prohibits online collection of personal information from children under 13 years old without verifiable parental consent. Customers concerned about COPPA can add an optional variable to their Experience Cloud ID service code that prevents it from setting cookies in the third-party domain of a browser. See COPPA Support in the Experience Cloud Identity Service. For version 1.5.3 or greater.
Version 1.5.2
September, 2015
- Fixed a bug in the Safari browser that prevented synchronization services from functioning when users blocked third-party cookies. (AAM-20764)
- Calls to the ID service now include the version ID in the
d_visid_ver=parameter. The returned ID helps internal teams with troubleshooting and support issues. (AAM-20824)
Version 1.5.1
August, 2015
-
Fixed a bug to prevent the ID service from requesting an iframe if there’s no data to synchronize or fire. (AAM-20164)
-
Fixed a bug that prevented the ID service from properly setting a multi-part, top-level domain cookie. For example, if you have a domain like
my_company.co.uk, under some circumstances, the ID service would set a cookie inco.ukonly. (AN-104683)This only affected a few clients that met all of the following criteria:
-
Using the ID service.
-
Enabled a grace periodor are using first-party cookies and users block third-party cookies.
-
Have pages with multi-part, top-level domains.
-
Documentation revisions in this release include:
- API Methods and Code Library: Reorganized content and text. In most cases, each method gets its own page.
- Requirements for the Experience Cloud Identity Service: Revised content and reorganized text.
Version 1.5
July, 2015
The Experience Cloud ID service supports multiple IDs and authentication states. This change also removes deprecated support for Audience Manager DPID mappings to user IDs used by the setCustomerIDs function. See Customer IDs and Authentication States
Version 1.4
May, 2015
As of version 1.4, the preferred method of setting configuration is passing in a config object in as the second parameter to the Visitor.getInstance function.
var visitor = Visitor.getInstance("016D5C175213CCA80A490D05@AdobeOrg",{
"loadTimeout":1000,
"trackingServer":"myco.sc.omtrdc.net",
"idSyncContainerID":80
});
See Experience Cloud.
Version 1.3.5
February, 2015
Fixed the handling of timeout on requests for AAM Blob and Location Hint. Now, on a timeout, the system will correctly leave those fields blank for the current page and make all callbacks. The timeout is treated as an error condition, so it will try again on the next page. (AN-94473, AN-94474)
Version 1.3.4
January, 2015
Reworked <head>/<body> tag finding for JSONP request <script> tag container, as well as the creation of the <script> tag to account for different DOM implementations (HTML vs XHTML) with possibly different case sensitivity settings. (AN-9355)