{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/product-analytics.user-lookup/",
    "json": "https://www.anchorterminal.com/niches/product-analytics.user-lookup/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/product-analytics.user-lookup/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/product-analytics.user-lookup/index.min.md"
  },
  "markdown": "Four or more companies' docs show a full fit.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 7 | 6 | 23 | 6 | 3 |\n\n## What counts as done\n\nThat user's recent events, flag evaluations or membership returned by exact id or email, with no truncation.\n\nMeasured, for our own tests: in one or two calls.\n\nHow 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\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **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.\n- **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.\n- **Matomo (InnoCraft Limited)**: Live.getLastVisitsDetails with a segment such as userId or visitorId returns one visitor's visits and events in one call.\n- **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.\n- **Pendo (Pendo.io, Inc.)**: visitorActivity returns one visitor's chronological product activity with console and network logs, and listVisitors and visitorMetadataSchema read metadata.\n- **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.\n- **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.\n\n## Does the job, with a limit\n\nIt 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.\n\n- **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.\n- **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.\n- **Harness Feature Management \u0026 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.\n- **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).\n- **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).\n- **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.\n- **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.\n\n- 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.\n- 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.\n- not this job: Mostly Good Metrics (Mostly Good Metrics): No per-user events or profile tool; query tools are aggregate-only.\n- not this job: Optimizely Experimentation (Optimizely North America Inc.): No endpoint or tool looks up one visitor's events or flag decisions.\n- 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.\n\n## What stops agents finishing\n\n- profile API forbidden for the service account role\n- segment targets truncated with no exact lookup\n- no flag evaluation for a given context\n\n## Around it\n\nBefore: support.read-ticket. After: support.reply-ticket.\n\n## Where this comes from\n\nWeight 6 of 100 in Product analytics \u0026 experimentation: 3 of 55 account links; Mixpanel, Fullstory and Pendo list user investigation among MCP uses\n\nAs 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.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Look up one user's events, flags or segment membership",
        "url": ""
      }
    ],
    "description": "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 \u0026 experimentation with the reason and a source.",
    "facts": null,
    "h1": "Look up one user's events, flags or segment membership",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/product-analytics.user-lookup/",
    "published": "",
    "section": "agents",
    "title": "Look up one user's events, flags or segment membership | Anchor…",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/product-analytics.user-lookup/"
  },
  "tokens": {
    "markdown": 1450,
    "slim": 330
  },
  "version": 1
}
