Pulse is the single source of truth for Uber's web data platform — definitions, health, and answers in one place. Internal use only.
Is the platform healthy, and how is the business doing today?
Ranked by weekly volume. See the full list in Data & Pipeline Catalog → Pipeline Log.
{{ selectedEntry.definition }}
{{ selectedPipeline.description }}
{{ selectedMetric.tooltip }}
Export a weekly rollup of this metric for offline analysis.
Export a sample of raw log rows for offline analysis.
SLA is the share of runs delivered within this pipeline's committed freshness window, measured over the trailing 7 days.
The authoritative record of every metric, event, and pipeline on the platform.
Definitions, ownership, and versioning for every metric and event on the platform.
Definitions, ownership, and versioning for every top-level KPI on the platform.
Current status across every core web data pipeline, based on daily, weekly, and monthly validation checks.
Propose a new event or metric for review by the data team.
Flag a data quality, freshness, or platform issue to the data team.
Get programmatic access via the Pulse API — API keys, docs, and endpoints.
How to use every part of Pulse — from browsing the catalog to getting data out via the API.
Today, "conversion," "session," and "active user" mean something slightly different in every LOB's dashboard — definitions live in stale docs or in people's heads, pipeline health is invisible until something breaks, and onboarding a new app team takes weeks of back-and-forth. Pulse exists to close that gap.
The thesis: get this trust layer right once, and every AI-driven build that comes after it — inherits it for free.