The mobile reporting in SiteCatalyst is a powerful resource for those who are investing in mobile apps, pages and advertisements.  This series of blog posts is to bring a few new mobile solutions to your attention.  These solutions are designed to enhance your mobile reporting experience and help you make more informed decisions related to mobile.

Mobile vs Non-Mobile

The Mobile vs Non-Mobile solution is a standard VISTA solution that places “Mobile” into a prop (traffic variable) or evar (commerce variable) when a hit comes in from a mobile device and it places “Non-Mobile” for all other traffic.  From this you get the following report.

In the above report you can see the percentage of Page Views, Visits and Daily Unique Visitors for your mobile traffic and compare it directly to your non-mobile traffic.  This report will help you to understand how much to invest in mobile websites and application.

You can also look at the report in a trended view to see how the use of mobile is changing over time.

You can also do some deeper analysis by breaking down reports by Mobile Vs Non-Mobile.  For example, this next report takes the product page and breaks it down by Mobile Vs Non-Mobile report to understand how much traffic on a specific page is coming from a Mobile device.

The final report I want to show you is fun because I took the last report and reversed the breakdown.  In the below report I take the value Mobile and break it down by Page Names to see the top pages with mobile page views.

Report

The part of this solution that I like the most is how simple the data sets are and how easy the reports are to understand.  You can only take action on a report when you truly understand what the data represents.  With the Mobile Vs Non-Mobile solution everyone in your company will quickly be able to understand and act on the results of the reports.

Get Started:

You can get started by going to our customers portal and downloading the whitepaper on the solutions.  And if you would like to request more information, you can do it on the customers portal or talk to your account manager.

Other posts you might be interested in:

As always, post your comments or e-mail me at pearcea (at) adobe.com.  It is your comments and e-mails that keep me posting and give me ideas for future posts.

5 comments
Meinhard Schramm
Meinhard Schramm

A report in your blog shows the page names. We are currently duplicating some pages to a more mobile friendly design. For example the product home page is now going to have a web (PC) version and a mobile version. The question is how we should track the pages: a) same page name for both pages and a prop/evar differentiating mobile/non-mobile b) separate page name with mobile differentiation in the page name c) report suite for mobile traffic - no mix of web/mobile traffic. One limitation for option b) is that we have only 500,000 unique values for page names and we are always above the limit. The reporting is broken for combined reporting for c) and partially b). The separation of reporting becomes more work in option a). There might be other options that we have not consider. What is Omniture's/your recommendation to address this challenge?

Adam Egbert
Adam Egbert

Hello, Eric, There are several different methods used by SiteCatalyst for tracking visitors. The first which you mentioned is to use a persistent cookie. The second, as indicated by Pearce, is used as a fallback when the persistent cookie is not accepted and utilizes a combination of the IP address and user agent string of the browser. The third method is to set the visitorId variable explicitly. This method should be used when the user is known and can be identified on the back end. For mobile implementations specifically, the DeviceID is often used. Best Regards, Adam Egbert Technical Consultant Adobe Sytems, Inc.

Ed Hewett
Ed Hewett

Eric, As Pearce says, you will be able to sub-relate the Mobile/Non-Mobile eVar by campaigns. However, you should also note viewing campaign performance by mobile device is already possible. If you want to sub-relate your mobile reports by campaign, just contact ClientCare or your account manager and they can configure the proper settings for you. Of course you'll want to make sure you are properly capturing your campaigns on mobile first--you may want to review the following post for more detail: http://blogs.omniture.com/2010/08/02/mobile-campaign-tracking/ . Regarding cookie acceptance on mobile you may want to read the cookie section of this post as a primer: http://blogs.omniture.com/2009/11/09/top-5-mobile-implementation-gotchas/. However, that's only part of the answer. As Pearce points out, eVars rely on the persistence of a visitor id (regardless of the identification method). In other words, if you are tagging an iPhone app, your eVars will persist even though this implementation method leverages an id unique to the device and not a cookie for visitor identification.

Eric Matisoff
Eric Matisoff

So here's a question. If we push Mobile/Non-Mobile into an eVar, are we then able to subrelate by s.campaign with events as a metric? Don't eVars require cookies in order for them to be persistent? And a lot of my research lately has shown that cookies are being stripped by carriers/phones/browsers. Please let me know if this is not an issue though, as it's just speculative.

Pearce Aurigemma
Pearce Aurigemma

Hey Eric, So here’s a question. If we push Mobile/Non-Mobile into an eVar, are we then able to subrelate by s.campaign with events as a metric? Good question, you will be able to sub-relate with metrics. Now that I think about it, it will be a really nice report. It will help you to see how campaigns are performing for mobile devices. Don’t eVars require cookies in order for them to be persistent? This should not be an issue as the evar persistence is dealt with server side and our servers are designed to handle situations where cookies are dropped to increase accuracy of reporting.