Product News https://www.flurry.com/ en How to Leverage Flurry Crash Analytics & Reporting to Improve Mobile App User Experience https://www.flurry.com/blog/improve-app-ux-crash-analytics-reporting/ <span class="field field--name-title field--type-string field--label-hidden">How to Leverage Flurry Crash Analytics & Reporting to Improve Mobile App User Experience</span> <div class="field field--name-field-blog-author-and-role field--type-string-long field--label-hidden field__item">By Bisera Ferrero, Director of Flurry Engineering</div> <span class="field field--name-uid field--type-entity-reference field--label-hidden"><span lang="" about="https://www.flurry.com/user/32/" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">LisaMoshfegh</span></span> <span class="field field--name-created field--type-created field--label-hidden">Wed, 12/16/2020 - 08:05</span> <div class="field field--name-field-blog-post-date field--type-datetime field--label-hidden field__item"><time datetime="2020-12-16T12:00:00Z" class="datetime">2020-12-16</time></div> <div class="field field--name-field-blog-tags field--type-entity-reference field--label-inline"> <div class="field__label">Tags</div> <div class="field__items"> <div class="field__item"><a href="https://www.flurry.com/taxonomy/term/3/" hreflang="en">Product News</a></div> <div class="field__item"><a href="https://www.flurry.com/taxonomy/term/299/" hreflang="en">Product Insights</a></div> </div> </div> <span class="a2a_kit a2a_kit_size_32 addtoany_list" data-a2a-url="https://www.flurry.com/blog/improve-app-ux-crash-analytics-reporting/" data-a2a-title="How to Leverage Flurry Crash Analytics & Reporting to Improve Mobile App User Experience"><a class="a2a_button_linkedin"></a><a class="a2a_button_facebook"></a><a class="a2a_button_twitter"></a><a class="a2a_button_google_plus"></a><a class="a2a_dd addtoany_share" href="https://www.addtoany.com/share#url=https%3A%2F%2Fwww.flurry.com%2Fblog%2Fimprove-app-ux-crash-analytics-reporting%2F&title=How%20to%20Leverage%20Flurry%20Crash%20Analytics%20%26%20Reporting%20to%20Improve%20Mobile%20App%20User%20Experience"></a></span> <div class="clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__item"><p><span><span><span><span><span><span>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.</span></span></span></span></span></span><span><span><span><span><span><span> </span></span></span></span></span></span></p> <p><a href="https://www.flurry.com/crash/"><span><span><span><span><span><span><span><span>Flurry Crash Analytics</span></span></span></span></span></span></span></span></a><span><span><span><span><span><span> 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 <span><span>the basic setup</span></span> to get the crash information is easy, the <span><span>enhanced setup requires</span></span> a bit of additional planning, but it allows you to harness the full power of Flurry Crash analytics.</span></span></span></span></span></span></p> <p><span><span><span><span><span><span>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.  </span></span></span></span></span></span></p> <p><img alt="The Flurry Crash Analytics user interface displays the events, breadcrumbs, and crash details in a list" data-entity-type="" data-entity-uuid="" src="https://www.flurry.com/sites/default/files/flurry-crash-analytics-user-interface.png" width="80%/" /></p> <h5><span><span><span><span><em><span>Fig. 1: The Flurry Crash Analytics user interface displays the events, breadcrumbs, and crash details in a list.</span></em></span></span></span></span></h5> <h2><span><span><span><span><span><span>Getting Started with Flurry Crash for iOS & Android</span></span></span></span></span></span></h2> <p><span><span><span><span><span><span>Crash reporting is a standard feature of the Flurry Analytics SDK. In other words, integrating Flurry Crash Analytics does not require a separate SDK. </span></span></span></span></span></span></p> <p><span><span><span><span><span><span>Getting started with Flurry Crash Analytics is easy. If your app is already integrated with Flurry, skip ahead to Step 3. </span></span></span></span></span></span></p> <p><span><span><span><strong><span><span>Step 1:</span></span></strong></span></span></span><span><span><span><span><span><span> </span></span></span></span></span></span><a href="https://login.flurry.com/signup"><span><span><span><span><span><span><span><span>Sign up for a free account</span></span></span></span></span></span></span></span></a><span><span><span><span><span><span> and add your app to Flurry. </span></span></span></span></span></span></p> <p><span><span><span><strong><span><span>Step 2: </span></span></strong></span></span></span><span><span><span><span><span><span> 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 </span></span></span></span></span></span><a href="https://developer.yahoo.com/flurry/docs/integrateflurry/ios/"><span><span><span><span><span><span><span><span>iOS</span></span></span></span></span></span></span></span></a><span><span><span><span><span><span>,  </span></span></span></span></span></span><a href="https://developer.yahoo.com/flurry/docs/integrateflurry/android/"><span><span><span><span><span><span><span><span>Android</span></span></span></span></span></span></span></span></a><span><span><span><span><span><span>, </span></span></span></span></span></span><a href="https://developer.yahoo.com/flurry/docs/integrateflurry/react-native/"><span><span><span><span><span><span><span><span>React Native</span></span></span></span></span></span></span></span></a><span><span><span><span><span><span>, or </span></span></span></span></span></span><a href="https://developer.yahoo.com/flurry/docs/integrateflurry/unity/"><span><span><span><span><span><span><span><span>Unity</span></span></span></span></span></span></span></span></a><span><span><span><span><span><span>  in our documentation pages. </span></span></span></span></span></span><span><span><span><span><span><span>Once you complete this step, your app’s data will flow into your Flurry dashboard.</span></span></span></span></span></span></p> <p><span><span><span><strong><span><span>Step 3:</span></span></strong></span></span></span><span><span><span><span><span><span> Enable Flurry Crash with an additional line of code:</span></span></span></span></span></span></p> <p><span><span><span><span><span><span><strong>iOS: </strong>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. </span></span></span></span></span></span></p> <p><span><span><span><span><span><span>ObjectiveC example:</span></span></span></span></span></span></p> <pre> <code>FlurrySessionBuilder* builder = [[FlurrySessionBuilder new] withCrashReporting:YES]; [Flurry startSession:flurryAPIKey withSessionBuilder:builder]; </code></pre> <p><strong><span><span><span><span><span><span>Android: </span></span></span></span></span></span></strong><span><span><span><span><span><span>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:</span></span></span></span></span></span></p> <pre> <code>new FlurryAgent.Builder() ... .withCaptureUncaughtExceptions(true) ... .build(this, FLURRY_API_KEY); </code></pre> <p><strong><span><span><span><span><span><span>React Native:  </span></span></span></span></span></span></strong></p> <pre> <code>new FlurryAgent.Builder() ... .withCrashReporting(true) ... .build(FLURRY_ANDROID_API_KEY, FLURRY_IOS_API_KEY);</code></pre> <p><strong><span><span><span><span><span><span>Unity:</span></span></span></span></span></span></strong></p> <pre> <code> new Flurry.Builder() .WithCrashReporting(true) ... .Build(FLURRY_API_KEY);</code></pre> <p><span><span><span><span><span><span>With this basic setup, the Flurry Dashboard will be reporting on all the crashes in your app.</span></span></span></span></span></span></p> <p><img alt="With basic setup complete on iOS or Android, the Flurry Dashboard will be reporting on all the crashes in your app." data-entity-type="" data-entity-uuid="" src="https://www.flurry.com/sites/default/files/flurry-dashboard-crash-reporting.png" width="80%" /></p> <h5>Fig. 2: <span><span><span><span><em><span>With basic setup complete on iOS or Android, the Flurry Dashboard will be reporting on all the crashes in your app.</span></em></span></span></span></span></h5> <h2><span><span><span><span><span><span>Journey to Crash: How to Log the Events Leading Up to a Crash</span></span></span></span></span></span></h2> <p><span><span><span><span><span><span>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.  </span></span></span></span></span></span></p> <h3><span><span><span><strong><span><span>Mapping Files Upload</span></span></strong></span></span></span></h3> <p><span><span><span><span><span><span>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 </span></span></span></span></span></span><a href="https://dev.flurry.com/developer/crash/overview"><span><span><span><span><span><span><span><span>Single App Overview</span></span></span></span></span></span></span></span></a><span><span><span><span><span><span> section. </span></span></span></span></span></span></p> <p><span><span><span><span><span><span>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 </span></span></span></span></span></span><a href="https://github.com/flurry/upload-clients"><span><span><span><span><span><span><span><span>Flurry’s Github repository</span></span></span></span></span></span></span></span></a><span><span><span><span><span><span>. </span></span></span></span></span></span></p> <p><span><span><span><span><span><span><img alt="Upload mapping files for iOS or Android apps to help developers efficiently isolate the causes of the app crash" data-entity-type="" data-entity-uuid="" src="https://www.flurry.com/sites/default/files/flurry-crash-upload-mapping-files.png" width="80%" /></span></span></span></span></span></span></p> <h5>Fig. 3: <span><span><span><span><em><span>Upload mapping files for iOS or Android apps to help developers efficiently isolate the causes of the app crash.</span></em></span></span></span></span></h5> <h3><span><span><span><strong><span><span>Breadcrumbs</span></span></strong></span></span></span></h3> <p><span><span><span><span><span><span>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.  </span></span></span></span></span></span></p> <p><span><span><span><span><span><span>Add the breadcrumbs throughout your code using the Flurry SDK API to log the breadcrumbs:</span></span></span></span></span></span></p> <p><strong><span><span><span><span><span><span>Android: </span></span></span></span></span></span></strong></p> <pre> <code>FlurryAgent.logBreadcrumb(BREADCRUMB_ERROR_MESSAGE);</code></pre> <p><strong><span><span><span><span><span><span>iOS: </span></span></span></span></span></span></strong></p> <pre> <code><span style="color: #aaa !important;">[Flurry leaveBreadcrumb:@"BREADCRUMB_ERROR_MESSAGE"];</span></code></pre> <p><span><span><span><strong><span><span>Custom Events</span></span></strong></span></span></span></p> <p><span><span><span><span><span><span>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 </span></span></span></span></span></span><a href="https://developer.yahoo.com/flurry/docs/analytics/gettingstarted/events/ios/"><span><span><span><span><span><span><span><span>iOS</span></span></span></span></span></span></span></span></a><span><span><span><span><span><span> and </span></span></span></span></span></span><a href="https://developer.yahoo.com/flurry/docs/analytics/gettingstarted/events/android/"><span><span><span><span><span><span><span><span>Android</span></span></span></span></span></span></span></span></a><span><span><span><span><span><span>. </span></span></span></span></span></span></p> <h2><span><span><span><span><span><span>Real Time Crash Analytics & Reporting! </span></span></span></span></span></span></h2> <p><span><span><span><span><span><span>Flurry Crash Analytics gives you a number of tools to tune into the crashes as soon as they are happening.  </span></span></span></span></span></span></p> <p><a href="https://dev.flurry.com/metrics/1000"><span><span><span><strong><span><span><span><span>Realtime Crash Dashboard</span></span></span></span></strong></span></span></span></a><span><span><span><span><span><span> is, just as the name implies—a real time numerical chart of the crashes happening without specific details as to what those crashes are. </span></span></span></span></span></span></p> <p><span><span><span><span><span><span><img alt="Flurry Realtime Crash Dashboard reports app crashes in real time." data-entity-type="" data-entity-uuid="" src="https://www.flurry.com/sites/default/files/flurry-real-time-crash-reporting.png" width="80%" /></span></span></span></span></span></span></p> <h5>Fig. 4: <span><span><span><span><em><span>Flurry’s Realtime Crash Dashboard reports app crashes in real time.</span></em></span></span></span></span></h5> <p><span><span><span><span><span><span>To dig deeper and to get the accurate, timely information of the crashes as they are happening in real time, there are further options: </span></span></span></span></span></span></p> <h3><span><span><span><strong><span><span>Jira Integration</span></span></strong></span></span></span></h3> <p><a href="https://developer.yahoo.com/flurry/docs/analytics/crash/jira/"><span><span><span><span><span><span><span><span>Integrate your Jira Cloud instance</span></span></span></span></span></span></span></span></a><span><span><span><span><span><span> and Flurry Crash Analytics will automatically create a ticket in your Jira instance as soon as a crash occurs, for the first time. </span></span></span></span></span></span></p> <h3><span><span><span><strong><span><span>Slack Integration</span></span></strong></span></span></span></h3> <p><span><span><span><span><span><span>Similarly to Jira Integration, after you provide Flurry with the </span></span></span></span></span></span><a href="https://developer.yahoo.com/flurry/docs/analytics/flurryalerts/slack/"><span><span><span><span><span><span><span><span>webhook URL</span></span></span></span></span></span></span></span></a><span><span><span><span><span><span> 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. </span></span></span></span></span></span></p> <h3><span><span><span><strong><span><span>Crash Alerts</span></span></strong></span></span></span><span><span><span><span><span><span> (email, Slack, and push notifications)</span></span></span></span></span></span></h3> <p><span><span><span><span><span><span>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 </span></span></span></span></span></span><a href="https://www.flurry.com/flurry-app/"><span><span><span><span><span><span><span><span>Flurry mobile app</span></span></span></span></span></span></span></span></a><span><span><span><span><span><span> - as push notifications.</span></span></span></span></span></span></p> <p><span><span><span><span><span><span>Visit </span></span></span></span></span></span><a href="https://dev.flurry.com/developer/crash/historical"><span><span><span><span><span><span><span><span>Flurry’s Crash dashboard</span></span></span></span></span></span></span></span></a><span><span><span><span><span><span> 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 </span></span></span></span></span></span><a href="https://developer.yahoo.com/flurry/docs/analytics/crash/crashanalytics/"><span><span><span><span><span><span><span><span>documentation pages</span></span></span></span></span></span></span></span></a><span><span><span><span><span><span> for more detailed information or reach out to us at </span></span></span></span></span></span><a href="mailto:support@flurry.com"><span><span><span><span><span><span><span><span>support@flurry.com</span></span></span></span></span></span></span></span></a><span><span><span><span><span><span> with any additional questions.</span></span></span></span></span></span></p> </div> Wed, 16 Dec 2020 16:05:02 +0000 LisaMoshfegh 587 at https://www.flurry.com Flurry Analytics' Guidance for Apple’s Updated App Data Collection Policy https://www.flurry.com/blog/flurry-guidance-apple-app-privacy-details/ <span class="field field--name-title field--type-string field--label-hidden">Flurry Analytics' Guidance for Apple’s Updated App Data Collection Policy</span> <div class="field field--name-field-blog-author-and-role field--type-string-long field--label-hidden field__item">By Raj Kaur, Senior Manager, Software Development Engineering</div> <span class="field field--name-uid field--type-entity-reference field--label-hidden"><span lang="" about="https://www.flurry.com/user/32/" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">LisaMoshfegh</span></span> <span class="field field--name-created field--type-created field--label-hidden">Mon, 12/07/2020 - 11:57</span> <div class="field field--name-field-blog-post-date field--type-datetime field--label-hidden field__item"><time datetime="2020-12-07T12:00:00Z" class="datetime">2020-12-07</time></div> <div class="field field--name-field-blog-tags field--type-entity-reference field--label-inline"> <div class="field__label">Tags</div> <div class="field__items"> <div class="field__item"><a href="https://www.flurry.com/taxonomy/term/3/" hreflang="en">Product News</a></div> <div class="field__item"><a href="https://www.flurry.com/taxonomy/term/5/" hreflang="en">Apple</a></div> <div class="field__item"><a href="https://www.flurry.com/taxonomy/term/23/" hreflang="x-default">ios</a></div> </div> </div> <span class="a2a_kit a2a_kit_size_32 addtoany_list" data-a2a-url="https://www.flurry.com/blog/flurry-guidance-apple-app-privacy-details/" data-a2a-title="Flurry Analytics' Guidance for Apple’s Updated App Data Collection Policy"><a class="a2a_button_linkedin"></a><a class="a2a_button_facebook"></a><a class="a2a_button_twitter"></a><a class="a2a_button_google_plus"></a><a class="a2a_dd addtoany_share" href="https://www.addtoany.com/share#url=https%3A%2F%2Fwww.flurry.com%2Fblog%2Fflurry-guidance-apple-app-privacy-details%2F&title=Flurry%20Analytics%27%20Guidance%20for%20Apple%E2%80%99s%20Updated%20App%20Data%20Collection%20Policy"></a></span> <div class="clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__item"><p><span><span><span><span><span><span>Apple is changing the information required to submit new apps and app updates to the app store effective December 8, 2020. The new submission process will give users transparency about app data usage via a new privacy details section of an app’s product page in the app store. This  “nutrition label” will also include data used by third-party partners integrated  into an app. If you are not familiar with Apple’s new policy, please familiarize  yourself with it </span></span></span></span></span></span><a href="https://developer.apple.com/app-store/app-privacy-details/"><span><span><span><span><span><span><span><span>here</span></span></span></span></span></span></span></span></a><span><span><span><span><span><span>. This blog post provides guidance on what data Flurry Analytics uses in your app.</span></span></span></span></span></span></p> <p><span><span><span><span><span><span>Developers that work with Flurry need to acknowledge and detail the Data Use around each type of data Flurry collects.  Please note that 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. </span></span></span></span></span></span></p> <p><span><span><span><span><span><span>As a user of  Flurry Analytics, you MUST select the following Data Types as they are collected by Flurry Analytics: </span></span></span></span></span></span><strong><span><span><span><span><span><span>Device ID, </span></span></span></span></span></span><span><span><span><span><span><span>Product Interaction, </span></span></span></span></span></span></strong><span><span><span><span><span><span><strong>Other Usage Data</strong>. </span></span></span></span></span></span><span><span><span><span><span><span>Optionally,  if you use Flurry Crash Analytics, you must select the following Data Types: </span></span></span></span></span></span><strong><span><span><span><span><span><span>Crash Data, </span></span></span></span></span></span></strong><span><span><span><span><span><span><strong>Performance Data</strong>. </span></span></span></span></span></span><span><span><span><span><span><span>If you use Flurry Revenue Analytics, you must select the following: </span></span></span></span></span></span><strong><span><span><span><span><span><span>Purchases.</span></span></span></span></span></span></strong></p> <p><span><span><span><span><span><span>The UI flow on </span></span></span></span></span></span><a href="https://appstoreconnect.apple.com/"><span><span><span><span><span><span><span><span>App Store Connect</span></span></span></span></span></span></span></span></a><span><span><span><span><span><span> is as follows:</span></span></span></span></span></span></p> <p><strong><span><span><span><span><span>Step 1:  Navigate to App Privacy section within App Store Connect and click Get Started </span></span></span></span></span></strong></p> <p><img alt="Apple's Data Privacy Updates - 1" data-entity-type="" data-entity-uuid="" src="https://www.flurry.com/sites/default/files/apple_data_privacy_changes/screen_1.png" width="100%" /></p> <p><strong>Step 2: <span><span><span><span><span>Select  “Yes, we collect data from this app” and select Next</span></span></span></span></span></strong></p> <p><img alt="Apple's Data Privacy Updates - 2" data-entity-type="" data-entity-uuid="" src="https://www.flurry.com/sites/default/files/apple_data_privacy_changes/screen_2.png" width="70%" /></p> <p><strong>Step 3: <span><span><span><span><span>Scroll down and check the boxes for ” Device ID” ,”Product Interaction”, and “Other Usage Data”  and click Save. </span></span></span></span></span></strong></p> <p><img .="" alt="Apple's Data Privacy Updates - 3" data-entity-type="" data-entity-uuid="" src="https://www.flurry.com/sites/default/files/apple_data_privacy_changes/screen_3.png" width="70%" /></p> <p><strong>Step 4: </strong><span><span><span><strong><span><span>Upon saving you will see at least 3 boxes populated in the Privacy Section where you will need to fill in  further information  on the data type being collected. </span></span></strong></span></span></span></p> <p><img alt="Apple's Data Privacy Updates - 4" data-entity-type="" data-entity-uuid="" src="https://www.flurry.com/sites/default/files/apple_data_privacy_changes/screen_4.png" width="70%" /></p> <p><strong>Step 5: <span><span><span><span><span>Click on “Set Up Device ID”  text, select the  “Analytics” checkbox and hit the Next button</span></span></span></span></span></strong></p> <p><img alt="Apple's Data Privacy Updates - 5" data-entity-type="" data-entity-uuid="" src="https://www.flurry.com/sites/default/files/apple_data_privacy_changes/screen_5.png" width="70%" /></p> <p><strong><span><span><span><span><span>Step 6: </span></span></span></span></span></strong><span><span><span><strong><span><span>On the next screen, </span></span></strong></span></span></span><span><span><span><span><strong><span><span>choose the option applicable to your app. Flurry does not link IDs to user identity</span></span></strong></span></span></span></span><span><span><span><strong><span><span>.</span></span></strong></span></span></span></p> <p><img alt="Apple's Data Privacy Updates - 6" data-entity-type="" data-entity-uuid="" src="https://www.flurry.com/sites/default/files/apple_data_privacy_changes/screen_6.png" width="70%" /></p> <p><span><span><span><strong><span><span>Step 7: On the last screen choose the option applicable to your app and click “Save”</span></span></strong></span></span></span></p> <p><img alt="Apple's Data Privacy Updates - 7" data-entity-type="" data-entity-uuid="" src="https://www.flurry.com/sites/default/files/apple_data_privacy_changes/screen_7.png" width="70%" /></p> <p><span><span><span><strong><span><span>Step 8: Repeat steps 5 and 6 for “Product Interaction” and “Other Usage Data” Data types. Once you have finished providing all the necessary information, the App Privacy page should look like the following:</span></span></strong></span></span></span></p> <p><img alt="Apple's Data Privacy Updates - 8" data-entity-type="" data-entity-uuid="" src="https://www.flurry.com/sites/default/files/apple_data_privacy_changes/screen_8.png" width="70%" /></p> <p><span style="font-size:11pt; font-variant:normal; white-space:pre-wrap"><span style="font-family:'Verizon NHG DS',sans-serif"><span style="color:#000000"><span style="font-weight:400"><span style="font-style:normal"><span style="text-decoration:none">If you have any questions, please contact  us at  </span></span></span></span></span></span><a href="mailto:support@flurry.com" style="text-decoration:none"><span style="font-size:11pt; font-variant:normal; white-space:pre-wrap"><span style="font-family:'Verizon NHG DS',sans-serif"><span style="color:#1155cc"><span style="font-weight:400"><span style="font-style:normal"><span style="text-decoration:underline"><span style="-webkit-text-decoration-skip:none"><span style="text-decoration-skip-ink:none">support@flurry.com</span></span></span></span></span></span></span></span></a><span style="font-size:11pt; font-variant:normal; white-space:pre-wrap"><span style="font-family:'Verizon NHG DS',sans-serif"><span style="color:#000000"><span style="font-weight:400"><span style="font-style:normal"><span style="text-decoration:none">.</span></span></span></span></span></span></p> </div> Mon, 07 Dec 2020 19:57:03 +0000 LisaMoshfegh 584 at https://www.flurry.com Improvements to Flurry Crash for iOS and Android https://www.flurry.com/blog/flurry-crash-for-ios-and-android/ <span class="field field--name-title field--type-string field--label-hidden">Improvements to Flurry Crash for iOS and Android</span> <div class="field field--name-field-blog-author-and-role field--type-string-long field--label-hidden field__item">By Dan Chen, Director of Engineering, Flurry Analytics</div> <span class="field field--name-uid field--type-entity-reference field--label-hidden"><span lang="" about="https://www.flurry.com/user/32/" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">LisaMoshfegh</span></span> <span class="field field--name-created field--type-created field--label-hidden">Fri, 11/13/2020 - 00:47</span> <div class="field field--name-field-blog-post-date field--type-datetime field--label-hidden field__item"><time datetime="2020-11-13T12:00:00Z" class="datetime">2020-11-13</time></div> <div class="field field--name-field-blog-tags field--type-entity-reference field--label-inline"> <div class="field__label">Tags</div> <div class="field__items"> <div class="field__item"><a href="https://www.flurry.com/taxonomy/term/3/" hreflang="en">Product News</a></div> </div> </div> <span class="a2a_kit a2a_kit_size_32 addtoany_list" data-a2a-url="https://www.flurry.com/blog/flurry-crash-for-ios-and-android/" data-a2a-title="Improvements to Flurry Crash for iOS and Android"><a class="a2a_button_linkedin"></a><a class="a2a_button_facebook"></a><a class="a2a_button_twitter"></a><a class="a2a_button_google_plus"></a><a class="a2a_dd addtoany_share" href="https://www.addtoany.com/share#url=https%3A%2F%2Fwww.flurry.com%2Fblog%2Fflurry-crash-for-ios-and-android%2F&title=Improvements%20to%20Flurry%20Crash%20for%20iOS%20and%20Android"></a></span> <div class="clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__item"><p><span><span><span><span><span><span>Our primary goal at Flurry is to help app developers build better apps for mobile users around the world. And we know firsthand how crashes and errors can negatively impact the user experience. To help our customers manage and respond to crashes, errors, and exceptions, we are pleased to announce a set of upgrades to our current Flurry Crash offering for iOS and Android apps. Using Flurry Crash doesn’t require a separate SDK; it’s built into our lightweight Analytics SDK that can be integrated in about 5 minutes. Here’s what’s new:</span></span></span></span></span></span></p> <div class="well values"> <ul class="value"><li><span><span><span><strong><span><span>Upload Mapping Files: </span></span></strong><span><span><span>Now you can upload your dSYM and Proguard mapping files directly into Flurry.</span></span></span></span></span></span> <span><span><span><span><span><span>To get the most detailed mapping files, you can find scripts to upload symbol files that can be integrated with your development workflow for iOS and Android apps on </span></span></span></span></span></span><a href="https://github.com/flurry/upload-clients"><span><span><span><span><span><span><span><span>Flurry’s Github repository</span></span></span></span></span></span></span></span></a><span><span><span><span><span><span>. </span></span></span></span></span></span></li> <li><span><span><span><strong><span><span>Crash Details:</span></span></strong></span></span></span><span><span><span><span><span><span> Once you’ve uploaded the mapping files, you’ll get details on every crash, error and exception, including the number of occurrences and the detailed stack trace so you can respond as soon as possible. Crash detail navigation has been simplified to help you quickly investigate the context for every crash.</span></span></span></span></span></span></li> <li><span><span><span><strong><span><span>Jira Cloud Integration: </span></span></strong></span></span></span><span><span><span><span><span><span>Automatically create a ticket the first time a crash occurs by integrating your Jira instance. </span></span></span></span></span></span></li> </ul></div> <p><img alt="New Flurry Crash Dashboard" data-entity-type="" data-entity-uuid="" src="https://www.flurry.com/sites/default/files/CrashNew2020-1.svg" /></p> <p><span><span><span><span><span><span>For more information on how to implement and use Flurry Crash, please review our documentation </span></span></span></span></span></span><a href="https://developer.yahoo.com/flurry/docs/analytics/crash/#crash-analytics"><span><span><span><span><span><span><span><span>here</span></span></span></span></span></span></span></span></a><span><span><span><span><span><span>. Please feel free to contact us with any questions or comments at </span></span></span></span></span></span><a href="mailto:support@flurry.com"><span><span><span><span><span><span><span><span>support@flurry.com</span></span></span></span></span></span></span></span></a></p> </div> Fri, 13 Nov 2020 08:47:59 +0000 LisaMoshfegh 578 at https://www.flurry.com Will the iPhone 12 Convince Consumers to Replace Older iPhones? https://www.flurry.com/blog/will-the-iphone-12-convince-consumers-to-replace/ <span class="field field--name-title field--type-string field--label-hidden">Will the iPhone 12 Convince Consumers to Replace Older iPhones?</span> <div class="field field--name-field-blog-author-and-role field--type-string-long field--label-hidden field__item">By: Peter Farago, Flurry GM and Aman Bansal, Flurry Analyst</div> <span class="field field--name-uid field--type-entity-reference field--label-hidden"><span lang="" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">Anonymous</span></span> <span class="field field--name-created field--type-created field--label-hidden">Fri, 09/25/2020 - 10:54</span> <div class="field field--name-field-blog-post-date field--type-datetime field--label-hidden field__item"><time datetime="2020-09-25T12:00:00Z" class="datetime">2020-09-25</time></div> <div class="field field--name-field-blog-tags field--type-entity-reference field--label-inline"> <div class="field__label">Tags</div> <div class="field__items"> <div class="field__item"><a href="https://www.flurry.com/taxonomy/term/5/" hreflang="en">Apple</a></div> <div class="field__item"><a href="https://www.flurry.com/taxonomy/term/290/" hreflang="en">App Insights</a></div> <div class="field__item"><a href="https://www.flurry.com/taxonomy/term/3/" hreflang="en">Product News</a></div> </div> </div> <span class="a2a_kit a2a_kit_size_32 addtoany_list" data-a2a-url="https://www.flurry.com/blog/will-the-iphone-12-convince-consumers-to-replace/" data-a2a-title="Will the iPhone 12 Convince Consumers to Replace Older iPhones?"><a class="a2a_button_linkedin"></a><a class="a2a_button_facebook"></a><a class="a2a_button_twitter"></a><a class="a2a_button_google_plus"></a><a class="a2a_dd addtoany_share" href="https://www.addtoany.com/share#url=https%3A%2F%2Fwww.flurry.com%2Fblog%2Fwill-the-iphone-12-convince-consumers-to-replace%2F&title=Will%20the%20iPhone%2012%20Convince%20Consumers%20to%20Replace%20Older%20iPhones%3F"></a></span> <div class="clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__item"><p>When Apple launches its annual line-up of new iPhones each Fall, it creates a surge in device adoption that spans the holiday season. Since the 2017 launch of the completely reimagined iPhone X, improvements to subsequent phones have been incremental, offering gains mainly related to the chipset, camera and screen. Since then Apple has released the iPhone XS and XR variants, the iPhone 11 line up and the 2nd Generation iPhone SE. The iPhone 12, coupled with 5G support, seems poised for stronger than usual uptake. For this analysis, we review the underlying drivers of iPhone device replacement including the relationship between consumer affluence and device age to understand how the upcoming iPhone 12 is positioned for this holiday season.</p> <p><b>Device Obsolescence</b></p> <p>A primary factor that drives new iPhone upgrades is device obsolescence. Apple doesn’t seem to explicitly plan this, but rapid innovation around both their hardware and operating systems results in reduced performance across older devices. Working against the growth of Apple’s annual iPhone unit sales is the fact that consumers are holding on to older devices longer. Today, <a href="https://9to5mac.com/2019/02/08/four-year-smartphone-upgrades/" target="_blank">consumers upgrade iPhones about every four years</a>, compared to every three years back in 2018. For the iPhone 12 launch, those using the iPhone 7, launched in September 2016, or older models are candidates to upgrade their devices this cycle. We offer analysis on this below.</p> <p><b>A Bigger Step</b></p> <p>It’s speculated that Apple’s iPhone 12 will feature greater improvements than typical releases, which will likely increase device uptake. From a design standpoint, it likely re-introduces a smaller screen version as well as a metal, sharper-edged frame not seen since the iPhone 4. It will get a step up in speed while also better conserving battery life with the more energy-efficient A14 Bionic chip. There is a lot of buzz around the camera, with the largest phone versions rumored to feature a 64MP main camera, which will be a large improvement over the 12MP camera on the iPhone 11. Leaked rear glass pane images suggest that Apple will include a LiDAR scanner in the iPhone 12 Pro and Max that will help support augmented reality in some games and shopping apps, for example, by scanning local surroundings and superimposing various graphics into scenes.</p> <p><b>A Shorter Window</b></p> <p>Earlier this year, Apple CFO Luca Maestri announced that the iPhone 12 launch would be delayed, projecting that supply would be “available a few weeks later” than usual. That puts the launch most likely in the October timeframe, and the delay is likely due to Broadcom falling behind on producing the microprocessors for the iPhone 12. Apple has reportedly gone to great lengths to overcome production challenges related to COVID-19 and, unless delays are longer than expected, this should not be a major factor in its most important market, the United States, as new device uptake tends to ramp closer to Christmas. </p> <p><b>The 5G Factor</b></p> <p>Interest for the iPhone 12 appears greater due to the expectations that the device will be 5G-enabled, promising consumers access to seamless connectivity, faster speeds and next-generation user experiences. That said, tests have shown that 5G speeds are not pervasively available and <a href="https://www.washingtonpost.com/technology/2020/09/08/5g-speed/" target="_blank">sometimes actually slower than 4G speeds</a>. The perception of a step-change in wireless technology could lead to a higher rate of iPhone upgrades this year, especially due to the pent-up demand created by Apple initially waiting to support 5G until this generation of iPhone. However, 5G may still be more of a future promise.</p> <p><b>Affluence & Age of Device Base</b></p> <p>Among the greatest factors in determining how well iPhone 12 may get adopted is simply whether consumers can afford them and what iPhone models they currently own. To better understand these factors, Flurry conducted some analysis, which we present below. Flurry Analytics, owned by Verizon Media, is used in over 1 million mobile applications worldwide, providing insights into more than 2 billion smartphones around the world. Take a look at the chart, and then we’ll go through it.</p> <p><img alt="Scatterplot" data-entity-type="" data-entity-uuid="" src="https://www.flurry.com/sites/default/files/FlurryChart-Template-1_1.svg" /></p> <p><i>Fig. 1 Affluent Customers Upgrade iPhones More Frequently</i></p> <p>In the chart above, we plotted countries by their consumer spending power and the age of their iPhone install base. On the x-axis we show how new the iPhone install base is. The farther to the right, the higher the percent of devices that are iPhone 8 or later models. On the y-axis we show the consumer spending power in a country, using household expenditure per capita. The higher up the chart, the more money is spent per household. The color of the dot relates to the size of a market, based on the monthly active iPhone devices Flurry detects in that market.</p> <p>Let’s take a look at a couple of examples to get oriented. Represented by a dark green dot, the U.S. is among the largest markets with the highest consumer spending power and has a high proportion of newer iPhone models in use. This means that people in the U.S. can afford new devices and also upgrade much more frequently than in other markets. By contrast, Vietnam, in the lower left of the chart, has below average spending power and a larger proportion of older devices in its install base. Because the population cannot likely afford to upgrade devices more frequently, they hold on to iPhone 7 and older devices for much longer.</p> <p>From our calculations, 63% of iPhones in use around the world are less than four years old (iPhone 8 or later models). For reference, we overlaid that average on the chart with a dashed gray vertical line. Countries to the right of the line replace their devices more frequently and overall have much newer phones. Those to the left of the line replace less frequently and have older devices, on average.</p> <p>Statistically, we found a +0.8 correlation between spending power (household expenditure per capita) and the share of newer devices (a higher percent of iPhone 8 or later models). That is a very strong positive association, which means that the more spending power in a market, the newer the phones. This makes sense since a new iPhone requires a substantial investment and it explains why the United States and Hong Kong, both with a high household expenditure per capita, also have relatively low percentage of older iPhones in their respective markets.</p> <p>Most of Apple’s smaller markets, represented by light red or gray dots, have low consumer spending power and a lower device replacement rate. This primarily includes most of Africa, as well as parts of Asia and Latin America. Consumers in these countries keep their iPhones for a longer period, likely due to having lower disposable income.</p> <p>Some bigger iPhones markets such as Brazil, Russia, India and Indonesia have relatively low consumer spending power combined with a low device refresh rate. This means that a less expensive base version of the iPhone 12 can have a disproportionate impact on these key markets to get people to upgrade their iPhones sooner. This aligns with a previous report that <a href="https://www.flurry.com/post/629523770176126976/apple-increases-sales-velocity-with-lower-priced" target="_blank">Apple’s low-cost iPhones have helped Apple strengthen its footing in many international markets</a>.</p> <p>Using our calculation that 37% of global iPhones are four or more years old, and that there are an <a href="https://www.computerworld.com/article/3572557/will-apples-iphone-12-generate-an-upgrade-supercycle.html" target="_blank">estimated 950 million active iPhones in the market</a>, we estimate that 350 million iPhones are ripe for upgrade based on their age. This gives Apple a sizable addressable market with its iPhone 12 line. From various leaks, including from technology analyst <a href="https://twitter.com/jon_prosser" target="_blank">Jon Prosser</a>, Apple’s lowest priced model is speculated to start at $549 (with a rumored iPhone 12 4G). If this is the case, then Apple appears well positioned to drive upgrades from the older part of their install base. At the same time, with the highest end model speculated to retail for $1399 (iPhone 12 Pro Max), they would also cover off early adopters and loyalists in more affluent markets that want the latest and greatest Apple has to offer. By all accounts we predict a stronger than typical uptake of the iPhone 12 line compared to previous year’s launches. We’ll monitor early uptake of the iPhone 12 line when it becomes available and share those findings with you. Make sure you subscribe to the <a href="https://www.flurry.com/blog/" target="_blank">Flurry blog</a> and follow us on <a href="https://twitter.com/FlurryMobile" target="_blank">Twitter</a> and <a href="https://t.umblr.com/redirect?z=https%3A%2F%2Fwww.linkedin.com%2Fcompany%2Fflurryanalytics&t=ZDUwZDllM2ZlZTMxMTI2MTc0NWYxMmM0MzRlM2UwZTVkNGE4NTQ4ZSxRT1pTRXBTag%3D%3D&b=t%3A4Jx60yfe0RaZE-Lq7ZwZrw&p=https%3A%2F%2Fflurrymobile.tumblr.com%2Fpost%2F628791612394389504%2Fapple-grows-2020-market-share-by-appealing-to&m=1&ts=1599782944" target="_blank">LinkedIn</a> for the latest reports on smartphone, app behavior, mobile development and other trends. </p> <p><i>iPhone is a trademark of Apple Inc., registered in the U.S. and other countries.</i></p> <p><i>The Flurry blog (<a href="https://www.flurry.com/blog/" target="_blank">https://www.flurry.com/blog/</a>) is an independent blog and has not been authorized, sponsored, or otherwise approved by Apple Inc.</i></p> </div> Fri, 25 Sep 2020 17:54:23 +0000 Anonymous 341 at https://www.flurry.com Now Available: Flurry SDK 11.0.0 for iOS 14 https://www.flurry.com/blog/now-available-flurry-sdk-1100-for-ios-14/ <span class="field field--name-title field--type-string field--label-hidden">Now Available: Flurry SDK 11.0.0 for iOS 14</span> <div class="field field--name-field-blog-author-and-role field--type-string-long field--label-hidden field__item">By: David Lundell, Senior Director of Product Management, Flurry Analytics</div> <span class="field field--name-uid field--type-entity-reference field--label-hidden"><span lang="" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">Anonymous</span></span> <span class="field field--name-created field--type-created field--label-hidden">Tue, 08/25/2020 - 09:09</span> <div class="field field--name-field-blog-post-date field--type-datetime field--label-hidden field__item"><time datetime="2020-08-25T12:00:00Z" class="datetime">2020-08-25</time></div> <div class="field field--name-field-blog-tags field--type-entity-reference field--label-inline"> <div class="field__label">Tags</div> <div class="field__items"> <div class="field__item"><a href="https://www.flurry.com/taxonomy/term/3/" hreflang="en">Product News</a></div> </div> </div> <span class="a2a_kit a2a_kit_size_32 addtoany_list" data-a2a-url="https://www.flurry.com/blog/now-available-flurry-sdk-1100-for-ios-14/" data-a2a-title="Now Available: Flurry SDK 11.0.0 for iOS 14"><a class="a2a_button_linkedin"></a><a class="a2a_button_facebook"></a><a class="a2a_button_twitter"></a><a class="a2a_button_google_plus"></a><a class="a2a_dd addtoany_share" href="https://www.addtoany.com/share#url=https%3A%2F%2Fwww.flurry.com%2Fblog%2Fnow-available-flurry-sdk-1100-for-ios-14%2F&title=Now%20Available%3A%20Flurry%20SDK%2011.0.0%20for%20iOS%2014"></a></span> <div class="clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__item"><p>Over the last few weeks we’ve prepared you for the upcoming release of iOS 14 in our emails, blog posts and in one-to-one conversations. To revisit our blog posts, here’s a round-up:</p> <ul><li><a href="https://flurrymobile.tumblr.com/post/624475748074389504/preparing-for-ios-14" target="_blank">Preparing for iOS 14</a></li> <li><a href="https://flurrymobile.tumblr.com/post/625130389505277952/how-ios-14-negatively-impacts-ad-revenue-for" target="_blank">How iOS 14 Negatively Impacts Mobile App Revenue for Publishers</a></li> <li><a href="https://flurrymobile.tumblr.com/post/625808584247246848/how-ios-14-disrupts-mobile-ad-campaign-attribution" target="_blank">How iOS 14 Disrupts Mobile Ad Campaign Attribution</a></li> <li><a href="https://flurrymobile.tumblr.com/post/626449503277531136/announcing-flurry-conversion-value-analytics-for" target="_blank">Announcing Flurry Conversion Value Analytics for iOS 14</a></li> </ul><p>Today we are letting you know that our 11.0.0 SDK for iOS is available. You can find complete documentation on how to upgrade <a href="https://developer.yahoo.com/flurry/docs/integrateflurry/ios/" target="_blank">here</a>. The new SDK includes the Conversion Value analytics <a href="https://www.flurry.com/post/626449503277531136/announcing-flurry-conversion-value-analytics-for" target="_blank">we announced last week</a> (documented in more detail <a href="https://developer.yahoo.com/flurry/docs/analytics/gettingstarted/ios14/SKAdNetwork/" target="_blank">here</a>) as well is opt-in authorization integration (please find documentation <a href="https://developer.yahoo.com/flurry/docs/analytics/gettingstarted/ios14/att/" target="_blank">here</a>).</p> <p>As a reminder, Flurry Analytics will continue to provide analytics whether your users opt-in to Apple’s App Tracking Transparency Framework or not. Our offering is based on the Identifier for Vendors (IDFV) instead of the Identifier for Advertisers (IDFA). Flurry will respect your users’ privacy choices and will not use any data for advertising purposes unless your end users opt-in. And Flurry is committed to continuing to help developers evolve as iOS 14 changes how apps are built, marketed and monetized.</p> <p>We hope the new SDK helps you be prepared for iOS 14. If you have any questions, concerns or comments during integration, please let us know at <a href="mailto:support@flurry.com" target="_blank">support@flurry.com</a>.</p> </div> Tue, 25 Aug 2020 16:09:37 +0000 Anonymous 346 at https://www.flurry.com Announcing Flurry Conversion Value Analytics for iOS 14 https://www.flurry.com/blog/announcing-flurry-conversion-value-analytics-for/ <span class="field field--name-title field--type-string field--label-hidden">Announcing Flurry Conversion Value Analytics for iOS 14</span> <div class="field field--name-field-blog-author-and-role field--type-string-long field--label-hidden field__item">By: David Lundell, Senior Director of Product Management, Flurry Analytics</div> <span class="field field--name-uid field--type-entity-reference field--label-hidden"><span lang="" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">Anonymous</span></span> <span class="field field--name-created field--type-created field--label-hidden">Fri, 08/14/2020 - 11:13</span> <div class="field field--name-field-blog-post-date field--type-datetime field--label-hidden field__item"><time datetime="2020-08-14T12:00:00Z" class="datetime">2020-08-14</time></div> <div class="field field--name-field-blog-tags field--type-entity-reference field--label-inline"> <div class="field__label">Tags</div> <div class="field__items"> <div class="field__item"><a href="https://www.flurry.com/taxonomy/term/3/" hreflang="en">Product News</a></div> </div> </div> <span class="a2a_kit a2a_kit_size_32 addtoany_list" data-a2a-url="https://www.flurry.com/blog/announcing-flurry-conversion-value-analytics-for/" data-a2a-title="Announcing Flurry Conversion Value Analytics for iOS 14"><a class="a2a_button_linkedin"></a><a class="a2a_button_facebook"></a><a class="a2a_button_twitter"></a><a class="a2a_button_google_plus"></a><a class="a2a_dd addtoany_share" href="https://www.addtoany.com/share#url=https%3A%2F%2Fwww.flurry.com%2Fblog%2Fannouncing-flurry-conversion-value-analytics-for%2F&title=Announcing%20Flurry%20Conversion%20Value%20Analytics%20for%20iOS%2014"></a></span> <div class="clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__item"><p>We are excited to announce a set of solutions to help publishers manage and understand the Conversion Value they set in order to measure post-install campaign performance. A new Flurry Analytics SDK will be available later this month to support this developer need ahead of Apple’s iOS 14 release.</p> <p>In last week’s blog we discussed the impact iOS 14 will have on attribution. We also discussed the Conversion Value and how important that will be to growth efforts in a post-iOS 14 world. If you missed it, you can read it <a href="https://www.flurry.com/blog/post/625808584247246848/how-ios-14-disrupts-mobile-ad-campaign-attribution" target="_blank">here</a>. Many of you told us you’re not sure what to do with Conversion Value. After all, you have 64 values with arbitrary meaning. This is where our new Conversion Value Analytics solution can help.</p> <p>Flurry Analytics SDK 11.0.0 will enable you to pass your Conversion Values to Flurry as standard Flurry User Properties. With Conversion Value as a User Property, you will be able to use Flurry to analyze your users’ Conversion Values with actual post-install behavior. For example:</p> <ul><li>See new devices broken out by Conversion Value</li> <li>Compare key Funnels by Conversion Value</li> <li>See any usage by Conversion Value</li> <li>Create Flurry User Segments by Conversion Value</li> </ul><p>Our SDK will also have another option: a utility that maximizes the information you can provide in the Conversion Value. The new Flurry SDK enables you to set your Conversion Values to easily track both retention and key events. We use the limited 6 bit value SKAdnetwork gives you to record both the daily user retention and up to four custom event combinations.</p> <ul><li>The first 2 bits will be automatically set to the number of days since install, so you will have User Property buckets corresponding to 0 days, 1 Day, 2 Days and 3+ Days. Please note that you need to set this on each session to make sure you capture this fully.</li> <li>The second 4 bits will be set to correspond to key event combinations across 4 default key events we have identified: Register, Log In, Subscribe, and In-App Purchase. You can overwrite these default values to represent any events you want. </li> </ul><p>So you’ll get 4 days and 4 events which Flurry will automatically set for you in any combination. Just set the event when triggered and Flurry will take care of the rest.</p> <p>You can simply set the Conversion Value yourself or use this utility. Either way you’ll be able to use Flurry to see what actions these users performed days, weeks and months later. Whichever option you choose, the Flurry Conversion Value offering has 4 distinct advantages:</p> <ol><li><i>Conversion Value User Properties are device-level.</i> When your ad network gets SKAdnetwork postback, there will be no device ID. By contrast, setting Conversion Value as a User Property allows you to use Flurry Analytics to tie it back into detailed user behavior beyond the install, all in a privacy-friendly way.</li> <li><i>Our reporting will be faster.</i> Apple’s SKAdnetwork postbacks will take up to 24 hours to get to your partner ad network, and then will need to propagate from there back to you. The Flurry Conversion Value User Property will be available in filters, breakouts and other Flurry reporting within a few hours.</li> <li><i>We follow SKAdnetwork’s timing logic.</i> Setting a Conversion Value will mirror the Conversion Value your ad network will receive in the SKAdnetwork postback because we will update the value and the 24-hour countdown timer in <a href="https://developer.apple.com/documentation/storekit/skadnetwork/3566697-updateconversionvalue?changes=_2" target="_blank">the same way SKAdnetwork does</a>.</li> <li><i>Our Conversion Value reporting can fill in the gaps.</i> Because some SKAdnetwork Conversion Value records may be dropped by Apple due to Apple reporting thresholds, our reporting may be more complete than what Apple provides to your networks.</li> </ol><p>As a reminder, we’ll release Flurry Analytics SDK 11.0.0 later this month, which will be iOS 14 compliant and will enable you to pass your Conversion Values to us as standard Flurry User Properties. If you have any questions about Conversion Value, iOS 14, or anything else, please reach out to us at <a href="mailto:support@flurry.com" target="_blank">support@flurry.com</a>. We’d love to hear from you.</p> </div> Fri, 14 Aug 2020 18:13:21 +0000 Anonymous 349 at https://www.flurry.com How iOS 14 Disrupts Mobile Ad Campaign Attribution https://www.flurry.com/blog/how-ios-14-disrupts-mobile-ad-campaign-attribution/ <span class="field field--name-title field--type-string field--label-hidden">How iOS 14 Disrupts Mobile Ad Campaign Attribution</span> <div class="field field--name-field-blog-author-and-role field--type-string-long field--label-hidden field__item">By: David Lundell, Senior Director of Product Management, Flurry Analytics</div> <span class="field field--name-uid field--type-entity-reference field--label-hidden"><span lang="" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">Anonymous</span></span> <span class="field field--name-created field--type-created field--label-hidden">Fri, 08/07/2020 - 09:26</span> <div class="field field--name-field-blog-post-date field--type-datetime field--label-hidden field__item"><time datetime="2020-08-07T12:00:00Z" class="datetime">2020-08-07</time></div> <div class="field field--name-field-blog-tags field--type-entity-reference field--label-inline"> <div class="field__label">Tags</div> <div class="field__items"> <div class="field__item"><a href="https://www.flurry.com/taxonomy/term/3/" hreflang="en">Product News</a></div> </div> </div> <span class="a2a_kit a2a_kit_size_32 addtoany_list" data-a2a-url="https://www.flurry.com/blog/how-ios-14-disrupts-mobile-ad-campaign-attribution/" data-a2a-title="How iOS 14 Disrupts Mobile Ad Campaign Attribution"><a class="a2a_button_linkedin"></a><a class="a2a_button_facebook"></a><a class="a2a_button_twitter"></a><a class="a2a_button_google_plus"></a><a class="a2a_dd addtoany_share" href="https://www.addtoany.com/share#url=https%3A%2F%2Fwww.flurry.com%2Fblog%2Fhow-ios-14-disrupts-mobile-ad-campaign-attribution%2F&title=How%20iOS%2014%20Disrupts%20Mobile%20Ad%20Campaign%20Attribution"></a></span> <div class="clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__item"><p>Last week we explained why the release of iOS 14 will reduce publisher ad revenue and how Flurry can help reverse some of that impact. This week we focus on how iOS 14 will also impair mobile ad campaign attribution. </p> <p>In the pre-iOS 14 world, Mobile Measurement Partners (MMPs) used IDFAs to report granular details about app install campaigns. 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 mobile attribution model has been upended.  </p> <p>To address the gap it is creating for MMPs, Apple has improved its own SKAdnetwork framework. SKAdnetwork helps advertising apps and ad networks connect their campaigns to installs.</p> <figure class="tmblr-full" data-orig-height="1068" data-orig-width="1630"><img data-orig-height="1068" data-orig-width="1630" src="https://64.media.tumblr.com/a162718bba546e5371eabf6067dd4a95/5a9a0d803982317f-ce/s540x810/33bd6cf4b82de809dcdfc24426f6d2280a626644.png" /></figure><p>When a new app is installed, the advertising app registers for attribution and sets a Conversion Value to indicate the value of the user. Apple will periodically send postbacks to the ad network that delivered the install, reporting the campaign, publisher app and conversion value associated with the install. </p> <p>For end users that have not opted into tracking, SKAdnetwork metadata is the only way for apps to measure campaign performance. And Conversion Value is the only indicator beyond the install event to gauge the quality of the install. To ensure user privacy, Apple has designated itself as the only intermediary that can track and report attribution for these installs.</p> <p>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 Apple from reporting attribution data to ad networks. With 6 bits – which creates a possible 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.</p> <p>Flurry will help simplify this process with new features we are developing. Starting with a new SDK we will release later this August, Flurry will first make it easy to set, manage and evaluate the Conversion Value that an app reports back to SKAdnetwork. The SDK will include a way to provide the Conversion Value as a Flurry User Property, enabling you to analyze and compare users with different Conversion Values. For example, you can see how users with one Conversion Value converted in one of your funnels versus users with a different Conversion Value. Or, you can breakout Flurry charts (including active users, new devices and sessions) to show top 10 Conversion Values.</p> <p>So how can publishers like you further use the 6 bit value within a limited time frame to effectively place a value on an install? Flurry will help you there, too. With Flurry, you can use the Conversion Value to indicate user retention and in-app behavior which Flurry Analytics already measures. Our August SDK release will make it easy for you to use Flurry’s out-of-the-box solution to set the ‘number of days since install’ along with key events that the end user triggered, such as Registration, Log In, Subscription or In-App Purchase. We’ll describe this solution in more detail in next week’s post. </p> <p>We’d love your feedback on this. To let us know what you think, or ask any questions, please send us a note at <a href="mailto:support@flurry.com" target="_blank">support@flurry.com</a>.</p> </div> Fri, 07 Aug 2020 16:26:13 +0000 Anonymous 351 at https://www.flurry.com How iOS 14 Negatively Impacts Ad Revenue for Mobile App Publishers https://www.flurry.com/blog/how-ios-14-negatively-impacts-ad-revenue/ <span class="field field--name-title field--type-string field--label-hidden">How iOS 14 Negatively Impacts Ad Revenue for Mobile App Publishers</span> <div class="field field--name-field-blog-author-and-role field--type-string-long field--label-hidden field__item">By: David Lundell, Senior Director of Product Management, Flurry Analytics</div> <span class="field field--name-uid field--type-entity-reference field--label-hidden"><span lang="" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">Anonymous</span></span> <span class="field field--name-created field--type-created field--label-hidden">Thu, 07/30/2020 - 21:46</span> <div class="field field--name-field-blog-post-date field--type-datetime field--label-hidden field__item"><time datetime="2020-07-31T12:00:00Z" class="datetime">2020-07-31</time></div> <div class="field field--name-field-blog-tags field--type-entity-reference field--label-inline"> <div class="field__label">Tags</div> <div class="field__items"> <div class="field__item"><a href="https://www.flurry.com/taxonomy/term/3/" hreflang="en">Product News</a></div> </div> </div> <span class="a2a_kit a2a_kit_size_32 addtoany_list" data-a2a-url="https://www.flurry.com/blog/how-ios-14-negatively-impacts-ad-revenue/" data-a2a-title="How iOS 14 Negatively Impacts Ad Revenue for Mobile App Publishers"><a class="a2a_button_linkedin"></a><a class="a2a_button_facebook"></a><a class="a2a_button_twitter"></a><a class="a2a_button_google_plus"></a><a class="a2a_dd addtoany_share" href="https://www.addtoany.com/share#url=https%3A%2F%2Fwww.flurry.com%2Fblog%2Fhow-ios-14-negatively-impacts-ad-revenue%2F&title=How%20iOS%2014%20Negatively%20Impacts%20Ad%20Revenue%20for%20Mobile%20App%20Publishers"></a></span> <div class="clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__item"><p>When Apple announced iOS 14, it outlined a new policy which requires app publishers to seek end user permission to access a user’s IDFA. While estimates on forecasted opt-in rates vary, the result is clear: the IDFA will become scarce. Among the implications for app developers, the most pressing is an expected large drop in advertising revenue. In this post, we’ll discuss how disabling the IDFA leads to a sizable drop in ad revenue.</p> <p>With the announced opt-in policy on iOS 14, app developers that rely on ad revenue should expect their ad performance and fill rates drop. Today, Ad Networks and Demand Side Platforms use the IDFA to reach target audiences. Going forward, when the IDFA becomes largely unusable, advertisers will no longer know which consumers they’re reaching. As a result, ad spending will drop, leading to lower CPMs and fill for application publishers.</p> <p>For consumers that permit tracking, the IDFA can continue to be used in ad requests. That said, Flurry expects that the significant majority of consumers will not permit tracking. For all intents and purposes, publishers should consider the IDFA mostly unusable. Without a targeting identifier, advertisers will be forced to bid blind and therefore lower their bid amounts. Advertisers will further bid lower because granular attribution will no longer be possible. We’ll go into more detail about attribution in a future blog post.</p> <p>In-app advertising suddenly will become a less viable revenue model. In response, publishers will be forced to either preserve IDFAs or pivot to other revenue models. </p> <ol><li>In-app purchase and subscriptions: Apps that are ad-supported, or employ a hybrid model, may shift to paid models.</li> <li>IDFA maximization: Some publishers may attempt to gate app functionality in order to incentivize opt-in.</li> </ol><p>We also recommend publishers explore a third approach: Leveraging their first party data for advertisers. Publishers can rebuild ad performance by using their own data to make their audiences more attractive to advertisers, even without an IDFA. </p> <p>Flurry can help make this happen. Using both the Flurry Analytics and Verizon Ads SDKs, publishers can gain superior fill and performance across a number of ad formats. Together, the Flurry and the Verizon Ads SDKs will package publisher audience profiles in a privacy-friendly way and make them available to advertisers. The more advertisers know about your users, the higher the CPMs and fill you can expect. Most importantly, this solution adheres to Apple’s new guidelines. Only data from your own apps is used, and data from third-party or your own opted-out users is never included.</p> <p>We are working out the release timing of this capability, which enables publishers to leverage their own data for improved advertising performance. To get early access to this solution, please contact <a href="mailto:support@flurry.com" target="_blank">support@flurry.com</a>.</p> </div> Fri, 31 Jul 2020 04:46:36 +0000 Anonymous 353 at https://www.flurry.com Preparing for iOS 14 https://www.flurry.com/blog/preparing-for-ios-14/ <span class="field field--name-title field--type-string field--label-hidden">Preparing for iOS 14</span> <div class="field field--name-field-blog-author-and-role field--type-string-long field--label-hidden field__item">By David Lundell, Senior Director of Product Management, Flurry Analytics</div> <span class="field field--name-uid field--type-entity-reference field--label-hidden"><span lang="" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">Anonymous</span></span> <span class="field field--name-created field--type-created field--label-hidden">Thu, 07/23/2020 - 16:21</span> <div class="field field--name-field-blog-post-date field--type-datetime field--label-hidden field__item"><time datetime="2020-07-23T12:00:00Z" class="datetime">2020-07-23</time></div> <div class="field field--name-field-blog-tags field--type-entity-reference field--label-inline"> <div class="field__label">Tags</div> <div class="field__items"> <div class="field__item"><a href="https://www.flurry.com/taxonomy/term/3/" hreflang="en">Product News</a></div> </div> </div> <span class="a2a_kit a2a_kit_size_32 addtoany_list" data-a2a-url="https://www.flurry.com/blog/preparing-for-ios-14/" data-a2a-title="Preparing for iOS 14"><a class="a2a_button_linkedin"></a><a class="a2a_button_facebook"></a><a class="a2a_button_twitter"></a><a class="a2a_button_google_plus"></a><a class="a2a_dd addtoany_share" href="https://www.addtoany.com/share#url=https%3A%2F%2Fwww.flurry.com%2Fblog%2Fpreparing-for-ios-14%2F&title=Preparing%20for%20iOS%2014"></a></span> <div class="clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__item"><p>At this year’s WWDC, Apple announced that iOS 14 will change how developers can collect and share end user data. We’re summarizing the most important changes here, and how we’re helping you prepare for iOS 14. </p> <p><b>Using Flurry Analytics</b></p> <p>Please note that Flurry Analytics is unaffected by these changes, and you can continue to use the service without any issues before and after iOS 14 is released.</p> <p><b>Managing Privacy with Your End Users</b></p> <p>With iOS 14, you will have to provide end users information and the choice to opt-in to data collection. Apple’s new App Tracking Transparency framework communicates these requirements, and those will take effect when iOS 14 goes GA. </p> <p>Two key elements of the App Tracking Transparency (ATT) framework include:</p> <ul><li><b>Tracking Opt-in Authorization: </b>If your app collects data about end users and shares that data with other companies, you must present an authorization prompt. Note that Apple indicated that first party analytics providers are not subject to the same opt-in. We will release a new SDK in August that will pass through your users’ consent data to Flurry. Invoking the opt-in prompt in iOS 14 is completely up to you. You decide when to prompt for authorization - or even whether you invoke the prompt at all. Your analytics from Flurry won’t be impacted by whether you display the prompt for opt-in authorization.</li> <li><b>App Store Disclosure:</b> Apps will now be required to indicate upon submission and on the app’s product page in the app store what data the apps collect, and what data is collected by the apps’ partners.</li> </ul><figure class="tmblr-full" data-orig-height="1196" data-orig-width="1260"><img alt="image" data-orig-height="1196" data-orig-width="1260" src="https://64.media.tumblr.com/b2d3152d037b6a4602aba11ae0a51429/5b7025acf821e3ed-11/s540x810/34c270db6f4911e862688a83e0e28103b71ebb32.png" /></figure><p>In iOS 14, users are opted out by default until you present Apple’s opt-in authorization. Until a user has specifically granted you authorization to track them, you do not have their authorization to track them as defined by Apple. Given our experience with GDPR and similar privacy controls, we anticipate opt-in rates will be at or below 20%. However, without an available identifier for use in ad targeting, CPMs will drop. Without a way to attribute app installs at the device level for most devices, attribution will be a challenge. The mobile ecosystem is just beginning to assess these types of impacts, and we will be sharing more with you as part of our industry insights series.</p> <p>Flurry agrees with Apple’s moves to provide transparency and choice to end users. And Flurry Analytics will be compliant with their new policies. </p> <p>Flurry commitment to our application publishers:</p> <ul><li>Flurry Analytics will continue to work, without interruption, whether end users opt-in to Apple’s new framework or not. </li> <li>Flurry will provide a new version of its SDK in August that will seamlessly pass end users opt-in selections to Flurry.</li> <li>Flurry will respect end user consent preferences. </li> <li>Flurry will respect Apple’s policy requirement to not combine data across apps and websites owned by other companies. </li> <li>Flurry will help you comply with the new App Store transparency page, providing guidance to ensure your app submission process goes smoothly.</li> </ul><p>Note that at the time of writing this post, Apple has yet to release its final guidance. As such, our guidance may evolve should Apple’s policies also evolve. In any  event, Flurry will continue to work with Apple to ensure that our privacy practices align with Apple policies.</p> <p>As always, please let us know if you have any questions and let us know how Flurry can help further by emailing us at <a href="mailto:support@flurry.com" target="_blank">support@flurry.com</a>.</p> </div> Thu, 23 Jul 2020 23:21:22 +0000 Anonymous 357 at https://www.flurry.com Apple’s iPhone SE 2 Building Momentum After Slow Start https://www.flurry.com/blog/apples-iphone-se-2-building-momentum-after-slow/ <span class="field field--name-title field--type-string field--label-hidden">Apple’s iPhone SE 2 Building Momentum After Slow Start</span> <div class="field field--name-field-blog-author-and-role field--type-string-long field--label-hidden field__item">By: Lisa Moshfegh, Product Marketing, and Aman Bansal, Flurry Analyst</div> <span class="field field--name-uid field--type-entity-reference field--label-hidden"><span lang="" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">Anonymous</span></span> <span class="field field--name-created field--type-created field--label-hidden">Thu, 06/25/2020 - 10:22</span> <div class="field field--name-field-blog-post-date field--type-datetime field--label-hidden field__item"><time datetime="2020-06-25T12:00:00Z" class="datetime">2020-06-25</time></div> <div class="field field--name-field-blog-tags field--type-entity-reference field--label-inline"> <div class="field__label">Tags</div> <div class="field__items"> <div class="field__item"><a href="https://www.flurry.com/taxonomy/term/290/" hreflang="en">App Insights</a></div> <div class="field__item"><a href="https://www.flurry.com/taxonomy/term/3/" hreflang="en">Product News</a></div> <div class="field__item"><a href="https://www.flurry.com/taxonomy/term/5/" hreflang="en">Apple</a></div> </div> </div> <span class="a2a_kit a2a_kit_size_32 addtoany_list" data-a2a-url="https://www.flurry.com/blog/apples-iphone-se-2-building-momentum-after-slow/" data-a2a-title="Apple’s iPhone SE 2 Building Momentum After Slow Start"><a class="a2a_button_linkedin"></a><a class="a2a_button_facebook"></a><a class="a2a_button_twitter"></a><a class="a2a_button_google_plus"></a><a class="a2a_dd addtoany_share" href="https://www.addtoany.com/share#url=https%3A%2F%2Fwww.flurry.com%2Fblog%2Fapples-iphone-se-2-building-momentum-after-slow%2F&title=Apple%E2%80%99s%20iPhone%20SE%202%20Building%20Momentum%20After%20Slow%20Start"></a></span> <div class="clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__item"><p>Following the Fall 2019 launch of the iPhone 11 series—the most expensive and advanced iPhones to date—Apple launched the value-priced 2nd generation iPhone SE on April 24, 2020. The popular 1st generation iPhone SE was offered in 2016 as a less expensive alternative to the then flagship iPhone 6S and 6S Plus devices. And the launch of the second generation version follows the same playbook by offering strong value at a low price point. In this report, Flurry looks at how well the launch of the 2nd generation iPhone SE (aka iPhone SE 2) fared in the United States.</p> <p>With four years between launches, shipping the follow-up iPhone SE 2 seems timely. The smartphone starts at just $399—a less expensive alternative to the iPhone 11 series, priced between $699 to $1,449 depending on the device and storage. With some consumers preferring the compact size of the original iPhone SE, Apple kept the iPhone SE 2 much smaller than current alternatives with a 4.7” display. It also uses the home button, popular among many consumers. To keep costs down, while still maintaining performance, the iPhone SE 2 features the same A13 Bionic chip used in the iPhone 11 as well as the iPhone XR camera, considered the best single camera system made by Apple. </p> <p>At the same time, this launch faces the unprecedented challenge of entering the market during the global COVID-19 pandemic. While a lower price-point could appeal to consumers during economic uncertainty, significant unemployment rates and the closure of Apple retail stores between March 13 and May 11 very likely impacted the launch. And, as we reported earlier, we <a href="https://flurrymobile.tumblr.com/post/621721046936141824/tablet-usage-spikes-during-covid-19" target="_blank">have observed an overall slowdown in new iPhones activated in the United States since March.</a></p> <p>As a mobile app analytics provider, Flurry sees app activity in over 1 million mobile applications across 2 billion smartphone devices each month, giving us unique insights into smartphone adoption. We start our analysis by reviewing the change in share for all Apple devices in the market since the iPhone SE 2 launch on April 24.</p> <figure class="tmblr-full" data-orig-height="914" data-orig-width="1622"><img alt="image" data-orig-height="914" data-orig-width="1622" src="https://64.media.tumblr.com/c0c19013cfeb94e4b5e51bea4353d0ff/54662b947ca75ada-80/s540x810/0efc7df5be52b8f980082f88720dd20bf9bbbcf6.png" /></figure><p>The chart above illustrates how Apple drives device replacement cycles. As new iPhones are released, older models decrease in share while more recent models tend to increase in share. The iPhone SE 2 captured a half a percentage point of the iPhone install base since launching. The iPhone XR, on the other hand, the darling of Apple’s lineup <a href="https://flurrymobile.tumblr.com/post/189780168835/iphone-xr-outselling-iphone-11-ahead-of-christmas" target="_blank">entering the 2019 Holiday season</a>, increased its share of install base during the same time period by only 0.1%. This could indicate the iPhone XR’s reign as Apple’s most popular device could be coming to an end, making way for the iPhone SE 2. On the high-end, we note the strong growth of the iPhone 11 and the iPhone 11 Pro Max, adding 1.5% and 0.7% of the install base, respectively.</p> <p>Next, let’s review the current install base for all Apple iPhones as of June 11, 2020.</p> <figure class="tmblr-full" data-orig-height="910" data-orig-width="1612"><img alt="image" data-orig-height="910" data-orig-width="1612" src="https://64.media.tumblr.com/309d0cf994111fb1ef57b83b3c2f2e31/54662b947ca75ada-74/s540x810/a70f2f3664fbd1a290539c0da26ba8b3e6dc6124.png" /></figure><p>The iPhone XR has the largest share of the iPhone install base with 14%. However, we expect the iPhone 11 to overtake the iPhone XR by the end of the year for two reasons. First, the iPhone 11’s adoption rate is nearly 15 times greater. Second, we expect the iPhone SE 2, which costs a third less, to further slow the growth of the more budget-oriented iPhone XR.</p> <p>While the iPhone SE 2 has a current 0.8% share among iPhone devices, we expect adoption to accelerate, especially as retail stores start to reopen. With diminished retail support, it’s reasonable to expect the device is off to a slower start. Additionally, with economic uncertainty caused by the COVID-19 pandemic, the more affordable iPhone SE 2 may appeal to customers who might have otherwise opted for a pricier model. </p> <p>Apple has also introduced more subscription services in recent years as an added revenue stream. Tuned for a better video experience than its predecessor, the less expensive iPhone SE 2 may also drive more subscriptions to Apple Music or Apple TV. Either way, we expect the iPhone SE 2 to drive upgrades among more budget conscious iPhone 6, 7 and 8 series owners, as well as drive device replacement among remaining 1st generation SE users. Finally, as an attractive low price alternative to Android customers, the iPhone SE 2 could convince some Android customers to make the switch to iOS. As always, we’ll keep an eye on adoption rates and report interesting findings. </p> <p><i>iPhone is a trademark of Apple Inc., registered in the U.S. and other countries.</i></p> <p><i>Flurry’s blog (flurry.com/blog) is an independent blog and has not been authorized, sponsored, or otherwise approved by Apple Inc.</i></p> </div> Thu, 25 Jun 2020 17:22:46 +0000 Anonymous 365 at https://www.flurry.com