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:
  • Create An Audience
  • Refine or edit an existing audience
  • Options for defining an audience:
  • 1. Audience Name & Audience Description:
  • 2. App Name:
  • 3. Period:
  • 4. Parameter value or count
  • 5. Using the “AND” Operator
  • 6. Firebase Experiments:
  • 7. The OR operator
  • 8. Exclusions
  1. The Platform
  2. User-Level Audience Reporting
  3. Creating Reports

Advanced Audience Builder

Create and refine user groups by their actions or behavior.

PreviousCreating Advanced User-Level ReportsNextCustom Event Metrics

Last updated 2 years ago

In this article, we will show you how to create and edit an audience and define some of the features and tricks when defining an advanced audience.

Overview:

The purpose of creating or refining a custom audience in the Advanced Audience Builder is to add details of the exact users you’d like to define for your reporting.

To do so, you need to define (or exclude) the events, attributes, and timeframes to isolate the proper group of users. Let’s get started with an example:

Create An Audience

From the main menu, click User-level Reporting > Advanced Audience Builder, or from the home screen click the button with the same name.

From there you can click + New audience in the top right.

Refine or edit an existing audience

If you'd like to change or alter a pre-existing audience, you can do so by clicking a pre-existing audience from the list or by clicking the audience name in the report.

From there you can edit the audience using the "edit" button.

Options for defining an audience:

1. Audience Name & Audience Description:

This can be very helpful in referring back to your audiences later. You’ll be using these naming conventions when you choose your audiences in reporting. This can be changed at a later date.

2. App Name:

This will filter user events & actions to selected apps. Because user identifiers are constant across apps, if no app filter is selected, user behavior and events will be measured across all apps.

3. Period:

The date selection is the time period the users have generated the events defined in the audience. A user may have installed outside of this period, but still, be included if you include an event that captures the user’s behavior.

4. Parameter value or count

A very valuable metric, this shows the count of events generated by this user. Event Count > 0 will return all users who’ve achieved 1 or more of these events.

In other scenarios, you can select the parameter value, experiment name, etc for each parameter.

5. Using the “AND” Operator

The AND operator will allow you to choose multiple combined events that define a single user. If a user achieves a single event of the two, they will not be included in this audience.

6. Firebase Experiments:

We automatically import your Firebase experiments, pre-populating the variants for ease of revenue-performance measurement of your AB tests.

7. The OR operator

The OR operations allows you to choose multiple events and include a user if they’ve achieved either event.

8. Exclusions

We also allow you to define an audience by choosing events to exclude users. Users who fire an event, or have an attribute included in this sections will NOT be included in your audience.

Clicking Create will build the audience your define. The length of time for this audience to be built will be dependent on the amount of data and the volume of users you have available.

Related Reading: :: ::

Using Audience Reporting
2. Run Report
3. Forecast Results
See an example of how to create an audience