The product
Replay and heatmaps show what happened. The catalog decides what you are allowed to call it. Agents help you instrument — they do not get to invent the dictionary.
Why LESP exists
LESP (LLM Event Schema Protocol) is the shared catalog of product events for a site. You name checkout once, in language a person and a model can both read. Every later track() call, replay marker, and funnel step uses that name. If an agent invents CheckoutStart next week, ingest refuses it.
Register the event in Event Studio with a short description of the moment that matters — “customer started payment,” not a leftover CSS class.
The SDK, data-insight-id tags, and any MCP client read the same glossary. The next agent session does not get a blank page and a guess.
Strict mode drops unknown semantic events. Behavioral noise (page views, rage clicks) still captures automatically. Product vocabulary stays intentional.
Replay, funnels, and the standup use the same words. You stop arguing whether checkout_started and CheckoutStart are the same conversion.
Event Studio — humans approve what agents propose
Watch the click that never became a booking.
The recorder starts before React hydrates, so you do not lose the first tap. Markers from the catalog sit on the same timeline as rage clicks — you see the moment, not only the drop-off rate.
Heatmaps, funnels, alerts, and consent sit on the same catalog — so a click map and a conversion goal are not two different stories.
Click and scroll rollups aggregated per path and viewport.
Custom funnel builder, conversion goals, and segment splits.
Agents author events and read sessions with the same glossary.
Slack, webhooks, scheduled CSV reports, and period compare.
page.view, clicks, scroll depth, rage_click — no catalog entry needed.
Consent-aware tracking, erasure workflows, and audit UI.
Multi-tenant dashboards, validation rollups, and ingest health.
Connect MCP, approve the catalog in Event Studio, and open a session that used those names.