# User Group Filter Condition Explanation In the User Group settings, you can group users based on characteristics and trends that match your business. This article explains what each filter condition represents in terms of user behavior, visit attribute data, and user attributes. Segment conditions are divided into the following 3 types. **Type 1: User Behavior** **1 Web Page:** Users who accessed a specified page become part of the corresponding group. **2 Event:** Users who triggered a specified event become part of the corresponding group. **3 Visit:** Users who accessed any page where the corresponding project tag is installed become part of the corresponding group. **Type 2: Visit Attributes** **1 Visit Type:** Grouping is done based on whether the user is a new visitor or a returning visitor. (Please note that this condition is different from "Visit" in Type 1: User Behavior) **2 Landing Page:** Users who started a visit with a specified page as the landing page become part of the corresponding group. **3 Referrer URL:** Users who came from a specified referrer page become part of the corresponding group. **4 Referrer Host:** This can be considered essentially the same as "Referrer URL". Host simply refers to the domain portion. For example, in the URL [x.ptengine.jp/a](/en/faq/experience-edit/filter-conditions.md), x.ptengine.jp is the host. **5 Campaign Name:** Specifies the utm\_campaign information attached to the URL. Users from the specified campaign become part of the corresponding group. **6 Source:** Specifies the utm\_source information attached to the URL. Users from the specified source become part of the corresponding group. **7 Medium:** Specifies the utm\_medium information attached to the URL. Users from the specified medium become part of the corresponding group. **8 Keyword:** Specifies the utm\_term information attached to the URL. Users from the specified keyword become part of the corresponding group. **9 Content:** Specifies the utm\_content information attached to the URL. Users from the specified content become part of the corresponding group. **10 Device Type:** Users who accessed from a specified device become part of the corresponding group. Three types of devices can be configured: PC, mobile, and tablet. **11 OS:** Users using a specified OS become part of the corresponding group. **12 OS Version:** Users using a specified OS version become part of the corresponding group. **13 Browser:** Users who accessed using a specified browser become part of the corresponding group. **14 Browser Version:** Users using a specified browser version become part of the corresponding group. **15 Resolution:** Users who used a specified browser resolution become part of the corresponding group. **16 Maker:** Users using a device from a specified maker become part of the corresponding group. **17 Country/Region:** Users accessing from a specified country/region become part of the corresponding group. (Area information is obtained from IP addresses) **18 Prefecture:** Users accessing from a specified prefecture become part of the corresponding group. (Area information is obtained from IP addresses) **Type 3: User Attributes** By setting user identification tags, you can acquire custom user attribute data. You can infer user needs, preferences, habits, etc. based on user attributes. Furthermore, by using this data to implement appropriate personalization for users, you can achieve improved user experience and maximum effectiveness. If you have acquired custom user attribute data through user identification tags, the following attributes are included by default. Users with a specified user label become part of the corresponding group. If you want to add other attributes, please refer to [this article](/en/faq/experience-edit/filter-conditions.md). **total session:** You can specify the number of sessions. Users matching the specified number of sessions become part of the group. **initial referring domain:** When the referrer of a user who accessed for the first time matches the settings, the user becomes part of the corresponding group. **initial referrer:** This is essentially the same as "initial referring domain" above. In "initial referring domain", what is specified is the domain. In this case, you can also set the URL. **distinct user ID:** Users matching the specified ID become part of the corresponding group. (User ID can be assigned via user identification tags.) **first seen:** You can specify the date when the user first accessed your site. Users matching the specified period become part of the corresponding group. **last active:** You can specify the date when the user last logged in. Users matching the specified period become part of the corresponding group. **country (last country):** You can specify the country where the user was located when they last logged in. Users matching the specified country become part of the corresponding group. **city (last city):** You can specify the city where the user was located when they last logged in. Users matching the specified city become part of the corresponding group. **region (last region):** You can specify the region where the user was located when they last logged in. Users matching the specified region become part of the corresponding group. **os (last os):** You can specify the OS that the user was using when they last logged in. Users matching the specified OS become part of the corresponding group. **browser (last browser):** You can specify the browser that the user was using when they last logged in. Users matching the specified browser become part of the corresponding group. --- # Agent Instructions: 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://helps.ptengine.com/en/faq/experience-edit/filter-conditions.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.