Flurry Destination
Flurry quick info
Flurry accepts Page, Alias, Group, Identify, and Track calls. If you reference it in the Integrations object, call it “Flurry”.
Flurry accepts device-mode data only from a mobile source.
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, let us know!
Getting Started
Before you start, make sure Flurry 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 | ⬜️ | ⬜️ | ⬜️ |
- From the Segment web app, click Catalog.
- Search for “Flurry” in the Catalog, select it, and choose which of your sources to connect the destination to.
- 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”.
- Follow the instructions in the GitHub repos: iOS SDK and Android SDK.
- 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.
React Native set up
To add the Flurry device-mode SDK to a React Native project:
- Navigate to the root folder of your project, and run a
yarn add @segment/analytics-react-native-flurry
command to add the destination SDK to your project. - Add an
import
statement to your project, as in the example below.import Flurry from '@segment/analytics-react-native-flurry'
- In the same project file, add the destination to the
using
list in theawait
command.await analytics.setup('YOUR_WRITE_KEY', { // Add any of your Device-mode destinations. This ensures they load before continuing. using: Flurry // ... })
- Finally, change to your iOS development folder (
cd ios
) and runpod install
.
Screen
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.
Identify
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:
[[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’re not familiar with the Segment Specs, 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"));
Settings
Segment lets you change these destination settings from the Segment app without having to touch any code.
Setting | Description |
---|---|
API Key (required) |
string . You can find your API Key on the Flurry Manage App Info page. |
Log Uncaught Exceptions to Flurry | boolean , defaults to FALSE . Enabling this will log uncaught exceptions. |
Collect User Location | boolean , defaults to TRUE . Enabling this will send tell the Flurry SDK to automatically collect the user location. |
Screen Tracks As Events | boolean , defaults to TRUE . Enabling this will send data through screen calls as events (in addition to pageviews). |
Session Continue Seconds | number , defaults to 10. 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 | boolean , defaults to TRUE . 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. |
This page was last modified: 23 Mar 2021
Need support?
Questions? Problems? Need more info? Contact us, and we can help!