LogoLogo
HomeThe PlatformBlogSchedule a demo
  • Getting Started
    • Welcome to AdLibertas
  • The Platform
    • How it works
    • User-Level Audience Reporting
      • Creating Reports
        • Creating a New User Report
        • Creating Advanced User-Level Reports
        • Advanced Audience Builder
        • Custom Event Metrics
      • Report Layout
        • Report Module: Audience Filtering
        • Chart Type Module: Absolute vs. Relative Reports
        • Daily Totals, Per User, Cumulative Totals
        • Lifecycle Reports
        • Forecasting Module
        • Statistics Module
        • Measuring Confidence
      • Advanced Reporting Methods
        • User Measurement & Calculation Details
        • Date Ranges: Define Audience vs. Create Report
        • Exclude GAID tracking opt-outs
        • Scheduled Reports: Keep Updated & Rolling
        • Reporting on a Firebase AB test
        • Understanding “Audience Restraints”
        • Adding user time to your reports
    • Consolidated Revenue Reporting
      • Reporting Discrepancies
      • Reporting Availability & Timezones
      • Ad Network Re-Repost; Also: Revenue Reconciliation Accuracy
      • Consolidated Reporting vs. Consolidated Inventory Reporting
      • Reporting Table – Column Descriptions Common Metrics (Calculated Fields)
      • Facebook Reporting
      • Consolidated Ad Revenue with multiple mediators
    • Business Analytics
      • Analytics Layout
      • Understanding the "Explore Data" button
      • The Data Table
      • Asking a Question
      • Saving a Question
      • Creating a custom dimension
      • Setting up a pulse
    • Custom Dashboards
      • Custom Dashboard Filters
      • Combining data into a single chart
    • Direct SQL Access
    • Exporting Data
      • Ad Network Reports
      • Chart Reports
      • Custom API connections
      • Downloading & Scheduling Data Reports
      • Deprecated: Line Item Change Log
    • General
      • Change your Username & Password
      • Adding Users to your Account
      • Sharing Collaborative Links
      • AdLibertas Cost
  • Data Integrations
    • Connecting in 3 steps
    • Ad Impression-Level Revenue Connections
      • AppLovin Max User Revenue API
      • ironSource Ad Revenue Measurement Integration
      • Impression level tracking with Admob Mediation
      • Collecting MoPub Impression-Level Data as a Firebase Event
    • Ad Network & Store Connections
      • Adding Ad Network Credentials
      • How does App Store Reporting work?
      • Adding access to Google Play
      • Adding Sub User to App Store Connect
      • Getting the most from Ad Network Reports
    • Analytics Connections
      • Data Set Status
      • Connect AdLibertas to Firebase
      • Connecting AdLibertas to BigQuery
      • Firebase Install Counts in Audience Reporting
      • Setting User Campaigns in Firebase
      • Why use revenue to determine Firebase AB test winners?
      • Firebase Best Practices: keeping Google BigQuery Costs Down
    • Custom Integrations
      • Sending Events via Webhooks to AdLibertas
      • Impression level tracking with Admob Mediation
      • Connecting AdLibertas to BigQuery
      • Importing a custom data set
    • IAP Connections
      • Tracking IAP & Subscriptions in Firebase and BigQuery
      • RevenueCat Integration: WebHooks
      • RevenueCat: Setting Universal Identifiers
    • MMP Connections
      • Connecting Adjust
      • Connecting AppsFlyer
      • Connecting Kochava
  • FAQs
    • General
      • Why does AdLibertas need credentials?
    • Audience Reporting
      • Why doesn't my daily active user count match Firebase?
      • Why doesn’t my retention rate match?
      • Why aren't my install rates matching?
      • Why doesn't my relative user count match retention?
      • What is the probability projected LTV becomes actual LTV?
      • Why doesn’t Firebase and AdLibertas revenue match?
    • Reporting
      • What is “non_mopub” revenue
      • How do customers use AdLibertas?
  • Privacy & Security
    • Privacy & Security Details
Powered by GitBook
On this page
  1. Data Integrations
  2. Analytics Connections

Firebase Install Counts in Audience Reporting

TL;DR: The best way to measure installs with Firebase data is using the first_touch_timestamp user property.

PreviousConnecting AdLibertas to BigQueryNextSetting User Campaigns in Firebase

Last updated 2 years ago

Firebase Analytics itself does not directly report on installs but does capture the first time a user opens the app. This is a property called user_first_touch_timestamp and is set the first time a user initializes the Firebase Analytics SDK. At this point, a first_open event is fired and automatically collected.

However, the first_open event is a misnomer in Firebase. The event first_open is actually tracked each time a user installs, reinstalls, or updates the app, meaning a single unique user can have multiple first_open events. AdLibertas builds audiences with this in mind and uses the user_first_touch_timestamp property to build retention curves and calculate new user counts. The user_first_touch_timestamp is only set on the first first_open event and does not change as long as the user has the app installed. A few things to note when looking at an Audience:

  • A user may download the app but never have an active session. This would show as an install event in the app store’s reporting or your MMP, but as it won’t have a corresponding,first_open won’t show in Audience Reporting.

  • A user may download the app, and open it on a different calendar day. The timestamp of the install event and the first_open event will fall on different days.

  • A user may have multiple first_open events if they uninstall, reinstall, or update the app.

  • A user may download and fire a first_open event, but “bounce” meaning they did not fire an engagement event or stay long enough in the app to be counted as an active session. These users are not counted towards daily active user counts.

  • A user may have multiple first_touch_timestamps, if they have re-installed. This can create confusing results where users have activity, prior to their first_touch_timestamp. To combat this, we recommend you exclude first_touch_timestamps that are outside of your install windows:

In Audience Reporting, we include an “Installs During Period %” metric to help you understand the percentage of users whose first touch timestamp occurs within the query’s date range.

  • A low percentage of “Installs During Period %” means the majority of users are reinstalling the app during the query’s date range.

  • A high percentage of “Installs During Period %” means the majority of users are installing the app for the first time.

Please refer to on first_open and other automatically collected events.

Firebase’s documentation