> For the complete documentation index, see [llms.txt](https://docs.dfinery.ai/user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dfinery.ai/user-guide/en/customer/audience.md). # Audience ## **What is an audience?** Audience refers to a group of customer data grouped according to certain criteria. For example, you Users who signed up in February can create a specific audience called and conduct CRM marketing targeting that audience. [Data linking](https://dfinery.gitbook.io/user-guide/v/ko/readme/event) is essential for audience creation and utilization. ## **Examples of audience usage** * Customers who purchased product A at least once in the past n days

* Customers with a Diamond membership level

## **Create an audience** Click the **'+ Create Audience' button.**

## **Group settings** 1. Click the '+ Add' button on the right.

2. Select events or user profiles in the filter conditions.

Division	Detailed filter conditions	Explanation
Event	-	Filter by all or all active events and standard and custom events
User Profile	User properties	Filterable by standard user profile properties and custom user profile properties
	Recent device properties	Filtering is possible through information collected from the user's most recently used device as of the previous day.
	Behavioral properties	Filterable through information collected on specific behavioral attributes defined in the definer

**Setting conditions with events** You can set a condition for how many times a specific event is performed within a specific period. yes) *Users who triggered the df\_purchase event 3 or more times in September 2024* {% hint style="danger" %} **Filter only users who have triggered an event at least once** ※ When setting a condition as an event, you cannot set a condition of whether the user performed the event or not, so you can basically set a condition of a user who performed the event at least once within the period. {% endhint %} * **When selecting 'Event/Event Attribute',**\ You can enter filtering conditions by selecting events such as purchases and their attribute information (product category, purchase amount, etc.).

**Setting conditions with user profiles** Unlike event conditions, user profile conditions do not set a period because the most recent value is saved.\ For user profile conditions, you can select one of the categories: 'User Properties', 'Recent Device Properties', or 'Behavior Properties'. yes) *VIP members in their 30s* * **When you select 'User Properties',**\ You can set filter conditions using standard user profile properties provided by DFINERY and custom user profile properties you added yourself.

* **When you select 'Recent device properties',**\ You can set filter conditions based on properties collected from the device most recently used by the user.

Recent Device Attributes Details (Table)

* Reference

Provided properties	Explanation
Recent device region	The region of the device the user recently used.
Recent device models	The model of the device the user recently used.
Recent news agency	This is the carrier the user recently used.
Latest browser version	The version of the web browser the user recently used.
Recent browsers	The web browser the user recently used.
Recent countries	The country where the user is currently located (IP based)
Recent city	The city where the user is currently located (IP based)
Recent Device ID	A unique identifier (ID) for the device the user recently used.
Recent IDFV	This is the IDFV of the device that the user recently used on iOS.
Recent IDFA	This is the IDFA of the device the user recently used on iOS.
Recent GAID	The GAID of the device the user recently used on Android.
Recent Google App Set ID	The App Set ID of the device the user recently used on Android.
Recent Cookie ID	The Cookie ID that the user recently used in his web browser.
Most recently used library version	The version of the SDK that the user recently used.
Recently used library platforms	The platform the user recently used.
Recent OS	The operating system (OS) that the user recently used.
Recent Languages	The language of the device the user recently used.
Recent time zone	The time zone of the device the user recently used.
Recent area	The region (city/province) where the user is currently located. (IP based)

* **When selecting 'Behavior Attribute',**\ You can enter filtering conditions by selecting user-specific behavior attribute information automatically calculated by cycle, such as the number of purchases or purchase amount during a specific period.

Behavior Attribute Details (Table)

* Reference

Provided Properties	Explanation
Last purchase date in 3 months	The last time a user purchased an item from the service in the past 3 months.
Last purchase date in the last 6 months	The last time a user purchased an item from the service in the past 6 months.
Last purchase date in the past year	The last time a user purchased an item from the service within the past year.
First purchase date in 3 months	The date and time when the user first purchased an item from the service in the past 3 months.
First purchase date in 6 months	The date and time when the user first purchased an item from the service in the past 6 months.
Date of first purchase in 1 year	The date and time when the user first purchased an item from the service in the past year.
Number of purchases in 3 months	The number of purchases made on a user's account or device in the last 3 months.
Number of purchases in 6 months	The number of purchases made on a user's account or device in the last 6 months.
Number of purchases per year	The number of purchases made on a user's account or device in the past year.
Purchase amount for 3 months	The amount of purchases made on your account or device in the last 3 months.
Purchase amount for 6 months	The amount of purchases made on your account or device in the last 6 months.
Purchase amount for 1 year	The amount of purchases made on your account or device in the past year.
Average purchase amount over 3 months	The average purchase amount for the user's account or device over the past 3 months.
Average purchase amount over 6 months	The average purchase amount for the user's account or device over the last 6 months.
Average purchase amount per year	The average purchase amount for a user's account or device over the past year.
Most purchased day of the week in 3 months	This is the day of the week on which users made the most purchases in the past 3 months. This can be used to understand users' purchasing patterns.
Most purchased day of the week in 6 months	This is the day of the week on which users made the most purchases in the last 6 months. This can be used to understand users' purchasing patterns.
Most purchased day of the year	This is the day of the week on which users made the most purchases in the past year. This can be used to understand users' purchasing patterns.
Most Purchased Time in 3 Months	This is the time period in which users made the most purchases in the past 3 months. This can be used to determine the time period in which users make purchases.
Most Purchased Time in 6 Months	This is the time period in which users made the most purchases in the past 6 months. This can be used to determine the time period in which users make purchases.
Most Purchased Time in 1 Year	This is the time period in which users made the most purchases in the past year. This can be used to determine the time period in which users make purchases.
#1 in purchase category for 3 months	This is the first most purchased item in the major categories that users have purchased the most in the last 3 months.
#1 in purchase category for 6 months	This is the first most purchased item in the major categories that users have purchased the most in the last 6 months.
#1 in purchase category for 1 year	This is the first most purchased item in the major categories that users have purchased the most in the past year.
Ranked 2nd in major purchase categories for 3 months	This is the second most purchased category among users over the past three months.
Ranked 2nd in major purchase categories for 6 months	This is the second most purchased category by users over the last six months.
Ranked 2nd in major purchase categories for the past year	This is the second most purchased category by users over the past year.
3rd most purchased category in 3 months	This is the third most purchased category among the items purchased by users in the last three months.
3rd most purchased category for 6 months	This is the third most purchased category by users over the last six months.
3rd most purchased category in 1 year	This is the third most purchased category by users over the past year.
#1 most purchased item for 3 months	This is the first most purchased item among products purchased by users in the last 3 months.
#1 most purchased item for 6 months	This is the first most purchased item among products purchased by users in the last 6 months.
#1 most purchased product in 1 year	This is the first most purchased item among products that users purchased the most in the past year.
2nd most purchased item in 3 months	This is the second most purchased item by users in the last 3 months.
2nd most purchased item in 6 months	This is the second most purchased item by users in the last 6 months.
2nd most purchased product in 1 year	This is the second most purchased item by users over the past year.
3rd most purchased item in 3 months	The third most purchased item by users in the last 3 months
3rd most purchased item in 6 months	The third most purchased item by users in the last 6 months
3rd most purchased product in 1 year	The third most purchased item by users over the past year
Last updated date	The last time the user information was updated.
Number of sessions per year (total active events)	The total number of user sessions. A session is a unit in which a user accesses an app or web service and engages in an activity for a certain period of time before it ends.
Number of events per year	The total number of user events. Events are various interactions that occur within an app or web, such as page views and searches.
Last activity date	The last time the user was active on the service.
First access date and time	The time when the user first accessed the service.

3. When you click '+ Add Condition', you can only add the same filter conditions. For example, if you selected an event as a filter condition, you can only select an event in the additional conditions, and if you started with a user profile condition, you can only set the additional conditions as a user profile\ \ Only AND conditions can be added, and OR conditions can be applied through a Venn diagram using the group palette.\ ![](/files/7ODhTBVJOEoK6m9o6EWc)![](/files/lWieVnrGa0YPfwgTLm05) ## **Group Palette Settings**

1. Drag and drop the created groups to create intersections, unions, differences, complements, and symmetric differences according to your purpose and needs. Audience calculations are not possible if there are any uncombined groups left.
* Detailed instructions on how to combine groups `?`can be found through the guide button ' ' at the top of the palette. * Intergroup bonding can be done up to 3 depth. * The number of groups that can be created is a minimum of 1 and a maximum of 4. 2. Click the 'Calculate Audience' button to calculate the parameters.\ Be sure to check the parameters through the audience calculation.

3. After that, click the Save Draft or Publish button to add an audience name and description.

4. You can check the saved audiences in the list.

5. When you enter the generated audience details screen, you can check the offsite campaign parameters or set whether to schedule it.

Once an audience has been published, the conditions and Venn diagram cannot be modified as this may affect the campaign (use) results.

Offsite campaign parameters are a feature that allows you to check the parameters for which messages can be sent based on the last calculated parameters.

## **Audience activation and retention** In CRM and reports, Active you can only select audiences by status. Custody However, since there is a limit to the number of audiences you can create, you can manage them separately if complex conditions are applied even if you no longer use the audience .

	Number	Note
Generation	Up to 100	Including temporary storage audience
Active	Up to 50
Custody	The number of creations minus the number of activations. Example) If 70 are created and 50 are activated, 30 can be stored.	Temporary saved audiences cannot be stored

{% hint style="danger" %} * **Audiences that are being used in CRM campaigns or report filters cannot be archived.**\ When archiving or deleting an audience, if the audience is being used in analysis or campaigns, you must directly deactivate and delete the audience or change it to archive status in the campaign area.
* **Audiences that have no intended use can be archived if campaign scheduling is enabled.** {% endhint %}

## **Viewable period** * You can set up to 100 days per group. * When the period is set to 'Relative', the selectable reference date can also be set to up to 100 days in advance. * When combining two groups, you can search for up to 200 days. ( [Related Guide](https://docs.dfinery.ai/user-guide/customer/audience/samples#id-200) ) ## **Limit rule** * The Not condition (exclude operator) is only supported when setting events and user profile properties that are always kept up to date. * The Not condition is not supported when setting event properties. * However, when setting up event triggering, the Not condition is also supported for event properties. * When creating an audience, data can be retrieved for up to 200 days. --- # 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: ``` GET https://docs.dfinery.ai/user-guide/en/customer/audience.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.