Release Notes

These are the release notes for Analytics 10.2, Fall 2011.

Additions

• A new Mobile Website space is available for licensed customers, including a mobile-focused dashboard, and a mobile-optimized JavaScript tag.
• Scenario Analysis reports are available in Analytics 10 with new visualization and updated scenario conversion rate calculation.
• User access rights can now be managed in Analytics 10 for space types that only appear in Analytics 10:  Facebook Pages, API-only Facebook Apps, API-only iOS Apps.
• Several additional sites are now recognized as “Social” traffic sources:  Yahoo! Pulse, Friendfeed, t.qq, Hyves.nl, Renren, Netlog, Mxit, Vkontakte, Seesmic, Iwiw, Me2Day, Blogger, Mxit.
• Updates to the list of spiders used by the spiders filter and used to populate the Spiders report.
• Numerous additional devices have been added to the list that populates the Mobile Devices dimension in reports.

Changes

• Organic search traffic originating from Google secure search will be recognized as a Google search engine and will have a search phrase of “Search phrase not provided”
• In Facebook Page spaces, some metric display names have been updated:
• “Wall Posts” has been changed to “Posts by Others”
• “Likes” has been changed to “Content Likes”
• “Fans (Lifetime)” has been changed to “Page Likes”
• Three reports added during the initial Analytics 10 release have had their display names changed. (This does not affect reports with similar names that existed prior to Analytics 10).
• The “Pages” report is now the “Site Pages” report.
• The “Search Engines” report is now the “Search: Engines” report.
• The “Search Phrases” report is now the “Search: Phrases” report.
• In the list of URL Rebuilding options shown in Analytics 9 Administration, the “No Rebuilding” option has been removed.

Issues Resolved

• An error that occurred when a user connects to a Facebook account with no eligible apps or spaces has been resolved and the messaging that is provided in this situation has been clarified. (ENG386138)
• When the profile limit has been reached, you are no longer prevented from editing space details. (ENG388148, ENG388044)
• An issue with sorting the time period dimension in reports in the Analytics 10 report view has been resolved. (ENG384650)
• An issue with clicking today’s date in the Analytics 10 custom calendar selector has been resolved. (ENG385410)
• Date formats are now treated consistently in the Analytics 10 custom calendar date selector.  (ENG387816, ENG388182)
• Double-byte character display issues have been resolved in Analytics 10 for search phrases, page titles, space names. (ENG386349, ENH387586, ENG388030)

Known Issues

• If a profile’s encoding is changed from the default UTF-8 to Shift_JIS encoding, then double-byte characters entered in the profile field will not display correctly in Analytics 10.  (ENG389159)

Known Limitations

(to be added at release time)

Release Notes

These are the release notes for the Data Extraction API, version 3.0.

Additions and Changes

These were added:

• Trended data is now available for all reports, including multi-dimensional reports, using the period_type parameter.
• You can now retrieve data on Analytics 10 spaces using these methods: list spaces, list space profiles, and keymetrics.
• The external data method gives you access to Facebook, iOS and PostRank data.
• HTML and CSV output formats are now available for the list profiles, list reports for profile, and get report definition methods.
• JSONP is now supported.
• Scenario analysis reports are now available.

These were changed:

• Generator, located at https://generator.webtrends.com, has been updated to generate REST URIs for version 3 of the Data Extraction API.  (There is also a link to the prior of Generator, which generates REST URIs for version 2.1)
• The URI format for the following methods has changed: list profiles, profile summary, list reports for profile, get report definition, get report data for period, key metrics. See “URI changes” in What’s New for details on the changes.
• The calendar date format for report data in JSON, XML and XML2 now conforms to the ISO 8601 standard. IN JSON, calendar dates are now represented differently. See “New data output formats” in What’s New for details.

 These were removed:

• These methods are deprecated in version 3:  list templates, get template definition
• The period parameter is no longer supported. Use the start_period, end_period and period_type parameters to specify time periods.

Issues Resolved

• Several previously observed trending-related issues have been resolved:
• Unable to trend pages report for a particular profiles (ENG370917, ENG368323)
• Trending returning same values in certain cases (ENG377808)
• No data for trending yearly, quarterly, weekly and current_year (ENG367425)
• Trend data stops unexpectedly for sources report (ENG373019)
• REST requests no longer have failures after measures have been added to a report and a custom date range is selected (ENG381944)
• A mismatch between the UI and REST results for Average Visitors per Day (ENG373802)
• An issue with using the “search” parameter in trended reports (ENG373100)
• Issues with extracting drilldown reports (ENG368028, ENG380056)
• Errors encountered when yearly periods specified (ENG380085)

Known Issues

• Searching for values that only occur in second dimension values returns an empty report (ENG386713)
• The label of the second dimension is not translated into the selected language for the key metrics extract for Facebook App and Facebook Page spaces.  (ENG387178)
• The Keymetrics report is not correctly extracting realtime hourly data when start_period and end_period indicate hours and userealtime=true (ENG389117)

Release Notes

These are the release notes for Analytics 10.1.2, Summer 2011.

Additions and Changes

These were added

• Google Plus and Urban Spoon are now being detected as “Social” traffic sources. (ENG386241, ENG385455)
• Traffic from Webtrends Mobile App SDKs is now recognized as browser “Webtrends Mobile SDK” instead of “Webtrends” (ENG386749)
• The user interface now includes breadcrumb navigation

These were removed

• Due to its expiring API availability, the option to include PostRank data in new website spaces has been removed.  PostRank data has also been removed from any existing spaces.

Issues Resolved

• Template-based measure-level rights are used where relevant to narrow the list of reports and measures viewed in Analytics 10 (ENG385445)
• The global search option is now available for searching on non-English characters.  (ENG386015)
• The current hour data is displaying correctly for key metrics. (ENG384301)
• Additional tokens have been translated into available languages. (ENG385660, ENG385737, ENG385381, ENG386044)
• Search phrases from Yahoo Japan Mobile are now being displayed correctly.  (ENG385689)
• An issue with editing group names has been resolved. (ENG385367)
• Thumbnail capture for pages with dynamic content such as iFrames has been improved. (ENG383746)
• It is now possible to create a non-profile space after the profile limit has been reached. (ENG383749)
• Alerts on the key metrics trend view are appearing as expected. (ENG385010)
• Issues with displaying thumbnails and data for some Facebook Page spaces have been resolved. (ENG385976)
• An issue with retrieving iTunes data with updated credentials was resolved. (ENG386546)
• Issues with the display of Dynamic Visitors measures have been resolved.  (ENG385794, ENG386766)

Known Limitations

• Punctuation marks (?, !, %, #, @, etc.) cannot be used at the beginning of a search string.

Release Notes

Released November 11, 2011

These are the release notes for Segments, Fall 2011.

Additions and Changes

This release includes a variety of capabilities to enhance marketers’ targeting abilities, by providing individual-level tracking of mobile applications and sites and some additional improvements to Segments.

Mobile person profile and behavior tracking

New visitor attributes specific to mobile (data source type, platform, device and geography/location) have been added to the Visitor Data Mart platform and are available in Segments to support segmentation by channel and data extraction.  Many of these attributes are collected as part of our mobile SDKs so they will populate automatically, once configured.

Extended Data Support

To accommodate additional behavioral data and additional data from external sources (eg – CRM, customer database), we’ve extended the number of attributes you can include in the Visitor Data Mart platform and leverage in Segments.  This includes custom visitor, visit, and event attributes.  This extended data support is available as an add-on to your existing annual license.  Please contact your Account Manager for details.

Visitor List within Segments

Marketers can request a visitor list from within the Segments interface, not requiring the use of Data Scheduler interface or SFTP server for access.  After creating a segment within Segments, you can click “Create Visitor List” to get a list of visitors for the segment. The visitor list is a one-time request that runs immediately, for a specific time range and is available in the Segments interface.

Segments usability: searching, filtering and sorting

Segments just got even easier to use.  Segments now includes the following capabilities: searching, filtering, and sorting.  You can:

• Search Segment names and descriptions, or the names and descriptions of other catalog objects (Visitor, Visit, Events, Score).
• Search for segments created by you.
• Sort the list of segments alphabetically, by creation date, or by recency of use.

Improved Referrer Tracking

Referrer tracking in Segments and the underlying Visitor Data Mart platform has improved.  Previously, the “First Hit Of Visit” parameter had to be detected in order to set the “Entry Page” and “Referring Domain” values for a visit. With this release, new profiles will have these values set even if the “First Hit Of Visit” parameter is not detected (e.g. – it occurred on a portion of the site not being loaded into this profile). Prior to this change, Entry Page and Referring Domain were marked “Unspecified” if the hit containing the “First Hit Of Visit” parameter was filtered out of the profile.  Please note that this change will be applied to new profiles only moving forward unless you request this change to your existing profiles.  We took this approach to mitigate any disruption to your current referrer tracking.  If you want this new method of referrer tracking enabled in existing profiles going forward, please contact Technical Support or your TAM.

Issues Resolved

• SearchPhrase punctuation: Formerly, all punctuation was removed from the “SearchPhrase” value on the “Search Clickthrough” Event. (ENG384410,  ENG385804, ENG385838)
• Double-byte character corruptions: Formerly, any double-byte characters that contained new line or non-breaking space values were corrupted.  (ENG384404, ENG385793)
• (ENG384910) In Segments, an error occurred when a query was cancelled.
• (ENG385176) The User drop-down list in Data Scheduler displayed deleted users.
• (ENG356035) Events appeared in a profile’s event retention settings even if they are not enabled.
• (ENG386919) If the double quote character was used in a filter name, a parsing failure occurred when the filter was applied to a profile.
• (ENG386584) In Segments, if a user without any profile rights logged in, an error message appeared and there was no way to return to the login page.
• (ENG386172) The event database loader failed to update the Visit column.
• (ENG387009) In the event database, the metadata for translation tables showed deleted columns.
• (ENG380580) In Score, the Scenario rule type had no multiplier and full conversion value.
• (ENG385403)The segment load status did not reset if an error was registered.
• (ENG381360) The segment population manager did not update status accurately in wtUsage.SegmentLoad table.
• (ENG381718) In Segments, a deleted rule set still appeared in the catalog.
• (ENG378028) In the Segments histogram view, deleting all but the last range caused an interminable loading state.
• (ENG378653) In Segments, when selecting a specific time range on the discover canvas, and then clicking “Build Segment”, the specific time range didn’t appear on the build canvas.
• The tranlsation file import process did not recognize changes to metadata. (ENG386802)
• The Test Rule Set dialog displayed a blank page when the start date was changed. (ENG374293)

Known Issues

• Not applicable.

Known Limitations

• Not applicable.

Released November 5, 2010

These are the release notes for Analytics On Demand Fall 2010 release.

Additions and Changes

• Profile Compare in Analytics Insight: To the date range compare functionality already in Insight, we’ve now added the ability to compare profiles.  Just like data compare, profile compare is available in every view in Insight, including both the account and profile dashboards as well as report view.  In the account dashboard, you can choose a single profile as your baseline and compare all others to it.  In the profile dashboard, you can compare two profiles side by side to see how two campaigns, channels, or web sites are performing in comparison to each other.  In the report view, you can see a comparison of any report for two profiles.
• Enhancements to Analytics Insight: Analytics Insight users will see performance enhancements in report response times. You can uncover trends and explore data faster than ever before.
• Mobile Application Report Pack option: A new set of pre-defined mobile application  reports is ready to use in Analytics On Demand.  This report pack option makes it easy to gather and present data for iOS, Android, BlackBerry or Palm applications.
• Mobile Browser and Mobile Device reporting: You can now select these dimensions when you create custom reports on your site’s mobile traffic.
• Mobile Device Filtering: When you create hit filters, you can select from a list of user-agent strings for mobile device filtering (select Browser > Mobile Devices).
• New measure: Single Page View Visits: The number of bounces–the count of visits in this time period where the measured dimension (for example search phrase) led to a single-page visit of a web site.
• New measure: Entry Page Visits: The number of visits in this time period where the measured dimension (page, keyword, or search phrase) led to a visit on a web site.
• New measure: Bounce Rate: The percentage of single-page view visits divided by the number of entry page visits–in other words, the ratio of bounces to total site visits for the specific dimension being measured. Use this metric to measure visit quality. A high bounce rate generally indicates that the specific dimension (such as search phrase) is not relevant to your visitors, because they rarely get past the entry page.

Issues Resolved

• iPad and iPhone were showing in multiple instances in platform reports.  (ENG375176)
  - iPhone, iPad, and iPod Touch entries will begin appearing as one entry: “Apple iOS”.   (Apple iPhone, Apple iPad, and Apple iPod Touch reporting is still available in the Mobile Devices report.)
  - “Macintosh” will begin appearing as “Macintosh OS X” where OS X is detected.
  Note: Custom report visit filters based on specific platform values may be affected, and may need to be adjusted.
• String conversion encoding parameters for Yahoo Japan and Excite Japan were updated to ensure accurate display of Japanese search phrases from these engines. (ENG375629)
• Reports of countries Gambia, Serbia, Montenegro, Aland Islands, Timor-Leste, and Asia-country unspecified had configuration updated to ensure proper display. (ENG375461)
• Apple iOS was added as a value in the Platforms report, replacing individual device entries for iPhone, iPad, and iPod Touch, which are still available in the Mobile Devices reports.  Added Macintosh OS X as a value in the Platforms report. (ENG375176,ENG375300)
• Added 21 more country-specific Google sites:  Algeria, Belarus, Benin, Burkina Faso, Cameroon, Central African Republic, Chad, Gabon, Kuwait, Lebanon, Macedonia, Madagascar, Mali, Montenegro, Mozambique, Niger, Palestinian Territory, Serbia, Sierra Leone, Tanzania, Togo.  Updated 4 engines to ensure traffic is being recognized: Google Argentina, Google Guyana, Google Cambodia, Seznam. (ENG375629, ENG376711, ENH377824)
• Server calls from Webtrends Mobile SDKs will no longer be identified incorrectly as spiders. (ENG375131)

Known Issues

• Insight: When you add a Google News feed as an RSS feed in Insight, using the default RSS feed format results in an error.  As a workaround, change the “output=rss” in the feed URL to “output=atom”.
• Insight: When a change is made to a custom report that significantly affects data, such as changing a dimension or deleting a measure, the report’s data is not viewable in Insight. You can still view the correct data in Analytics Reports.
• Insight:  Calendar days that do not actually contain data are selectable when creating a date range.

Known Limitations

• Insight uses an email-to-SMS gateway for SMS alerts.  Not all mobile carriers support these messages.  If you do not see your carrier in our SMS list, please first verify that your carrier supports email-to-SMS gateway messages.  Then submit your request and contact information as private feedback via the Help/Give Feedback link in Insight.  We will contact you to verify the carrier’s email-to-SMS-gateway message format before sending.

User Interface

• Added an I18N checkbox in Event Tracking section.

Tag (.js and .html output)

• Changed the default setting for i18n flag from true to false.

Version 1.1

January 2012 (1.1.0.375)

• Fixed a memory leak that was present when sending events to a Webtrends On Premises Data Collection server (SDC).
• Fixed other minor memory leaks.
• Fixed issue where a dropped network connection could result in the loss of an event.

October 2011 (1.1.0.370)

• Changed the location of the event data store from NSDocumentDirectory to NSCachesDirectory.  During app upgrade, any existing event data is automatically moved to the NSCachesDirectory as well.
• Changed visitor id from hashed UDID value to a randomly generated value.  All UDID-related code has been removed.  The visitor id is no longer configurable (i.e. the wt_dc_id_method configuration setting is no longer supported).
• Added configuration setting to control sending events while app is backgrounded.  wt_dc_enable_background_send = <yes | no>.  Default = no.
• Added configuration setting to suspend internal thread used to send data collection events.  wt_dc_queue_paused_onstartup = <yes | no>.  Default = no.  The thread is normally created during app startup.  The configuration setting enables you to start the thread in a paused state.  The thread can be resumed by calling this method:
  [self resumeWebtrendsNotifications];

August 2011 (1.1.0.362)

Common Changes (all platforms):

• Removed wt_dc_dcsverbose configuration setting.  This functionality is now enabled by setting wt_dc_debug=true.
• Removed wt_dc_location_enabled configuration setting.  Webtrends no longer integrates GPS in the SDKs so this has been removed.
• Removed wt_dc_internet_check_url configuration setting.   The SDKs no longer need to use an internet check URL to determine if the end-point is reachable, but rather determine this based off the status of the first hit.
• Removed wt_dc_version configuration setting.  This is now generated within the SDK itself.
• Fixed issue where the library would log certain debug messages when configured with wt_dc_debug=false.
• If Application Properties are unchanged, then a warning is logged.
• Added capture of User Locale (WT.ul) and Locale Country (WT.uc).
• Ensured that Custom Data updates/overwrites existing settings.

iOS Specific Changes:

• Application state methods may now receive an application name argument [ENG381000]

• The CoreLocation Framework is no longer required by the library [ENG3810048]

• Added the build number to the Webtrends.h header file [ENG377583]

• Passing an empty string as a customer parameter value will now “clear out” existing value [ENG383299]

• More detailed information is now captured in the Device Model parameter (WT.dm).  Instead of using the values “iPod”, “iPod Touch”, and “iPad”, the library now captures the raw “Model Identifier” (as returned by uname system call).  The format of the Model Identifier is model,number, where model is a human readable string like iPod1, iPhone2, iPad1, and number provides additional detail on the model type (see http://www.everymac.com/ultimate-mac-lookup/ for details).  This helps to better distinguish between models and also automatically captures values for new device models as they come onto the market.  Here are some sample values:

• Now capturing Country Code (WT.g_co).

• Now capturing Screen Resolution (WT.sr).

• Added applicationName argument to the following methods: eventForAppLaunch, eventForError, eventforAppExit, eventForAppBackground, eventForAppForeground, eventForNotification [ENG381000]

• Disabled sending of events while application is backgrounded state.

Version 1.0

July 2011  (1.0.1.269)

• Fixed issue when target build was iOS 5.  Would cause EXC_BAD_ACCESS, SIG_ABRT, or NSInternalInconsistencyException errors in certain cases.

February 2010 (1.0.1.267)

• Fixed build error “duplicate symbol _OBJC_METACLASS_$_Reachability” that occurred when linking the library with an application using the Apple’s Reachability class.

November 2010 (1.0.1.243)

• Fixed issue affecting applications that use CoreData.  In certain cases the library would merge application data model entities into it’s persistent store.
• The library no longer throws NSInternalInconsistencyException during parameter validation.  Now, rather than throw exceptions, the SDK simply logs a message to the console using the NSLog function.

October 2010 (1.0.1.238)

• No longer copying Webtrends.plist file into Documents folder.  Webtrends.plist now remains in the application bundle.  This helps eliminate confusion around getting configuration settings to stick during rebuild/deploy cycle.
• The library version string is no longer logged to the console when wt_dc_debug=false.
• Deprecated wt_dc_id_method=webtrends_id setting.  The default setting is now system_id.  The system_id value is now hashed.
• Deprecated the wt_dc_version setting.  The library version number is now compiled into the library.

October 2010 (1.0.1.232)

• Merged arm6 and arm7 builds into a single library suitable for use with iPhone, iPod Touch, and iPad devices.  SDK now resides in a single downloadable file named “Webtrends-<version>-iOS.zip”.
• Linked library against iOS SDK 4.1.
• Fixed issue with malformed new visitor tracking parameter (WT.vt_f).
• Fixed issue with thread management that could cause EXC_CRASH (SIGABRT) error in certain cases.
• Fixed issue with event queuing during absence of internet connectivity.

August 2010 (1.0.0.223)

• At startup, the SDK validates the format of the following settings: wt_dc_dcsid, wt_dc_url.  If setting is invalid, an NSInternalInconsistency exception was thrown.  Now, rather than throw an exception, the SDK simply logs a message to the console using the NSLog function.

July 2010 (1.0.0.215)

• Fixed runtime error “-[NSAutoreleasePool release]: This pool has already been drained, do not release it (double release).”

June 2010 (1.0.0.209)

• Fixed linker error generated when building xCode 3.2.3 with iOS 4 support (“Undefined symbols:”).

May 2010 (1.0.0.196)

• Changed default settings for wt_dc_location_enabled (to false) and wt_dc_location_method (to oncepersession).

April 2010 (1.0.0.194)

• Created separate builds for ARM6 and ARM7 instruction sets.  ARM7 is recommended for iPad-only development.
• Added SDK version string to debug console output.
• Fixed minor memory leak.

April 2010 (1.0.0.178)

• Fixed memory leak in WTEvent EncodeValue.

March 2010 (1.0.0.177)

• Cleaned up logging messages.
• Persist visitor id across application updates.
• Added sample application.
• Changed version string to match corporate standard.

March 2010 (1.0.160)

• Maintenance release.

February 2010 (1.0.142)

• Maintenance release.

February 2010 (1.0.90)

• Initial release.

Version 1.1 ( 1.1.0.128 )

Common changes to all SDKs

• Removed wt_dc_dcsverbose configuration setting.  This functionality is now enabled by setting wt_dc_debug=true.
• Removed wt_dc_location_enabled configuration setting.  Webtrends no longer integrates GPS in the SDKs so this has been removed.
• Removed wt_dc_location_method configuration setting.  Webtrends no longer integrates GPS in the SDKs so this has been removed.
• Removed wt_dc_internet_check_url configuration setting.   The SDKs no longer need to use an internet check URL to determine if the end-point is reachable, but rather determine this based off the status of the first hit.
• Removed wt_dc_version configuration setting.  This is now generated within the SDK itself.
• Fixed issue where the library would log certain debug messages when configured with wt_dc_debug=false.
• If Application Properties are unchanged, then a warning is logged.
• Added capture of User Locale (WT.ul) and Locale Country (WT.uc).
• Ensured that Custom Data updates/overwrites existing settings.

Blackberry Specific

• Added capture of  Country Code (WT.g_co).
• Reduced memory usage.
• Optimized event storage mechanism, and sending of data.
• Reduced memory footprint.
• Reduced SDK initialization time (lazy load, programmatic config).
• Deprecated onActivityStart, onActivityPause, onActivityEnd.
• V1 event stores will be upgraded to our V2 schema.
• Data isolation improvements.
• Added “clear out event database” parameter to Initialize method.
• Added wt_dc_persist_events config setting to disable event persistence.
• Made the following config settings case-insensitive: wt_dc_dcsid, wt_dc_url.
• Exposed Webtrends logging class and added event based logging.

February 2011 (1.1.0.100)

• Removed wt_dc_dcsverbose setting.  This functionality is now enabled by setting wt_dc_debug=true.
• Javadoc is now available in a downloadable file named “Webtrends-<version>-RIM-javadoc.zip”.

January 2011 (1.1.0.86)

• Fixed issue where the library would log certain debug messages when configured with wt_dc_debug=false.
• Removed connect type detection (WT.ct).  Connection type is controlled at the application level and is not detectable by the library.
• Fixed issue in onAdImpressionEvent method where compound values were not being handled correctly.
• Fixed issue with operating system detection (WT.os).  Now correctly returning device software version.
• Enhanced LoadConfigFile method to look for webtrends.xml in root of the project file if not found in the specified class path.

October 2010 (1.1.0.75)*

• Added advanced analytics methods.
• Added control over permission-related user prompts.
• Simplified visitor id mechanism.
• Simplified event queuing mechanism.
• Additional debug logging.
• Relinked SDK using JDE 4.5.

* If you are upgrading from a prior release of the SDK, please copy over your configuration settings to the latest configuration file (webtrends.xml), and rebuild your application.

Version 1.0

May 2010 (1.0.0.191)

• Initial release.

Version 1.1 (1.1.0.15)

Common changes to all SDKs

• Removed wt_dc_dcsverbose configuration setting.  This functionality is now enabled by setting wt_dc_debug=true.
• Removed wt_dc_location_enabled configuration setting.  Webtrends no longer integrates GPS in the SDKs so this has been removed.
• Removed wt_dc_location_method configuration setting.  Webtrends no longer integrates GPS in the SDKs so this has been removed.
• Removed wt_dc_internet_check_url configuration setting.   The SDKs no longer need to use an internet check URL to determine if the end-point is reachable, but rather determine this based off the status of the first hit.
• Removed wt_dc_version configuration setting.  This is now generated within the SDK itself.
• Fixed issue where the library would log certain debug messages when configured with wt_dc_debug=false.
• If Application Properties are unchanged, then a warning is logged.
• Added capture of User Locale (WT.ul) and Locale Country (WT.uc).
• Ensured that Custom Data updates/overwrites existing settings.

Windows Phone 7 Specific

• Added capture of  Country Code (WT.g_co).
• Exposed Webtrends logging class, and added event based logging.
• Optimized event data storage mechanism so that is uses binary serialization instead of XML serialization.

Version 1.0

February 2011 (1.0.0.118)

• Initial release.

Version 1.1

December 2011 (1.1.0.40)

• Added support for installation referrals from Android Market

Android Market supports the use of the “referrer” parameter in download links.  This information is useful for campaign attribution — knowing the source of the application install.  Android Market sends the referrer to your app at the time of installation.  The library captures the referrer and persists it for use with event collection methods. The referrer is always sent by the onConversionEvent method via the WT.fr parameter.  Additionally, you may retrieve the referrer using the firstReferrer method and pass it as custom data to any of the event collection methods.  Here is an example:

// instantiate a map object to contain custom data

Map <String, String> customData = new HashMap<String, String>();

// store install referrer in map

customData.put("WT.fr", WebtrendsDataCollector.firstReferrer());

// send custom event

wtEvent.onCustomEvent("/install/referrrer", "InstallReferr Event", customData);

To make use of this feature you must  add the following to your Android Manifest file:

<receiver android:name="com.webtrends.mobile.analytics.WebtrendsReferrerReceiver" android:exported="true">

<intent-filter>

<action android:name="com.android.vending.INSTALL_REFERRER" />

</intent-filter>

</receiver>

Note:  If you use more than one broadcast receiver for the INSTALL_REFERRER action, you must ensure that they do not block each other.

• Removed all StrictMode violations that were causing Application Not Responding (ANR) dialogs.
• Added logging to help identify cases where ConfigureDC method was not being called.
• Removed unnecessary event datastore trim at startup.
• Added “Connection: close” header to requests to terminate connection on each request.
• Removed BATTERY_STATS permission from HelloWorld sample app.  This permission is not required by the library.

August 2011 (1.1.0.33)

• Removed extraneous jUnitHelperClasses files from library.

August 2011 (1.1.0.32)

Common changes to all SDKs

• Removed wt_dc_dcsverbose configuration setting.  This functionality is now enabled by setting wt_dc_debug=true.
• Removed wt_dc_location_enabled configuration setting.  Webtrends no longer integrates GPS in the SDKs so this has been removed.
• Removed wt_dc_location_method configuration setting.  Webtrends no longer integrates GPS in the SDKs so this has been removed.
• Removed wt_dc_internet_check_url configuration setting.   The SDKs no longer need to use an internet check URL to determine if the end-point is reachable, but rather determine this based off the status of the first hit.
• Removed wt_dc_version configuration setting.  This is now generated within the SDK itself.
• Fixed issue where the library would log certain debug messages when configured with wt_dc_debug=false.
• If Application Properties are unchanged, then a warning is logged.
• Added capture of User Locale (WT.ul) and Locale Country (WT.uc).
• Ensured that Custom Data updates/overwrites existing settings.

Android Specific

• Re-wrote event queuing mechanism.  Removed health check ping.
• Removed wt_dc_version configuration setting.  The version is now compiled into the library.
• Javadoc is now available in a downloadable file named “Webtrends-Android-javadoc.zip”.
• Removed retry when no internet connection.  ENG377871: Android SDK – Unable to resolve host due to lack of an internet connection causes events to be dropped
• Added capture of  Country Code (WT.g_co).
• Now capturing Screen Resolution (WT.sr).
• Exposed Webtrends logging class, and added event based logging.
• ConfigureDC interface change, applicationName argument no longer needed.
• onActivityPause deprecated, use onActivityEnd instead.

Version 1.0

November 2010 (1.0.0.160)

• Fixed issue where library would cause “Error checking internet connection.  UnknownHostException: Host is unresolved: dc.webtrends.com:443″ error.

October 2010 (1.0.0.148)

• Fixed issue where library would cause “Activity webtrends.android.com.contentView has leaked IntentReceiver” error.

October 2010 (1.0.0.144)

• Fixed issue where library would cause “Transmission timed out, or was frozen, assuming data was sent successfully” error.

September 2010 (1.0.0.140)

• Fixed issue with internet connectivity check.
• Fixed issue where certain error responses would generate “General Exception Error while transmitting data”.

May 2010 (1.0.0.138)

• Changed default settings for wt_dc_location_enabled (to false) and  wt_dc_location_method (to oncepersession).

April 2010 (1.0.0.136)

• Fixed issue where library accessed GPS even though configured  with wt_dc_location_enabled = false.
• Fixed issue where library would  cause “The application <name> has stopped unexpectedly.”  error at startup if GPS was disabled via Android device  settings.

March 2010 (1.0.0.130)

• Rebuilt using Java 1.5

March 2010 (1.0.0.124)

• Added  wt_dc_version setting.  This contains “major.minor.md.build_number”  versioning information.  The build_number is automatically updated by  the build process.  Value is written to the user agent field of the library  log.  This way we can identify the library version used by the app.
• Added  wt_dc_enabled setting.  This allows you to turn off measurement via a  configuration setting (rather than removing code).  Helpful when  troubleshooting application issues (i.e. you can take library out of the  equation).
• Added wt_dc_timezone setting.  This contains the  datasource time zone used for realtime new day, new session detection.
• Implemented  new first time visitor parameter (WT.vt_f=1).
• Implemented service  provider parameter (WT.dc=service_provider).
• WebtrendsUncaughtExceptionHandler  now produces length validated parameters (WT.er, WT.er_st, WT.er_st).
• Additional  informational logging.
• Added a method to clear event queue.
• Added a method to pause/resume sending events to data collection.  This  allows you to temporarily suspend dc-related http traffic.
• We now retain visitor id across application upgrades.
• We are now  utilizing the corporate build system to produce the deliverable.  This  is why the version specifier changed.

February 2010 (2.0.18)

• Initial release.

Release Notes

These are the release notes for Analytics 10.1.1, Summer 2011.

Additions and Changes

These were added

• The new Microsoft SharePoint Website space is available for licensed customers, including out-of-box reporting, and SharePoint-specific tagging capabilities.
• Analytics 10 has been localized into French, German, Italian, Japanese and Spanish
• BlackBerry PlayBook and BlackBerry Tablet OS are now recognized in browser, platform, and device reports.

Issues Resolved

• Template-based viewing restrictions on reports are recognized.  The reports available to for a user to view are limited as expected based on that user’s template access rights.  (ENG384950)
• Page Dashboard and Space Dashboard are populating as expected. (ENG385818, ENG385820, 383241, ENG384344)
• Issues with logging into subaccounts and with navigating among parent accounts and subaccounts have been resolved.  (ENG383648, 385473, ENG385845)
• A user’s alerts are now disabled when that user is deleted. (ENG384330)
• Email alerts will indicate the profile name. (ENG385092)
• The date selection will persist when navigating from the Pages report to the Pages Dashboard. (ENG385128)
• Adding a Facebook connection is now successful whenever the Facebook account has at least one page or one application.  (ENG385294)
• Issues with viewing month total metrics have been resolved. (ENG385260)
• Issues with editing Groups have been resolved. (ENG385190, ENG385390)
• Uploading a custom thumbnail for site spaces with a non-standard domain value is now possible. (ENG385300)
• Analytics 10 Onsite Ads reports are now showing Impressions and Clickthroughs correctly. (ENG384353)
• CSV report download file names now contain profile and report names. (ENG384977)
• Double-byte search phrases from Soso and Baidu are now viewable. (ENG385241)

Known Issues

• In Analytics 10, users are able to view all measures in the reports to which they have viewing access.  Template-based viewing restrictions on measures are not recognized.  (Note that profile access rights and template-based viewing restrictions on reports are recognized.) (ENG385445)

Known Limitations

• The global search option is not yet available for searching on non-English characters.  (ENG386015)

Release Notes

These are the release notes for Analytics 9, Summer 2011.

Additions and Changes

These were added

• The list of social media sites used to determine the “Social” traffic source has been expanded to include  Badoo, Bebo, Blogster, Classmates.com, douban, Fotolog, Foursquare, Friends Reunited, GREE, hi5, Kaixin001, Mixi, MyLife, myYearbook, Orkut, Qzone, Skyrock, Sonico, StudiVZ, Tagged, Trombi, Tuenti, Viadeo, Yahoo! Mobage, Xing, Yelp. (ENG382632)
• A new Express Analysis V9 report template has been added and made available to all new customers since May 6, 2011. (ENG384385)

This was/these were changed

For more information, see the Analytics 10.1 Release Notes.

Issues Resolved

• Issues with filtering on recently added/changed traffic sources (“Social”, “Social Campaigns”, “Other Campaigns”, “Unknown Referrer”, “Referring Sites”) have been resolved (ENG384029)
• Server calls with a user-agent indicating the presence of EasyBits are no longer being detected as the Microsoft Bits spider. (ENG384452)

Known Issues

(Not applicable)

Known Limitations

(Not applicable)

Release Notes

These are the release notes for Analytics 10.1, Summer 2011.

Additions and Changes

These were added

• The new Microsoft SharePoint Intranet space is available for licensed customers, including out-of-box reporting, and SharePoint-specific tagging capabilities.
• Management of third-party credentials (Facebook, iTunes) has been streamlined.  It is now easier to update existing credentials, change the credentials assigned to a space, and to remove unused credentials using Settings > My Connections.
• Internet Explorer 7 is now supported.

These were changed

• The individual report view has been enhanced to show more data on the screen using a “full-screen” capability.
• Overall performance of the dashboards and report views has been improved.

For more information, see the Analytics 9 Release Notes.

Issues Resolved

• The Page Dashboard now populates correctly when the required Analytics 10 reports are added to a profile that existed prior to the Analytics 10 release.  (ENG383687)
• Real-Time key metrics data in the “Today” and “24 hour” views are now appearing in the UI.  (ENG383789, ENG383790, ENG384511, ENG383422, ENG383446)
• Data issues in the Onsite Ads: Clickthrough report have been resolved (ENG384353)
• Historical third-party data from Facebook, iTunes and PostRank is now populating for expected periods, regardless of the end-user’s locale. (ENG383244, ENG382439, ENG383371, ENG384114, ENG383360)
• Synchronization issues of report categories from OnDemand to Analytics 10 have been resolved. (ENG384255, ENG383289, ENG383274, ENG383591, ENG383766)
• Profile/space synchronization issues have been resolved (ENG383934, ENG384306)
• Several issues with Alerts have been resolved, including alerting on “Does Not Reach” alerts, editing alerts, and display of alerts in Analytics 10 (ENG383320, ENG379974, ENG382926, ENG383173, ENG383190, ENG383136, ENG382656, ENG383112, ENG383878)
• Report categories with the same name are now consolidated into a single report category in the Analytics 10 UI (ENG383222)
• Links from elements on the Page Dashboard are now linking to the expected location (ENG383014, ENG383018, ENG383009, ENG384424, ENG384464, ENG384465, ENG384466)
• The Exit Page Visits measure is now calculating correctly in all cases (ENG382315, ENG383830)
• Remaining issues with displays of country flags have been corrected. (ENG383498)
• Workflow improvements have been made to the Groups feature (ENG383111)
• Report table limits on new reports have been updated to improve performance (ENG383859)
• Page Dashboard date range recognition and Visits and Bounce Rate display issues have been resolved (ENG383519, ENG383579)
• Real-time data in the “24 hour” and “Today” views is displaying as expected (ENG383422, ENG383446, ENG383789, ENG383790)
• Issues with space search and filter have been resolved (ENG383262, ENG382792)
• Profile compare, sorting, and % change display issues have been resolved (ENG382009, ENG379556)
• Dashboard display issues with % change and decimal values have been resolved (ENG383929, ENG382715)
• When viewing a report, then pivoting to another profile, the report displays immediately (ENG383218)
• Campaign Landing Page Discovery report now drills down correctly to all levels (ENG383058)
• Facebook “posts” terminology used in Facebook Page spaces key metrics and posts overlay has been clarified (ENG383797)
• Issues with navigating among accounts and sub-accounts have been resolved (ENG383648)
• External data source on/off settings are now being recognized and followed (ENG383698)
• Downloads and Revenue key metrics now appear properly when selected on the Spaces dashboard (ENG382939)
• New report templates have been modified to auto-include custom reports that are added to profiles using those templates.  These templates were updated: “Website (Analytics 10)”, “Mobile Application (Analytics 10)”, “Facebook Application (Analytics 10)”.  (ENG384389)

Known Issues

In Analytics 10, users are able to view all measures and reports in the profiles to which they have viewing access.  Template-based viewing restrictions on measures and reports are not recognized. (ENG384950)

Known Limitations

The “Delete Space” capability is intentionally limited to be available only if the space contains fewer than 2 profiles.

User Interface

• Removed Tag Integration section (eliminating Ad Director and Quantcast integration).
• Added docx and xlsx to Download links file types text box.
• Changed all Marketing Warehouse references to Visitor Data Mart.

Tag (.js and .html output)

• The tag version changed from 9.3.0 to 9.4.0.
• Changed the default setting for i18n flag from false to true.
• Removed the document.write statement from dcsCreateImage function.
• Added defensive code to dcsEvt and dcsSaveProps functions.
• Corrected dcssip parameter inside the <noscript> section of the inline HTML tag.
• Changed to protocol-relative URL inside the <noscript> section of the inline HTML tag.

Release Notes

On May 2, the first release of Analytics 10 will be available for new On Demand customers and a controlled rollout period begins.

Most existing customers will gain access to Analytics 10 beginning on May 16.  Initial usage for each account will begin with access enabled only to users in an Administrator role.  An Administrator will be able to use this “administrators only mode” in order to adequately prepare their account prior to rolling out to the rest of their organization.  Once preparation is complete, the Administrators can then grant access to their user base (through a checkbox in the Analytics 10 “Settings” area).

Note: The existing Analytics offering, formerly known as Webtrends On Demand, will continue to be available and referred to as Analytics 9. For more information, see the Analytics 9 Release Notes.  (The Insight user interface will be retired in late July, 2011, after customers have transitioned their Insight use to Analytics 10.)

Released May 2, 2011

Additions and Changes

Analytics 10 is an innovative platform and user interface that brings new power and simplicity to measuring marketing performance across the digital landscape.  Now, you can measure:

• Across digital channels: Mobile apps, social, and site measures are presented together, so your view is at the brand-level, not silos of channel data.

• Beyond “tagged” data: Feeds, APIs, and public data are analyzed and reported on, in addition to tagged data.

• Campaigns without complicated setup:  The campaign setup process is guided by detection of relevant parameters for landing and conversion pages.  You can track campaign success with easy click-through and conversion tracking.

Analytics 10 Features

• New user interface: An infographic-like interface makes data visualization and navigation easy.
• Spaces: A “space” is an application, website, or platform instance to be tracked. Profiles are automatically organized under spaces.
• Rapid creation of spaces is available for Websites, Facebook Pages, Facebook Applications, and mobile applications for iPhone/iOS, Android, BlackBerry and Windows 7, as well as generic mobile apps.
• All space types come with rich, channel-specific out-of-the-box insight  — more data than any other analytics solution.
• Facebook:  Track apps and pages with no tagging required.  Near-instant access to Facebook API data, visualized in the rich Analytics 10 interface.
• Facebook Apps also include ability to track with Webtrends tagged data to provide additional insight.
• For iOS mobile apps, iTunes Connect key metrics data is retrieved.
• User administration features.
• Page dashboard:  Combines metrics for a URL into one dashboard, dynamically generated.  Provides traffic source, geographic, and search related information for entry pages.  Integration of page statistics from bit.ly, Twitter and Facebook is available.
• Groups: Groups let you aggregate profiles and spaces for custom views of your data (like a playlist).
• Simplified campaign tracking via suggested landing pages and conversion pages.
• Campaign dashboard provides insight into key metrics for a campaign.
• Improved profile dashboard: Richer visualization with additional key metrics and integration of API, RSS and web data.
• Enhanced report views with trending everywhere.  More visualization and trending/compare options available.
• Full cross-compatibility with Analytics 9 (formerly On Demand).  Existing profiles are available in Analytics 10 and vice versa.
• A “Classic” profiles list is available for easy reference to profiles and their report data.

Issues Resolved

(Not applicable)

Known Issues

This section will be updated, if applicable, at release time.

Known Limitations

• Internet Explorer 7 is not supported with the initial release.
• Scenario Analysis and Path Analysis visualizations are not yet available in Analytics 10.  They are still available in Analytics 9 (On Demand).
• Parent/Child profiles do not appear in Analytics 10.  They are still available in Analytics 9 (On Demand).

Release Notes

These are the release notes for Analytics 9, Spring 2011.

Additions and Changes

Traffic Source Enhancements

A new traffic source was added, and the terminology has changed for other traffic sources.

• New traffic sources: “Social” and “Social Campaigns”.
• “Unknown Referrer” is the new term for  “Direct”.
• “Referring Sites” is the new term for “Other Referrers”.
• “Other Campaigns” is the new term for “Non-Search Campaigns”.

Analytics 10 Alignment

The profile creation process now includes a new selection, Profile Type, to align Analytics 9 profiles with Analytics 10 space types: websites and mobile apps.  New reports and templates are also available for each profile type.

For more information, see the Analytics 10 Release Notes

Issues Resolved

• The Errors measure used in mobile app reporting has been updated to correctly detect all error events. (ENG380524,ENG381036)
• Several entries have been added to the list of spiders that are detected by the Spiders report:  ADGBOT, AppEngine-Google, Curious George, Flamingo_SearchEngine, Google Web Preview, HttpComponents, httpunit, iisbot, NTTE Poller, PostRank, Servers Alive URL check, Tasapspider, Truveo, Twisted PageGetter, YioopBot (ENH379555)
• Insight alerts that have been set to alert when a measure “Does not reach” a specified value by “End of day” will now trigger appropriately (ENG379252)
• REST URLs of format Excel (HTML) that are shared in Insight will now include the parameter suppress_error_codes=true, simplifying import into Excel (ENG380760)

Known Issues

(to be added at release time)

Known Limitations

(to be added at release time)

Released April 29, 2011

Additions and Changes

Segments available for same day targeting

Marketers can now leverage intra-day segment extracts to execute same day targeting in their action system of choice, including Webtrends Optimize for on-site targeting and email solutions. Now accessible in Data Scheduler, intra-day segment extracts can be scheduled to run 2, 3, or 4 times daily. All extracts in Data Scheduler from the Visitor Data Mart platform are now also available intra-day.

More Timely Extracts

Many of our customers integrate visitor data from Webtrends Visitor Data Mart into their broader business systems each day. Additionally, many customers use visitor segments daily to drive ongoing targeting. Delivery of this data in a timely manner each day is critical. With this release, these daily extracts are prioritized above weekly, monthly, and ad-hoc extracts to ensure consistency in ongoing targeting and system integration activities.

Issues Resolved

• Data Scheduler requests using the Visitor business object now use the visit event and visit time rather than Visitor and recent visit time. Formerly, visitors would be excluded from the extract if they had a return visit between the end of the requested time period and the current day. (ENG370901)
• Data Scheduler requests using the Customer business object use the now use the visit event and visit time rather than Visitor and recent visit time. (ENG381317)
• Custom attributes on Visit/Visitor events that contain scientific notation no longer produce errors. Scientific notation is treated the same as other non-numeric data–’NULL’ is imported. (ENG379571)

Known Issues

Webtrends Explore only supports Internet Explorer 9 in compatibility mode. Firefox 4 is not supported.

Known Limitations

This section will be updated, if applicable, at release time.

Released November 5, 2010

These are the release notes for Score, Segments and Visitor Data Mart – the Fall 2010 On Demand release.

Additions and Changes

Visitor Data Mart, Score and Segments

Enhanced visitor identification – Visitor Data Mart now includes an optional enhanced visitor identification method combing two of our proven visitor identification approaches, resulting in improved accuracy and counting of unique visitors. Please contact Tech Support or your TAM to take advantage of this enhancement for existing profiles.

Addition of numeric attributes to Segments and integration of Score with Segments – with these enhancements, you can:

• Leverage behavior scores for relevant targeting, using scores as segment criteria
• Apply predictive indicators to targeting: visit recency, frequency and monetary value
• Schedule Score extracts in Data Scheduler

Known Issues

• Invalid Purchase Events are incorrectly detected when a parameter value ends with semicolon. (ENG377004)
• Qualifying URL and Qualifying Parameters on Event Trigger don’t work with the Purchase Event. (ENG377008)
• “Unspecified” is inserted into wtShoppingCartAddEvent table when an SDC log containing multiple values is imported. (ENG377065)
• In the VDM_Loader, ProductSKU doesn’t support multiple values in Purchase event. (ENG377134)
• In Score, the ‘default Multiplier’ value is rounded when a rule for ProductView is edited. (ENG377606)
• In Score, the button text disappears when setting a specific content group score rule type in New Content Group rule. (ENG377611)
• In Segments, when a segment group is deleted, it remains in the Group list until the browser is refreshed. (ENG377670)
• In Segments, the “Save as Group” button is active for non-numeric attributes. (ENG377669)