> For the complete documentation index, see [llms.txt](https://user.netmera.com/netmera-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://user.netmera.com/netmera-user-guide/targeting/people.md). # People People is the user database in Netmera. Each record can include profile attributes, linked devices, events, permissions, targeting data, and message history. Use People to find users, build target lists, save groups with tags, and export results. Choose the search method that matches your goal. Use **Select People** for common filters, such as users in a city or users with push permission. Use **Advanced** when rules need AND/OR logic, such as premium or gold users in Istanbul. Use **Find Person** to investigate one known user by External ID or email. After you build a list, review the resulting users before taking action. You can save the list as a tag for later targeting or export selected identifiers for analysis and external processing. **Path:** `Targeting > People` ### Search users You can search in three ways: 1. **Select People**: quick filtering with predefined fields. 2. **Advanced**: build rules with condition groups. 3. **Find Person**: open a single user by identifier. ### Select People Select People is the fastest way to build a list. Combine predefined filters from different categories to narrow the resulting user list. For example, select users in a specific city through **Profile**, then limit the list to a specific **App Version**.
#### Permissions Use these filters to include or exclude users based on opt-in status. Use permission filters before a campaign when delivery depends on the user’s notification or location choice. * **Push Permission**: targets users who allowed or blocked push notifications. * **Category Permission**: targets users by category-level permissions (when your app uses notification categories). * **Location Preferences**: targets users by location permission status (allowed / denied). #### User grouping Use these filters to target existing user groups. Use **Tag** for a group you saved or managed manually. Use **Segment** for a group whose membership changes with its rules and user behavior. * **Tag**: targets users you labeled earlier. Tags are manual or operational groupings. * **Segment**: targets users in a segment. Segment membership can change dynamically based on rules and behavior. #### Profile Use this to target users by profile attributes. Profile attributes store information about users. The available attributes depend on the profile data configured for your application. * **Profile**: filters by attributes like age, gender, membership level, city, or any custom profile attribute. For example, combine `City = Istanbul` with `Membership Level = Premium` to find premium users in Istanbul. #### Engagement Use these filters to target users based on interaction and incentive state. For example, use **Response** to find users who clicked a message. Use the result for a follow-up campaign. * **Response:** filters users based on whether they interacted with previous messages, with optional message label and date-based filtering. When you select a message label in Response, you can optionally apply an In the Last or Date Between filter. This lets you include or exclude users based on whether they received or interacted with labeled messages within a specific period. * **Promotion**: filters users by whether they have a promotion code/value (or not). * **Blacklist**: include or exclude users based on blacklist status (for example, to avoid messaging blocked users). {% hint style="info" %} Date filters in Response filter is available for continuous push notification campaigns, including automated, transactional, geofence, and workflow campaigns. {% endhint %}
#### Device / technical Use these filters when you need technical scoping (platform, version, provider, etc.). Combine these filters with profile or engagement filters when the message needs technical scoping. For example, find users on the latest app version who did not click a selected message. * **Platform**: iOS vs Android. * **Device Count**: targets users by how many devices are linked to their profile (useful for multi-device vs single-device users). * **Device Type**: phone vs tablet (and other device categories if available). * **Device**: device model/manufacturer based targeting. * **Operator**: telecom operator based targeting. * **App Version**: target or exclude specific app versions. * **Operating System**: OS version level targeting (for example iOS 17+). * **Android Provider**: provider-level targeting (for example Google vs Huawei). * **Installation Source**: acquisition source via Adjust (requires Adjust integration). * **App Tracking**: Android-only targeting based on installed apps (App Tracking feature). * **App Installation**: targets users by install status or install timing windows.
### Advanced search Advanced search lets you build complex rules. You combine conditions and groups with AND/OR logic. Use **Advanced** when the target criteria need more than a simple filter combination. It lets you group related conditions and apply separate AND/OR logic to each group. {% hint style="info" %} **AND vs OR** * **OR**: at least one condition in the group must match. * **AND**: all conditions in the group must match. For example, `City = Istanbul AND Membership Level = Premium` returns users who meet both conditions. You can nest logic with a group. For example, `City = Istanbul AND (Membership Level = Premium OR Membership Level = Gold)` returns premium or gold users in Istanbul. {% endhint %} #### Add Condition Use **Add Condition** to add a single rule. Each condition defines one requirement. Select the filter, operator, and value that a user must match.
#### Add Group Use **Add Group** to nest conditions and build more complex logic. Use a group when different condition sets need separate AND/OR logic. Review the resulting user list before tagging or exporting it.
### Work with search results After you build a user list, you typically do one of these actions: #### Start Tagging Use **Start Tagging** to create a tag from the result list. You can later message, export, or manage that tag from the Tags dashboard. Tags save a group based on the criteria you selected. For example, create a tag for users who clicked a campaign, then use that tag in later targeting. {% hint style="info" %} See [Tags](/netmera-user-guide/targeting/tags.md) for tag management and messaging flows. {% endhint %} #### Export Selected Users to File Use Export to download the current list for analysis or external processing. Select the identifiers required by the next system or analysis. For example, export **External ID**, **Email**, and **MSISDN** when all three are needed. You can export multiple user identifiers in the same file. This export uses the same behavior described in [Export Module](/netmera-user-guide/targeting/export-users.md). Key points: * Identifier selection supports **multi-select** (e.g., External ID + Email + MSISDN). * Each selected identifier becomes a **separate column**. * Missing values are exported as `null`. * Format is `.csv` or `.xlsx` (depending on the screen).
### Find a specific user Use Find Person to open a single user quickly. Search by external ID or email. Use this method when you need one user, not a filtered list.
### User Details Click a user’s External ID to open User Details. You can review profile, devices, activity, and messaging history. Use User Details to investigate the selected user’s profile, devices, activity, targeting data, permissions, and message history. Available tabs include: * Profile * Devices * Events * Messages * Targeting * Device Opt-In * User Opt-In * Blacklist * Privacy * Coupon Codes #### Messages tab
The Messages tab shows the user’s message history for a selected date range. It is useful for support, audits, and troubleshooting. Use it to investigate delivery issues, review a support request, or audit message activity. For failed deliveries, you can see details like: * **Failure reason** (error message) * **Error code** (if provided by the SMS provider) Date range rules: * Query in **30-day** intervals. * Access up to the **last 6 months (180 days)**. If you need to review more than 30 days, query the required period in separate 30-day intervals. ### Choose the right search method | If you want to… | Use | | --------------------------------------------- | ------------------------------------------------- | | Build a user list with common filters | **Select People** | | Combine nested conditions with AND/OR logic | **Advanced** | | Find one specific user | **Find Person** | | Save a reusable group from results | **Start Tagging** | | Download users for analysis or another system | **Export Selected Users to File** | | Investigate one user’s message history | **Find Person** → **User Details** → **Messages** | --- # 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://user.netmera.com/netmera-user-guide/targeting/people.md?ask=&goal= ``` `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.