Telemetry
Integration collection

Browser and Edge Telemetry Integrations

Collect bounded frontend and edge outcomes through trusted server boundaries while protecting API keys, privacy, consent, and route cardinality.

Reviewed by the Telemetry product team on . Runtime boundaries, shared event fields, verification workflow, and upstream implementation sources. Review standards and ownership

3 implementation guides

Every guide includes a server-side snippet, delivery and privacy boundaries, a verification query, related SQL, and links to upstream documentation.

Browse guides

Selection framework

Choose the boundary that knows the result

Keep the ingestion key out of the browser

Send a small allowlisted payload to an application-owned endpoint, then forward it with a server-side credential and bounded timeout.

Collect outcomes, not page contents

Use route templates, Web Vitals, controlled error categories, and release fields. Exclude raw URLs, DOM text, form values, cookies, and arbitrary messages.

Treat browser delivery as sampled

Navigation, blockers, connectivity, and page termination can lose client events. Do not use best-effort browser collection as an exact billing or audit ledger.

Shared event contract

Keep the first schema interoperable

  • metric_name, metric_value, route_template, release, and navigation_type
  • edge region, status, duration_ms, cache outcome, and environment
  • sample policy, consent state, bounded device category, and correlation ID

Adapt these fields to the workflow, but keep units, status categories, identifiers, and ownership explicit before several services depend on the same table.

Verification

Exercise failure paths before alerts

  1. 1Inspect the production browser bundle and confirm it contains no Telemetry API key.
  2. 2Reject unknown origins, event names, fields, values, and oversized bodies.
  3. 3Exercise consent, blocked delivery, page termination, and rate limiting.
  4. 4Query sample count beside every Web Vital, error rate, or release comparison.

Implementation guides

Match the framework, provider, or runtime

Sourced implementation guide

Browser JavaScript and Web Vitals Telemetry

Collect Core Web Vitals and bounded frontend outcomes through a rate-limited server proxy without exposing a Telemetry API key.

Open guide
Sourced implementation guide

Next.js Server Event Analytics

Send SQL-ready events from Next.js route handlers and server actions without exposing an ingestion key to the browser.

Open guide
Sourced implementation guide

Cloudflare Worker Telemetry

Log edge request status, latency, provider failures, cron runs, and queue workers from Cloudflare Workers.

Open guide

Verify one end-to-end workflow first

Create a free API key, choose the closest runtime guide, and send one known success and failure before expanding coverage.

Start free