Skip to contentSkip to navigationSkip to topbar
On this page
Looking for more inspiration?Visit the
(information)
You're in the right place! Segment documentation is now part of Twilio Docs. The content you are used to is still here—just in a new home with a refreshed look.

Flurry Destination


Destination Info
  • Accepts Page, Alias, Group, Identify and Track calls.
  • Refer to it as Flurry in the Integrations object
Connection Modes
Device-modeCloud-mode
Web Web
Mobile Mobile
Server Server

Flurry(link takes you to an external page) 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(link takes you to an external page), Android(link takes you to an external page).


Getting Started

getting-started page anchor
  1. From the Segment web app, click Catalog.
  2. Search for "Flurry" in the Catalog, select it, and choose which of your sources to connect the destination to.
  3. In the destination settings, enter 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(link takes you to an external page) and Android SDK(link takes you to an external page).
  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.


If you're not familiar with the Segment Specs, 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.


If you're not familiar with the Segment Specs, take a look to understand what the Identify method does.

An example iOS call would look like:

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

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.


If you're not familiar with the Segment Specs, take a look to understand what the Track method does.

An example iOS call would look like:

1
[[SEGAnalytics sharedAnalytics] track:@"Item Purchased"
2
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"));

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

Property nameTypeRequiredDescription
API Keystring
required

You can find your API Key on the Flurry Manage App Info page(link takes you to an external page).


Log Uncaught Exceptions to Flurryboolean

Optional

Enabling this will log uncaught exceptions.

Default: false

Collect User Locationboolean

Optional

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

Default: true

Screen Tracks As Eventsboolean

Optional

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

Default: true

Session Continue Secondsnumber

Optional

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.

Default: 10

Send Data to Flurry Over HTTPSboolean

Optional

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.

Default: true