Skip to content
Telemetry
Integration collection

Browser and edge integrations

Send approved frontend and edge events through your server. Keep API keys there, check consent, and use route templates instead of raw URLs.

Reviewed by the Telemetry product team on . We checked where the code runs, shared event fields, verification steps, and the linked implementation guides. Who reviews this page

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

Log where the final result is known

Keep the ingestion key out of the browser

Send only approved fields to an endpoint you control. Forward them with a server-side credential and a 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.

Expect some browser events to be lost

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

Use the same field definitions across services

  • 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 your workflow. Document units, allowed statuses, and identifiers before several services write to the same table. Name the team responsible for the schema.

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

Setup guide with source links

Browser JavaScript and Web Vitals telemetry

Send Core Web Vitals and approved frontend result fields through a rate-limited server proxy. Keep the Telemetry API key on the server.

Open guide
Setup guide with source links

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
Setup guide with source links

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