---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/segment/connections/sources/catalog/libraries/mobile/android/wear#article
headline: Analytics-Android Wear
url: https://www.twilio.com/docs/segment/connections/sources/catalog/libraries/mobile/android/wear
inLanguage: en
dateModified: 2025-10-28T22:08:48.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# Analytics-Android Wear

> \[!WARNING]
>
> End-of-support for the Analytics-Android SDK is scheduled for March 2026. Segment's future development efforts concentrate on the new [Analytics-Kotlin](/docs/segment/connections/sources/catalog/libraries/mobile/kotlin-android/) SDK. If you'd like to upgrade to Analytics-Kotlin, see the [migration guide](/docs/segment/connections/sources/catalog/libraries/mobile/kotlin-android/migration/).

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

All of Segment's client libraries are open-source, so you can [view Analytics-Android on GitHub](https://github.com/segmentio/analytics-android), or check out our [browser and server-side libraries](/docs/segment/connections/sources/catalog/) too.

## Getting Started

To get started with Analytics-Android Wear check out our [quickstart guide](/docs/segment/connections/sources/catalog/libraries/mobile/android/quickstart/) 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. Note that you can only use the Android SDK v2 or later 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.

```java
compile('com.segment.analytics.android:wear:+@aar') {
  transitive = true
}
```

## Initializing the client

The entry point of the library is through the `WearAnalytics` class. Segment maintains a global default instance. Unlike the Android mobile SDK, this instance is not configurable because it doesn't have its own settings. It proxies all calls to the device, which then call the analytics client on the phone. A later step explains how to customize the phone client.

```java
WearAnaytics analytics = WearAnalytics.with(context);
analytics.track(...);
```

## Setting up the Phone Manifest

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

```xml
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
    package="...">

  ...

  <application ...>

    <service
        android:name="com.segment.analytics.PhoneAnalyticsListenerService">
      <intent-filter>
        <action android:name="com.google.android.gms.wearable.BIND_LISTENER"/>
      </intent-filter>
    </service>

    <meta-data android:name="com.google.android.gms.version"
        android:value="@integer/google_play_services_version"/>

  </application>

</manifest>
```

## Custom Client

To customize the analytics client, you can subclass `PhoneAnalyticsListenerService` and override the `getAnalytics()` method. By default Segment uses the singleton instance, but you can provide Segment with custom instances. We recommend that you reuse the same instance in your phone app. Remember to register your subclassed service instead of the Segment default one.

The `getAnalytics()` method is used for every call, so make sure you return the same instance each time.

## Track

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

You probably want to track an event whenever the user clicks, taps or submits something in your app. You can read more about how it works in the [Track spec documentation](/docs/segment/connections/spec/track).

```java
analytics.track("Viewed Product", new Properties().putValue("name", "Moto 360"));
analytics.track("Purchased Item", new Properties().putValue("sku", "13d31").putRevenue(199.99));
```

| Field        | Type                  | Description                                                                     |
| ------------ | --------------------- | ------------------------------------------------------------------------------- |
| `name`       | *String,required*     | A name for the tracked action.                                                  |
| `properties` | *Properties,optional* | A map of properties for this action, e.g. revenue if the action was a purchase. |

## Screen

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

You might 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 [in the Screen call spec documentation](/docs/segment/connections/spec/screen).

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

```java
analytics.screen("Photo Feed", "", new Properties().putValue("Feed Length", "26"));
analytics.screen("Purchase Screen", "Smartwatches", new Properties().putValue("sku", "13d31"));
```

| Field        | Type                  | Description                                              |
| ------------ | --------------------- | -------------------------------------------------------- |
| `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,optional* | A map of properties for this screen.                     |