> 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 Netmera user database for finding users, reviewing profiles, building lists and exporting results.

The **People** screen is the starting point for understanding who is in your audience. It answers two different questions from a single place: "How many people match these conditions, and who are they?" and "Where is this specific person, and can we reach them?"

Marketing, CRM and support teams use People before launching a campaign to validate an audience size, to test a targeting idea without saving a segment, or to find a single user when investigating a delivery issue or a customer complaint.

To open the screen, go to **Targeting > People**.

The screen has two tabs:

<table><thead><tr><th width="160.29296875">Tab</th><th>Purpose</th><th>Typical question it answers</th></tr></thead><tbody><tr><td><strong>Filter people</strong></td><td>Build an audience from filter rules and groups, and see how many people match.</td><td>"How many users with mobile permission opened the app in the last 7 days?"</td></tr><tr><td><strong>Find Person</strong></td><td>Look up one person by a known identifier.</td><td>"Is the user with External ID <code>12345</code> reachable by email?"</td></tr></tbody></table>

{% hint style="info" %}
People is an exploration tool. Filters built here are for checking audience size and composition. To reuse an audience in campaigns or journeys, create it as a segment
{% endhint %}

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FAT6dITvO9umEjtDdxj8g%2FEkran%20Resmi%202026-09-29%2011.58.01.png?alt=media&amp;token=7425a2e4-976f-4f94-9c07-db72439c2bd8" alt=""><figcaption></figcaption></figure>

### Filter people

**Filter people** lets you describe an audience as a set of conditions and immediately see how many people meet them. Instead of guessing audience size or waiting for a campaign report, you can combine permissions, behaviors, profile attributes, segments, tags and device information, and check the result before any message goes out.

The tab is made up of three working areas:

1. **Frequently used** shortcuts and the group bar (top left)
2. **Filter builder**, where groups and rules are created (left)
3. **Rule Description** and **Matching people** panels (right)

#### Key concepts

Understanding three building blocks makes every audience on this screen easier to read and build.

<table><thead><tr><th width="163.921875">Concept</th><th width="338.77734375">Definition</th><th>Example</th></tr></thead><tbody><tr><td><strong>Filter rule</strong></td><td>A single condition made of a filter type, an operator and a value.</td><td><code>Channel Permission</code> <code>Equals</code> <code>Mobile</code></td></tr><tr><td><strong>Filter group</strong></td><td>A container that holds one or more rules and combines them with a single logical operator (AND or OR). Groups are labeled automatically as Group A, Group B, Group C and so on.</td><td>Group A: "Channel Permission equals Mobile" AND "Platform equals iOS"</td></tr><tr><td><strong>Logical operator</strong></td><td>Defines how rules inside a group, and groups relative to each other, are combined.</td><td><strong>AND</strong>: all conditions must be true. <strong>OR</strong>: at least one condition must be true.</td></tr></tbody></table>

#### Frequently used

The **Frequently used** area shows rules that have been added often in your account, as ready-made chips.

This saves time when the same conditions are used repeatedly. Clicking a chip adds that exact rule, with its filter type and value already set, to the filter builder, so there is no need to reopen the rule picker and search for the value again.

{% hint style="info" %}
Frequently used chips are built from your account's own usage, so the list differs between accounts and changes over time.
{% endhint %}

#### Group bar

Directly under **Frequently used**, a **Group** tag is shown for each filter group currently in the builder. When there are two groups, two **Group** tags appear.

Each tag has an **×** icon. Clicking **×** removes that group together with all rules inside it. This is a quick way to clean up the builder without scrolling to each group's delete icon.

#### Building a filter

The filter builder is where the audience logic is written. Each group is displayed as a bordered box with its label (**Group A**, **Group B**…), its operator selector, its rules and its own action links.

**1. Add a filter rule**

1. Click **Add Filter Rule**, either inside a group (the blue link) or below all groups (the outlined button).
2. The rule picker opens. The left column lists filter types, the right column lists the available values for the selected type.
3. Select a filter type from the left column.
4. Use the search box (for example, **Search in Channel Permission**) to narrow down long value lists, then select a value.
5. The rule is added to the group as a numbered row, for example **1 Channel Permission · Equals · Mobile**.

Each rule row contains:

<table><thead><tr><th width="204.18359375">Element</th><th>Description</th></tr></thead><tbody><tr><td><strong>Rule number</strong></td><td>The rule's order within its group (1, 2, 3…). Used to refer to rules when reading the logic.</td></tr><tr><td><strong>Filter type</strong></td><td>The data the rule checks, such as Channel Permission.</td></tr><tr><td><strong>Operator</strong></td><td>How the value is compared, such as <strong>Equals</strong>. Available operators depend on the filter type.</td></tr><tr><td><strong>Value</strong></td><td>The value being compared, such as <strong>Mobile</strong>. Click it to change the value.</td></tr><tr><td><strong>Delete icon</strong> (red, right)</td><td>Removes this single rule from the group.</td></tr></tbody></table>

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FrGCqcgP3JrhFiQvomawZ%2FEkran%20Resmi%202026-09-29%2012.00.54.png?alt=media&amp;token=2cec48c5-4ff2-4835-af48-138b0e8850d2" alt=""><figcaption></figcaption></figure>

**2. Choose how rules in a group are combined**

Every group has an operator selector next to its label, set to **AND** by default. Change it to **OR** from the dropdown when needed.

<table><thead><tr><th width="126.9453125">Group operator</th><th width="222.984375">Logic</th><th>Result</th></tr></thead><tbody><tr><td><strong>AND</strong></td><td>Every rule in the group must be true.</td><td>Narrows the audience. Each additional rule removes people who do not meet it.</td></tr><tr><td><strong>OR</strong></td><td>At least one rule in the group must be true.</td><td>Widens the audience. Each additional rule brings in more people.</td></tr></tbody></table>

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FXnoKWXDioG0iqjU1xWBU%2FEkran%20Resmi%202026-09-29%2012.00.21.png?alt=media&amp;token=4939ffc9-de0e-4844-981e-64959ba5e920" alt=""><figcaption></figcaption></figure>

**3. Add more groups**

Groups make it possible to express logic that a single operator cannot, such as "(A and B) or C".

* **Add Filter Group** below all groups creates a new top-level group (Group B, Group C…).
* **Add Filter Group** inside a group creates a nested group within that group, for more complex conditions.

When there are two or more top-level groups, a connector selector (**AND** or **OR**) appears between them on the left, and the same connector is shown between the groups in the **Rule Description** panel.

<table><thead><tr><th width="221.38671875">Connector between groups</th><th>Result</th></tr></thead><tbody><tr><td><strong>AND</strong></td><td>A person must satisfy every group.</td></tr><tr><td><strong>OR</strong></td><td>A person must satisfy at least one group.</td></tr></tbody></table>

{% hint style="info" %}
A group with no rules does not add any condition. Before checking results, make sure each group contains at least one rule, or remove empty groups with the red delete icon or the **×** on the group bar.
{% endhint %}

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FX4xyEHsD8af0CZGltDIG%2FEkran%20Resmi%202026-09-29%2012.01.39.png?alt=media&amp;token=42448a0d-f7ca-46c6-b10e-2253431c17b4" alt=""><figcaption></figcaption></figure>

**4. Delete rules and groups**

<table><thead><tr><th width="281.04296875">Action</th><th>How</th></tr></thead><tbody><tr><td>Delete a single rule</td><td>Click the red delete icon at the right end of the rule row.</td></tr><tr><td>Delete a group and all of its rules</td><td>Click the red delete icon at the top right of the group box, or click <strong>×</strong> on the group's tag in the group bar.</td></tr></tbody></table>

#### Filter rules

The rule picker lists every filter type available on the People screen. Filter types appear in the left column of the picker; selecting one shows its available values in the right column, with a search box to narrow long value lists. Each filter type reads a different part of a person's data in Netmera, so choosing the right one is the first step in expressing an audience accurately.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FCMf75uhZBgPyZiD3Dhxc%2FEkran%20Resmi%202026-09-29%2011.59.04.png?alt=media&amp;token=75e4b186-982c-4db2-96ab-a807a6c08453" alt=""><figcaption></figcaption></figure>

The table below lists all filter types in the order they appear in the picker. The **Category** column shows the kind of data each one checks:

* **Permission**: whether the person can be reached, and on which channel. Include at least one permission filter when checking an audience for an actual send.
* **Audience**: who the person is and which existing audiences they belong to.
* **Engagement**: what the person has done in the app and in response to messages.
* **Device & App**: the devices the person uses and the state of the app on them.
* **Network**: the person's mobile network.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FtpnrC9QFHlxEcEpG4gT2%2FEkran%20Resmi%202026-09-29%2011.59.40.png?alt=media&amp;token=4b8b2323-3047-4f08-baa7-26d3c940cba0" alt="" width="563"><figcaption></figcaption></figure>

<table><thead><tr><th width="48.98046875">#</th><th width="133.8515625">Filter type</th><th width="277.9140625">What it checks</th><th>Typical use</th><th data-hidden>Category</th></tr></thead><tbody><tr><td>1</td><td><strong>Channel Permission</strong></td><td>Whether the person has permission to receive messages on a channel. Values: <strong>Mobile</strong>, <strong>Web</strong>, <strong>SMS</strong>, <strong>Email</strong>, <strong>WhatsApp</strong>.</td><td>Checking how many people can receive a message on the channel you plan to use.</td><td>Permission</td></tr><tr><td>2</td><td><strong>Behavior</strong></td><td>Events the person has performed, such as app opens, purchases or custom events.</td><td>Targeting people who did, or did not, perform a specific action.</td><td>Engagement</td></tr><tr><td>3</td><td><strong>Profile Attribute</strong></td><td>Values stored on the person's profile, such as city, gender, membership level or custom attributes.</td><td>Targeting by demographic or CRM data.</td><td>Audience</td></tr><tr><td>4</td><td><strong>Segment</strong></td><td>Membership in an existing segment.</td><td>Reusing a defined audience and combining it with other rules.</td><td>Audience</td></tr><tr><td>5</td><td><strong>Tag</strong></td><td>Tags assigned to the person.</td><td>Targeting people labeled through the API, SDK or file imports.</td><td>Audience</td></tr><tr><td>6</td><td><strong>Platform</strong></td><td>The platform of the person's devices, such as iOS, Android or Web.</td><td>Sending platform-specific content or checking platform distribution.</td><td>Device &#x26; App</td></tr><tr><td>7</td><td><strong>Platform Permission</strong></td><td>Push notification permission status on a specific platform.</td><td>Separating people who have granted push permission on iOS, Android or Web.</td><td>Permission</td></tr><tr><td>8</td><td><strong>Response</strong></td><td>How the person responded to previous messages, such as opens or clicks.</td><td>Retargeting engaged people or re-engaging unresponsive ones.</td><td>Engagement</td></tr><tr><td>9</td><td><strong>Message Category</strong></td><td>The person's opt-in status for message categories defined in your account, such as Bilgilendirme (Informational).</td><td>Respecting category preferences and commercial message consent before sending.</td><td>Permission</td></tr><tr><td>10</td><td><strong>Device Type</strong></td><td>The type of device, such as phone or tablet.</td><td>Adjusting content or layout by device type.</td><td>Device &#x26; App</td></tr><tr><td>11</td><td><strong>Device Model</strong></td><td>The specific device model.</td><td>Troubleshooting model-specific issues or targeting a device range.</td><td>Device &#x26; App</td></tr><tr><td>12</td><td><strong>Location Tracking</strong></td><td>Whether the person has granted location permission to the app.</td><td>Validating the reachable audience for geofence and location-based campaigns.</td><td>Permission</td></tr><tr><td>13</td><td><strong>App Installation</strong></td><td>App installation status or installation date.</td><td>Onboarding audiences for new installs, or identifying long-term users.</td><td>Device &#x26; App</td></tr><tr><td>14</td><td><strong>App Version</strong></td><td>The app version installed on the person's device.</td><td>Prompting users on older versions to update, or targeting a feature to versions that support it.</td><td>Device &#x26; App</td></tr><tr><td>15</td><td><strong>Operating System</strong></td><td>The operating system version of the device.</td><td>Targeting OS versions that support a specific feature, or excluding unsupported ones.</td><td>Device &#x26; App</td></tr><tr><td>16</td><td><strong>Android Provider</strong></td><td>The push provider on the person's Android device, such as Google (FCM) or Huawei (HMS).</td><td>Separating audiences by push infrastructure, for example Huawei devices without Google services.</td><td>Device &#x26; App</td></tr><tr><td>17</td><td><strong>Operator</strong></td><td>The mobile network operator of the person's device.</td><td>Operator-specific campaigns or diagnosing carrier-related delivery issues.</td><td>Network</td></tr><tr><td>18</td><td><strong>Promotion</strong></td><td>Promotions associated with the person.</td><td>Targeting or excluding people who have received or are eligible for a promotion.</td><td>Audience</td></tr><tr><td>19</td><td><strong>App Tracking (Android Only)</strong></td><td>Whether app usage tracking is enabled on the person's Android device.</td><td>Scoping audiences that rely on installed app data, available only for Android.</td><td>Permission</td></tr><tr><td>20</td><td><strong>Installation Source</strong></td><td>The source the app was installed from, such as a store or campaign.</td><td>Measuring or targeting users acquired through a specific channel.</td><td>Device &#x26; App</td></tr><tr><td>21</td><td><strong>Advertising ID Permission</strong></td><td>Whether the person has allowed access to the device advertising identifier (IDFA on iOS, GAID on Android).</td><td>Building audiences for ad-network matching or attribution use cases.</td><td>Permission</td></tr><tr><td>22</td><td><strong>Blacklist</strong></td><td>Whether the person is on a blacklist in your account.</td><td>Excluding blocked users from an audience, or checking how many people are blacklisted.</td><td>Permission</td></tr><tr><td>23</td><td><strong>Device Count</strong></td><td>The number of devices associated with the person.</td><td>Identifying single-device or multi-device users.</td><td>Device &#x26; App</td></tr></tbody></table>

{% hint style="info" %}
Available values and operators depend on the filter type and on the data in your account. For example, Segment and Tag list the segments and tags created in your account, and Message Category lists the categories defined in your settings.
{% endhint %}

#### Rule Description

The **Rule Description** panel on the right translates the filter builder into plain language, group by group. For example, a group containing one rule is shown as:

> **Group A** Channel Permission equals Mobile

When there is more than one group, the panel shows each group in its own box and places the connector (**AND** or **OR**) between them.

This panel is the fastest way to confirm that the audience logic says what you intend, especially when groups, nested groups and mixed operators are used. Read it before checking results. If the sentence does not match your intention, adjust the builder first.

{% hint style="info" %}
Rule Description is read-only. All changes are made in the filter builder on the left, and the panel updates as you edit.
{% endhint %}

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FKOH86q9c2WqQCPieYerd%2FEkran%20Resmi%202026-09-29%2012.12.30.png?alt=media&amp;token=8c08d1de-a4f6-4713-a1cb-bc835f8e4eb1" alt="" width="563"><figcaption></figcaption></figure>

#### Matching people

The **Matching people** panel shows the result of the current filter.

<table><thead><tr><th width="150.42578125">Element</th><th>Description</th></tr></thead><tbody><tr><td><strong>People match</strong></td><td>The number of people who meet all conditions in the filter builder.</td></tr><tr><td><strong>Show results</strong></td><td>Runs the filter and loads the matching people, so you can see who they are rather than only how many.</td></tr></tbody></table>

Use **Show results** after the logic is final and confirmed in **Rule Description**. If you change any rule or operator afterwards, run **Show results** again to see the updated audience.

{% hint style="info" %}
If the count shows **0**, check the following before assuming the audience is empty: the filter has been run with **Show results**, no group is empty, the operators are correct (AND narrows, OR widens), and the selected values exist in your account's data.
{% endhint %}

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FOT9z0sTHARptdtsMJBnJ%2FEkran%20Resmi%202026-09-29%2012.12.54.png?alt=media&amp;token=86acbed6-56d5-4901-a232-a64c39f6b87a" alt="" width="563"><figcaption></figcaption></figure>

#### Examples

The following examples show how the same building blocks produce different audiences.

**Example 1: Single condition**

**Goal:** Count everyone who can receive mobile push notifications.

<table><thead><tr><th width="154.30859375">Group</th><th width="171.35546875">Operator</th><th>Rules</th></tr></thead><tbody><tr><td>Group A</td><td>AND</td><td>1. Channel Permission · Equals · Mobile</td></tr></tbody></table>

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FpDja3T15enrKGwVuGE7k%2FEkran%20Resmi%202026-09-29%2012.14.52.png?alt=media&amp;token=2214802f-4ce9-4a70-85ae-ca3648720f00" alt=""><figcaption></figcaption></figure>

**Rule Description:** Group A — Channel Permission equals Mobile.

**Example 2: All conditions required (AND)**

**Goal:** Find people who have mobile permission and have opted in to informational messages.

<table><thead><tr><th width="154.81640625">Group</th><th width="175.2421875">Operator</th><th>Rules</th></tr></thead><tbody><tr><td>Group A</td><td>AND</td><td>1. Channel Permission · Equals · Mobile</td></tr><tr><td></td><td></td><td>2. Message Category · Equals · Notification</td></tr></tbody></table>

A person must meet both rules to be counted.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FkSzzu6kIeGZgquutapvR%2FEkran%20Resmi%202026-09-29%2012.15.17.png?alt=media&amp;token=50688c93-1bfe-42fc-add0-03f1268a0d55" alt=""><figcaption></figcaption></figure>

**Example 3: Any condition is enough (OR)**

**Goal:** Find everyone reachable by either SMS or email.

<table><thead><tr><th width="155.140625">Group</th><th width="174.734375">Operator</th><th>Rules</th></tr></thead><tbody><tr><td>Group A</td><td>OR</td><td>1. Channel Permission · Equals · SMS</td></tr><tr><td></td><td></td><td>2. Channel Permission · Equals · Email</td></tr></tbody></table>

A person who meets either rule is counted.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FPS3hbzjc39K2NTGGP1O2%2FEkran%20Resmi%202026-09-29%2012.15.34.png?alt=media&amp;token=c92d7f5d-c7ec-4eea-a38f-e2edca3d1a63" alt=""><figcaption></figcaption></figure>

**Example 4: Combining groups**

**Goal:** Find people who have mobile permission and use a single device, or people who belong to a VIP segment regardless of other conditions.

<table><thead><tr><th width="154.57421875">Group</th><th width="175.359375">Operator</th><th>Rules</th></tr></thead><tbody><tr><td>Group A</td><td>AND</td><td>1. Channel Permission · Equals · Mobile</td></tr><tr><td></td><td></td><td>2. Device Count · Greater Than · 1</td></tr><tr><td><em>Connector</em></td><td><strong>OR</strong></td><td></td></tr><tr><td>Group B</td><td>AND</td><td>1. Segment · Equals · Active users in 7 days</td></tr></tbody></table>

Logic: **(Channel Permission = Mobile AND Device Count > 1) OR (Segment = Active users)**

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FJTUxpfw6huXdF7JFsgVw%2FEkran%20Resmi%202026-09-29%2012.17.07.png?alt=media&amp;token=b3af7c48-53d9-4e65-9b71-965a8f8cba2a" alt=""><figcaption></figcaption></figure>

#### Export Selected Users to File

After clicking show results, 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).

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2F5NKcGlkxxiS7lGdJWYNl%2FEkran%20Resmi%202026-09-29%2011.57.13.png?alt=media&amp;token=5dae27be-826d-409e-a53c-08c0d2305b25" alt="" width="563"><figcaption></figcaption></figure>

### Find Person

**Find Person** looks up a single person by an identifier you already know. Where Filter people works with audiences, Find Person works with individuals: it is the right tool when a customer contacts support, when a specific test device needs to be verified, or when you need to check whether a known user can be reached on a given channel.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FE26tmem6vmQz8LHge8a0%2FEkran%20Resmi%202026-09-29%2012.18.25.png?alt=media&amp;token=2f4ddada-1d55-461c-9852-3e4e9da55bb2" alt="" width="563"><figcaption></figcaption></figure>

#### How to find a person

1. Open the **Find Person** tab.
2. Select the identifier type from the dropdown on the left. **External ID** is selected by default.
3. Enter the value in the **Enter the identifier** field.
4. Click **Find person**. The button becomes active once a value is entered.
5. Matching results are listed in the table below the search bar.

To clear the input and start a new search, click the **×** icon inside the field.

#### Identifier types

<table><thead><tr><th width="203.0859375">Identifier</th><th>What to enter</th><th>When to use</th></tr></thead><tbody><tr><td><strong>External ID</strong></td><td>The user ID your own system assigns and sends to Netmera.</td><td>The most reliable option when your CRM or backend user ID is known.</td></tr><tr><td><strong>Email</strong></td><td>The person's email address.</td><td>Support cases where the customer shares their email.</td></tr><tr><td><strong>Phone Number</strong></td><td>The phone number registered for SMS.</td><td>Investigating SMS delivery or SMS consent.</td></tr><tr><td><strong>WhatsApp Number</strong></td><td>The number registered for WhatsApp messaging.</td><td>Investigating WhatsApp delivery or WhatsApp consent.</td></tr></tbody></table>

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2F6xJlG8kDJtaxBequXd7u%2FEkran%20Resmi%202026-09-29%2012.19.02.png?alt=media&amp;token=bd50f65a-1f4f-4d13-8544-1ae6b2199c7c" alt="" width="563"><figcaption></figcaption></figure>

{% hint style="info" %}
Enter the identifier exactly as it is stored in Netmera. For phone and WhatsApp numbers, use the same format your integration sends, including the country code if it is stored that way.
{% endhint %}

#### Search results

Each result row summarizes the person and their reachability at a glance.

<table><thead><tr><th width="139.33203125">Column</th><th>Description</th></tr></thead><tbody><tr><td><strong>User</strong></td><td>The person's Netmera user ID (for example, <code>KUBRUKmqxvJAe</code>). Click it, or the <strong>></strong> icon next to it, to open the person's full profile.</td></tr><tr><td><strong>External ID</strong></td><td>The External ID associated with the person, if one is set.</td></tr><tr><td><strong>Reachability</strong></td><td>Icons for the channels the person can be reached on: <strong>Mobile</strong>, <strong>Email</strong>, <strong>SMS</strong> and <strong>WhatsApp</strong>. Highlighted icons indicate channels where the person is reachable; greyed-out icons indicate channels where they are not.</td></tr><tr><td><strong>Last seen</strong></td><td>The date and time of the person's most recent activity, in DD/MM/YYYY HH:mm format.</td></tr></tbody></table>

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FEO2h3EswsevgjabJTDdj%2Fimage.png?alt=media&amp;token=e84810fc-58e5-4084-902d-387c4f032974" alt=""><figcaption></figcaption></figure>

**Reachability** and **Last seen** together answer the most common support questions quickly. A person who is not receiving push notifications may have the Mobile icon greyed out (no permission or no active device), or may not have been seen for a long time (the app may have been uninstalled).

### User Details

**User Details** is the full profile page of a single person. It brings together everything Netmera knows about that person, including identity, devices, consent, activity and delivery history, so that a question about one user can be answered from one page without cross-checking several reports.

Support teams use it to investigate why a person did or did not receive a message. Marketing and CRM teams use it to verify that profile data, consent and events are arriving correctly from the integration. QA and product teams use it to set up test users for campaign previews.

To open User Details, search for a person in Find Person and click the Netmera user ID in the **User** column, or the **>** icon next to it.

The page is made up of four areas:

1. **Profile header**: who the person is and which channels they can be reached on
2. **Actions** menu: operations performed on the person
3. **Identity fields**: the identifiers and contact details stored for the person
4. **Detail tabs**: profile attributes, devices, events, messages, consent and privacy data

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FYeWtS7Z3G3eKWGWL5xcn%2Fimage.png?alt=media&amp;token=71c87980-05ec-4c6a-b8a9-307686fd16f2" alt=""><figcaption></figcaption></figure>

#### Profile header

The profile header gives an instant summary of the person at the top of the page.

<table><thead><tr><th width="191.12890625">Element</th><th>Description</th></tr></thead><tbody><tr><td><strong>Avatar</strong></td><td>A circle with the person's initials. When no name is stored, the initials are taken from the display name, such as <strong>NE</strong> for <em>netmera</em>.</td></tr><tr><td><strong>Display name</strong></td><td>The person's name. When Name and Surname are empty, the External ID is shown instead.</td></tr><tr><td><strong>Netmera User ID</strong></td><td>The unique identifier Netmera assigns to the person.</td></tr><tr><td><strong>Channel badges</strong></td><td><strong>Push</strong>, <strong>Email</strong>, <strong>SMS</strong> and <strong>WhatsApp</strong>. These show the channels the person can be reached on, matching the <strong>Reachability</strong> icons in Find Person.</td></tr></tbody></table>

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2F1Z0aOz4ipagfPVGEU3Ny%2FEkran%20Resmi%202026-09-29%2012.31.30.png?alt=media&amp;token=7c5da7cb-b3fe-4868-8c76-a77c83089966" alt=""><figcaption></figcaption></figure>

#### Actions

The **Actions** menu at the top right lists operations that change how Netmera treats this person.

<table><thead><tr><th width="221.6015625">Action</th><th width="274.33203125">What it does</th><th>When to use</th></tr></thead><tbody><tr><td><strong>Assign as tester</strong></td><td>Adds the person as a test user. Test users can receive test messages before a campaign is sent to the real audience.</td><td>Previewing push notifications on a real device before launch.</td></tr><tr><td><strong>Assign as email tester</strong></td><td>Adds the person as a test recipient for email.</td><td>Checking email rendering, links and personalization in a real inbox before sending.</td></tr><tr><td><strong>Remove personal data</strong></td><td>Deletes the personal data stored for the person in Netmera.</td><td>Fulfilling a data deletion request under KVKK, GDPR or similar regulations.</td></tr></tbody></table>

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FtswjC6dlmSyDO4W53emI%2FEkran%20Resmi%202026-09-29%2012.31.49.png?alt=media&amp;token=4345cdc4-3963-42d3-b981-8ecd07313356" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**Remove personal data** permanently deletes the person's personal data and cannot be undone. Use it only when a verified deletion request has been received, and confirm the correct person is open by checking the Netmera User ID and External ID first.
{% endhint %}

#### Identity fields

Identity fields list the identifiers and contact details stored for the person. They are the first place to check when a message does not reach someone: an empty Email field, for example, means the person cannot receive email regardless of their permissions.

<table><thead><tr><th width="231.0859375">Field</th><th>Description</th></tr></thead><tbody><tr><td><strong>Netmera User ID</strong></td><td>The unique ID assigned by Netmera. Click the copy icon to copy it.</td></tr><tr><td><strong>External ID</strong></td><td>The user ID sent from your own system. Click the copy icon to copy it.</td></tr><tr><td><strong>Name</strong></td><td>The person's first name.</td></tr><tr><td><strong>Surname</strong></td><td>The person's last name.</td></tr><tr><td><strong>Email</strong></td><td>The email address used for email messages.</td></tr><tr><td><strong>Phone Number</strong></td><td>The phone number used for SMS messages.</td></tr><tr><td><strong>WhatsApp Number</strong></td><td>The number used for WhatsApp messages.</td></tr></tbody></table>

{% hint style="info" %}
Copy the Netmera User ID or External ID when sharing a case with the support or development team. These IDs identify the person exactly, while names and emails may not be unique.
{% endhint %}

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2F1Z0aOz4ipagfPVGEU3Ny%2FEkran%20Resmi%202026-09-29%2012.31.30.png?alt=media&amp;token=7c5da7cb-b3fe-4868-8c76-a77c83089966" alt=""><figcaption></figcaption></figure>

#### Detail tabs

The tabs below the identity fields group the rest of the person's data by topic, so each question has a dedicated place to look.

<table><thead><tr><th width="177.796875">Tab</th><th>What it shows</th><th>Typical question it answers</th></tr></thead><tbody><tr><td><strong>Profile</strong></td><td>Profile attributes, both defined and calculated. See the <strong>Profile</strong> tab.</td><td>"What attribute values does this person have?"</td></tr><tr><td><strong>Devices</strong></td><td>The devices registered for the person, with platform and device details.</td><td>"Which devices does this person have, and are they still active?"</td></tr><tr><td><strong>Events</strong></td><td>Events the person has performed.</td><td>"Is the purchase event arriving from the app?"</td></tr><tr><td><strong>Messages</strong></td><td>Messages sent to the person.</td><td>"Did this person receive yesterday's campaign?"</td></tr><tr><td><strong>Targeting</strong></td><td>The targeting groups the person belongs to, such as segments and tags.</td><td>"Why was this person included in, or excluded from, a campaign?"</td></tr><tr><td><strong>Category Opt-in</strong></td><td>The person's opt-in status for each message category.</td><td>"Has this person opted out of promotional messages?"</td></tr><tr><td><strong>User Opt-in</strong></td><td>The person's SMS or email opt-in status at the user level.</td><td>"Has this person given consent to receive messages by SMS or email?"</td></tr><tr><td><strong>Blacklist</strong></td><td>Whether the person is on a blacklist.</td><td>"Is this person blocked from receiving messages?"</td></tr><tr><td><strong>Email Bounces</strong></td><td>Bounce records for the person's email address.</td><td>"Why are emails to this address not delivered?"</td></tr><tr><td><strong>Privacy</strong></td><td>Lists everyone who has accessed this person's private data.</td><td>"Who has accessed this person's private data?"</td></tr><tr><td><strong>Coupon Codes</strong></td><td>Coupon codes assigned to the person.</td><td>"Which coupon code did this person receive?"</td></tr></tbody></table>

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FLEJVRuxX237VdwRS6ZHf%2FEkran%20Resmi%202026-09-29%2012.32.32.png?alt=media&amp;token=e3c0a300-b950-4da6-b4c0-bf88361039e1" alt=""><figcaption></figcaption></figure>

#### Profile tab

The **Profile** tab lists the person's profile attributes in two groups. Each group heading shows how many attributes it contains, such as **DEFINED 5** or **CALCULATED 9**.

Use **Search attributes** at the top of the tab to find an attribute by name, which is useful in accounts with many custom attributes.

**Defined attributes**

Defined attributes are profile attributes created in your account and sent to Netmera through the SDK, the REST API or file imports. They hold business data about the person, such as a branch name, a membership level or a visit score.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FUkAcMDGZFkRzvvNRUrdY%2FEkran%20Resmi%202026-09-29%2012.32.54.png?alt=media&amp;token=a69ba29d-e6db-4c3a-8576-3a15927ec218" alt=""><figcaption></figcaption></figure>

Examples from the screen:

| Attribute              | Example value |
| ---------------------- | ------------- |
| Mobil Active           | false         |
| Weekly Web Site Visit  | 0.25          |
| Monthly Web Site Visit | 0.66          |
| Installation Date      | 304           |

The attributes listed here depend on the profile attributes defined in your account, so they differ between accounts. These are the same attributes used by the **Profile Attribute** filter type in Filter people.

**Calculated attributes**

Calculated attributes are computed automatically by Netmera from the person's activity. They require no integration work and are updated as new activity arrives. They summarize engagement, usage and revenue in a way that can be read at a glance and used in targeting.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FUkAcMDGZFkRzvvNRUrdY%2FEkran%20Resmi%202026-09-29%2012.32.54.png?alt=media&amp;token=a69ba29d-e6db-4c3a-8576-3a15927ec218" alt=""><figcaption></figcaption></figure>

<table><thead><tr><th width="338.9453125">Attribute</th><th>Description</th></tr></thead><tbody><tr><td><strong>Campaign Responsiveness</strong></td><td>A measure of how the person responds to campaigns.</td></tr><tr><td><strong>Total revenue - last 7 days</strong></td><td>The total revenue generated by the person in the last 7 days.</td></tr><tr><td><strong>Total revenue - last 30 days</strong></td><td>The total revenue generated by the person in the last 30 days.</td></tr><tr><td><strong>Last app open date</strong></td><td>The date the person last opened the app (DD/MM/YYYY).</td></tr><tr><td><strong>Average session length - last 30 days</strong></td><td>The average duration of the person's app sessions in the last 30 days, in seconds.</td></tr><tr><td><strong>Total session length - last 7 days</strong></td><td>The total time the person spent in the app in the last 7 days, in seconds.</td></tr><tr><td><strong>Total session length - last 30 days</strong></td><td>The total time the person spent in the app in the last 30 days, in seconds.</td></tr><tr><td><strong>Total app open - last 7 days</strong></td><td>The number of times the person opened the app in the last 7 days.</td></tr><tr><td><strong>Total app open - last 30 days</strong></td><td>The number of times the person opened the app in the last 30 days.</td></tr></tbody></table>

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FZfEJ35O2VBOjKVmKYOv7%2FEkran%20Resmi%202026-09-29%2012.33.26.png?alt=media&amp;token=e417eb84-1ba3-421e-984b-155590918c88" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Calculated attributes are a quick way to judge whether a person is active. A recent **Last app open date** and a non-zero **Total app open** indicate an engaged user; an old date and zero opens indicate a user who may need a re-engagement campaign.
{% endhint %}

### Best practices

* **Confirm logic in Rule Description before running results.** Most unexpected counts come from an operator set to AND instead of OR, or the reverse.
* **Start broad, then narrow.** Begin with a single rule, check the count, then add rules one by one. This shows how much each condition affects the audience.
* **Always include a Channel Permission rule** when checking audience size for a campaign. A count without it includes people who cannot receive the message.
* **Use Frequently used chips** for recurring conditions to avoid rebuilding the same rules.
* **Use a Segment rule** instead of rebuilding a known audience from scratch.
* **Prefer External ID in Find Person** when it is available. It is unique per user and avoids ambiguity that can occur with shared emails or phone numbers.

### Troubleshooting

<table><thead><tr><th width="353.2890625">Situation</th><th>What to check</th></tr></thead><tbody><tr><td><strong>people match</strong> shows 0</td><td>Run <strong>Show results</strong>. Check for empty groups, AND/OR operators, and whether the selected values exist in your data.</td></tr><tr><td>Count is much larger than expected</td><td>An OR operator may be set where AND was intended, either inside a group or between groups.</td></tr><tr><td>Count is much smaller than expected</td><td>Too many AND conditions, or a restrictive rule such as a narrow Behavior date range.</td></tr><tr><td><strong>Find person</strong> button is disabled</td><td>Enter a value in the identifier field.</td></tr><tr><td>No result in Find Person</td><td>Confirm the correct identifier type is selected and the value matches the stored format exactly.</td></tr><tr><td>Person is found but not receiving messages</td><td>Check the <strong>Reachability</strong> icons for the channel in question and the <strong>Last seen</strong> date, then open the profile for details.</td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://user.netmera.com/netmera-user-guide/targeting/people.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.