Hello Webtrends Developers. 

I'm excited to announce a major upgrade to our Webtrends Data Extraction API: version 3.

V3 Documentation



Why a version 3?

Although Webtrends regularly upgrades and enhances the REST Web Services throughout the year, new versions and announcements are reserved for significant releases in which major new functionality and capability is added.  V3 brings with it some features that will make it easier to build your HTML5 dashboards, trend your multi-dimensional data, or build your own localized interface to the data. We've been hard at work (if I do say so myself). 


With that said, here are all the details.



What's new?

New Trending Features and Formats 

You've always been able to trend Webtrends data via REST but it brought with it some limitations including limits on multi-dimensional data (it's pretty challenging to trend cross-correlated dimensional data) and some legacy report data.


I'm happy to say that all the dimensional data in v3 is trendable.


When you jump into multi-dimensional trending it's easy to get buried in your data so we also added more than one view on this trend data with a period_type parameter depending on what you are trying to trend.


For example: if you are trying to build your trend lines where time is the critical dimension, choose period_type=indv.


If you are trying to trend specific items of data over a date range, choose period_type=trend.


Or if what you want is the multi-dimensional detailed data but aggregated across your date range period_type=agg





JSONP Data Format

Building HTML dashboards?  JSON data is fast, efficient and well supported... except you might have found that you can't include an external JSON data package directly into your HTML because the source is from an external domain (dx.webtrends.com).  JSONP stands for JSON with padding and it is the accepted format for indicating a non-script data package which means it is not an executable script from another domain, i.e. browsers won't block the inserted data from another domain. 


It's a simple yet useful addition.  Check wikipedia on more details about JSONP.



Localization and International Dates

Now your data is fully localized including data headers.  This may not have been an issue for users consuming XML data in your single language spreadsheet or app but if you wanted to build a dashboard out of the data (HTML) or create an Excel pivot table directly from the output of the REST request, it sure was a hassle when you cross languages.  Now you can build your own language selector in Excel and the returned data is localized and ready.


Additionally, dates in raw data formats (XML, XML2 and JSON) all conform to ISO 8601, the accepted international date format:  2012-01-01.


If you are in HTML format, dates will be formated in the chosen style for your Webtrends profile.



A10 Spaces

Webtrends Analytics 10 introduced "Spaces" for your various types of data.  You can now select key metrics, report lists and even your profile list for each space.



Facebook and Mobile External Data

External Data that Webtrends is pulling into your Space dashboards is also available including Facebook, iTunes, etc.  Not only does this give you one easy place to pull this data back out, we've added value to the data... it trendable, and the lifeline for the data is the life of your Webtrends data rather than the limited time it is available in the various external data source (usually about 60 days).



Generator update

v3 of the DX REST Generator is also now available at Generator.webtrends.com and has been updated to v3



Please note we also know that v2_1 is still important to many users and it is still available via link on Generator for those still working with existing REST urls).  Go to the v2.1 DX REST Generator directly from here






There are a host of other features and changes as well.

Please take a closer look at the v3 documentation.

Should you have the need, version 2_1 is naturally still working and available.


We'd like your feedback too.  Particularly if there is something specific in version 2 that you don't see and there isn't a better way to do it in v3.  Comment, or send us an email with your needs, we're listening I can assure you.