Product Insights

How to Create Custom Dashboards

LisaMoshfegh — Tue, 13 Apr 2021 17:04:09 +0000

How to Create Custom Dashboards

By Mohamed Kahiye, Product Manager

LisaMoshfegh Tue, 04/13/2021 - 10:04

2021-04-13

Tags

Product Insights

Product News

Building a Custom Dashboard in Flurry Analytics is not only simple, but it takes just a few seconds and will save you time in the future when you need to review the product metrics that matter for your business. You can create unlimited dashboards, each with a specific audience or feature in mind.

Step 1: On any report measuring app sessions, activity, or event data, click the star icon in the top right corner.
Step 2: In the drop-down menu, you can name the report and either save it to an existing dashboard or create a new dashboard. Note that you can save a report to multiple dashboards.
Step 3: Easily access your dashboards by clicking the star icon in Flurry’s left hand navigation menu.

For example, many customers have created separate dashboards to measure iOS apps and Android apps separately, or dashboards by region or territory.

To view your custom dashboards, click the Dashboards icon--which is the star icon--on Flurry’s main navigation bar on the far left side of our developer portal. From there, you’ll be able to access all the different dashboards you have created.

Any dashboards created in the developer’s portal are automatically saved in the Flurry mobile app, and vice versa, meaning your most important metrics are with you on-the-go. Our goal at Flurry Analytics is to make product insights more accessible to app developers and help them build better apps that users love. Flurry Custom Dashboards are a new way for Flurry customers to conveniently view the product metrics they care about in one place. If you’ve used our new feature, we would love to hear from you. We welcome your feedback at support@flurry.com.

How to Build a Conversion Funnel for your Mobile App

LisaMoshfegh — Tue, 30 Mar 2021 21:06:50 +0000

How to Build a Conversion Funnel for your Mobile App

By Lisa Moshfegh, Product Marketing

LisaMoshfegh Tue, 03/30/2021 - 14:06

2021-03-29

Tags

Product Insights

Mobile app conversion funnels measure your app users as they complete a series of steps in your mobile application. Understanding the key conversion moments in your app is key to building a successful app business. In this post, we’ll walk you through how to create your first conversion funnel in Flurry Analytics.

An example of a conversion funnel would be completing a series of onboarding steps or signing up for an account. Conversion funnels can either directly generate revenue, such as completing a purchase or viewing an advertisement, or they can drive engagement, such as signing up for an email newsletter or creating an account.

Creating an account and integrating Flurry’s SDK takes about 5 minutes. To get the most out of Flurry’s Conversion Funnel analysis, make sure you have your app’s custom events integrated.

Building a Simple Mobile Conversion Funnel in Flurry Analytics

Step 1: Login to Flurry Analytics

Step 2: Choose Your Conversion Funnel’s Settings

Select your preferred time zone, the type of chart you’d like to see, and the type of conversion. We offer two types of funnels: User Conversion and Repeated Conversion. A User Conversion is a conversion funnel that a user would complete one time only, such as launching the app and completing the onboarding process. A Repeated Conversion is a recurring conversion funnel that users can complete repeatedly.

Step 3: Select the Key Steps in Your Conversion Funnel

Select steps that complete your funnel. In our example, we’re using Install, userRegistration, and InAppPurchase. Let’s see how this basic funnel looks.

The solid blue bars represent the users who entered each step. In this case, we’re using a waterfall chart and the diagonal blue and white lines represent the drop off from the prior step. If you hover over each step with your cursor, you will see actual numbers and percentages.

Step 4: Add Constraints

Add constraints to each step for deeper analysis with the “Add Constraint” button. For example, you could analyze users who registered through a particular registration channel, or users who spent over a certain dollar amount.

Deeper Analysis Through Filters and Breakouts

Once your funnel is built, you can run more analysis using filters and breakouts. Filters allow you to filter out data you are not interested in seeing in your funnel. Breakouts allow you to break out each step by certain parameters. Let’s review an example of each.

If you select the Breakout drop-down you will be able to choose from a variety of breakouts: device type, country, estimated age and gender, and many more. Let’s choose Estimated Age.

In the example above, we have broken out our funnel by estimated age to allow you to measure the different conversion rates of different age brackets. Next, we’ll try a filter. Let’s say you only care about adults aged 18 - 44 and want to filter out app users under 18 or over 44. Click the “+ Add Filter” button and select “Estimated Age” to choose the three age brackets we’re interested in: 18 - 24, 25 - 34, and 35 - 44. Click “Run” to see your conversion funnel for app users between 18 and 44 years old.

Here, you see the same mobile conversion funnel, but it only includes adults aged 18 - 44 years old, and has filtered out any user that does not fall within that age range.

The default time period when you run a conversion funnel is the past 365 days, but you can use the Session Date filter to specify a more precise time period. For example, if you have focused on optimizing a particular step in the past 30 days, you would select “within the last 30 days” to see your more recent conversion funnel.

Once you have built your conversion funnel, you can easily download and export your data if needed, or save your funnel for future use. You can even set your funnel to private so only you can access it, or set it to public and make it available to all Flurry users associated with your app. Building and analyzing your app’s conversion funnel over time can help boost user engagement and ultimately increase revenue. If you have any questions about using Flurry Analytics for conversion funnel analysis, please contact us at support@flurry.com.

What App Developers Need to Know about Apple’s App Tracking Transparency

LisaMoshfegh — Fri, 26 Feb 2021 18:38:23 +0000

What App Developers Need to Know about Apple’s App Tracking Transparency

By David Lundell, Head of Product Management, Flurry Analytics

LisaMoshfegh Fri, 02/26/2021 - 10:38

2021-02-26

Tags

Product Insights

ios 14

Apple

Q: What is App Tracking Transparency?

Apple will soon implement new privacy protocols that require app developers to obtain authorization to track users across apps and websites owned by other companies. If your app collects data about end users and shares that data with other companies, you must present a tracking authorization prompt.

Q. Can I still use Flurry Analytics once Apple launches App Tracking Transparency?

Yes! Apple has indicated that first party analytics providers are not subject to required tracking opt-in. Flurry does not rely on the Identifier for Advertisers (IDFA), fingerprinting or other device IDs which would require end-user opt-in. Flurry leverages the Identifier for Vendors (IDFV) for first-party analytics, an Apple approved use.

Q: Do I need to present a tracking prompt to my users because my app includes the Flurry SDK?

No. Invoking the opt-in prompt in iOS 14 is completely up to you. You decide when to prompt for authorization - or even whether to invoke the prompt at all. Your analytics from Flurry won’t be impacted by whether you display the prompt for opt-in authorization.

Q. Will Flurry only provide analytics for users that opt in?

No. Flurry provides analytics reporting on all of your users regardless of opt-in state.

Q: When will Apple launch App Tracking Transparency?

Starting with the beta versions of iOS 14.5, iPadOS 14.5, and tvOS 14.5, developers will be required to ask users for their permission to track them. We are still waiting for Apple to announce when these will be widely released, but industry insiders predict sometime in March.

Q: What do I need to do on my app’s product page in the App Store?

Developers that work with Flurry need to acknowledge and detail the Data Use around each type of data Flurry collects. As a Flurry Analytics customer, you MUST select the following Data Types as they are collected by Flurry Analytics: Device ID, Product Interaction, Other Usage Data. Optionally, if you use Flurry Crash Analytics, you must select the following Data Types: Crash Data, Performance Data. If you use Flurry Revenue Analytics, you must select the following: Purchases.

Please see this blog post for detailed steps to update your app’s data collection practices as they relate to Flurry Analytics. The information we are providing is only relevant to your use of Flurry Analytics. Based on your own app’s data collection practices or those of other third-parties you work with, you may need to select additional data types.

Q: Do I need to upgrade to Flurry’s latest SDK to be compliant with Apple’s App Tracking Transparency?

No. Flurry customers will continue to receive the same data and services from Flurry Analytics regardless of SDK version. We recommend minimum Android Flurry SDK v.12.0.0 and minimum iOS Flurry SDK v10.0.0.

To take advantage of Flurry’s Conversion Value analytics, upgrade to the latest version of the Flurry SDK. For more information on how to use Conversion Value to measure post-install campaign campaign effectiveness and LTV, please see this blog post.

Q: Does Flurry respect end user App Tracking Transparency authorization (i.e. user tracking opt-in)?

Flurry will respect Apple’s policy requirement to not combine data across apps and websites owned by other companies in cases where end users have not provided affirmative consent to tracking. In other words, Flurry doesn’t track unless the app obtains tracking consent.

Q: What does ATT mean for me as an app publisher who relies on advertising revenue?

Today, Ad Networks and Demand Side Platforms use the IDFA to reach target audiences. When the IDFA becomes largely unavailable, advertisers will have fewer tools for targeting and attribution. As a result, ad spending will likely drop, leading to lower CPMs and fill for application publishers. For more details on how ATT will likely impact app developers who rely on advertising revenue - and for how Flurry can help - please read our blog post.

Q: What does ATT mean for me as an app publisher who relies on advertising to drive user acquisition?

In the pre-iOS 14 world, Mobile Measurement Partners (MMPs) used IDFAs to provide app install campaign performance insights. With freely collected IDFAs, advertisers could learn which app showed an ad, the specific campaign and creative used to drive an install, and even actions taken by end users after downloading an advertised app. As we enter a new era in which the majority of IDFAs will no longer be available, this traditional mobile attribution model will be impacted. To address the gap it is creating for MMPs, Apple has improved its own SKAdnetwork framework. To learn more about how Flurry can help you leverage SKAdnetwork, please read our blog post here.

Q: What is SKAdnetwork?

SKAdnetwork is Apple’s solution to attribution challenges, including those introduced by the App Tracking Transparency framework. SKAdnetwork helps advertising apps and ad networks connect their campaigns to installs. For end users that have not opted into tracking, SKAdnetwork metadata is the only way for apps to measure campaign impact on installs.

Q: What is SKAdnetwork Conversion Value?

For end users that have not opted into tracking, Conversion Value is the only indicator beyond the install event to gauge the quality of the install. Conversion Value is a six bit value set by the app after users launch a new app for the first time. Apps can update the conversion value within 24 hours. Updating the value automatically resets a 24-hour timer, which postpones the SKAdnetwork postback to ad networks. With up to 64 different values and a limited time in which to set those values, apps will need to be smart about using Conversion Value to effectively describe and predict the user’s expected lifetime value. No matter how you choose to set your Conversion Value, Flurry can help you better understand lifetime value by automatically setting the Conversion Value as a Standard User Property. Please see this blog post for details.

Flurry is here to help navigate app developers through this disruption of traditional app business models. Please contact us at support@flurry.com if you have any questions.

How to Leverage Flurry Crash Analytics & Reporting to Improve Mobile App User Experience

LisaMoshfegh — Wed, 16 Dec 2020 16:05:02 +0000

How to Leverage Flurry Crash Analytics & Reporting to Improve Mobile App User Experience

By Bisera Ferrero, Director of Flurry Engineering

LisaMoshfegh Wed, 12/16/2020 - 08:05

2020-12-16

Tags

Product News

Product Insights

App developers must find new opportunities to delight app users while also increasing an app’s profitability. And on top of creating an engaging user experience, driving user acquisition, or finding new ways to monetize, the ability to quickly resolve crash incidents is essential for sustaining a positive user experience.

Flurry Crash Analytics simplifies identifying and responding to crashes, errors, and exceptions in a mobile app. It does so by giving you, the app developer, the tools to completely reconstruct the crash (bug) in order to isolate its cause. Although the basic setup to get the crash information is easy, the enhanced setup requires a bit of additional planning, but it allows you to harness the full power of Flurry Crash analytics.

When fully leveraged, the Flurry Crash Analytics UI displays the events, breadcrumbs, and crash details in a single time ordered list capturing all pieces of information related to the session in which the crash occurred. This unified view can provide sufficient information required to reproduce the steps that led to a crash and as such can be of great help when improving the code to address the reported crash.

Fig. 1: The Flurry Crash Analytics user interface displays the events, breadcrumbs, and crash details in a list.

Getting Started with Flurry Crash for iOS & Android

Crash reporting is a standard feature of the Flurry Analytics SDK. In other words, integrating Flurry Crash Analytics does not require a separate SDK.

Getting started with Flurry Crash Analytics is easy. If your app is already integrated with Flurry, skip ahead to Step 3.

Step 1: Sign up for a free account and add your app to Flurry.

Step 2: Integrate Flurry’s SDK in about 5 minutes. You can do this via CocoaPods (iOS), jcenter (Android), or let us walk you through easy integration steps. Find step-by-step integration instructions for iOS, Android, React Native, or Unity in our documentation pages. Once you complete this step, your app’s data will flow into your Flurry dashboard.

Step 3: Enable Flurry Crash with an additional line of code:

iOS: In iOS, only a single crash processor can be active. For this reason, the Flurry Analytics SDK does not enable crash by default and requires you to enable it explicitly.

ObjectiveC example:

FlurrySessionBuilder* builder = [[FlurrySessionBuilder new]
                                 withCrashReporting:YES];
[Flurry startSession:flurryAPIKey withSessionBuilder:builder];

Android: On Android, Crash Analytics is enabled by default and requires no explicit call to send Crashes to Flurry Analytics. This means that data for your Android apps is already flowing into Flurry Crash Analytics. For Caught Exceptions and Logged Errors, you can optionally update your error handling methods, with the method call below, to log these issues into Flurry:

new FlurryAgent.Builder()
        ...
        .withCaptureUncaughtExceptions(true)
        ...
        .build(this, FLURRY_API_KEY);

React Native:

new FlurryAgent.Builder()
        ...
        .withCrashReporting(true)
        ...
        .build(FLURRY_ANDROID_API_KEY, FLURRY_IOS_API_KEY);

Unity:

      new Flurry.Builder()
                  .WithCrashReporting(true)
                  ...
                  .Build(FLURRY_API_KEY);

With this basic setup, the Flurry Dashboard will be reporting on all the crashes in your app.

Fig. 2: With basic setup complete on iOS or Android, the Flurry Dashboard will be reporting on all the crashes in your app.

Journey to Crash: How to Log the Events Leading Up to a Crash

To help developers efficiently isolate the causes of the app crash and to resolve the bug that resulted in the crash, Flurry Crash Analytics exposes the additional features: the upload of the mapping files and Breadcrumbs. Flurry Crash Analytics creates a Journey to Crash - the time ordered list capturing all the steps that led to the crash. In addition, it combines all the CustomEvents logged within the app prior to the crash.

Mapping Files Upload

To get details of every crash, error, and exception, including the number of occurrences and the detailed stack trace, upload your dSYM or Proguard mapping files in the Single App Overview section.

You can also integrate the mapping file upload with your development workflow. The scripts to do so, for iOS and Android apps, are available on Flurry’s Github repository.

Fig. 3: Upload mapping files for iOS or Android apps to help developers efficiently isolate the causes of the app crash.

Breadcrumbs

As the name implies, the Breadcrumbs are just that, traces of information left throughout the app’s code to help trace the flow of events a user experienced leading up to the crash. The app developers leave the Breadcumbs throughout the code, capturing the valuable information to help themselves understand the execution of code outside of what's recorded in the stack trace. Knowing the sequence of things the user did within the app before it crashed, helps developers reproduce the crash and diagnose the problem.

Add the breadcrumbs throughout your code using the Flurry SDK API to log the breadcrumbs:

Android:

FlurryAgent.logBreadcrumb(BREADCRUMB_ERROR_MESSAGE);

iOS:

[Flurry leaveBreadcrumb:@"BREADCRUMB_ERROR_MESSAGE"];

Custom Events

To enhance crash reporting and identify exactly where crashes occur in your app, integrate custom events. With custom events integrated, you will unlock endless possibilities to analyze your app’s audience and how your users use your app. For step-by-step instructions, please visit our documentation pages for iOS and Android.

Real Time Crash Analytics & Reporting!

Flurry Crash Analytics gives you a number of tools to tune into the crashes as soon as they are happening.

Realtime Crash Dashboard is, just as the name implies—a real time numerical chart of the crashes happening without specific details as to what those crashes are.

Fig. 4: Flurry’s Realtime Crash Dashboard reports app crashes in real time.

To dig deeper and to get the accurate, timely information of the crashes as they are happening in real time, there are further options:

Jira Integration

Integrate your Jira Cloud instance and Flurry Crash Analytics will automatically create a ticket in your Jira instance as soon as a crash occurs, for the first time.

Slack Integration

Similarly to Jira Integration, after you provide Flurry with the webhook URL of the slack channels where the alerts are to be delivered, Flurry Crash Analytics will be sending all the new crash incidents to that slack channel.

Crash Alerts (email, Slack, and push notifications)

You can monitor crash occurrences, such as Total Errors, Symbolicated Crash Devices, Symbolicated Crash Occurrences, Symbolicated Crash Impact Rate and receive alerts via email, Slack or - if you have the Flurry mobile app - as push notifications.

Visit Flurry’s Crash dashboard to begin reviewing and addressing the individual crashes in your app. You are now all set to manage and respond to crashes, errors and exceptions in your mobile app. Please see our documentation pages for more detailed information or reach out to us at support@flurry.com with any additional questions.