Flurry Destination

Segment makes it easy to send your data to Flurry (and lots of other destinations). Once you've tracked your data through our open source libraries we'll translate and route your data to Flurry in the format they understand. Learn more about how to use Flurry with Segment.

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

Getting Started

To get started with Flurry and Segment, you’ll want to first integrate your mobile app with our iOS or Android sources. Flurry can only accept data sent directly from their iOS and Android SDKs. For that reason we can only send data directly from our iOS and Android SDKs to Flurry. Data recorded in our server-side sources, Xamarin, or Analytics.js cannot be sent to Flurry.

Once the Segment library is integrated with your app, toggle Flurry on in your Segment destinations, and add your application’s API Key which you can find in your Flurry 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!

The next thing you’ll want to do is identify the user, so that Flurry can give you more user-centric data.

Note: Flurry does not display data in real time. We’ve seen that it can take anywhere from a few hours to a few days for certain types of data to sync with Flurry.


The first thing you’ll want to do is to identify a user with any relevant information as soon as they log-in, or sign-up. You record this with our identify method.

identify takes the userId of a user and any traits you know about them.

When you call identify, we’ll set the user ID in Flurry, and set any special Flurry traits you provide, such as gender, or age.


Next you’ll want to track your user’s behavior so that you can figure out how to increase engagement, virality, or whatever key action is critical to your business. You can use the track method to do this.

Whenever you call track from our iOS or Android library, we’ll log an event with Flurry.

Supported Sources and Connection Modes

📱 Device-based
☁️ Cloud-based

To learn more about about Connection Modes and what dictates which we support, see here.

This destination requires a Device-based Connection Mode for Mobile data. Follow the steps above to ensure you have packaged the Flurry SDK with Segment’s.


Segment lets you change these destination settings via your Segment dashboard without having to touch any code.


You can find your API Key on the Flurry Manage App Info page.

Log Uncaught Exceptions to Flurry

Enabling this will log uncaught exceptions.

Collect User Location

Enabling this will send tell the Flurry SDK to automatically collect the user location.

Screen Tracks As Events

Enabling this will send data through screen calls as events (in addition to pageviews).

Session Continue Seconds

The number of seconds the app can be in the background before starting a new Flurry session upon resume. Default from Flurry is 10 seconds.

Send Data to Flurry Over HTTPS

Enabling this will send data to Flurry securely. This option is ignored for the latest versions of the Flurry SDK, which use HTTPS by default.

If you have any questions, or see anywhere we can improve our documentation, please let us know!