A fake SaaS landing page whose only real job is to send pageviews and custom events to your live Relay analytics deployment so you can watch them appear.
No banners, no consent gymnastics — every visit here uses a daily-rotating anonymous hash.
Beacons go straight to your own ingestion endpoint, not a third-party tracker.
Add a GA4 destination in Relay and these same events forward server-side.
/api/event. Use the SPA buttons below to fire
history-based pageviews without a full reload.
These tabs change the URL with history.pushState (watch the address bar:
?tab=…) — no reload. Back/Forward work. Each switch is a soft pageview the
history_change trigger picks up.
A single verdict for the whole pipeline: is data flowing, and are destinations accepting it?
Pages, referrers, events and conversions — the classics, cookieless and first-party.
Rules that watch your traffic and conversions and page you when something drifts.
form_submit-style event through the same data-* mechanism.
The email demonstrates user-data hashing / scrubbing: it never reaches storage
raw — Relay scrubs it to [email] at ingest, and hashing presets forward only a SHA-256.
The button below intentionally throws an uncaught JavaScript error to demo
Relay's error tracking (js_error trigger). It's isolated — the rest of the page
keeps working after it fires.
This banner sits far down the page and animates in when scrolled into view — the
element_visibility trigger fires on the same intersection.