Oracle Infinity Product Release Notes for March 1, 2018

Version 1

    The following enhancements have been made to Oracle Infinity Data Collection:

    • The BrightCove video tracking tag plugin now supports the latest BrightCove API.
    • Debug messages are updated to appear in the Java console of a browser to indicate whether the Do Not Track (DNT) flag is set in a client browser window. This should help users understand if a tag is triggering opt-out logic and helps clients to identify what opt-out logic is used by the Oracle Infinity Tag.
    • The Debug plugin has expanded logic around accepting values for wt.co_f  (first party cookie) to handle dashes and non-alphabetic characters in the auto-detected wt.co_f values. In previous versions of the debug plugin, wt.co_f values that included a dash character appear red in the pop-up indicating they are invalid, when in fact they are properly collected. The pop-up window logic for the debug plugin is also updated so that now a pop-up window will only appear if _ora.debug=v (or a higher debug level) is present in the query string. This change protects against scenarios where an administrator may inadvertently leave the debug plugin active on a live site.
    • The session parameter, wt.vt_f, is no longer used and is removed from the Oracle Infinity Tag. This parameter will no longer be generated by the Oracle Infinity Tag. For clients using the Oracle Migration Plugin in association with a Webtrends tag, wt.vt_f_d will still be passed by that Webtrends tag to the Oracle Infinity environment.
    • The Meta tag format is updated in the Oracle Infinity Tag to honor both ORA and WT for automatic detection of Infinity-specific meta tags embedded on a page. This update allows the Oracle Infinity Tag to read past meta tags and allows clients to deploy new meta tags specifically for Oracle Infinity data collection.
    • The ORA.Collect function is updated to include new Boolean options:
      • applyMutations: This option tells the Collect call whether or not to apply registered mutations to the payload. If set to false, no information from plugins that use mutations to modify payload data will be present. The default value is False.
      • sendSessionInfo: This option tells the Collect call to automatically pass visitor information along with the collect payload. Typically this will just be the WT.co_f parameter and time stamp information. The default value is True.
    • The URL fragment plugin is updated to include an enabled=true|false configuration option, so that the fragment plugin can be enabled or disabled without having to remove the plugin entirely. This change helps users mange the fragment plugin similar to how other plugins are managed.

     

    The following Oracle Infinity Data Collection defects have been resolved:

    • Logic in the tag asset coordination service is updated to address an issue in which the parameter used to dynamically load tag contexts (_ora.context) was not being honored in all cases. Using the context parameter now properly swaps contexts when provided with a valid context ID.
    • The Oracle Infinity Tag function now properly identifies Microsoft Internet Explorer 11 and Edge with improved accuracy.