Real-user monitoring
See what the user actually did — in release context.
The JS SDK collects page views, clicks, unhandled errors, and Core Web Vitals into the same pipeline, stamped with the flag and variation each session was in. Follow a checkout drop-off from the click all the way to the backend span that 500’d.
FreeIncluded from the Free tier.
checkout-funneltreatment vs controlProduct analytics, joined to the flag that shipped.
What you get
Why Foredeck for product analytics.
Auto-collected front-end events
Page views (incl. SPA routes), tagged clicks, unhandled errors, and Web Vitals — opt-in, best-effort, never breaking the host app.
Exposure-stamped
Every event carries the flag/variation the session was in, so funnels and vitals are joinable to your rollouts.
Vitals & funnels
p50/p75/p95 for LCP, INP, CLS, TTFB, plus error rate and session metrics out of the box.
RUM → backend traces
A browser interaction can start a trace that continues into your backend spans — front-end action to root-cause span.
How it works
Three steps, one pipeline.
Turn on UI collection in the browser SDK with one call.
Events flow in stamped with the current flag/variation.
Read funnels and vitals per variation, and jump to the trace behind a drop-off.
Better together
Works with the rest of the platform.
Tracing
FreeFollow one call across every service — spans stamped with the variation.
Explore Tracing →Experiments
FreeEvery rollout, automatically measured — experiments included free.
Explore Experiments →Metrics
FreeDefine a metric once, use it everywhere.
Explore Metrics →SDKs & OpenFeature
FreeEvery stack, no lock-in — flags, metrics, RUM, and tracing in one SDK.
Explore SDKs & OpenFeature →One object, one pipeline. The same rollout you ship is automatically measured, guarded, and — when it breaks — traceable, because every signal is joined to the flag and variation the unit was in.
Get in