> 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)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.adlibertas.com/the-platform/user-level-audience-reporting/advanced-reporting-methods/understanding-audience-restraints.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.