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. The Platform
  2. User-Level Audience Reporting
  3. Advanced Reporting Methods

Date Ranges: Define Audience vs. Create Report

Previous Reading: Audience Reporting Walk-through :: Creating an audience :: Running Reports :: Absolute vs. Relative Reports

PreviousUser Measurement & Calculation DetailsNextExclude GAID tracking opt-outs

Last updated 2 years ago

Overview

To understand the nuances with user-level dates it's helpful to start with the. Defining an audience is a discrete, separate step from running a report of user performance. So you need to define discrete date windows when you and then again when you view user performance by This is simply because you may want to define users by their behavior during one timeframe, then see their performance over a different timeframe.

This important level of detail can be confusing when first using Audience Reporting – but once mastered it can uncover powerful insights of your users.

Example: Define an Audience

When you create an audience, you can restrict dates on users that meet the criteria you’ve defined. In the example below, the users have completed a “DailyCompleted” Event within the last 7 days.

Absolute Report: defining an audience by activity but reporting over a different timeframe

Step 3: Run a Relative Report on a different timeframe

  • Restrict user install dates limit the Audience Users to have installed within the timeframe. Users whose install date falls out of the defined timeframe will not be included in the report.

  • Days in Lifecycle indicate how many days will be shown in the report (0-14)

So in the below case, User A would show the event at 14d of activity, while User C would only have activity on the first 3d after their install.

This means the will find all users who meet these criteria. In the example below, Users A and C would be a part of the audience. User B, would not be included.

Now when you , you can specify a different timeframe to measure the performance of users A & C.

This is an important feature in, you can define an audience using a different timeframe than your report. This means you can measure a user's performance over an earlier timeframe than the behavior or action you're using to define the audience. In the example below we’re actually choosing a reporting date frame that precedes the window of the audience definition.

For , user performance starts at install.

Audience Builder
Run a Report
Absolute Reporting
Relative Reporting
concept of reporting
create an audience
running a report.
Users who’ve fired at least one DailyCompleted event in the last 7d
An audience report run over the last 7 days.
In a relative report, both user A & User C will have the same day 0.
User C's action will be measured on day 3, User A on day 14.