Version 9.6

• Support SameSite in the uuidCookie
• Update Visitor to latest version in tests

Version 9.5

Updating submitUniversalAnalytics method to match with Google Analytics Tracker Object (DIL.modules.GA).

Version 9.4

CORE-40964 Enabling Chrome SameSite Flags Provokes Errors with DIL.create

When DIL and Visitor were in a third party iframe, a problem arose in DIL instantiation due to Chrome's SameSite=True;secure requirements for cookies. This problem has been fixed.

Version 9.3

CORE-31926 Add a config to enable/disable logging
CORE-31927 Add a config to enable/disable URL & Cookie destinations

DIL has three new configs, which are optional and default to true if not specified: enableLogging, enableUrlDestinations, enableCookieDestinations.

// Client side DIL
var dilInstance = DIL.create({
...,
enableLogging: true,
enableUrlDestinations: true,
enableCookieDestinations: true
};

// Server side forwarding
s.AudienceManagement.setup…({
...,
enableLogging: true,
enableUrlDestinations: true,
enableCookieDestinations: true
});

With enableLogging set to true, messages will be output to the developer console. Whether enableLogging is set to true or false, messages will also be placed in the dilInstance.log array.

dilInstance's initialization configs can be inspected in dilInstance.initConfig .

Version 9.2

CORE-29099 Launch property is throwing console warning with visitorAPI version 4.1+

CORE-28582 Multiple issues reported for DIL version 9.1 and visitor API version 4.1

DIL has a more stable way of determining which version of `visitor.publishDestinations' to use. There is also a new config for enabling h_referer to be passed in the /event call (defaults to true):

// Client side DIL
var dilInstance = DIL.create({
...,
enableHrefererParam: false // don't send h_referer
};

// Server side forwarding
// Does not apply

Version 9.1

CORE-23693 [DIL] Change the way we call visitor.publishDestinations

DIL has a new way of calling `visitor.publishDestinations' (v2) of Visitor v4.1.0+. For Visitor v3.3.0 to v4.0.0, DIL continues to use v1. For v2, DIL supports firing URL destinations on page (as opposed to just in the iframe) through Visitor, which is toggled in the AAM customer portal. This functionality allows the referrer information of the current page to be exposed if desired.

Version 9.0

CORE-18876 [DIL] Wait for Opt In approval before firing event calls

CORE-19519 [DIL] Should automatically send the URL of the page in the h_referer signal

CORE-21404 [IAB] Implement IAB plugin in DIL

DIL refers to the window.adobe.optIn object to determine if it has user's consent for IAB or Opt in data read/write.

DIL sends the URL of the page on a new signal called h_referer. This h_referer will override the header referrer value. Additionally, it adds d_dil_ver= to the /event calls.

Version 8.1

CORE-24189 DIL 8.0 code no longer accepted by Google Tag Manager due to stricter security policy

DIL is now compliant with stricter security policies regarding using equivalents of eval. This version is only available from DTM and as standalone code, not Launch or AppMeasurement Audience Management Module. Future versions will include this change.

Version 8.0

• Remove shared features with ID Service from library.

DIL now has a hard dependency on Visitor 3.3+. It relies on ID Service to fire ID syncs and URL destinations. It will throw an error if Visitor is missing/old/not configured. ID Service is configured with the following:

// Client side DIL
var dilInstance = DIL.create({
    ...,
    visitorService:{
      namespace: "INSERT-EXPERIENCE-CLOUD-ORGANIZATION-ID-HERE"
    }
  };
   
  // Server side forwarding
  aamModule.setup…({
    ...,
    visitorService:{
      namespace: "INSERT-EXPERIENCE-CLOUD-ORGANIZATION-ID-HERE"
    }
});