# Look up one user's events, flags or segment membership

> Look up one user's events, flags or segment membership: 7 companies fully do it, 6 with a limit, 23 carry the tag. Every listing in Product analytics & experimentation with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/product-analytics.user-lookup/
- Markdown: https://www.anchorterminal.com/niches/product-analytics.user-lookup/index.md (~1,450 tokens)
- Slim: https://www.anchorterminal.com/niches/product-analytics.user-lookup/index.min.md (~330 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/product-analytics.user-lookup/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Four or more companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 7 | 6 | 23 | 6 | 3 |

## What counts as done

That user's recent events, flag evaluations or membership returned by exact id or email, with no truncation.

Measured, for our own tests: in one or two calls.

How agents ask for it: what did this customer do before churning; which flags does this customer have on; is this user in the beta segment; show this user's sessions

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **Amplitude (Amplitude, Inc.)**: /api/2/usersearch finds a user by user id or Amplitude id, then /api/2/useractivity returns up to 1,000 events with offset paging; get_amp_user_data covers it over MCP.
- **Fullstory (Fullstory, Inc.)**: List Sessions returns a user's most recent sessions by uid or email, /api/v1/export/userEvents returns one user's events, and review-open accepts an email or user uid.
- **Matomo (InnoCraft Limited)**: Live.getLastVisitsDetails with a segment such as userId or visitorId returns one visitor's visits and events in one call.
- **OpenPanel (OpenPanel AB)**: find_profiles searches by email or name, and get_profile returns a profile with its most recent events; get_profile_sessions orders sessions newest first.
- **Pendo (Pendo.io, Inc.)**: visitorActivity returns one visitor's chronological product activity with console and network logs, and listVisitors and visitorMetadataSchema read metadata.
- **PostHog (PostHog Inc. (formerly Hiberly Inc.))**: persons-retrieve and persons-cohorts-retrieve read one person and their cohorts, and feature-flags-evaluation-reasons-retrieve shows how every flag evaluates for a distinct_id and why.
- **Woopra (Woopra, Inc.)**: /profile/actions looks up one profile by a unique key such as email, pid or id and returns its visits and action timeline in one call.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Countly (Countly Ltd)**: user_profiles_query searches by free text with totals and paging, and user_profiles_get reads one profile, but the users plugin is Enterprise only and exact-email lookup isn't stated.
- **Flagsmith (Bullet Train Ltd)**: GET /api/v1/identities/ returns one identity's flags and traits by identifier, but it is the SDK API with an environment key, not an MCP tool, and there are no events.
- **Harness Feature Management & Experimentation (Harness Inc.)**: Segment keys can be listed with fme_segment_definition list_keys, but there is no tool to evaluate flags for a given key, and identity writes aren't wired in native mode.
- **LaunchDarkly (Catamorphic, Co. (dba LaunchDarkly))**: POST flags/evaluate returns a context's flag values over REST, but the MCP lacks it (open issue 93), and get-segment truncated targets at ten with no exact lookup (open issue 97).
- **Mixpanel (Mixpanel, Inc.)**: Profile Event Activity returns events for given distinct_ids over inclusive dates, but it is in maintenance mode at 60 queries an hour, and Engage returned 403 for a service account with no email lookup (acc-21).
- **Statsig (Amplitude, Inc.)**: Check Feature Gate(s) evaluates gates for a given user object, but results depend on the attributes the caller supplies, and no endpoint returns one user's event history.
- **Userpilot (Userpilot, Inc.)**: With the profile permission the MCP reads one user's or company's profile and activity, but tool names, lookup keys and truncation aren't documented.

- not this job: GrowthBook (GrowthBook, Inc.): No endpoint returns one user's events or flag evaluations; user data stays in the warehouse and flags evaluate in the SDK.
- not this job: Heap (Content Square, Inc.): Identify and Add User Properties write user data; no endpoint reads one user's events or profile back.
- not this job: Mostly Good Metrics (Mostly Good Metrics): No per-user events or profile tool; query tools are aggregate-only.
- not this job: Optimizely Experimentation (Optimizely North America Inc.): No endpoint or tool looks up one visitor's events or flag decisions.
- not this job: RudderStack MCP (RudderStack, Inc.): Profile tools return profile project models, statistics and history, not one user's events by id or email.

## What stops agents finishing

- profile API forbidden for the service account role
- segment targets truncated with no exact lookup
- no flag evaluation for a given context

## Around it

Before: support.read-ticket. After: support.reply-ticket.

## Where this comes from

Weight 6 of 100 in Product analytics & experimentation: 3 of 55 account links; Mixpanel, Fullstory and Pendo list user investigation among MCP uses

As data: https://www.anchorterminal.com/api/v1/use-cases/product-analytics.user-lookup.json, or the MCP tool get_use_case with id product-analytics.user-lookup. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
