Tag Archives: mobile apps

Track that App! Native Event Tracking is a must.

hand-tapping-iphone

If you’ve got an app in the App Store or with Google Play, you’re probably fixated with how your app is performing.

You probably get some sort of report, letting you know how many downloads or purchases of your respective app occurred over some pre-defined period.

And this report represents a measure of your apps success.

Right?

Wrong!

There are all kinds of tools out there that help you track the performance of your mobile app.

There are basic tools, which tell you how many times your app has been downloaded (which you can typically get from the respective app stores).

And others which tell you about conversions, time on app, entry and exit points.

But these tools offer only the most basic insight into the success (or lack thereof) of your app.

More sophisticated tools let you capture details about usage and engagement.

If you want to dig a little deeper beneath the surface, you can track native events – the specific taps, swipes and scrolls that define mobile application usage.

In my humble opinion, native event tracking is the sweet spot when it comes to apps.

What exactly users are doing with my app.

If your app is a basic wrapper app or a launcher, with a simple native entry point sitting atop a complete mobile web experience, then read no further.

This post isn’t for you.

But if you’ve got a truly native application, which takes full advantage of the device’s API, then you’re going to want to know much more than you’re getting from a download report.

If you’re really interested in understanding precisely what users are doing with your app, after they’ve downloaded and installed it – beyond open, close and time spent – then read on.

If you’ve spent the kind of time that I have with apps, app developers and clients, you know that metrics are supremely important.

No reputable company would launch a website without ensuring that their Google Analytics dashboard was popping (or some other form of online data tracking).

But what about your mobile apps?

Are you paying attention to the events taking place on the device itself, beyond the mobile web entry and endpoints that may be accessed by the app?

Apps provide a deeper level of engagement than a standard mobile website.

So being able to leverage the native features and functions of a mobile device, thereby driving deeper levels of engagement, means that you can capture vitally rich information from each and every user.

Tracking usage patterns of the mobile apps you develop can aid your brand determine where to add (or withdraw) development resources to maximize user engagement.

And that’s where native event tracking come in.

As the name explains, ‘native event tracking’ refers to the tracking (=recording, capture and storage) of the native (=occurring on the mobile device) events (=interactions with the app).

And while Google is the top of the food chain when it comes to online analytics, there are a couple of other players in the native event tracking space.

For example, there’s Flurry, which provides SDKs for mobile application developers interested in tracking usage patterns.

There’s AppClix from Mobile Visions, which has a comprehensive dashboard that integrates easily with other analytics providers, like Flurry, Pinch Media or Localytics.

Omniture by Adobe, which is perhaps one of the more recognizable names in the game, also offers mobile application developers with native tracking tools.

Their native SDKs allow you to measure applications across a host of mobile platforms, including iOS, Android, PhoneGap, Windows 8, Symbian and Blackberry.

And there’s also Tracker, whose API allows you to implement usage tracking and analytics in mobile applications.

There are a host more, of both the paid and open source variety, which can all adequately track mobile application usage to a greater or lesser degree.

But for me, one stands out above the rest.

And it’s (one again) Google.

Having recently worked on a project utilizing Google’s Analytics for Mobile Apps SDK, I can say that it’s the most robust and comprehensive native events tracking application I’ve worked with.

The great thing about it, is that it’s totally customizable.

Does your app allow users to swipe, pinch, tap, scroll, press, shake, toggle?

Then you can track it all with Google.

Using a very basic methodology: _trackEvent (category, action, opt_label, opt_value, opt_noninteraction) you’re able to generate supremely in-depth user engagement data from mobile applications.

The best thing about using Google’s event tracking protocols is that it’s FREE!

In addition, if you’re already using Google for your web analytics, the dashboard and reports are virtually the same.

Now, to each, his or her respective own.

Having worked with GA for a minute, it’s my SDK of choice.

But if you’re working with an app developer, one question to ask is how they intend (or what mechanism they intend to use) to track native events.

And if you’re developing apps on your own, do not neglect native event tracking.

There’s no better way to learn about (and leverage) your users’ behavior.

Class dismissed.

Now get out there and track those apps!

Leave a Comment

Filed under apps, digital advocacy, mobile

The difference between an app and a mobile site is…

The other day, I nearly smacked the sh*t out of my wife.

Or rather, I had the urge to smack the sh*t out of my wife.

Now, I’m not a violent person.

Nor do I support domestic violence of any kind.

But she asked me a question…

So vile…

So base….

That it took every sinew in my body to restrain myself.

What, pray tell, did she ask to create such an impassioned emotional response?

“What’s the difference (between an app and a mobile site)?”

Can you believe it?

The nerve of this heifer.

I’ve been married to this broad for almost 13 years.

I’ve been in the mobile app/technology space for over a decade.

Over this period, I regaled her with stories of my exploits in cyberspace.

I converted her from a cave dwelling savage to a member of civilized society.

Where once stood a technophobe, now exists a technophile.

I brought her from a clamshell to a smartphone.

Raised her from the ignorance of PCs to the enlightenment of Apple.

Brought her from the dark of online social isolation to the light of social media and networking.

But, I digress.

Why did I want to inflict bodily harm?

Well, she was “pinning” on her Droid II and remarked how fluid the Pinterest mobile website was.

I casually remarked that if the mobile site worked so well, that the app would probably work better.

Following my advice, she fumbled around trying to locate the link to the Google Play Store on her device before realizing that the app was already installed.

Apparently, months ago, when she became the Pinterest-junkie she is today, I had installed the app to feed her voracious pinning appetite.

She had been using the app for a hot minute, thinking she was on their mobile site.

It was then, that she uttered those three dreaded words: what’s the difference.

They cut me like a knife.

She was looking down at her phone and didn’t see the murderous rage in my eyes.

We were in a public place (Ruby Tuesday) with the kids, so I channeled my inner Shaolin monk to avoid lunging across the table and throttling her.

Could she really not know the difference?

Maybe all the times she feigned sleep as I recounted my days’ work, she was really dozing off and not paying attention.

I should have known, with all those Help Desk moments, assisting her to remotely recover a file she thought she had deleted or locate a download on her computer.

Perhaps she was…daft?

My rage was quickly replaced by pity for my poor ignorant spouse, who continually failed to avail herself of her husband’s brilliance.

And it dawned on me.

If my bottom bitch didn’t know the difference between an app and a mobile site, perhaps my thirteen readers didn’t either.

I must right this wrong.

First, let’s start with definitions.

An app is a software application that’s written in the language of the mobile platform upon which it operates.

A mobile site is a website that has been optimized for browsing on mobile devices.

Now lets look at the primary differences between them, in the areas of: access, connectivity, content and compatibility.

Access

Apps are usually accessed directly from the mobile device. Typically, there is an icon for the particular app you wish to utilize, which launches the app. Click it and you’re off!

Mobile sites, on the other hand are usually accessed from within the mobile web browser. In order to access a mobile site, you’ve got to open up your browser, plug in the URL and hit enter. On many smartphones, though, you can now create a shortcut, which allows you to save the location of the web page as an icon on your device, which then opens up like an app.

Connectivity

Apps are usually available whether you’re online or offline. While many apps require an Internet or wifi connection to update their content, most are built to be used regardless of whether a connection exists. Typically, if a user is offline they can continue to use their app, and it will update once they’re in range of a signal.

Mobile sites require a cellular or wifi connection to be used. If you’re not in range of a wifi signal or rocking a device with a robust 3G or 4G, then connecting to a mobile site will be slightly…problematic.

Content

When you’re on an app, the content in the app can be stored on the device, pulled from the web and downloaded to the device, or both. Most game apps usually have content stored on the device. They user isn’t required to be online in order to play. Many games in the Apple app store, however, are now adding Game Center capabilities, which allow you to play against other users remotely. Game center content requires an Internet or wifi connection.

If you’re on a mobile site, the content is only available online. If you can’t get online, you can’t get to the content of the mobile site you’re trying to reach. Period. If you’ve got cached web pages, they’ll appear when you open up your browser, but once you try to load/reload that page, you’re screwed.

Compatibility

Apps are designed specifically for the devices they operate upon. An iOS app will not work on an Android device. An Android app will not work on an IOS device. And nothing works on Blackberries. Compatibility is not really the forte of apps.

Mobile sites, on the other hand, are compatible across devices and browsers. With the exception of Flash (which still does not work on iOS devices) most features and functions on mobile sites work on virtually all mobile devices.

My sweet ignorant wife got the abridged version of this breakdown.

Hopefully it stuck.

In my pity, I no longer harbored the desire to smack the shit out of her.

While my pimp hand is strong, so is my compassion for the enfeebled.

Hopefully my explanation of the differences between apps and mobile sites are too.

Note to my wife: If you’re reading this blog, these are just jokes. I never want to smack the shit out of you…except when you’re talking to me while sports are on the tele…or when you prattle on endlessly about inane topics you know I could give a fuck about…or when you get on me for being on my phone. But aside from that, you know I loves you.

6 Comments

Filed under apps, iPhone, mobile