Expo

Get Started

Guides

API Reference

Get Started

Guides

API Reference

Segment

expo-analytics-segment provides access to https://segment.com/ mobile analytics. Wraps Segment's iOS and Android sources.

Note: Session tracking may not work correctly when running Experiences in the main Expo app. It will work correctly if you create a standalone app.

Platform Compatibility

Android Device	Android Emulator	iOS Device	iOS Simulator	Web
				Pending

Installation

expo install expo-analytics-segment

If you're installing this in a bare React Native app, you should also follow these additional installation instructions.

API

import * as Segment from 'expo-analytics-segment';

`Segment.initialize({ androidWriteKey, iosWriteKey })`

Segment requires separate write keys for iOS and Android. You will need to log in to Segment to recieve these https://segment.com/docs/guides/setup/how-do-i-find-my-write-key/

Arguments

Accepts an object with the following keys:

androidWriteKey (string) – Write key for Android source.
iosWriteKey (string) – Write key for iOS source.

`Segment.identify(userId)`

Associates the current user with a user ID. Call this after calling Segment.initialize() but before other segment calls. See https://segment.com/docs/spec/identify/.

Arguments

userId (string) – User ID for the current user.

`Segment.identifyWithTraits(userId, traits, options?)`

Arguments

userId (string) – User ID for the current user.
traits (object) – A map of custom properties.
options (object) – (optional) map that can include any of these common fields. Defaults to null.

`Segment.reset()`

Clears the current user. See https://segment.com/docs/sources/mobile/ios/#reset.

`Segment.track(event)`

Log an event to Segment. See https://segment.com/docs/spec/track/.

`Segment.trackWithProperties(event, properties, options?)`

Log an event to Segment with custom properties. See https://segment.com/docs/spec/track/.

Arguments

event (string) – The event name.
properties (object) – A map of custom properties.
options (object) – (optional) map that can include any of these common fields. Defaults to null.

`Segment.group(groupId)`

Associate the user with a group. See https://segment.com/docs/spec/group/.

Arguments

groupId (string) – ID of the group.

`Segment.groupWithTraits(groupId, traits, options?)`

Associate the user with a group with traits. See https://segment.com/docs/spec/group/.

Arguments

groupId (string) – ID of the group.
traits (object) – free-form dictionary of traits of the group.
options (object) – (optional) map that can include any of these common fields. Defaults to null.

`Segment.alias(newId, options?)`

Associate current identity with a new identifier. See https://segment.com/docs/spec/alias/.

Arguments

newId (string) – Identifier to associate with.
options (object) – (optional) extra dictionary with options for the call, see here for possible configuration options. An example options object would be:

{
  "integrations": {
    "Sentry": {
      "enabled": true
    }
  },
  "context": {
    "ip": "0.0.0.0"
  }
}

Returns

A Promise resolving to a boolean indicating whether the method has been executed on the underlying Segment instance or not.

`Segment.screen(screenName)`

Record that a user has seen a screen to Segment. See https://segment.com/docs/spec/screen/.

Arguments

screenName (string) – Name of the screen.

`Segment.screenWithProperties(screenName, properties, options?)`

Record that a user has seen a screen to Segment with custom properties. See https://segment.com/docs/spec/screen/.

screenName (string) – Name of the screen.
properties (object) – A map of custom properties.
options (object) – (optional) map that can include any of these common fields. Defaults to null.

`Segment.flush()`

Manually flush the event queue. You shouldn't need to call this in most cases.

Opting out (enabling/disabling all tracking)

Depending on the audience for your app (e.g. children) or the countries where you sell your app (e.g. the EU), you may need to offer the ability for users to opt-out of analytics data collection inside your app. You can turn off forwarding to ALL destinations including Segment itself: (Source – Segment docs)

import * as Segment from 'expo-analytics-segment';

Segment.setEnabledAsync(false);

// Or if they opt-back-in, you can re-enable data collection:
Segment.setEnabledAsync(true);

Note: disabling the Segment SDK ensures that all data collection method invocations (eg. track, identify, etc) are ignored.

This method is only supported in standalone and detached apps. In Expo client the promise will reject.

The setting value will be persisted across restarts, so once you call setEnabledAsync(false), Segment won't track the users even when the app restarts. To check whether tracking is enabled, use Segment.getEnabledAsync() which returns a promise which should resolve to a boolean.