Crittercism Destination

Crittercism quick info

Crittercism accepts Group, Identify, and Track calls. If you reference it in the Integrations object, call it “Crittercism”.

Crittercism accepts device-mode data only from a mobile source.

Our Crittercism destination code is open sourced on GitHub. Feel free to check it out: iOS, Android.

Getting Started

To get started with Crittercism and Segment, you’ll want to integrate our Android or iOS SDK into your mobile app.

Once the Segment library is integrated with your app, toggle Crittercism on in your Segment destination catalog, and add your App Id which you can find in your Crittercism app settings. These new settings will take up to an hour to propagate to all of your existing users. For new users it’ll be instantaneous!

React Native set up

To add the Crittercism device-mode SDK to a React Native project:

  1. Navigate to the root folder of your project, and run a yarn add @segment/analytics-react-native-crittercism command to add the destination SDK to your project.
  2. Add an import statement to your project, as in the example below.
    import Crittercism from '@segment/analytics-react-native-crittercism'
  3. In the same project file, add the destination to the using list in the await command.
    await analytics.setup('YOUR_WRITE_KEY', {
      // Add any of your Device-mode destinations. This ensures they load before continuing.
      using: Crittercism
      // ...
  4. Finally, change to your iOS development folder ( cd ios ) and run pod install.


Crittercism can show you information about the user using your app. You can record that info with our identify method. You should put the identify call as soon as you know the user’s identity. This usually happens after they register or log in.


When an error occurs, you’ll want to know what user actions led to the crash. Crittercism allows you to leave “breadcrumbs” for this purpose.

Whenever you call track, we’ll leave a breadcrumb in Crittercism. Track takes the name of the event and any optional properties you want to associate with the event.

Supported Sources and Connection Modes

Before you start, make sure Crittercism supports the source type and connection mode you’ve chosen to implement. You can learn more about connection modes here.

Web Mobile Server
📱 Device-mode ⬜️ ⬜️
☁️ Cloud-mode ⬜️ ⬜️ ⬜️

This destination requires that you use a Device-based Connection Mode for Mobile data. Make sure you package the Crittercism mobile SDK with the Segment mobile library.


Segment lets you change these destination settings from the Segment app without having to touch any code.

Setting Description
App ID
string. You can find your App ID on the Crittercism Settings page. It should be 24 characters long, and look something like this: 93ac1026a7928a581c000002.
Custom Version Name (Android) string. Override the default version name of your app that is reported to Crittercism (Android only). Check out the Crittercism docs for more info.
Enable Service Monitoring (Android) boolean, defaults to TRUE .

Whenever an app makes a network call, Crittercism monitors and captures certain information automatically (Android only). Check out the Crittercism docs for more info.
Include the Version Code (Android) boolean, defaults to FALSE .

This will include the version code from the manifest file in your app’s version name (Android only). Check out the Crittercism docs for more info.
Monitor Web View (iOS) boolean, defaults to FALSE .

Monitor network traffic generated by UIWebViews (iOS only). Check out the Crittercism docs for more info.
Collect Logcat Data (Android) boolean, defaults to FALSE .

If you want to include system log data in your crash logs, enable this setting (Android only). Check out the Crittercism docs for more info.

This page was last modified: 23 Mar 2021

Get started with Segment

Segment is the easiest way to integrate your websites & mobile apps data to over 300 analytics and growth tools.
Create free account