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
  • Overview:
  • 1. Report Name & Description
  • 2. Absolute Date Range
  • 3. Relative User Day
  • 4. Both
  • 5. Restrict User install dates (Relative Reports only)
  • 6. Days in Lifecycle (Relative Reports only)
  • 7. Absolute Date Period (Absolute Reports only)
  • 8. Custom Metrics
  • 9. Choosing Audiences
  1. The Platform
  2. User-Level Audience Reporting
  3. Creating Reports

Creating Advanced User-Level Reports

Advanced reporting allows you to create and refine reports on users identified in the Advanced Audience Builder.

PreviousCreating a New User ReportNextAdvanced Audience Builder

Last updated 2 years ago

This article will walk you through how you can create an advanced report to compare and contrast different audiences.

Overview:

Once you’ve created an advanced audience, you’ll want to define the date range you’d like to see your audience reported on, as well as choose other audiences to compare and contrast performance.

Navigate to Audience Reporting > Audience Reporting > +New Advanced Report

From here you can add multiple audiences to compare them against each other.

1. Report Name & Description

A method to differentiate the reports you create. Can be very helpful to find and reference in the future.

2. Absolute Date Range

An absolute report shows your audience over a set, defined date range. For example, let’s say you have an audience defined as all users who’ve clicked an onboarding button, an absolute report will show all of these users' performance during the defined time period.

3. Relative User Day

A relative report (also called a user-cohort report) is a report that shows all of your defined audience starting with the same install date. For example, let’s say you have an audience defined as all users who’ve clicked an onboarding button, the relative report will show all of these users from the date they’ve installed the app.

Because the relative report shows the user’s journey from day 0, only users who have an install date are included in relative reports.

Because this report can traverse all of your data looking for user install dates, it takes longer to run than absolute reports.

4. Both

Shows both absolute and relative reports. Because this traverses much more data, these reports take longer than a single type.

5. Restrict User install dates (Relative Reports only)

This feature will allow you to restrict the timeframe of relative users to a certain timeframe. Helpful if you’d like the report to run faster, or if you want to only include users who’ve been added to the app during a certain timeframe.

6. Days in Lifecycle (Relative Reports only)

Allows you to choose the number of days returned for a user’s lifecycle. For instance “30” would only return the first 30-days of a user’s lifecycle.

7. Absolute Date Period (Absolute Reports only)

The time period in actual dates which you want to display your audience performance

8. Custom Metrics

This allows you to add metrics to your report. A metric is defined as a discrete user event: such as in_app_purchase, or session_start. Custom Metrics will show in your report as an average, per daily active user, and as a total of your audience.

9. Choosing Audiences

Here you’ll be allowed to choose one or more audiences to measure revenue performance over time. Keep in mind your audience is defined by the events they’ve engaged with during a time period, the reports are those user’s performance over the