Flurry Destination

Flurry provides you with the tools and resources you need to gain a deep level of understanding about your users’ behavior in your apps.

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

This document was last updated on January 10, 2019. If you notice any gaps, outdated information or simply want to leave some feedback to help us improve our documentation, please let us know!

Getting Started

The first step is to make sure Flurry supports the source type and connection mode you’ve chosen to implement. You can learn more about what dictates the connection modes we support here.

WebMobileServer
📱 Device-mode
☁️ Cloud-mode
  1. From your Segment UI’s Destinations page click on “Add Destination”.
  2. Search for “Flurry” within the Destinations Catalog and confirm the Source you’d like to connect to.
  3. Drop in your Flurry “API Key” in Segment’s Settings UI. You can retrieve this from your Flurry Admin > Apps > API Key. It should look like “4KKKGS3BAK4WW8WJ93DN”.
  4. Follow the instructions in the Github repos: iOS SDK and Android SDK.
  5. Once the Segment library is integrated with your app, toggle Flurry on in your Segment UI.

Note: Flurry does not always 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.

Screen

If you haven’t had a chance to review our spec, please take a look to understand what the Screen method does.

An example iOS call would look like:

[[SEGAnalytics sharedAnalytics] screen:@"Home"];

An example Android call would look like:

Analytics.with(context).screen("Feed");

Note: When you toggle the Screen Tracks As Events option on in your Flurry Segment UI - we will treat screen calls as events when sending them to Flurry.

Identify

If you haven’t had a chance to review our spec, please take a look to understand what the Identify method does.

An example iOS call would look like:

[[SEGAnalytics sharedAnalytics] identify:@"f4ca124298", traits: @{
    @"age" : @"23",
    @"gender" : @"Male"
}];

An example Android call would look like:

Analytics.with(context).identify("f4ca124298", new Traits().putAge("23").putGender("Male"));

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.

Track

If you haven’t had a chance to review our spec, please take a look to understand what the Track method does.

An example iOS call would look like:

[[SEGAnalytics sharedAnalytics] track:@"Item Purchased"
                           properties:@{ @"item": @"Sword of Heracles", @"revenue": @2.95 }];

An example Android call would look like:

Analytics.with(context).track("Signed up", new Properties().putValue("plan", "Enterprise"));

This destination requires Device-mode for Mobile data. Follow the steps above packaged the Flurry SDK with Segment’s.

Settings

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

API Key

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.

Adding Flurry to the integrations object

To add Flurry to the integrations JSON object (for example, to filter data from a specific source), use one of the 1 valid names for this integration:
  • Flurry


  • Questions? Need help? Contact us!
    Can we improve this doc?
    Email us: docs-feedback@segment.com!