AppMeasurement Release History

AppMeasurement Release History
AppMeasurement Release History
Contents
AppMeasurement Release History................................................................................3
AppMeasurement for JavaScript...................................................................................................................3
JavaScript H Code - Legacy.......................................................................................................................10
Flash-Flex...................................................................................................................................................21
iOS..............................................................................................................................................................26
Android.......................................................................................................................................................37
PhoneGap...................................................................................................................................................45
Windows 8.1 Universal App Store..............................................................................................................46
Windows Phone 8.......................................................................................................................................46
WinRT for Windows 8.................................................................................................................................47
Mac OS X...................................................................................................................................................48
Windows Silverlight, NET, IIS, XBOX..........................................................................................................49
Java............................................................................................................................................................51
BlackBerry..................................................................................................................................................51
Symbian......................................................................................................................................................52
PHP............................................................................................................................................................52
Contact and Legal Information....................................................................................53
ii
AppMeasurement Release History
AppMeasurement Release History
This section contains a release history for AppMeasurement libraries across web and mobile platforms.
The latest version of each library can be downloaded in Reports & Analytics > Admin Tools > Code Manager.
AppMeasurement for JavaScript
Cumulative release notes for AppMeasurement for JavaScript.
JavaScript 2.3.0
Release date: 07/20/2017
• Fixed bug where s.Util.getQueryParam was capturing #
• Added v6.10 of dil.js (AN-145701)
JavaScript 2.2.0
Release date: 06/08/2017
• Added support for multiple AppMeasurement instantiation order. (AN-138237)
• Inclusion of version 2.2.0 Visitor API. (AN-144042)
JavaScript 2.1.0
• Included latest version of dil.js (AN-140396)
• Added support for adobe_mc_ref parameter which overrides the page referrer. (AN-131920)
• Re-Included Visitor API 2.1.0. (AN-140873)
• Added mcorgid parameter. (AN-139586)
• Added cp (customerPerspective) parameter. (AN-140897)
JavaScript 2.0.0
Release date: 03/09/2017
• Moved to a new build process that requires a version number update to 2.0.0. (AN-137878)
• Moved mboxMCSDID handling into the correct section location where the tracking call is made. (AN-138483)
JavaScript 1.8.0
Release date: 01/19/2017
• Include VisitorAPI 2.0.0
• Re-sequenced function calls and checks so that the SDID is consumed after the abort check has completed.
(AN-134364)
• Added the following pre- and post-tracking call hooks. (AN-134567)
• s.registerPreTrackCallback
• s.registerPostTrackCallback
3
These functions take as parameters: the callback (a function), and the parameters to that function. For example:
s.registerPreTrackCallback(function(requestUrl,a,b,c) {
console.log("pre track callback");
console.dir(requestUrl); // Request URL
console.dir(a); // param1
console.dir(b); // param2
console.dir(c); // param3
}, "param1", "param2", "param3");
The callback is invoked with the requestUrl and any parameters passed in when the callback is registered.
This occurs either before or after the tracking call, depending on which method is used to register the callback.
The order in which these callbacks are called is not guaranteed. Callbacks registered in the pre function are
invoked after the final tracking URL is created. The post callbacks are called upon a successful tracking call
(if the tracking call fails, these functions are not called). Any callback registered with
registerPreTrackCallback do not affect the tracking call. Also, calling any of the tracking methods
in any registered callback is not recommended and could cause an infinite loop.
JavaScript 1.7.0
Updated: 11/10/2016
• Include Visitor API 1.10.1.
JavaScript version 1.7.0
Updated: 10/20/2016
• Update Audience Manager module with Demdex Integration Library (DIL) 6.6. (AN-132065)
• Inclusion of Visitor API 1.9.0. (AN-132072)
JavaScript version 1.7.0
Updated: 9/15/2016
• Update AppMeaurement Audience Manager Module with DIL 6.5 and Additional Configurations (AN-129411)
• Inclusion of Visitor API 1.8.0 (AN-129887)
JavaScript version 1.6.4
Updated: 8/18/2016
• Updated AppMeasurement to read and write AMCV cookies. (AN-127098)
• Inclusion of Visitor API 1.7.0.
Note: Also see the following release notes for JavaScript version 1.6.3, which includes updated
requirements for Marketing Cloud ID service.
JavaScript version 1.6.3
Updated: 8/4/2016
• Fixed an issue where AppMeasurement prematurely terminated request connections. (AN-126448)
Important: Version 1.6.0 of the Marketing Cloud ID service requires AppMeasurement for JavaScript
version 1.6.3 or higher. If you want to upgrade to version 1.6.0 of the Marketing Cloud ID service, please
make sure you are using AppMeasurement code verison 1.6.3 or higher.
4
AppMeasurement Release History
JavaScript version 1.6.2
Release Date: July 21, 2016
• Inclusion of Visitor API 1.6.0.
• Fixed an issue causing AppMeasurement to call the wrong obfuscated method in the Visitor API. (AN-126006)
• Fixed an issue causing the JavaScript error: "Attribute only valid on v:image". (AN-124009)
JavaScript version 1.6.1
Release date: June 16, 2016
Inclusion of Visitor API 1.5.7.
JavaScript version 1.6.1
Release Date: May 19, 2016
JavaScript version 1.5.6
• Inclusion of Visitor API 1.5.6
• Fixed the handling of link click tracking in Firefox that was not firing the complete event.
JavaScript version 1.6
Release Date: April 21, 2016
• The AppMeasurement Activity Map module has been integrated in the AppMeasurement standard module, so
that you only have to reference one .js file. Additionally, Activity Map tracking is activated by default.
(AN-112689)
• Fixed a truncation issue occurring with the order of query-string variables in AppMeasurement, so that
pageURLRest is last. (AN-114647)
JavaScript version 1.5.4
Release Date: March 17, 2016
• Inclusion of Visitor API 1.5.4
• Support for Visitor API 1.5.4+ opt-out
JavaScript Version 1.5.3
Release Date: January 21, 2016
• Fixed handling of Audience Manager module when POSTs are used for tracking calls. (AN-115381)
• Moved the rest of the page URL ("-g") to the end of the tracking request query string. (AN-114647)
JavaScript Version 1.5.2
Release Date: November 5, 2015
• Inclusion of Visitor API 1.5.3.
• Fixed detection of IE11 for URL Truncation 2047 (AN-114914)
JavaScript Version 1.5.1
Release Date: September 17, 2015
• Inclusion of Visitor API 1.5.2
5
JavaScript Version 1.5.1
Release Date: August 29, 2015
• Inclusion of Visitor API 1.5.1.
JavaScript Version 1.5.1
Release Date: July 16, 2015
• Updated Audience Manager module to use AAM DIL 6.2 - getCustomer IDs from VisitorAPI.js and pass them
in /event call to AAM. (AN-104978)
JavaScript Version 1.5
Release Date: June 18, 2015
• Support for Visitor API 1.5, which uses the getCustomerIDs method to gather Customer IDs and authenticated
state, and sends the IDs in with data collection requests.
• Fixed the creation of duplicate destinationing iframe in AudienceManagement module (DIL 6.1)
• Fixed the known issue described in release 1.4.5.
JavaScript Version 1.4.5
Release Date: May 21, 2015
Feature
Description
iOS Extension
Starting in iOS SDK version 4.5, a new iOS extension lets you collect usage data from your
Apple Watch Apps, Today Widgets, Photo Editing widgets, and all the other iOS extension
apps.
See iOS Extension Implementation.
Android Wearable Extension
Starting in Android SDK version 4.5, a new Android extension lets you collect data from your
Android Wearable app.
See Android Wearable Extension.
• Inclusion of Visitor API 1.4.
• Updated AudienceManagement module to use DIL version 6.0.
Known Issue
In the VisitorAPI / AppMeasurement Audience Manager Module integrations, there will be two destination
publishing iFrame requests made in IE6-9: //fast.<subdomain>.demdex.net/dest5.html and
//fast.<subdomain>.demdex.net/dest4.html. The correct behavior, as seen in other browsers, is
to only load //fast.<subdomain>.demdex.net/dest5.html.
JavaScript Version 1.4.4
Release Date: April 16, 2015
6
Feature
Description
Custom data with lifecycle
metrics
You can now include custom context data variables with lifecycle metrics.
AppMeasurement Release History
Feature
Description
Beacon tracking support in
PhoneGap
The trackBeacon and clearCurrentBeacon calls are now available in PhoneGap.
A minor fix to clear the light-server call profile ID after the trackLight call.
JavaScript Version 1.4.3
Release Date: February 19, 2015
• Made all handling of delayed tracking calls consistent, which fixes issues with backed-up variables during the
delay, such as the clicked object.
• Changed to not do automatic referrer tracking after the first tracking call so the 2nd, 3rd, etc tracking call
(usually link tracking) will not double-count the referrer when s.referrer was manually set before the first
tracking call.
• The distribution zip was updated to include Visitor API 1.3.5.
JavaScript Version 1.4.2
Release Date: January 15, 2015
• Fixed handling of WebKit prerender handling to prevent tracking of pre-rendered pages that are not viewed.
• The distribution zip was updated to include Visitor API 1.3.4 and an updated AudienceManagement module
that includes DIL version 5.5.
JavaScript Version 1.4.1
Release Date: September 18, 2014
• Added a tagContainerMarker variable that allows the implementation to specify up to 4 characters that
are appended to the version string along with an additional dash character delimiter. This is used by dynamic
tag management.
// JavaScript
s.tagContainerMarker = "D1.0";
// Data Collection request
//.../b/ss/myrsid/1/JS-1.4.1-D1.0/s43317392037311?...
The 4 characters are limited to characters that are allowed in URL file paths, such as alpha-numeric and period.
• On pages that are dual-tagged with H Code, fixed a loop that might occur during automatic link tracking
(download and exit) with when forced link tracking is enabled (default in Webkit browsers). Additionally,
added a general safeguard around automatic link tracking to prevent similar loops. This safeguard limits
automatic link tracking of repeated clicks to the same object to once every 10 seconds. This safeguard applies
only to automatic link tracking, so manual link tracking (s.tl) calls are not limited. Clicks to different objects
are also not impacted by this safeguard and will be tracked.
• Fixed handling of clicked object when a delay is needed.
• Fixed an issue that caused a double page-view count when s.t was called from a link onclick function, if the
Visitor API does not have the needed values yet.
• HTTP POST support.
Important: For an Analytics call to use the POST method instead of the GET method in
AppMeasurement (a method of solving truncated URLs in IE), you must be using the latest Visitor ID
Service implementation for Marketing Cloud.
7
JavaScript Version 1.4
Release Date: August 21, 2014
• Removed tracking of browser plug-ins (p query parameter) as plug-ins are no longer reported in version 15.
• Addition of the AudienceManagement Module in the download zip.
Added support for additional eVars (76 - 250) and events (101-1000).
Note: H-Code does not support the additional eVars and events.
JavaScript Version 1.3.2
Release Date: June 19, 2014
• Fixed handling of done and waiting flags for Visitor API fields such as the legacy Analytics Visitor ID, that
was causing errors.
• Support for new features in visitor ID service 1.3.
JavaScript Version 1.3.1
Release Date: May 22, 2014
• AppMeasurement for JavaScript s_gi function was not correctly finding instances created using H code s_gi.
Note that this issue only impacted some dual tagging implementations where AppMeasurement for JavaScript
and H code were on the same page with separate instances, and s_gi was being used to find instances by
report suite.
JavaScript Version 1.3
Release Date: April 17, 2014
• Support for the Marketing Cloud Visitor ID service.
JavaScript Version 1.2.4
Release Date: March 13, 2014
• Bug fixes for heartbeat video.
JavaScript Version 1.2.3
Release Date: February 20, 2014
• Bug fixes for heartbeat video.
JavaScript Version 1.2.2
Release Date: February 6, 2014
• Fixed a compatibility issue with the Audience Manager DIL module. Audience Manager customers must also
update to version 4.8 of the DIL module.
JavaScript Version 1.2.1
Release Date: November 15, 2013
• Fixed page events that are used for heartbeat video measurement.
8
AppMeasurement Release History
JavaScript Version 1.2
Release Date: November 14, 2013
• Added support for heartbeat video measurement.
• VisitorAPI.js was added to support Visitor ID Service.
JavaScript Version 1.1.1
• Prevented a link tracking call from being sent from Opera browsers for links that start with "opera:" ("opera:"
is similar to "about:" and "chrome:" in other browsers).
• Added alt="" to all Image objects to comply with Accessible Video and Communications Act.
JavaScript Version 1.1
Release Date: September 18, 2013
• Fixed support for placing the library and page code in the head tag.
• Added missing module onLoad support.
JavaScript Version 1.0.3
Release Date: August 15, 2013
• Added support for deployment through Adobe tag management.
• Fixed an issue that prevented hierarchy variables from being set on the AppMeasurement object.
JavaScript Version 1.0.2
Release Date: July 18, 2013
• The hash/fragment is now ignored by automatic link tracking. Previously the following URL was automatically
tracked since the entire href ended in .pdf:
<a href="index.htm#anchor.pdf">Test Link</a>
Now the hash/fragment is ignored so the link is tracked only when the filename ends in an extension that
matches.
JavaScript Version 1.0.1
Release Date: May 23, 2013
A new JavaScript AppMeasurement library is now available in Code Manager. This library provides the same
core functionality of s_code.js, but is lighter and faster for use on both mobile and desktop sites.
• 3-7x faster than the H.25 code.
• Only 21k uncompressed and 8k gzipped (H.25 code is 33k uncompressed and 13k gzipped).
• Native support to get query parameters, read and write cookies, and perform advanced link tracking.
• Small and fast enough to be used with mobile sites, and robust enough to be used on the full desktop web,
allowing you to leverage a single library across all web environments.
See AppMeasurement for Javascript in the Analytics Implementation Guide.
Note: Some plug-ins are not supported in this new version. See Plug-in Support for details.
9
JavaScript H Code - Legacy
Cumulative release notes for Legacy JavaScript H code.
Note: To find the current library version, use DigitalPulse Debugger.
Legacy JavaScript Version H.27.5 - Update
Release Date: June 16, 2016
Inclusion of Visitor API 1.5.7.
Legacy JavaScript Version H.25.5 - Update
Release Date: May 19, 2016
Inclusion of Visitor API 1.5.5.
Legacy JavaScript Version H.27.5 - Update
Release Date: November 5, 2015
• Inclusion of Visitor API 1.5.3.
Legacy JavaScript Version H.27.5 - Update
Release Date: September 17, 2015
• Inclusion of Visitor API 1.5.2.
Legacy JavaScript Version H.27.5 - Update
Release Date: August 20, 2015
• Inclusion of Visitor API 1.5.1.
Legacy JavaScript Version H.27.5 - Update
Release Date: June 18, 2015
• Inclusion of Visitor API 1.5.
Legacy JavaScript Version H.27.5 - Update
Release Date: May 21, 2015
• Inclusion of Visitor API 1.4
Legacy JavaScript Version H.27.5 - Update
Release Date: April 16, 2015
• Added Integrate module to s_code.js in legacy AppMeasurement for JavaScript H.X ZIP file. (AN-101001)
Legacy JavaScript Version H.27.5
Release Date: February 19th, 2015
10
AppMeasurement Release History
• Inclusion of Visitor API 1.3.5.
• Changed to not perform automatic referrer tracking after first tracking call, so the 2nd, 3rd, etc., tracking call
(usually link tracking) will not double count the referrer when s.referrer was manually set before the first
tracking call. (AN-92647)
Legacy JavaScript Version H.27.4 - Update
Release Date: January 15, 2015
• The distribution zip was updated to include Visitor API 1.3.4.
Release Date: September 18, 2014
• Added a tagContainerMarker variable that allows the implementation to specify up to 4 characters that
are appended to the version string along with an additional dash character delimiter. This is used by dynamic
tag management.
// JavaScript
s.tagContainerMarker = "D1.0";
// Data Collection request
//.../b/ss/myrsid/1/JS-1.4.1-D1.0/s43317392037311?...
H.27.3
Release Date: August 21, 2014
• Internal changes to support upcoming features.
H.27.2
Release Date: June 19, 2014
• Fixed handling of done and waiting flags for Visitor API fields such as the legacy Analytics Visitor ID, that
was causing errors.
• Support for new features in visitor ID service 1.3.
H.27.1
Release Date: June 11, 2014
• Fixed an issue in the Analytics for Target integration that caused some hits to incorrectly be merged.
H.27
Release Date: May 22, 2014
• Support for the Marketing Cloud Visitor ID service.
• Support for the Analytics for Target integration.
H.26.2
Release Date: October 17, 2013
• Added alt="" to all Image objects to comply with Accessible Video and Communications Act.
H.26.1
Release Date: July 18, 2013
11
• The hash/fragment is now ignored by automatic link tracking. Previously the following URL was automatically
tracked since the entire href ended in .pdf:
<a href="index.htm#anchor.pdf">Test Link</a>
Now the hash/fragment is ignored so the link is tracked only when the filename ends in an extension that
matches.
H.26
Release Date: April 29, 2013
• the useForcedLinkTracking option that is described in Manual Link Tracking Using Custom Link Code
now applies to Firefox 20+ (previously this applied to WebKit browsers only).
• Image object ID generation is now unique between instances. This prevents collisions when more than one
instance is on the same page.
H.25.5
Release Date: April 19, 2013
• Fixed an issue in forced link tracking that caused a JavaScript error on some Android 2.2 Devices.
• In video auto tracking on Windows Media Player, fixed an issue in scrubbing that caused time played to not
be tracked correctly.
H.25.4
Release Date: February 2013
• Changed automatic exit link tracking to always ignore links with HREF attributes that start with #, about:,
or javascript:.
• Refined scope of click events affected by useForcedLinkTracking. The automatic forced link tracking
applies only to:
• <A> and <AREA> tags
• The tag must have an HREF attribute
• The HREF can't start with #, about:, or javascript:
• The TARGET attribute must not be set, or the TARGET needs to refer to the current window (_self, _top,
or the value of window.name)
H.25.3
Release Date: January 2013
• Added support to send URLs longer than 255 bytes to support the expansion of the Page URL field in Adobe
Data Collection servers. Page URLs longer than 255 bytes are split, with the first 255 bytes appearing in the
g= parameter, with the remaining bytes appearing later in the query sting in the -g= query parameter. This
helps prevent long URLs from taking precedence over other data in the case of browser truncation, but still
enables capturing of long URLs.
• Fixed handling URL decoding for strings that are encoded with a mixed use of escape and
encodeURIComponent.
• Fixed an issue in WebKit browsers where link tracking fails if the first server call on the page times out.
• Added a new fallback visitor identification method. See Identifying Unique Visitors.
12
AppMeasurement Release History
• Added a new abort flag that can be set inside doPlugins. Setting this flag to true causes the
AppMeasurement library to not continue with that tracking call. The abort flag is reset with every tracking call,
so if a subsequent tracking call also needs to be aborted the flag will need to be set again inside doPlugins.
s.doPlugins = function(s) {
s.campaign = s.getQueryParam("cid");
if ((!s.campaign) && (!s.events)) {
s.abort = true;
}
};
This lets you centralize the logic you use to identify activity that you do not want to track, such as some custom
links or external links in display ads.
H25.2
Release Date: October 2012
• Added support for reporting an additional version number in the JavaScript version report. Previously this
version was limited to 2 characters (for example, 1.8). Support was added for a 3 character version number
(for example, 1.8.5).
• Fixed an issue with Tag Manager that prevented repeated values in Dependant Code blocks from being sent.
H.25.1
Release Date: September 2012
• Forced URL encoding for the following characters:
~
!
*
(
)
'
This resolves issues with un-escaped characters being stored in the ClickMaps_sq cookie.
• Fixed an issue that might cause the video complete event to not be sent when using a custom media.monitor
method that tracks the media close event:
If(media.event==”CLOSE”) {
…
}
H.25
Release Date: July 2012
Made an update to ensure that link tracking completes successfully on WebKit browsers (Safari and Chrome).
After this update, download and exit links that are automatically tracked (determined by
s.trackDownloadLinks and s.trackExternalLinks) are tracked successfully. If you are tracking
custom links using manual JavaScript calls, you need to modify how these calls are made.
For example, exit and download links are often tracked using code similar to the following:
<a href="http://anothersite.com" onclick="s.tl(this,'o','link name',null)">
FireFox and Internet Explorer execute the track link call and open the new page. However, WebKit browsers
might cancel execution of the track link call when the new page opens. This often prevents track link calls from
completing when using WebKit browsers.
13
To workaround this behavior, H.25 includes an overloaded track link method (s.tl) that forces WebKit browsers
to wait for the track link call to complete. This new method executes the track link call and then handles the
navigation event, instead of using the default browser action. This overloaded method requires an additional
parameter, called doneAction, to specify the action to take when the link tracking call completes.
To use this new method, update calls to s.tl with an additional doneAction parameter, similar to the
following:
<a href="http://anothersite.com" onclick="s.tl(this,'o','link
name',null,'navigate');return false">
Passing 'navigate' as the doneAction mirrors the default browser behavior and opens the URL specified by
the href attribute when the tracking call completes.
The following table summarizes the configuration variables and updates made to H.25 to support this functionality.
Variable
Description
useForcedLinkTracking
This flag is used to disable forced link tracking for WebKit browsers. Forced link tracking is enabled
by default for WebKit browsers and is ignored by other browsers.
Default Value
true
Example
s.useForcedLinkTracking = false
forcedLinkTrackingTimeout
The maximum number of milliseconds to wait for tracking to finish before performing the
doneAction that was passed into s.tl. This value specifies the maximum wait time. If the
track link call completes before this timeout the doneAction is executed immediately. If you
notice that track link calls are not completing you might need to increase this timeout.
Default Value
250
Example
s.forcedLinkTrackingTimeout = 500
trackLink (s.tl)
Tracks exit, download, and custom links. Provides an optional parameter to specify a navigation action
to execute after the track link call completes on WebKit browsers.
Syntax
s.tl(linkObject,linkType,linkName,variableOverrides,doneAction)
doneAction: (optional) Specifies the action to take after the link track call is sent or has timed out
(based on the value specified by s.forcedLinkTrackingTimeout). The
doneAction can be the string 'navigate', which causes the method to set
document.location to the href attribute of linkObject. The doneAction
can also be a function allowing for advanced customization.
If providing a value for doneAction in an anchor onclick event, you must return false
after the s.tl call to prevent the default browser navigation.
To mirror the default behavior and follow the URL specified by the href attribute, provide a string
of 'navigate' as the doneAction.
14
AppMeasurement Release History
Variable
Description
Optionally, you can provide your own function to handle the navigation event by passing this function
as the doneAction.
Examples
<a href="..."
onclick="s.tl(this,'o','MyLink',null,'navigate');return
false">Click Here</a>
<a href="#"
onclick="s.tl(this,'o','MyLink',null,function(){if(confirm('Proceed?'))document.location=...});return
false">Click Here</a>
H.24.4
Release Date: April 2012
This update is recommended for all customers.
• Made an enhancement to detect when a page is prerendered using Google Chrome Prerender
(https://developers.google.com/chrome/whitepapers/prerender). Since Prerender loads and executes JavaScript
and other code, this could result in page views being sent before a user clicks to visit your site. The JavaScript
library now waits until the user visits your site before sending server calls for these prerendered pages.
• Added the timestamp variable to the JavaScript library for customers who want to customize timestamp
data similar to other AppMeasurement libraries.
s.timestamp=Math.round((new Date()).getTime()/1000);
s.timestamp="2012-04-20T12:49:31-0700";
H.24.3
Release Date: February 2012
• Fixed an issue that caused extra data to be included in the image request for customers using Javascript
Object.prototype overrides. All Object.prototype usage is now skipped when handling context
data variables.
• Fixed an issue that caused the pe query parameter to be passed twice with the same value in some circumstances.
• Fix to ClickMap tracking in JavaScript to ignore clicks to the body tag, even when the tag has an onClick
event handler.
• Added time stamp to variables used with light tracking calls (trackLight).
H.24.2
Release Date: January 2012
• Updated video tracking with a new method to track complete video views. See Measuring Video in SiteCatalyst.
• Fixed an issue that caused an "Attribute only valid on v:image" JavaScript error for OnClick events on VML
elements in IE.
• Fixed a bug where context data variables were not included in link server calls, despite being referenced in
linkTrackVars. Context data variables are used with Processing Rules.
H.24.1
Release Date: November 2011
• Updated video tracking to combine hits for segments and milestones that occur at the same time.
15
H.24
Release Date: November 2011
• Internal updates to support Adobe Tag Manager.
H.23.9
Release Date: November 2011
• Internal updates to support Adobe Tag Manager.
H.23.8
Release Date: October 2011
• Fixed an issue that caused the linkTrackVars=none and linkTrackEvents=none settings to not
apply when using automatic exit link tracking. These settings now apply for automatic exit links so that props,
eVars, and events are not sent in with the exit link image request.
H.23.7
Release Date: September 2011
• Removed border attributes from image tags on mobile devices to comply with Wireless Markup Language
(WML) standards. This fixes rendering issues on some mobile devices.
H.23.6
Release Date: August 2011
Fixed accuracy of percentage measurements in video tracking.
H.23.5
Release Date: July 2011
• Added support for Adobe Tag Manager.
H.23.4
Release Date: June 2011
• Fixed an issue that caused JavaScript errors when accessing certain properties of Vector Markup Language
(VML) shape elements.
• Referral strings that are over 255 characters are now truncated by shortening the path rather than the query
string. This fixes issues were query string parameters were truncated and not collected.
H.23.3
Release Date: May 2011
• Fixed an issue that prevented the video tracking (pev3) variable from being sent.
• Fixed an issue that prevented the s_gi call from enabling code to be compatible with both G and H code.
When you pass a 1 as the second parameter to this call the code is now configured to be compatible with both
versions.
H.23.2 - SiteCatalyst 15
Release Date: April 2011
16
AppMeasurement Release History
• Support for contextData that drives server-side processing rules (v15 only).
• Support for light server calls (v15 only).
• Support for assigning a value other than 1 to a counter event in the events list.
• Support for new method of tracking video using conversion eVars and events (currently in beta).
• Removed support for setting Media.trackWhilePlaying to false. It will always be true.
• Added debugTracking flag to enable logging of requests send to Firebug console just like the other platforms.
• Make sure "+" is always URL-encoded regardless of browser.
Pre-SiteCatalyst 15
H.22.1
• Added ability to disable partners in the Integrate module and externaly force a delay on tracking.
• Fixed IE URL length check to always truncate to 2047 characters.
H.22
• Added support for 25 more props and eVars.
• Fixed issue with doPlugins being called more than once for the same tracking call.
• Fixed issue with 1/2 second delay durring video tracking.
H.21.1
• Changed URL encoding and decoding to start using encodeURIConponent and decodeURIComponent when
availible. If this new method is used and s.charSet is set s.charSet will be forced to UTF-8.
• Changed the formatting of the query-string for ClickMap data to take care of a bug with multi-suite tagging
and using the back button.
H.21
• Reworked support for cloning instance for exit surveys.
• Added ClickMap support for button elements.
H.20.3
• Reorder query-string variables in Google referrers to keep "q", "ie", "start", "search_key", "word", "kw", and
"cd" the start of the query-string to try and prevent truncation of these variables.
H.20.2
• Rolled back YouTube support to separate the media changes and core JavaScript code changes.
• Reworked loading of external modules to work in all browsers and support timing out in all browsers.
• Added cleaning of tracking server prefix (visitor namespace or first repiort suite ID) to fix SSL cert matching
and prevent messing with the tracking server.
• Made JavaScript code compression optional.
H.20.1
• Minor enhancements to module system to handle modules requesting JSON objects better.
• New partner integration module.
H.20
• Huge speed improvements in core JavaScript code.
• Media autotrack support for embeded YouTube video players.
17
H.19.4
• Fixed double URL-encoding with media tracking.
H.19.3
• New "track while playing" media changes. Turn this on by setting s.Media.trackWhilePlaying to true. You can
set s.Media.trackSeconds to track after every X seconds have passed. You can set s.Media.trackMilestones to
a list of percentages within the media item to track after they have passed. You can call s.Media.track() to track
the state of the media item now along with any other variables you have set and are in s.Media.trackVars and/or
s.Media.trackEvents. Lastly you can setup a s.Media.monitor method that will be called every 5 seconds with
the state of the media item so you can make more exact decisions for when to call s.Media.track().
H.18
• Added s.trackingServerBase variable that will allow a client to start using omtrdc.net instead of 2o7.net.
• Changed s.dc to expect "d1" and "d2" instead of 112 and 122 to support the new tracking domain design.
• Changed s.vmk to s.visitorMigrationKey and added s.visitorMigrationServer and s.visitorMigrationServerSecure
to allow for greater control over visitor migration.
H.17
• Change query-string truncation detection keys.
• Support for s.mobile flag to prefer mobile visitor identification.
H.16
• Automatic building of the page referrer will only happen with the first tracking call on the page. Manualy
setting the referrer must be done with every tracking call because it is cleared once the tracking request is sent
off.
• Fixed truncation of numbers to take care of Netscape 4 crash.
• Links with HREF starting with # will not be counted as an exit link.
• Support for s.dynamicVariablePrefix.
H.15
• Implemented new module system. Most new major functionality will be implemented as modules. All plugins
and universal tag plugins will be migrated to modules.
• Addition of media tracking module. A new cookie s_br was created to support media tracking.
• Addition of survey module.
• You can now pass in a JavaScript object as the first argument to s.t() and the fourth argument to s.tl() to give
one time variables overrides. This will help implementations with more AJAX heavy sites.
• Reworked code to remove use of eval().
• Reworked older browser code rewriting functions so they can be used my module system to add support for
older browsers.
• G to H migration functions are not defined until an instance of the tracking class is created.
• Code is now formatted differently as a result of development time savers added to the code generator and to
make the code less scary.
H.14
• Fixed JavaScript error caused by image onload firing after page has been left (tracking onunload).
• Changed ClickMap tracking to detect and ignore SHAPE objects.
18
AppMeasurement Release History
• Fixed problem with G to H migration functions.
• Added visitor sampling and dynamic account selection config variables to those that are pulled in for G to H
migration.
• Global G to H migration functions are only defined if migration is turned on.
H.13
• purchaseID is not controlled by linkTrackVars.
• ClickMap cookie handling fixed for customers adding prototypes to the base Object class.
• G to H migration will now declare the global versions of variables as blank if they are undefined.
• G to H migration will now pull in linkTrackVars and linkTrackEvents from the old globals.
• Fixed bug in calling Universal Tag method si() multiple times.
H.12
• Screen resolution tracking is fixed.
H.11
• Most of the JavaScript code is compressed now.
• Additional tracking requests for the same instance are queued up until the first finishes.
• Each request is sent with a different image object to avoid clobbering the last one.
• Fixed handling of HREFs in some browsers where the toString method does not give you a full URL.
• Added technology variables
(s.resolution,s.colorDepth,s.javascriptVersion,s.javaEnabled,s.cookiesEnabled,s.browserWidth,s.browserHeight,s.connectionType,s.homepage,s.plugins)
that can be read by plugins.
• Fixed bug in finding an already created instance for a report suite.
• All of the global functions besides s_gi() are defined compressed or uncompressed in strings in s_gi().
H.10
• Added support for setting s.charSet="Auto". This will try and automaticaly handle different character sets by
doing the URL encoding by hand instead of letting the JavaScript engine do it using escape(). The URL encoding
will use the %u#### syntax for characters above 127. This will only work in newer browsers that have the
String.charCodeAt method. All older browsers will just pass in ISO8859-1 as s.charSet and let the browser
URL encode the strings which could cause broken strings to show up in the reports if they are using something
other than ISO8859-1 and have visitors with older browsers.
• Added transactionID variable.
• The code will nolonger document.write() out an "anchor" image on the page to keep setting the source of. The
code will only use dynamic image objects.
• Custom s.pageURL and s.referrer will not be truncated to 255 characters.
• JavaScript version is now based on checks for new functionality added in each version of JavaScript defaulting
to 1.0 and checking up to 1.7. Previously the check was only based on navigator.appVersion and
navigator.userAgent which are nolonger enough to figure out the JavaScript version.
• New G.X compatibility functions are now in the code. These functions are s_co(), s_gs(), and s_dc().
• IE ActiveX use to detect homepage and connection type are not wrapped up in error catching to avoid JavaScript
errors when ActiveX is turned off.
H.9
• Reworked Universal Tag (Partner Plugins) event listening to be consistent between browsers.
19
• Added new variables (dc, trackingServer, & trackingServerSecure) to control the tracking server.
• Added new variable visitorID to allow customers to pass in their own visitor IDs.
• Reworked how existing instances are found in s_gi() to work better with dynamic account selection and
multi-suite tagging. The instance returned is nolonger a copy.
• Added a new s.sa() method to change the account(s) to use for the instance.
H.8
• Added Universal Tag (Partner Plugins) support.
H.7
• Added check to make sure cookie domain has atleast one period in it before using.
H.6
• Changed to also use an image object to make requests if ss is set because instances with ss set have not created
an anchor and done the checks to set ios.
• Changed to use a fake target if the "clicked" object is not something we would normaly track clicks for to turn
off the 1/2 second delay.
H.5
• Changed cookie setting to always set a domain even if it ends up being the full hostname. This takes care of
Firefox differentiating between no domain and using the full hostname.
H.4
• Body onclick will now validate the clicked object before trying to track it. VML objects will not pass this
validation so they will be ignored.
• Addition of variableProvider variable to be used for DFA integration.
H.3
• Enabled link tracking for Opera version 7 and up now that it supports image objects.
• Changed error trapping to use try-catch for all version 5 and up browsers.
• Changed when anchor image is added to the document so it supports dynamic account selection.
• Added support for fpCookieDomainPeriods variable which if set will be used instead of cookieDomainPeriods
to build the first-party cookie domain.
• Changed gv() method to be a little more warning friendly in Firefox strict mode even thoug it does not matter.
H.2
• Addition of vmk to control visitor migration from 2O7.net to a CNAME.
H.1
• Made URL-encoding smarter by detecting how characters between 128 and 255 will be encoded. This may
change the character-set passed along or cause a special unicode character to be tacked onto the end of some
variables.
• Made a couple changes to the tracking method that is called to track the page view and every click to speed it
up when the click does not need to be tracked right away or not at all.
• Fixed handling of linkTrackEvents for events that have a unique ID.
20
AppMeasurement Release History
Flash-Flex
Cumulative release notes for Flash. Flash apps using ActionScript can be measured on the desktop and on the
web.
Note: To find the current library version, turn on debug logging.
April 20, 2017
Version 4.0.3
• Inclusion of Visitor API 1.6.1.
August 18, 2016
Flash 4.0.2 - Update
Inclusion of Visitor API 1.6.0.
May 19, 2016
Flash 4.0.1 - Update
Inclusion of Visitor API 1.5.6
April 21, 2016
Adobe has released a security update APSB16-13 for the AppMeasurement for Flash library. This update resolves
an important vulnerability in the library, applicable only when debugTracking is enabled, that could be
abused to conduct DOM-based XSS attacks.
Important: This issue affects AppMeasurement for Flash only when debugTracking has been enabled
(debugTracking is disabled in the default configuration). If affected, we strongly advise you to
disable debugTracking immediately. Here is some sample code:
public var s:AppMeasurement;
s = new AppMeasurement();
s.debugTracking = false; // set to false or remove line
// for default "disabled” behavior
Affected versions are AppMeasurement for Flash version 4.0 and earlier on all platforms.
Note: Due to security reasons, we will no longer be distributing an AS2 version of AppMeasurement for
Flash. We will continue to support data collection from existing AS2-based projects. However, we highly
recommend that customers upgrade their implementations to AS3 and incorporate the latest security
features of AppMeasurement for Flash.
AppMeasurement for Flash customers affected by this issue must rebuild projects with the updated library
available for download from the Analytics Console More… (AN-121780)
November 5, 2015
Flash Version 4.0 - Update:
21
• Inclusion of Visitor API 1.5.3.
September 17, 2015
Flash Version 4.0 - Update:
• Inclusion of Visitor API 1.5.2.
August 20, 2015
Fash Version 4.0 - Update:
• Inclusion of Visitor API 1.5.1.
June 18, 2015
Flash Version 4.0 - Update
• Inclusion of Visitor API 1.5.
• Use Visitor API 1.5+ getCustomerIDs method to gather Customer IDs and Authenticated State, and send them
in with data collection requests (AN-102131)
May 21, 2015
Flash Version 3.9.2 - Update:
• Inclusion of Visitor API 1.4
February 19, 2015
Flash Version 3.9.2:
• Inclusion of Visitor API 1.3.5.
• Changed to not perform automatic referrer tracking after first tracking call, so the 2nd, 3rd, etc., tracking call
(usually link tracking) will not double count the referrer when s.referrer was manually set before the first
tracking call. (AN-92647)
• Removal of deprecated Heartbeat video tracking embedded in the Media module. The supported Heartbeat
video tracking has been moved to a separate Video Analytics library.
September 18, 2014
Flash Version 3.9.1:
• Added cookie support testing to Flash (k = Y/N query-string variable) and pf=1 to query-string when cookie
support test is possible (browser with JavaScript access).
• Support for new features in visitor ID service 1.3.2.
August 21, 2014
Flash Version 3.9:
• Added latitude and longitude variables.
• Support for new features in visitor ID service 1.3.1.
Version 3.8.1
Release Date: June 19, 2014
• Fixed handling of done and waiting flags for Visitor API fields such as the legacy Analytics Visitor ID, that
was causing errors.
22
AppMeasurement Release History
• Support for new features in visitor ID service 1.3.
Version 3.8
Release Date: April 17, 2014
• Support for the Marketing Cloud Visitor ID service.
Version 3.7.3
Release Date: March 13, 2014
• Multiple bug fixes to Heartbeat video tracking.
Version 3.7.2
Release Date: February 6, 2014
• Multiple bug fixes to Heartbeat video tracking.
Version 3.7.1
Release Date: November 14, 2013
• Multiple bug fixes to Heartbeat video tracking.
Version 3.7
Release Date: October 17, 2013
• Support for heartbeat video tracking.
• VisitorAPI.swc was included to support Visitor ID Service.
• Dropped support for Flash player 9 with ActionScript 3. The minimum Flash Player version for ActionScript
3 is 10.
Version 3.6.2
Release Date: September 18, 2013
• Internal changes to support an upcoming beta release.
Version 3.5.5
Release Date: August 15, 2013
• Disabled re-queuing of failed requests when offline tracking is disabled.
Version 3.5.4
Release Date: February 21, 2013
• Fixed an issue with URL encoding/decoding in ActionScript 2.
Version 3.5.3
Release Date: January 31, 2013
• Added support to send URLs longer than 255 bytes to support the expansion of the Page URL field in Adobe
Data Collection servers. Page URLs longer than 255 bytes are split, with the first 255 bytes appearing in the
g= parameter, with the remaining bytes appearing later in the query sting in the -g= query parameter. This
23
helps prevent long URLs from taking precedence over other data in the case of browser truncation, but still
enables capturing of long URLs.
• Added a new fallback visitor identification method. See Identifying Unique Visitors.
• Added a new abort flag that can be set inside doPlugins. Setting this flag to true causes the
AppMeasurement library to not continue with that tracking call. The abort flag is reset with every tracking call,
so if a subsequent tracking call also needs to be aborted the flag will need to be set again inside doPlugins.
s.doPlugins = function(s) {
s.campaign = s.getQueryParam("cid");
if ((!s.campaign) && (!s.events)) {
s.abort = true;
}
};
This lets you centralize the logic you use to identify activity that you do not want to track, such as some custom
links or external links in display ads.
Version 3.5.2
Release Date: November 8, 2012
• Internal updates for Audience Manager integration.
Version 3.5.1
Release Date: October 22, 2012
• Changed ActionScript 3 builds to ignore any setting of s.charSet because we always use UTF-8
Version 3.5
Release Date: September 13, 2012
Important change to variable binding: In version 3.5, an option to disable variable binding was added for
customers who need to start and end literal string values with curly braces. Variable binding using curly braces
is used primarily when configuring OSMF video players using XML tags:
<autoTrackMediaName>{media.player.metadata(http://www.corp1.com/,episodeID)}</autoTrackMediaName>
A new attribute, called autoBind, is available to override the default behavior in XML tags:
<autoTrackMediaName autoBind=false>{123}</autoTrackMediaName>
Setting autoBind to false causes the value to be considered a literal string and variable binding is not used.
When this attribute is not set to false the behavior in XML tags remains the same.
Impact on ActionScript Code
Though not commonly used, this syntax is also available to bind AppMeasurement variables in your ActionScript
code. If you are unsure whether or not you are using variable binding, search your code for AppMeasurement
variable values that start and end with curly braces. For example:
s.eVar1 = "{source}";
If you are using variable binding, you should change this code to use the new bindVariable method:
s.bindVariable("eVar1","source");
Optionally, instead of changing each location, you can revert to the pre-version 3.5 behavior by setting
autoBindVariablesByValue to true:
s.autoBindVariablesByValue = true;
Additional Fixes:
24
AppMeasurement Release History
• Fixed an issue that might cause the video complete event to not be sent when using a custom media.monitor
method that tracks the media close event:
If(media.event==”CLOSE”) {
…
}
Version 3.4.9
Release Date: July 19, 2012
• Added a master-only meta policy, see http://www.adobe.com/devnet/flashplayer/articles/fplayer9_security.html.
Version 3.4.8
Release Date: June 21, 2012
• Changed to always use UTF-8 in AS3 builds. This prevents issues with strings for some multibyte languages.
Version 3.4.7
Release Date: April 26, 2012
Video measurement: Added handling of inconsistent complete offset reported by Brightcove player API. Now
if the offset is reported as zero, on complete we use the length as the offset. This fixes issues with the new method
of tracking completes using an offset value.
Version 3.4.6
Release Date: January 19, 2012
• Updated video tracking with a new method to track complete video views. See Measuring Video in SiteCatalyst.
Version 3.4.5
Release Date: September 8, 2011
• Enabled props to contain a literal zero value "0". Previously props with a literal zero value were not sent.
Version 3.4.3
Release Date: May 2011
• In OSMF, fixed issues when using proxy plugins when tracking OSMF video players. This fix enabled OSMF
ProxyElements to be tracked when the element they are proxying is not being tracked.
• Fixed an issue that caused an error measuring video on Flash Player 9.0.16.
Version 3.4.2
Release Date: April 2011
• Support for contextData that drives server-side processing rules (SiteCatalyst v15 only) .
• Support for light server calls (currently in beta) .
• Support for new method of tracking video using conversion eVars and events (currently in beta).
• Support for assigning a value other than 1 to a counter event in the events list.
• Removed support for setting Media.trackWhilePlaying to false. It will always be true.
25
iOS
Cumulative release notes for iOS.
Note: To find the current library version, turn on debug logging.
Mobile library downloads are available on GitHub and on Developer Connection.
4.x documentation
3.x documentation
4.13.4
The iOS SDK version 4.13.4 (Feb 16, 2017) includes the following changes:
Feature
Description
In-App Messaging
Fixed an issue preventing the proper app version to be used when determining an audience. This issue
occurred when a user had an app version upgrade without a new Lifecycle launch.
Acquisition
Added a three-second delay prior to making API calls for Apple Search Ad data on app installs (as per the
recommendation of the documentation).
4.13.3
The iOS SDK version 4.13.3 (Jan 19, 2017) includes the following changes:
Feature
Description
In-App Messaging
You can now disable fullscreen messages when VoiceOver is running.
Analytics
Improved handling of read-only database access.
General
Fixed an issue that could sometimes cause a crash when calling a tracking method from the background
while using App Groups.
4.13.2
The iOS SDK version 4.13.2 (Nov 10, 2016) includes the following changes:
Feature
Description
Visitor ID Service
Added timestamp and Marketing Cloud Organization ID to adobe_mc parameter.
Configuration
Invalid IDFAs (00000000-0000-0000-0000-000000000000) passed to the SDK via
setAdvertisingIdentifier: will be ignored.
Deep Linking
26
When calling trackAdobeDeepLink, variables prefixed with "adb" and "ctx" are now handled
properly.
AppMeasurement Release History
Feature
Description
Acquisition
Data from Apple Search Ads will now be sent along with your acquisition data.
4.13.1
The iOS SDK version 4.13.1 (Oct 20, 2016) includes the following changes:
Feature
Description
Acquisition
The SDK now supports custom acquisition data to be returned appropriately by
AdobeDataCallback invocations.
Target
Visitor ID Service parameters are now passed in Target requests via mboxParams.
Bug Fixes
• Fixed an issue that could cause a crash when trying to sync new ID to the VisitorID service at the same time
as sending tracking hits to Adobe Analytics.
• Fixed an issue that was causing build warnings when targeting iOS versions older than 8.
4.13.0
The iOS SDK version 4.13.0 (Sep 15, 2016) includes the following changes:
Feature
Description
In-App Messaging
New feature: Added a new message type that opens a deep link URI.
4.12.0
The iOS SDK version 4.12.0 (Aug 18, 2016) includes the following changes:
Feature
Description
Visitor ID Service
Added new method to append visitor identity to a given URL in order to transfer identity to a web-based
implementation.
In-App Messaging
Fixed an issue that could cause a crash when setting the "target" attribute to "_blank" in an HTML tag in a
custom full-screen message.
4.11.0
The iOS SDK version 4.11.0 (June 22, 2016) includes the following changes:
Feature
Description
Target methods
You can now use the following new Target method:
• targetLoadRequestWithName:defaultContent:profileParameters:orderParameters:mboxParameters:requestLocationParameters:callback:
27
4.10.0
The iOS SDK version 4.10.0 (May 20, 2016) includes the following changes:
Feature
Description
Target methods
You can now use the following new Target methods:
• targetLoadRequestWithName:defaultContent:profileParameters:orderParameters:mboxParameters:callback:
• targetThirdPartyID
• targetSetThirdPartyID:
• targetPcID
• targetSessionID
TVJS methods
You can now use the following new Target TVJS methods:
• targetThirdPartyID
• targetSetThirdPartyID
• targetPcID
• targetSessionID
Adobe Target for
TVML/TVJS
You can now use the following property names when configuring your ADBTarget element:
• id
• total
• purchasedProductIds
• mboxParameters
4.9.0
The iOS SDK version 4.9.0 (May 5, 2016) includes the following changes:
Feature
Description
Deep linking
You can implement deep linking in your applications to drive users to app or web link destinations.
4.8.6
The iOS SDK version 4.8.6 (March 9, 2016) includes the following changes:
Feature
Description
Track app crashes
The iOS SDK version 4.8.6 contains critical changes that prevent false crashes from being reported. We
highly recommend that you update to version 4.8.6.
4.8.5
The iOS SDK version 4.8.5 (February 18, 2016) includes the following changes:
Feature
Description
Opt-out and privacy settings Starting with iOS SDK 4.8.5, privacy settings set via the setPrivacyStatus method affect activity
from Analytics, Target, and Audience Manager.
28
AppMeasurement Release History
4.8.0
The iOS SDK version 4.8.0 (November 2, 2015) includes the following changes:
Feature
Description
New Marketing Cloud
Visitor ID Service methods
Added the following new methods:
• visitorSyncIdentifiers:authenticationState:
• visitorSyncIdentifierWithType:identifier:authenticationState:
• visitorGetIDs
Changed the visitorSyncIdentifiers:identifiers method to
visitorSyncIdentifiers:
New TVJS methods
Added the following new methods:
• visitorSyncIdentifiersAuthenticationState
• visitorSyncIdentifierWithTypeIdentifierAuthenticationState
• visitorGetIDsJs
New ADBMobile JSON
Config variable
Added the following variable:
• analyticsForwardingEnabled
4.7.0
The iOS SDK version 4.7.0 (October 15, 2015) includes the following changes:
Feature
tvOS Support
App Transport Security
Support
PhoneGap Plugin methods
Description
tvOS is supported for Apple TV.
Starting with iOS 9, Apple introduced App Transport Security, a set of requirements that conforms to best
practices for secure connections.
Added the following new methods:
Configuration Methods
• setPushIdentifier
• setAdvertisingIndentifier
• keepLifecycleSessionAlive
• trackingSendQueuedHits
Tracking Methods
• trackPushMessageClickthrough
New Target method:
• targetClearCookies
Acquisition Methods
• acquisitionCampaignStartForApp
Audience Manager Methods
• audienceGetVisitorProfile
29
Feature
Description
• audienceGetDpuuid
• audienceGetDpid
• audienceSetDpidAndDpuuid
• audienceSignalWithData
• audienceReset
Visitor ID Service Methods
• visitorGetMarketingCloudId
• visitorSyncIdentifiers
App Extensions and Apple Watch Methods
• setAppGroup
• syncSettings
• initializeWatch
4.6
The iOS SDK version 4.6 (September 17, 2015) includes the following changes:
Feature
Description
Push Messaging to Analytics Adobe Mobile Services and the Adobe Mobile SDK allow you to send push messages to Analytics segments.
Segments
The SDK also allows you to easily report users that have opened your app as a result of opening the push
message.
Acquisition Methods
Allows developers to start an app acquisition campaign as if the user had clicked a link. This is helpful for
creating manual acquisition links and handling the app store redirect yourself.
Postbacks
Postbacks let you send data collected by the SDK to a separate third-party server. Leveraging the same
triggers and traits you use to display an in-app message, you can configure the SDK to send customized
data to a third-party destination.
Identifiers
Added the following new identifiers:
• setPushIdentifier
• setAdvertisingIdentifier
• The trackPushMessageClickThrough
WatchKit Support for
WatchOS 2
Added WatchKit support for WatchOS 2.
4.5
The iOS SDK version 4.5 includes the following changes:
30
Feature
Description
iOS Extension
Starting in iOS SDK version 4.5, a new iOS extension lets you collect usage data from your Apple Watch
Apps, Today Widgets, Photo Editing widgets, and all the other iOS extension apps.
AppMeasurement Release History
Feature
Description
We strongly recommend that you use the iOS SDK rather than using your own wrapper.
Apple provides a set of APIs that lets the Watch app communicate with the containing app (sending requests
to the containing app and then receiving responses).
Although you can send tracking data as a dictionary from the Watch app to the containing app and then call
any tracking method on the containing app to send the data, this solution has limitations.
In most cases when a user is using the Watch app, the containing app is running in the background and it
is only safe to call TrackActionInBackground, TrackLocation, and
TrackBeacon. Calling other tracking methods interferes with lifecycle data, so you should use only
these three methods to send the data from Watch app.
Even if these three tracking methods meet your requirements, we recommend using the iOS SDK because
the SDK for watch app includes all Mobile features except in-app messaging.
4.4
Feature
Description
Custom data with lifecycle
metrics
You can now include custom context data variables with lifecycle metrics.
Beacon tracking support in
PhoneGap
The trackBeacon and clearCurrentBeacon calls are now available in PhoneGap.
4.3
Release Date: November 24, 2014
• New - Adobe Marketing Cloud ID integration
• Improved debug logs for clarity
4.2
Release Date: October 16, 2014
• New - In App Messaging Capabilities.
• New - Location for config file can now be specified during app startup.
• New - Points of Interest can now be updated automatically without requiring a new config file.
• New - Analytics calls are now sent as HTTP POST requests.
• Cleared up log messages, added more verbose logging when debugLogging is enabled.
• Multiple performance and stability enhancements.
4.1.3
Release Date: September 18, 2014
• Resolved potential crash that could occur if Audience Manager Submit Signal call or Target Load Request call
failed due to an unknown network error.
4.1.2
Release Date: August 5, 2014
31
• Resolved deadlock issue that could occur with the specific configuration of privacyStatus:optunknown and
offlineEnabled:false
4.1.1
Release Date: August 4, 2014
• Resolved issue that could cause Lifecycle hit to not get sent when referrer timeout was >= 5 seconds and offline
tracking was disabled.
4.1.0
Release Date: April 17, 2014
• Bluetooth beacon tracking.
• App acquisition analytics.
• Apps that are timestamp enabled, crash hits are backdated to the correct session.
• Apps that are timestamp enabled, previous session is sent in a hit that is backdated to the correct session. (no
longer previous session)
• Hit batching.
4.0.2
Release Date: February 20, 2014
• Resolved issue that caused incorrect behavior when the same media item was opened in sequence without
closing previous item.
4.0.1
Release Date: January 30, 2014
• Resolved issue that could cause multiple hits to be sent when database was corrupted.
• Resolved issue that could cause large session length averages if a device had incorrect time settings.
3.3.2
Release Date: January 30, 2014
• Resolved issue that could cause large session length averages if a device had incorrect time settings.
4.0.0
Release Date: 27 September, 2013
iOS SDK 4.x for Marketing Cloud Solutions is now available providing the following new features:
• Significant performance enhancements. All processing is performed on background threads, the SDK is fully
thread safe.
• Geo-location & points-of-interest
• Lifetime value
• Timed events
• Opt-in/opt-out management
• Audience Manager Support
• Lifecycle metrics passed to Target as mbox parameters
• Standardized on context data and processing rules
32
AppMeasurement Release History
3.3.0
Release Date: 23 September, 2013
• Added support for ARM64 and X64 Simulator architectures (iPhone 5s)
3.2.1
Release Date: 16 August, 2013
• Optimized by removing unused code.
• Fixed potential crash that could occur when clearVars was used in a threaded scenario.
3.2
Release Date: 6 August, 2013
• Added support for Adobe Audience Manager.
• Lifecycle data is now sent with Target Mbox requests when lifecycle tracking is enabled.
3.1.8
Release Date: 20 June, 2013
• Fixed a bug introduced in 3.1.7 that was causing issues with lifecycle on devices below iOS 5.0.
3.1.7
Release Date: 23 May, 2013
• Added code to prevent excessive lifecycle hits from being sent via location notifications and Newsstand
notifications that launch an app.
3.1.6
Release Date: 18 April, 2013
• Fixed an issue that was causing previous session length to sometimes be calculated incorrectly.
3.1.5
Release Date: 21 March, 2013
• ADMS_Measurement.visitorID now gets pre-populated with the default value.
3.1.4
Release Date: 21 February, 2013
• Deprecated offlineThrottleDelay as the setting is no longer necessary due to thread optimization. The
setting still exists to preserve backwards compatibility, but no longer has any effect.
3.1.3
Release Date: November 2012
• Fixed a potential EXEC_BAD_Access issue when setting the Products variable manually.
• Fixed a potential invalid selector crash when an mbox timed out.
• Added ad tracking support to media measurement.
33
3.1.2
Release Date: October 2012
• Added a lifecycleSessionTimeout configuration variable that lets you specify the length of time, in
seconds, that must elapse between app launches before the launch is considered a new session.
• Fixed an issue in the media module that caused events set on the measurement object to overwrite events set
by the media module.
• Fixed an issue that caused an exception when allocating an mbox through the Test&Target integration.
3.1.0
Release Date: September 2012
• Added support for armv7s architecture
• Removed support for armv6 architecture
• Minimum supported iOS SDK is now 4.3
3.0.2
Release Date: August 2012
• Customers using media monitor delegate will no longer see two close events
• Resolved an issue where close hits could sometimes cause a loop condition in media monitor
3.0
Release Date: July 2012
Initial release.
Notes
- In order to use this library you must be a SiteCatalyst v15 customer. We make use of Processing Rules heavily
in this version of the library, so we also recommend your analysts are certified to use processing rules.
Enhancements
• Added "Auto-Tracking" functionality
• Reduced library size to appx. 90k in final build.
• Added "trackEvents" and "trackAppState" methods
• Improved context data support and functionality. (Recommend using context data for all information sent)
• Simplified tracking so a basic tracking implementation can be done in 5 minutes.
Changes
• AppMeasurement Class is now ADMS_Measurement
• ADMS_Measurement now acts as a proper Singleton
• Changed getters and setters for eVars, props, lists, hiers, pevs
• All variables passed into "track" calls will only persist for that call.
Modified the following variables
34
Previous (version
2.x)
Current (version 3.x)
account
reportSuiteIDs
dc
dataCenter
AppMeasurement Release History
Previous (version
2.x)
Current (version 3.x)
pageName
appState
contextData
persistentContextData
state
geoState
zip
geoZip
server
appSection
debugTracking
debugLogging
trackOffline
offlineTrackingEnabled
offlineLimit
offlineHitLimit
OfflineThrottleDelay
offlineThrottleDelay
Repurposed the following variables:
• linkURL (sent with trackLinkURL:)
• linkName (sent with trackLinkURL:)
• linkType (sent with trackLinkURL:)
• lightProfileID (sent with trackLight:)
• lightStoreForSeconds (sent with trackLight:)
• lightIncrementBy (sent with trackLight:)
• trackingServerSecure (trackingServer is used when ssl is on)
Removed the following variables:
• timestamp
• userAgent
• dynamicVariablePrefix
• visitorNamespace
• pageURL
• pageType
• referrer
• linkLeaveQueryString
• usePlugins
• useBestPractices (handled by AutoTracking)
• delegate
• retrieveLightData
• deleteLightProfiles
• retrieveLightProfiles
Previous iOS Version (2.x)
The following release notes apply to the 2.x version of AppMeasurement for iOS. We recommend customers
upgrade to the 3.x version when possible.
2.1.12
Release Date: April 2012
• Added support for SiteCatalyst 15 video measurement.
35
• Resolved issues regarding linktrackvars and context data.
• Made several additional performance enhancements.
2.1.11
Release Date: March 2012
• Fixed an issue that caused offline tracking to stop sending data in some circumstances.
2.1.10
Release Date: February 2012
• Fixed an issue that caused an EXC_BAD_ACCESS exception in some circumstances when multiple threads
attempted to simultaneously make a tracking call.
• Added time stamp to variables used with light tracking calls (trackLight).
2.1.8
Release Date: January 2012
• Significantly increased performance of tracking thread.
• Moved offline hit storage to a location that is not synchronized to iCloud to conform to iCloud best practices.
• Updated the library to the Apple fat binary format so you no longer need to include the specific library for your
build architecture.
2.1.6
Release Date: November 2011
• Added support for iOS 5.
• AppMeasurement for iOS was updated to no longer use the deprecated UDID value as the default value for
visitorID. If you set a custom visitorID in your application (for example, s.visitorID = @12345), then
you are unaffected by this change. If you do not set a custom visitorID, instead of using the UDID as the value
for visitorID, a random visitorID is generated on initial launch and then stored in a user defaults key. This key
is used by AppMeasurement from that point forward. This key is also saved and restored during the standard
application backup process.
• Updated calls from the iOS Best Practices plug-in that are not associated with a page view to send hits using
trackLink. This helps prevent these hits from recording page views with the default value of "application
name/version" name.
2.1.3
Release Date: October 2011
• Improved delegate handling. This fixes an issue that caused the iOS Best Practices Plug-in to crash when
bringing the application out of the background.
2.1.2
Release Date: September 2011
• Updated the header to enable use of prop and eVar 51-75.
2.1.1
Release Date: August 2011
• Ability to search report suites and metrics when running a report.
36
AppMeasurement Release History
• Support for context data that drives server-side processing rules (v15 only).
• Support for light server calls (currently in beta).
Android
Cumulative release notes for Android mobile library.
Note: To find the current library version, turn on debug logging.
Mobile library downloads are available on GitHub and on Developer Connection.
4.x documentation
3.x documentation
4.13.4
The Android SDK version 4.13.4 (Feb 16, 2017) includes the following changes:
Feature
Description
In-App Messaging
Fixed an issue preventing the proper app version to be used when determining an audience. This issue
occurred when a user had an app version upgrade without a new Lifecycle launch.
Lifecycle
Fixed an issue that could prevent an app version upgrade from being properly reported.
Acquisition
Fixed a bug that was causing deferred deep links to not be triggered on the first launch.
4.13.3
The Android SDK version 4.13.3 (Jan 19, 2017) includes the following changes:
Feature
Description
In-App Messaging
Fixed an issue that prevented the display of alert messages with no click-through button.
Analytics
Improved handling of read-only database access.
Universal Links
Fixed a bug that was causing deferred deep links attached to acquisition data to fire on successive launches.
4.13.2
The Android SDK version 4.13.2 (Nov 10, 2016) includes the following changes:
Feature
Description
Visitor ID Service
Added timestamp and Marketing Cloud Organization ID to adobe_mc parameter.
Deep Linking
When calling trackAdobeDeepLink, variables prefixed with "adb" and "ctx" are now handled
properly.
37
4.13.1
The Android SDK version 4.13.1 (Oct 20, 2016) includes the following changes:
Feature
Acquisition
Acquisition
Target
Description
The SDK now supports custom acquisition data to be returned appropriately by
AdobeDataCallback invocations.
The SDK now stores Google Play Referrer variables and custom variables and returns them appropriately
in AdobeDataCallback invocations.
Visitor ID Service parameters are now passed in Target requests via mboxParams.
Bug Fixes
• Fixed a bug where data requests to the phone would sometimes timeout.
4.13.0
The Android SDK version 4.13.0 (Sept 15, 2016) includes the following changes:
Feature
Description
In-App Messaging
New feature: Added a new message type that opens a deep link URI.
Tracking Deep Links
New feature: Added the ability to enable tracking of 3rd party deferred deep links.
• processAdobeDeepLink
4.12.0
The Android SDK version 4.12.0 (Aug 18, 2016) includes the following changes:
Feature
Description
Visitor ID Service
Added new method to append visitor identity to a given URL in order to transfer identity to a web-based
implementation.
4.11.0
The Android SDK version 4.11.0 (June 22, 2016) includes the following changes:
Feature
Description
Target methods
You can now use the following new Target method:
• loadRequest
4.10.0
The Android SDK version 4.10.0 (May 20, 2016) includes the following changes:
Feature
Target methods
38
Description
Added new syntax and example for the loadRequest method.
AppMeasurement Release History
Feature
Description
Added the following new Target methods:
• setThirdPartyID
• getThirdPartyID
4.9.0
The Android SDK version 4.9.0 (May 5, 2016) includes the following changes:
Feature
Opt-out and privacy settings
Description
You can implement deep linking in your applications to drive users to app or web link destinations.
4.8.3
The Android SDK version 4.8.3 (February 18, 2016) includes the following changes:
Feature
Opt-out and privacy settings
Description
Starting with Android SDK 4.8.3, privacy settings set via the setPrivacyStatus method affect
activity from Analytics, Target , and Audience Manager.
4.8.0
The Android SDK version 4.8.0 (November 2, 2015) includes the following changes:
Feature
Description
New Marketing Cloud
Visitor ID Service methods
Added the following methods:
• syncIdentifer
• syncIdentifiers
• getIdentifiers
New ADBMobile JSON
Config variable
Added the following variable:
• analyticsForwardingEnabled
PhoneGap Plugin methods
Added the following new methods
Configuration Methods
• setPushIdentifier
• setAdvertisingIndentifier
• keepLifecycleSessionAlive
• trackingSendQueuedHits
Target Methods
• targetClearCookies
Acquisition Methods
• acquisitionCampaignStartForApp
Audience Manager Methods
39
Feature
Description
• audienceGetVisitorProfile
• audienceGetDpuuid
• audienceGetDpid
• audienceSetDpidAndDpuuid
• audienceSignalWithData
• audienceReset
Visitor ID Service Methods
• visitorGetMarketingCloudId
• visitorSyncIdentifiers
4.6.1
The Android SDK version 4.6.1 (September 24, 2015) includes the following changes:
Feature
Description
Android SDK version 4.6.1
SDK 4.6.0 or earlier supports Android 2.2(API 8) - Android 5.1.1 (API 22)
SDK 4.6.1 or later supports Android 2.3(API 9) or later
4.6
The Android SDK version 4.6 (September 17, 2015) includes the following changes:
Feature
Description
Push Messaging to Analytics Adobe Mobile Services and the Adobe Mobile SDK allow you to send push messages to Analytics segments.
Segments
The SDK also allows you to easily report users that have opened your app as a result of opening the push
message.
Acquisition Methods
Allows developers to start an app acquisition campaign as if the user had clicked a link. This is helpful for
creating manual acquisition links and handling the app store redirect yourself.
Postbacks
Postbacks let you send data collected by the SDK to a separate third-party server. Leveraging the same
triggers and traits you use to display an in-app message, you can configure the SDK to send customized
data to a third-party destination.
Identifiers
Added the following new identifiers:
• setPushIdentifier
• submitAdvertisingIdentifierTask
4.5
The Android SDK version 4.5 includes the following changes:
Feature
Description
Android Wearable Extension Starting in Android SDK version 4.5, a new Android extension lets you collect data from your Android
Wearable app.
40
AppMeasurement Release History
4.4
The Android SDK version 4.4 includes the following changes:
Feature
Description
Custom data with lifecycle
metrics
You can now include custom context data variables with lifecycle metrics.
Beacon tracking support in
PhoneGap
The trackBeacon and clearCurrentBeacon calls are now available in PhoneGap.
4.3
Release Date: November 24, 2014
• New - Adobe Marketing Cloud ID integration
• Improved debug logs for clarity
• Resolved potential crash when checking for in-app messages
4.2
Release Date: October 16, 2014
• New - In App Messaging Capabilities.
• New - Location for config file can now be specified during app startup.
• New - Points of Interest can now be updated automatically without requiring a new config file.
• New - Analytics calls are now sent as HTTP POST requests.
• Resolved issue that could cause app crashes to not be tracked in certain scenarios.
• Cleared up log messages, added more verbose logging when debugLogging is enabled.
• Multiple performance and stability enhancements.
4.1.7
Release Date: August 4, 2014
• Resolved issue that could cause Lifecycle hit to not get sent when referrer timeout was >= 5 seconds and offline
tracking was disabled.
4.1.6
Release Date: July 17, 2014
• Added protections around exceptions that occur if the database become corrupted, or could not be created.
• Added protections for issues that could occur when config cannot be loaded (generally due to a null context).
• Added protections for exceptions that could occur when updating the context data of a timed action.
4.1.1
Release Date: April 23, 2014
• Fixed a potential issue that could occur if referrer tracking is enabled and a tracking call is made prior to
lifecycle.
4.1.0
Release Date: April 17, 2014
41
• - New - Bluetooth beacon tracking.
• - New - Apps that are timestamp enabled, crash hits are backdated to the correct session.
• - New - Apps that are timestamp enabled, previous session is sent in a hit that is backdated to the correct session.
(no longer previous session).
• - New - Hit batching.
• - Fixed google play referrer tracking with a configurable timeout to allow for delayed google referrer data.
• - Resolved StrictMode warnings that could occur in specific scenarios.
• - Resloved an issue that could very rarely cause the library to lock if certain methods were called in a specific
order.
4.0.4
Release Date: February 24, 2014
• Resolved issue that could cause extended media time played if stop was called and close was called later with
no calls in between.
• Resolved issue where a media close hit was sent even if the media was not played for any length of time.
4.0.3
Release Date: February 20, 2014
• Added safety to network code to prevent crash caused by Android bug:
https://code.google.com/p/android/issues/detail?id=54072
4.0.2
Release Date: January 30, 2014
• Resolved issue that could cause multiple hits to be sent when database was corrupted.
• Resolved issue that could cause large session length averages if a device had incorrect time settings.
3.2.5
Release Date: 30 January, 2014
• Added protections against corrupted databases causing hits to repeat.
• Added max session length limit to avoid extremely large sessions when device times are incorrect.
4.0.1
Release Date: 14 November, 2013
• Resolved incorrect formatting of trackLocation data in specific locales.
4.0.0
Release Date: 27 September, 2013
Android SDK 4.x for Marketing Cloud Solutions is now available providing the following new features:
• Significant performance enhancements. All processing is performed on background threads, the SDK is fully
thread safe.
• Geo-location & points-of-interest
• Lifetime value
• Timed events
• Opt-in/opt-out management
42
AppMeasurement Release History
• Audience Manager Support
• Lifecycle metrics passed to Target as mbox parameters
• Standardized on context data and processing rules
3.2.3
Release Date: 23 September, 2013
• Fixed a bug in Audience Manager not allowing null values or keys in parameter.
3.2.2
Release Date: 12 September, 2013
• Fixed a bug where media events in linkTrackEvents were not added to the request.
• Fixed a potential exception related to ContextData being modified after being passed into a track call.
3.2.1
Release Date: 16 August, 2013
• SSL Connections now use strict host validation
• Fixed bug where hits would rapidly retry for a few seconds when network connection was lost and
offlineTracking was disabled.
3.2
Release Date: 6 August, 2013
• Added support for Adobe Audience Manager.
• Lifecycle data is now sent with Target Mbox requests when lifecycle tracking is enabled.
• Resolved an issue that could cause SQLite to force close cursors, resulting in unnecessary log entries.
3.1.0
Release Date: 13 June, 2013
• Updated offline storage to use SQLite.
• Fixed a bug where offline limit could reset to default (1000).
• Updated startActivity to now accept an Activity or Application context.
• Fixed a bug where setting lifcycleSessionTimeout to 0 would result in multiple launch events throughout the
app.
3.0.8
Release Date: 18 April, 2013
• Fixed encoding issue with some UTF8 characters.
3.0.7
Release Date: 18 April, 2013
• Fixed an issue that was causing previous session length to sometime be calculated incorrectly.
• New visitor IDs will no longer be based off of deviceID or subscriberID.
• Fixed a potential crash when encoding special characters in variables.
43
3.0.6
Release Date: 21 March, 2013
• Fixed issue where visitorID could not be read without setting it first.
• Changed naming conventions in some error log messages for clarity.
• Changed accessibility of multiple base classes to avoid confusion.
• Multiple performance enhancements
3.0.5
Release Date: 21 February, 2013
• Deprecated offlineThrottleDelay as the setting is no longer necessary due to thread optimization. The
setting still exists to preserve backwards compatibility, but no longer has any effect.
• Fixed potential synchronization issue on offline hit cache.
• Clarified warning message when setting hierarchical vars over #5.
• Fixed issue that could cause OSVersion to be misreported on versions of Android > 4.0.
• Multiple performance enhancements.
• Resolved a potential exception that could be caused by a malformed url.
3.0.4
Release Date: November 2012
• Added a lifecycleSessionTimeout configuration variable that lets you specify the length of time, in
seconds, that must elapse between app launches before the launch is considered a new session.
• Added ability to set the timeout value for the session length calculation, using a lifecycleSessionTimeout
configuration setting.
• Fixed security issues.
3.0.3
Release Date: October 2012
• Added support for Google Play Campaign Tracking.
3.0.2
Release Date: September 2012
• Resolved an issue where close hits could sometimes cause a loop condition in media monitor.
3.0.1
Release Date: August 2012
• Context override parameters are now sent in as Hashmap<String, Object> (they were formerly
Hashmap<String, String>).
3.0
Release Date: July 2012
Initial release.
44
AppMeasurement Release History
Previous Android Version (1.x)
The following release notes apply to the 1.x version of AppMeasurement for Android. We recommend customers
upgrade to the 3.x version when possible.
1.2.3
Release Date: March 2012
• Fixed an issue that caused an exception in some circumstances when passing data using Context Data.
1.2.2
Release Date: February 2012
Fixed an issue that caused link tracking calls to double-URL-encode the pev1 - pev3 values.
Added time stamp to variables used with light tracking calls (trackLight).
1.2.1
Release Date: January 2012
• Added Android 3.x and 4.x compatibility.
• Implemented a UUID for visitor ID on Android devices that do not have SIM cards (For example, Kindle Fire).
1.2
Release Date: June 2011
• Updated the library to use the device ID for the SiteCatalyst visitor ID value when no SIM card is inserted in
the device. By default the library uses the subscriber ID as the visitor ID which is not present if no SIM card
is inserted.
1.1.4
Release Date: April 2011
• Support for all tablets including the Xoom.
• Ability to search report suites and metrics when running a report.
• Support for contextData that drives server-side processing rules (v15 only).
• Support for light server calls (currently in beta).
PhoneGap
Navigation title:PhoneGap
Cumulative release notes for PhoneGap.
If you are building apps with PhoneGap, you can use AppMeasurement libraries for iOS or Android to measure
the app. See PhoneGap iOS and Android Plug-ins for Adobe Analytics.
iOS documentation.
Android documentation.
45
Windows 8.1 Universal App Store
Navigation title:Windows 8.1 Universal App Store
4.0
Release Date: January 15, 2015
Initial release.
Windows Phone 8
Note: To find the current library version, turn on debug logging.
Mobile library downloads are available on Developer Connection.
Note: The Windows Phone 8 SDK is replaced by the Windows 8.1 Universal App Store on page 46 SDK.
No further development will occur on this SDK.
3.0.4
Release Date: August 21, 2013
• Context Data keys now allow underscores.
3.0.5
Release Date: May 22, 2013
• Bug fixes and performance improvements.
3.0.4
Release Date: April 18, 2013
• Fixed an issue that was causing previous session length to sometimes be calculated incorrectly.
3.0.3
Release Date: March 21, 2013
• Fixed a localization issue with DateTime objects.
3.0.2
Release Date: February 26, 2013
• ADMS_Measurement.visitorID now gets pre-populated with the default value.
• Fixed an issue that was sometimes causing auto-responses from cache.
3.0.1
Release Date: February 21, 2013
46
AppMeasurement Release History
• Deprecated offlineThrottleDelay as the setting is no longer necessary due to thread optimization. The
setting still exists to preserve backwards compatibility, but no longer has any effect.
• DayOfWeek is now 1-based starting on Sunday to match the values collected on other platforms.
• Fixed an issue with offline storage that was sometimes causing the app to crash.
WinRT for Windows 8
Note: To find the current library version, turn on debug logging.
Mobile library downloads are available on Developer Connection.
Note: The WinRT for Windows 8 SDK is replaced by the Windows 8.1 Universal App Store on page 46
SDK. No further development will occur on this SDK.
4.0
Release Date: June 17, 2014
New version with new features including geo-location, lifetime value, timed actions, and opt-in support.
3.1.1
Release Date: May 22, 2014
Bug fixes and performance improvements.
3.1.0
Release Date: October 17, 2013
• Windows 8.1 compatibility
3.0.5
Release Date: April 18, 2013
• Fixed an issue that was causing previous session length to sometimes be calculated incorrectly.
3.0.4
Release Date: March 21, 2013
• ADMS_Measurement.visitorID now gets pre-populated with the default value.
• Fixed an issue with retrieving device info.
3.0.3
Release Date: February 21, 2013
• Deprecated offlineThrottleDelay as the setting is no longer necessary due to thread optimization. The
setting still exists to preserve backwards compatibility, but no longer has any effect.
• DayOfWeek is now 1-based starting on Sunday to match the values collected on other platforms.
• Added auto-subscribing to event listeners in the TrackingHelper.js to streamline lifecycle tracking.
47
3.0.2
Release Date: November 2012
• Screen resolution is now accurately being collected for C#, C++, and HTML5/WinJS platforms.
• ADMS_Churn class is now internal. To use best practices for application lifecycle tracking, use the following
calls:
public void ADMS_Measurement.StartSession();
public void ADMS_Measurement.StopSession();
• Added public double maxSessionLength variable to ADMS_Measurement to allow you to set a
maximum session length for the previous user session. If the registered session length exceeds the max, your
max session length will be sent. Default maxSessionLength is 3600 (seconds).
• Added a lifecycleSessionTimeout configuration variable that lets you specify the length of time, in
seconds, that must elapse between app launches before the launch is considered a new session.
• Added new Previous Session Length metric to the lifecycle metrics.
• Updated TrackingHelper for clarity.
• Fixed media module bug.
3.0.1
October 2012
Initial release.
Mac OS X
Navigation title:
Note: To find the current library version, turn on debug logging.
Mobile library downloads are available on Developer Connection.
3.2.2
Release Date: 30 January, 2014
• Resolved issue that could cause large session length averages if a device had incorrect time settings.
3.2.1
Release Date: 16 August, 2013
• Optimized by removing unused code.
• Fixed potential crash that could occur when clearVars was used in a threaded scenario.
3.2
Release Date: 5 Aug, 2013
• Added support for Adobe Audience Manager.
• Lifecycle data will now be sent with Target Mbox requests.
48
AppMeasurement Release History
3.1.7
Release Date: 23 May, 2013
• Added code to prevent excessive lifecycle hits from being sent via location notifications and Newsstand
notifications that launch an app.
3.1.6
Release Date: 18 April, 2013
• Fixed an issue that was causing previous session length to sometimes be calculated incorrectly.
3.1.5
Release Date: 21 March, 2013
• ADMS_Measurement.visitorID now gets pre-populated with the default value.
3.1.4
Release Date: February 2013
Initial release. This version is based on the iOS 3.1.4 codebase, so the initial version number was set to match
iOS.
Windows Silverlight, NET, IIS, XBOX
Note: To find the current library version, turn on debug logging.
1.4.2
Release Date: August 2014
• Removed support for the Microsoft Silverlight Analytics Framework. Adobe is no longer supporting or
distributing the Microsoft Silverlight Analytics Framework integration for AppMeasurement.
• Internal changes to support upcoming functionality.
1.4.1
Release Date: March 2013
• Fixed exception with getting default referrer in Silverlight outside of a browser context and properly exposed
SSL property in the Microsoft Silverlight Analytics Framework component.
1.4
Release Date: February 2013
• Added support to send URLs longer than 255 bytes to support the expansion of the Page URL field in Adobe
Data Collection servers. Page URLs longer than 255 bytes are split, with the first 255 bytes appearing in the
g= parameter, with the remaining bytes appearing later in the query sting in the -g= query parameter. This
helps prevent long URLs from taking precedence over other data in the case of browser truncation, but still
enables capturing of long URLs.
• Added a new fallback visitor identification method. See Identifying Unique Visitors.
49
• Added a new abort flag that can be set inside doPlugins. Setting this flag to true causes the
AppMeasurement library to not continue with that tracking call. The abort flag is reset with every tracking call,
so if a subsequent tracking call also needs to be aborted the flag will need to be set again inside doPlugins.
s.doPlugins = function(s) {
s.campaign = s.getQueryParam("cid");
if ((!s.campaign) && (!s.events)) {
s.abort = true;
}
};
This lets you centralize the logic you use to identify activity that you do not want to track, such as some custom
links or external links in display ads.
1.3.8
Release Date: September 2012
• Fixed an issue that might cause the video complete event to not be sent when using a custom media.monitor
method that tracks the media close event:
If(media.event==”CLOSE”) {
…
}
1.3.7
Release Date: April 2012
• Added support for XBOX.
1.3.6
Release Date: February 2012
• Windows Phone 7: Fixed an issue that caused the offlineThrottleDelay to not apply correctly.
• Added time stamp to variables used with light tracking calls (trackLight).
1.3.5
Release Date: January 2012
• Updated video tracking with a new method to track complete video views. See Measuring Video in Adobe
Analytics.
1.3.4
• New support and build for Windows Phone platform including offline tracking.
• Support for doRequest delegate to override how requests are sent out for tracking data.
• Support for contextData that drives server-side processing rules (v15 only).
• Support for light server calls (currently in beta).
• Support for assigning a value other than 1 to a counter event in the events list.
• Support for new method of tracking video using conversion eVars and events (currently in beta).
50
AppMeasurement Release History
Java
1.4
Release Date: March 9, 2017
• Added missing variables that are available in JavaScript. (AN-136736)
1.3
Release Date: November 10, 2016
• Added SSL hostname verification. (AN-130350)
• Removed support for Java 1.4. Only 1.5+ is supported.
1.2.7
Addition of s.ipAddress variable to override the IP address used in the tracking request
1.2.6
Release Date: April 17, 2013
• Added support for non-sun HTTPS client implementations, such as
weblogic.net.http.SOAPHttpsURLConnection
1.2.5
Release Date: October 17, 2013
• Added exception catching around use of request and response objects.
BlackBerry
Mobile library downloads are available on GitHub and on Developer Connection.
Note: To find the current library version, turn on debug logging.
4.0.0
Release Date: November 4, 2013
Initial release of the 4.x version for BlackBerry 10. See Marketing Cloud for Blackberry 10 - Adobe Analytics.
1.3
Release Date: October 2011
Updated request transport handling to prevent transport errors when using WAP2. In addition, a new method
was added to set the list of available transports. See AppMeasurement for BlackBerry for details.
51
Symbian
Note: To find the current library version, turn on debug logging.
1.1
Symbian library updated to include the latest Symbian app developer code.
PHP
Note: To find the current library version, turn on debug logging.
1.2.2
Release Date: August 2014
• Internal changes to support upcoming functionality.
1.2.1
Release Date: July 2012
• Added a check for the "off" returned for the $_SERVER['HTTPS'] in IIS. Without this check, typecasting to
boolean ((bool)$_SERVER['HTTPS']) returned true in IE whether the request was made through HTTP or
HTTPS. This caused non-secure pages to try to make a secure image request.
1.1
Measurement Library for PHP 1.1 includes the following updates from version 1.0:
• Better GeoSegmentation accuracy (when sendFromServer is enabled).
• Fixed bug so user can now append to userAgent variable.
• Image beacon is now more compliant with more mobile browsers.
• The imageDimensions variable now defaults to 5x5 when mobile is enabled.
• Refined bot detection list.
• Added debug information (HTTP headers, response, errors, and so forth) when debugTracking and
sendFromServer are enabled.
• Added the debugFilename variable (when sendFromServer is enabled).
• The pagename variable defaults to $_SERVER['SCRIPT_NAME'] when neither pagename nor pageURL
are set.
• Full support for CGI implementations of PHP.
• Performance enhancements.
52
AppMeasurement Release History
Contact and Legal Information
Information to help you contact Adobe and to understand the legal issues concerning your use of this product
and documentation.
Help & Technical Support
The Adobe Experience Cloud Customer Care team is here to assist you and provides a number of mechanisms
by which they can be engaged:
• Check the Marketing Cloud help pages for advice, tips, and FAQs
• Ask us a quick question on Twitter @AdobeExpCare
• Log an incident in our customer portal
• Contact the Customer Care team directly
• Check availability and status of Marketing Cloud Solutions
Service, Capability & Billing
Dependent on your solution configuration, some options described in this documentation might not be available
to you. As each account is unique, please refer to your contract for pricing, due dates, terms, and conditions. If
you would like to add to or otherwise change your service level, or if you have questions regarding your current
service, please contact your Account Manager.
Legal
©
2017 Adobe Systems Incorporated. All Rights Reserved.
Published by Adobe Systems Incorporated.
Terms of Use | Privacy Center
Adobe and the Adobe logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the
United States and/or other countries. A trademark symbol (®, ™, etc.) denotes an Adobe trademark.
All third-party trademarks are the property of their respective owners. Updated Information/Additional Third
Party Code Information available at http://www.adobe.com/go/thirdparty.
53
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising