Vocalfy Analytics · Collection API showcase

Posts every 0 event from docs/EVENTS.md and logs each request & response.

Configuration

Campaign referer & server context

referer is the ?referer= param on this page's URL (a UTM-like ad tag). The SDK reads it and posts it in session.start.props.referer — only when present. It is not the HTTP Referer header and is not part of context.

referer

Separately, the server derives this context on every event (the /collect response has no body, so this is what the server sees):

ip
user_agent
origin

Plus server-generated: event_uid, received_at, guest_id / user_id.

What the server actually stored

Pulls live state from GET /stats (admin-only, needs the metrics token) — buffer depth, Redis status, and the latest events exactly as stored in Redis, fully enriched by the server (event_uid, guest_id, context…).

Event catalog

Activity log
total 0 ok 0 fail 0
No requests yet — hit “Run ALL” or send an individual event.