engage emea 2010 - integrating mobile web tracking
TRANSCRIPT
Integrating Mobile Web Tracking
Paul Lawbaugh, WebtrendsEric Butler, Webtrends
Web Mobile Social Apps Games Video
Webtrends Mobile Analytics
Mobile Web Native Apps Campaign Apps
Webtrends Analytics
Mobile Measurement
Mobile WebSites designed specifically for viewing via mobile device browsers
Leveraging Webtrends JavaScript, or server-side, or client-side
LandscapeModern SmartPhone browsers, most based on webkit, are rapidly becoming the new standard (Apple, Google (Android), BlackBerry, Palm, Polaris, Nokia, SonyEricsson)
Others are adopting similar functionality (Firefox, Opera, IE)
New capabilities with HTML5 are giving browsers similar functionality to Apps (location, control of device functionality)
The Challenging Legacy
WAP 1.0 – WMLOlder or simple devices, limited cookie support, WBMP images, no support for JavaScript
WAP 2.0 – XHTML MPContemporary devices, limited cookie support, supports GIF images, some JavaScript support
SmartPhones make it easierMore sophisticated browsers makes tracking easy
Traditional web site tagging and reporting works great
Accept first party cookies by default
Client side JavaScript
As most modern browsers support HTML5, CSS3 and JavaScript, standard Webtrends JavaScript solutions work perfectly
The default behavior of many new modern browsers is to block 3rd party cookies, which has impact on cross-domain tracking
Use the Webtrends Tag Builder to instrument the JavaScript you need - http://tagbuilder.webtrends.com
Client side tracking: image request
Image request can be composed server-side and included in the page.
When the page is rendered by the browser, the image is requested and the corresponding data is collected.
Example:http://statse.webtrendslive.com/mydcsid/dcs.gif?dcsuri=mypage.asp&dcsdat=1068089121752&wt.ti=my%20page%20title
Combining Old and NewUse JavaScript solution for browsers that support it
Leverage the “noscript” portion of the tagIf the browser supports JavaScript, it’ll run fine,
and for those that don’t, the noscript portion will execute
Customize the noscript request with server-side generated parameters
Server side tracking
Data can be sent directly from your server to the Webtrends Data Collection API (DCAPI) on each hit/event.
Note: Use the DCAPI rather than the normal Webtrends Tag/SDC server as it simplifies the request/response on your side.
Example:http://dc.webtrends.com/v1/dcst2axhq00000oqoz417slqm_2m2n/events.svc?dcsformat=plain&dcsverbose=truePost params:
dcsuri= (URI stem (directory path))dcsua= (useragent string)WT.ti=[pagetitle]co_f= [one of the several visitor ID parameters WebTrends supports]
Webtrends Configuration
Create a new corresponding Profile for your mobile web presence to track it independently
Rollup the data across mobile sites and/or all sites via rollup profiles
Leverage JavaScript solution where your use cases permit it
Resources•Webtrends Tag Builder
http://tagbuilder.webtrends.com/•Webtrends Developer Network
http://developer.webtrends.com/•Webtrends SDK Documentation
http://product.webtrends.com/DC/iphone/index.html
http://product.webtrends.com/DC/android/index.html
http://product.webtrends.com/DC/blackberry/index.html