Analytics for Android Wear

Analytics for Android Wear makes it dead simple to send your data to any tool without having to learn, test or implement a new API every time.

All of our client libraries are open-source, so you can view Analytics for Android on Github, or check out our browser and server-side libraries too.

Getting Started

To get started with Analytics for Android Wear check out our quickstart guide which will help you install analytics tracking in your mobile app in just a few minutes. Once you’ve installed the SDK, read on for setting it up the wear part of your App. Please note that you can only use the Android SDK v2 or higher with wear, and that any Beta APIs below are subject to change.

Adding the Wear dependency

Add the wear module to your phone and wear applications.

compile('') {
  transitive = true

Initializing the client

The entry point of the library is through the WearAnalytics class. We maintain a global default instance. Unlike the mobile SDK, this instance is not configurable, simply because it doesn’t have it’s own settings! It will proxy all the calls to the device, which will then call the analytics client on the phone. We’ll show you how to customize the phone client.

WearAnaytics analytics = WearAnalytics.with(context);

Setting up the Phone Manifest

In your AndroidManifest.xml, you’ll need to register the PhoneAnalyticsListenerService service.

<manifest xmlns:android=""


  <application ...>

        <action android:name=""/>

    <meta-data android:name=""



Custom Client

To customize the analytics client, you can subclass PhoneAnalyticsListenerService and override the getAnalytics() method. By default we use the singleton instance, but you can provide us with your custom instances. We recommend reusing the same instance in your phone app. Remember to register your subclassed service instead of ours. The getAnalytics() method is consulted for every call, so make sure you return the same instance each time.


The track method lets you record the actions your users perform, and record adiditonal properties the action.

You’ll want to track an event whenever the user clicks, taps or submits something in your app. You can read more about how it works.

analytics.track("Viewed Product", new Properties().putValue("name", "Moto 360"));
analytics.track("Purchased Item", new Properties().putValue("sku", "13d31").putRevenue(199.99));
name String,requiredA name for the tracked action.
properties Properties,optionalA map of properties for this action, e.g. revenue if the action was a purchase.


The screen method lets you record the screens your users view.

You’ll want to record a screen event an event whenever the user opens a screen in your app. This could be a view, fragment, dialog or activity depending on your app. You can read more about how it works.

Not all services support screen, so when it’s not supported explicitly, the screen method tracks as an event with the same parameters.

analytics.screen("Photo Feed", "", new Properties().putValue("Feed Length", "26"));
analytics.screen("Purchase Screen", "Smartwatches", new Properties().putValue("sku", "13d31"));
name String,optional*A name for the screen. Optional if category is provided.
category String,optional*A category for the screen. Optional if name is provided.
properties Properties,optionalA map of properties for this screen.

Questions? Need help? Contact us!
Can we improve this doc?
Email us:!