> For the complete documentation index, see [llms.txt](https://docs.adlibertas.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adlibertas.com/the-platform/user-level-audience-reporting/advanced-reporting-methods/understanding-audience-restraints.md).

# Understanding “Audience Restraints”

When using Audience Reporting when you [create an audience](https://docs.adlibertas.com/the-platform/user-level-audience-reporting/creating-a-new-user-report), you’re defining a data-set of users through conditions (actions, behaviors, or user properties.) **Audience Restraints give you the ability to restrain these defining conditions to only apply to certain timeframes as referenced against user’s install/re-install event.**

### **Condition Restraint**

<figure><img src="/files/oeKeeC0wTPcvWzhhmSRO" alt=""><figcaption></figcaption></figure>

![Then you can choose a timeframe or session metric](/files/CKT2u9iqJqfg1jslbDvE)

![As well as an operator. Above you’re limiting the condition to happen less than or equal to 45 min from a user’s install/re-install event.](/files/HVsRjpsQdb7tWMYU7JT3)

#### **Some notes:**

* A user’s install event is defined as day 0
* While the event defining the condition needs to be within the defined audience timeframe, the user’s install date does not.
* The user’s install (by default) is the first\_open\_timestamp

### **Audience Restraint**:

The Audience Restraint applies the same defined restraint to all conditions in the defined audience.

![All conditions added to the audience will need to happen on the user’s day of install/re-install.](/files/hBhY2FJUynivkXx5FU4X)

More reading:

[Audience Reporting Walkthroughs](https://docs.adlibertas.com/the-platform/user-level-audience-reporting)