DC Storm

DC Storm release new version with StormIQ 2.3

Veröffentlicht: 12. Apr 2007

Including integration with YSM, new reporting features and tracking documentation.

Yahoo API

Yahoo are migrating their interface from an XML based interface to a new SOAP API. For continued usage this requires an interface to be written to allow Storm to continue working with Yahoo. The development of this is ongoing and spreads over several cycles culminating in transition of IQ to using the Yahoo API at the end of April

Reporting Changes

A number of reporting updates to improve client access to useful data:
Traffic Source Metric Report has changed to Sales / Action Report
Source type summary selector(eg. PPC) on:

• Site performance
• Sales / Action
• Data Perspective Selector (Landing / Visit / Sale) added to Sales / Action Report
• Unique Selector added to (newly named) Sales / Action Report
• Help added to reports (similar to help for graphs)
• Improved error handling so that the ugly and confusing error messages don’t feature
• A re-jig of the various selectors for consistency across the reports
• Alternative Conversion Rules

 

JS Error Corrections

There are a couple of issues in the way the javascript deals with odd characters (%, $ etc) in column names. This results in occasional odd behaviour in IQ and possible logouts. This work should mitigate this.

Submissions Updates

The submission process is sub-optimal and requires a thorough re-design. This is mitigating work – some quick wins to improve both user experience and level of support required.

JS tracking Enhancements

This includes a number of changes and enhancements to the javascript (js) code:

• Advanced search terms parsing e.g. must include, must not include, must contain exact phrase
• Additional SEs added as recognised natural search engines
  • www.sensis.au
  • www.ninemsn.au
• Accommodate comparison sites
• Cost per click
• Category extracted from tracking parameter
• Other fixes and bug corrections
• Session increment bug fixed
• Extended parameters that can be passed in _$ja

 

Tracking Documentation

• Tracking instructions and examples in Resource Centre
• Pdf document for offline use
• Includes all features of tracking implementation

Onclick Tracking

This feature enables pageviews (and thus process steps) and sales to be linked to a click event of a page element. This means that things like document downloads and clickouts can be tracked and information gathered.
Additionally, the event can be used to set a StormLite tracking cookie so that a visitors progress offsite can be linked to the clickout – for instance when completing a sale recommended on a comparison site.