{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/product-analytics.instrument-verify/",
    "json": "https://www.anchorterminal.com/niches/product-analytics.instrument-verify/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/product-analytics.instrument-verify/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/product-analytics.instrument-verify/index.min.md"
  },
  "markdown": "Two or three 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| 3 | 10 | 16 | 9 | 5 |\n\n## What counts as done\n\nThe expected events appear in the project with the right properties and identity, confirmed by reading the newest events through the API or MCP.\n\nMeasured, for our own tests: they appear within 5 minutes of sending.\n\nHow agents ask for it: is this event being tracked; why isn't signup showing up; add tracking for the new feature; audit our identify calls; send this backend event\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **Matomo (InnoCraft Limited)**: The Tracking HTTP API sends events from any backend, and Live.getLastVisitsDetails returns the latest raw visits with their events, filterable by segment, but the docs state no ingestion latency against the 5-minute bar.\n- **RudderStack MCP (RudderStack, Inc.)**: get_live_events polls real-time source, transformation and destination events, get_source_event_properties shows observed property types, and Tracking Plan violation tools flag schema mismatches.\n- **Statsig (Amplitude, Inc.)**: Log Custom Events sends server events and GET /console/v1/events returns recently logged events in a rolling window, with /events/{eventName} for one event, but ingestion latency isn't stated against the 5-minute bar.\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- **Amplitude (Amplitude, Inc.)**: HTTP V2 sends events and /api/2/useractivity returns a user's events from the most recent, but it is per user, not filtered by event name, and no ingestion-to-query latency is stated against the 5-minute bar.\n- **Countly (Countly Ltd)**: /o/export/db reads drill_events with a Mongo filter and sort {ts:-1}, and sdk_logs_list shows raw SDK payloads by device_id, but the MCP log tool has no sort and no ingestion latency is stated.\n- **Fullstory (Fullstory, Inc.)**: v2 Create Event sends a server-side event, List Sessions returns a user's most recent sessions by uid or email, and get_session_events gives a chronological transcript, but no ingestion latency is stated and there is no newest-events feed by event name.\n- **LaunchDarkly (Catamorphic, Co. (dba LaunchDarkly))**: search-timeline-events returns one session's track and identify calls in time order and get-metric-events lists metric events, but verification is per session through observability, not a newest-events feed by event name, and latency isn't stated.\n- **Mixpanel (Mixpanel, Inc.)**: Raw Event Export filters by event and where over an inclusive date range, and Get-Issues reports data quality, but export has no sort parameter, is limited to 60 queries an hour, and no ingestion latency is stated.\n- **Mostly Good Metrics (Mostly Good Metrics)**: POST /v1/events ingests from any backend with plan rate limits (1,000 a minute on Free), but no documented tool returns the newest raw events; list_events and list_event_types cover names.\n- **OpenPanel (OpenPanel AB)**: The Track API ingests events and query_events and /export/events return raw records with properties, but no sort parameter is in the spec; the arbitrary-order bug (acc-36) was closed as completed on 2026-09-04 and not verified here.\n- **Pendo (Pendo.io, Inc.)**: visitorActivity returns one visitor's chronological timeline over up to 31 days and searchEntities orders Track Events by recency, but the MCP sends no events and the Track API wasn't read.\n- **PostHog (PostHog Inc. (formerly Hiberly Inc.))**: execute-sql can read the newest events with ORDER BY timestamp, and a user debugged an untracked event over MCP (acc-02), but harness subagents lacked the MCP tools (acc-16) and ingestion latency isn't stated.\n- **Userpilot (Userpilot, Inc.)**: The Track Event HTTP API records events in real time, and the MCP can read a user's recent activity with profile permission, but no tool returns the newest events by name and the read path is undocumented.\n- **Woopra (Woopra, Inc.)**: Server-side track and identify calls are documented, and /profile/actions returns one profile's action timeline by email or id, but there is no newest-events feed by event name and latency isn't stated.\n\n- not this job: Flagsmith (Bullet Train Ltd): Exposure and conversion events are recorded for experiments against a connected warehouse; no endpoint or tool reads back the newest tracked events.\n- not this job: GrowthBook (GrowthBook, Inc.): GrowthBook reads events from the team's warehouse; it has no ingestion endpoint or newest-events read of its own beyond the read-only SQL tool.\n- not this job: Harness Feature Management \u0026 Experimentation (Harness Inc.): fme_event_type only lists event types seen in the last 30 days; live tail is a UI feature, and no endpoint returns the newest events.\n- not this job: Heap (Content Square, Inc.): Server-side Track and Bulk Track send events to identified users, but verification is through the Live data feed in the UI; no API reads back the newest events.\n- not this job: Optimizely Experimentation (Optimizely North America Inc.): Events export arrives daily, the next day by 13:00 UTC; no endpoint reads back the newest events.\n\n## What stops agents finishing\n\n- no endpoint returns the newest events in order\n- subagents in a harness lack the MCP tools\n- client capture slows the app and the fix is not discoverable\n- event volume limits on the free cloud tier\n- no SDK for the backend's language\n\n## Around it\n\nBefore: code.edit-repo. After: product-analytics.metric-question.\n\n## Where this comes from\n\nWeight 9 of 100 in Product analytics \u0026 experimentation: 5 of 55 account links; vendors (PostHog wizard, Amplitude sdk-setup skill, RudderStack MCP) put setup and debugging forward\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/product-analytics.instrument-verify.json, or the MCP tool get_use_case with id product-analytics.instrument-verify. 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": "Set up, send and verify event tracking",
        "url": ""
      }
    ],
    "description": "Set up, send and verify event tracking: 3 companies fully do it, 10 with a limit, 16 carry the tag. Every listing in Product analytics \u0026 experimentation with the reason and a source.",
    "facts": null,
    "h1": "Set up, send and verify event tracking",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/product-analytics.instrument-verify/",
    "published": "",
    "section": "agents",
    "title": "Set up, send and verify event tracking: who does it | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/product-analytics.instrument-verify/"
  },
  "tokens": {
    "markdown": 1700,
    "slim": 330
  },
  "version": 1
}
