Date Ranges: Define Audience vs. Create Report
Previous Reading: Audience Reporting Walk-through :: Creating an audience :: Running Reports :: Absolute vs. Relative Reports

Overview

To understand the nuances with user-level dates it's helpful to start with the concept of reporting. 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 create an audience and then again when you view user performance by running a report. 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.
Users who’ve fired at least one DailyCompleted event in the last 7d
This means the Audience Builder will find all users who meet these criteria. In the example below, users A and C would be a part of the audience. Users B, would not be included.
An audience report run over the last 7 days.
Now when you Run a Report, you can specify a different timeframe to measure the performance of users A & C.

Example: Running an Absolute Report on a different timeframe

For Absolute Reporting, this is the time period in which you want to see the performance of your audience. In the example below we’re actually choosing a date frame that precedes the window of the audience definition.
Remember our audience was defined as users who've triggered an event in the last 7 days but our report is measuring the performance of these users over the last 14 days. User C hadn’t installed and therefore will not be included in the first 12 days of April activity.
The absolute report over the full 14d will not include user C’s activity.

Step 3: Run a Relative Report on a different timeframe

For Relative Reporting, user performance starts at install.
  • 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 have 14 of activity, while User C would only have activity on the first 3d after their install.
In a relative report, both user A & User C will have the same day 0.
Copy link
Outline
Overview