> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt # People Canonical URL: https://posthog.com/docs/data/persons > **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://app.posthog.com` (app host for links). ## On this page - [How to create person profiles](#how-to-create-person-profiles) - [Duplicate person profiles](#duplicate-person-profiles) - [The persons list](#the-persons-list) - [Viewing person profiles](#viewing-person-profiles) - [Deleting person data](#deleting-person-data) People in PostHog represent the users behind your events. You can view them in the [People tab](https://app.posthog.com/persons). People have **person profiles** with [properties](https://posthog.com/docs/product-analytics/person-properties.md). This enables you to do things like: - Filter on person properties - Create [cohorts](https://posthog.com/docs/data/cohorts.md) - Use person properties for targeting feature flags, A/B tests, and surveys. - Track initial UTM values and referrers across anonymous and [identified](https://posthog.com/docs/product-analytics/identify.md) users. - Query the `persons` table using [SQL insights](https://posthog.com/docs/data-warehouse/sql.md) ## How to create person profiles Person profiles are created when you capture an [identified event](https://posthog.com/docs/data/anonymous-vs-identified-events.md) – an event that includes identifying information like a user ID or email through the [`identify`](https://posthog.com/docs/product-analytics/identify.md) call. ### Understanding distinct IDs vs person profiles Every event in PostHog has a **distinct ID** – a unique identifier that groups events together. However, not every distinct ID has a person profile: - **Anonymous events** – Events captured before `identify` is called use an anonymous distinct ID (a UUID generated by the SDK). These events are recorded but don't create a person profile. - **Identified events** – After you call `identify`, PostHog creates a person profile and links it to both the identified distinct ID and any previous anonymous events from that session. ### What happens without a person profile If you see a UUID in the PostHog UI instead of a user's name or email, it means: 1. The user hasn't been identified yet – they only have anonymous events 2. No person profile exists for this distinct ID Anonymous events are still captured and stored. When you later call `identify` for this user, PostHog automatically: - Creates a person profile - Merges the anonymous events with the identified user - Links the anonymous distinct ID to the person profile ### When profiles are automatically created Person profiles are created when you: - Call [`posthog.identify()`](https://posthog.com/docs/product-analytics/identify.md) with a distinct ID - Set person properties using [`posthog.setPersonProperties()`](https://posthog.com/docs/product-analytics/person-properties.md) - Capture an event with `$set` or `$set_once` properties **`$set` and `$set_once` aren't stored on events** These properties only tell PostHog how to update person data during ingestion — they aren't kept on the stored event, so you can't filter, break down, or query events by them. To query the values you set, use [person properties](https://posthog.com/docs/product-analytics/person-properties.md) instead. To control costs, you can [configure anonymous vs identified events](https://posthog.com/docs/data/anonymous-vs-identified-events.md) for events that don't need person profiles. A [data warehouse](https://posthog.com/docs/data-warehouse.md) table can also enrich profiles that already exist. See [warehouse properties](https://posthog.com/docs/data-warehouse/warehouse-properties.md). It never creates a profile, so a customer who has not used your product yet stays out of PostHog until they do. ## Duplicate person profiles If your [`identify`](https://posthog.com/docs/product-analytics/identify.md) implementation has gaps, a single real-world user can end up with multiple person profiles. For example, if a user visits your app on a phone and a laptop but `identify` is only called on one device, each device creates its own profile with a separate anonymous distinct ID. This usually points to a misconfiguration — when `identify` is called correctly on every device and session, PostHog merges these into one profile automatically. The most common cause of duplicate profiles is using different distinct IDs for the same user across systems without calling [`alias`](https://posthog.com/docs/product-analytics/identify.md#alias-assigning-multiple-distinct-ids-to-the-same-user) to link them. When PostHog can't merge two already-identified profiles, it blocks the merge and logs a "Refused to merge an already identified user" [ingestion warning](https://posthog.com/docs/data/ingestion-warnings.md). If you're seeing this warning, it means your users are accumulating duplicate profiles that won't be merged automatically. Duplicate profiles inflate counts that rely on person profiles, such as cohort sizes and feature flag targeting. If you notice these numbers are higher than expected, check your [ingestion warnings](https://posthog.com/docs/data/ingestion-warnings.md) and verify that you're calling [`identify`](https://posthog.com/docs/product-analytics/identify.md) as soon as a user logs in on every device and browser. To fix existing duplicates, see [how to merge users](https://posthog.com/docs/product-analytics/identify.md#how-to-merge-users). ## The persons list The [People tab](https://app.posthog.com/persons) displays a list of all people in your project. By default, the list includes the following columns: - **Person** - display name for the person - **ID** - the person's distinct ID - **Created at** - when the person profile was first created - **Last seen** - when the person was last active, rounded to the nearest hour (opt-in, see below) - **Delete** - option to delete the person You can sort the list by any column and customize which columns are visible by clicking the **Configure columns** button above the table. ### Last seen The **Last seen** column tracks when a person was last active. This feature is **opt-in** — to enable it for your project, go to [Settings > Product analytics > Person last seen tracking](https://app.posthog.com/settings/environment-product-analytics#person-last-seen-at). When disabled, the column is not updated after the person is first created. When enabled: - The value updates **hourly** — the event timestamp is rounded down to the nearest hour, so multiple events within the same hour won't cause repeated writes. - If a person was active within the last hour, the column displays "last hour" instead of a specific time. - Individual events can opt out of updating this value by setting the event property `$update_person_last_seen_at` to `false`. ## Viewing person profiles Clicking on a person in the [People tab](https://app.posthog.com/persons) opens their profile and shows all their properties. ![Person profile](https://res.cloudinary.com/dmukukwp6/image/upload/posthog.com/contents/images/docs/data/people/person-profile-light-mode.png) - **Events** shows all the events a person has triggered, which you can search and filter to find specific events. - **Recordings** shows all of the session replays a person has generated. Note this is subject to the retention policy of your plan, so people who haven't been active recently may have none. - **Logs** shows every [log](https://posthog.com/docs/logs.md) emitted on behalf of this person — backend OTel logs, frontend SDK logs, anything carrying the `posthogDistinctId` attribute (or a [custom attribute key](https://posthog.com/docs/logs/link-person.md#customizing-the-attribute-key) you've configured). Useful for debugging a specific user's issue across services. - **Cohorts** shows all the [cohorts](https://posthog.com/docs/data/cohorts.md) a person belongs to. - **Related groups:** shows [groups](https://posthog.com/docs/product-analytics/group-analytics.md) (e.g. organizations, projects, and instances) a person belongs to. - **Feature flags:** shows all [feature flags](https://posthog.com/docs/feature-flags.md) that are enabled for the person. - **History:** shows any manual changes that have been made to the person's profile. ## Deleting person data ### In the PostHog app - Search for the person via their unique ID. For example, their email. - Click on the person's ID - Click **Delete person** to remove them and all their associated data. You will be prompted to confirm this action. You can also choose to delete their session recordings at this step. **Avoid reusing deleted distinct IDs** User deletion requests are not immediate, but processed asynchronously. We recommend that you *avoid* reusing a deleted `distinct_id` value for a new user, as it may lead to unexpected results while the deletion is being processed. Once the deletion process is fully processed, PostHog does not retain any data associated with the deleted `distinct_id`. If you must reuse the `distinct_id`, you can do so using the **Reset deleted person** tool, available from the dropdown at the top-right of the [**persons page**](https://app.posthog.com/persons). This tool enables you to reset a deleted `distinct_id` so that future events associated with it create a new person profile. If you instead want to split a person with multiple IDs (e.g. to isolate bad data tied to a specific `distinct_id`), use the **Split IDs** button on their person profile. ### Via the API You can also delete persons data via the API. When deleting a person, you can pass `delete_events=true` to delete their events and `delete_recordings=true` to delete their [session recordings](https://posthog.com/docs/session-replay.md). Recording deletion uses crypto-shredding to permanently destroy encryption keys, making the recordings unrecoverable. See the [data deletion docs](https://posthog.com/docs/privacy/data-storage.md#data-deletion) for more information.