The Value Of Google Analytics For Mobile
In the marketing game, numbers are crucial. I’m not telling you anything you don’t know. There’s a reason why MarketingLand has a whole area designated for analytics. If you’re a website owner or marketer, chances are you spend a lot of time looking at Google Analytics for your website. Do you give your mobile site and app the same kind of attention?
Why Use Analytics For Mobile?
The main reasons to use analytics for mobile are the same as the reasons for using analytics on any website. Analytics answer a number of important questions:
- Where is traffic coming from (for mobile web)?
- Where is traffic going within the site or app?
- What features in the site or app are getting the most use?
- Are people getting stuck trying to perform some function?
- Are people meeting (sales) goals when using the site or app?
How do I use Google Analytics for mobile?
For a regular mobile website, when you make a new account, go to the “Advanced” tab, choose “A site built for a mobile phone”. You’ll need to select the site’s server-side language from the list, and then you’ll get the right code to put into your mobile website. Tests have determined that regular Google Analytics do not always work correctly. In fact, one test showed that as many as 88% of mobile pageviews did not show up using regular Google Analytics.
For an iPhone or Android app, though, you’ll need to use the iOS or Android SDK.
Four Things to Look For In App Analytics
There are a lot of things that you can learn by adding analytics into an app. Here are some that can make a big difference in your business:
• What features are users using? This is probably the most important thing to find out. There are two reasons that certain features get used more than others.
The first is that those are the most important features. The second is that the other features are difficult to access or use. If the features that are being used are those that meet your company’s goals best, then the app is on target.
Imagine an airline app, for example, that has a number of features. One goal might be to tell people about flight delays and restrictions to prevent trouble at the gate. Another goal might be to help people book seats for the same reason. A third goal, however, might be to allow customers to purchase tickets.
It’s important to define the goals you have for an app, and to measure whether people are accessing them. If people aren’t accessing them, it might be a sign that the app design doesn’t encourage using that feature.
• Where are users getting stuck? Let’s go back to the airline example. It’s important to see whether people trying to purchase tickets are abandoning their carts. It’s equally important to see whether people trying to save their seats succeed.
If people often abandon their carts, there may be some difficulty in booking tickets this way. There might be a good way to solve it, or it might be useful to put in a phone number link to help people with complicated processes.
• Are users returning? Which actions do users come back for? For an app, usage numbers are almost as important as installation numbers. While some company goals might be met with a single use (for example, purchasing tickets for an airline), most apps can only be judged to be effective if users come back regularly.
• Is there a problem with use on certain devices? This can catch simple mistakes like Flash-based functions which won’t work on iOS or on many Android phones, but can also catch errors that are deeper in the app use, particularly on Android where there are so many different devices.
If a certain Android build can’t access an important feature, it could cost the company hundreds, or even thousands, of sales. This is why analytics segmentation is critical.
Obviously there are many other uses for analytics on a mobile site or app, but they differ for different types of apps. Leave a comment on what information you’re looking for in mobile analytics.
Opinions expressed in this article are those of the guest author and not necessarily Marketing Land. Staff authors are listed here.