Flurry provides analytics and advertising solutions. Their analytics services include demographic, traffic source, and event reporting.
Flurry has limits around the number of unique event names and attributes their platform can process as noted here: https://developer.yahoo.com/flurry/docs/analytics/gettingstarted/events/ios/
In order to activate mParticle’s integration with Flurry, you will need the Flurry Project API Key for each app that you’d like to setup.
All purchase events logged via mParticle’s eCommerce SDK methods will be forwarded to Flurry as though they were logged using Flurry’s
logEventWithParameters SDK methods.
All calls to mParticle’s
logScreen SDK method will be forwarded to Flurry as Page Views - equivalent to a call to Flurry’s
logPageView SDK method. The page name will match the screen name passed to the
All Screen Views that are automatically tracked by mParticle’s Android SDK will also be forwarded to Flurry as Page Views.
mParticle will forward all app events with an
eventValue attribute as Timed Events to Flurry. You will need to manually manage the timing of the events that you’d like to measure.
By default, mParticle will forward the appropriate Device ID (IDFA on iOS and Android ID on Android) to Flurry as the User ID. Alternatively, if “Use CustomerId” is enabled, mParticle will use
MPUserIdentityCustomerId (or its hash if “Hash CustomerId” is enabled) when available and the hash of device id otherwise.
If “Include user attributes” is enabled, mParticle will forward users’
$Gender attributes to Flurry, to enable demographic reporting.
If mParticle’s location tracking SDK functionality is enabled in your app, mParticle will forward location information to Flurry. The forwarded location data will correspond to the user’s location at the time that his/her app session ended (mParticle forwards event data to Flurry in batches that correspond to full user sessions).
|Setting Name||Data Type||Default Value||Description|
||Your app’s Flurry Project API Key.|
|Setting Name||Data Type||Default Value||Platform||Description|
|Hash Customer ID||
||True||All||If enabled, mParticle will hash your users’ Customer ID values before forwarding them to Flurry. You should enable this if your Customer ID values contain PII (personally identifying information). Please note that if filtering is configured to exclude forwarding the Customer ID, this configuration parameter has no effect.|
|Track Geographic Location||
||True||All||If enabled, Flurry will track where your app is being used and report this back to you at the city level. Otherwise, Flurry will use the IP address of the user’s device and report this information at the country level.|
||False||All||Used to allow the Flurry SDK to report uncaught exceptions|
Was this page helpful?