Skip to content

Record a tracking session you can review

pulsecheck puts network hits, dataLayer pushes and consent changes in one Chrome DevTools timeline. Export the session as Markdown or JSONL for an audit.

Install pulsecheckWhy it matters
DevToolspulsecheck
ElementsNetworkpulsecheck
Recording checkout
Consentdefault
dataLayerbegin_checkout
GA4purchase
event_name: purchaseNetwork request

Illustrative interface with sample data. No live account is connected.

Keep the evidence in event order

See the flow together

Network events, dataLayer pushes, page changes and consent updates share one timeline.

Hand off a reviewable session

Markdown includes the context and full event order. JSONL keeps the same session in a structured format.

Share only after a review

Redaction runs before export. Measurement and deduplication keys remain, and arbitrary text still needs a human check.

Illustrative interface with sample data. No live account is connected.

Capture the flow

  1. 1Install the extension
  2. 2Open DevTools and name the scenario
  3. 3Walk through and export

Turn the recording into a diagnosis

  • Trace the measured funnel
  • Investigate duplicates and missing events
  • Rank fixes and define the roadmap
$3,000Attribution audit, fixed scope, two weeks. October 2026.Explore the attribution audit

A session shows what happened in the browser. Audit the wider measurement setup

Source code and setup instructions

pulsecheck

Questions people usually ask

Where does recording happen?

In a Chrome DevTools panel on a normal website. Open the panel before starting the flow. Recording ends when DevTools closes.

What can it capture?

Network hits, dataLayer and digitalData pushes, consent changes and page changes. Parsers cover GA4, Meta, Yandex Metrica, Amplitude and TikTok, with a generic fallback.

Does it send recordings to a backend?

The extension has no backend, account, telemetry or extension-owned network requests.

What can I export?

Markdown for review and JSONL for structured processing. Both contain the recorded session in event order.

Are exports fully anonymous?

No. Detected sensitive fields are masked, but measurement IDs are preserved and unstructured strings have limits. Review every export before sharing it.

Can it compare against a tracking plan?

The companion analysis skill describes a workflow for comparing observed events and parameters with a supplied plan.

Make the next tracking issue explainable

Record the scenario, keep the event order and use the audit to connect the browser evidence with the rest of the funnel.

Explore the attribution audit