Skip to main content
Zenovaydocs
2 min read

Try It Live

This page builds the exact request the Zenovay tracker sends when it records an event, so you can read it field by field before wiring anything into your own site. Edit the event name to watch the payload update, then send it to see the response.

Cookieless by default. The visitor and session IDs below are generated in memory for this page only. Nothing is written to a cookie or to local storage.

How sending works

The button runs in one of two modes, depending on whether the team has pointed it at a sandbox website:

  • Simulated mode (default). No request leaves your browser. You get the representative 200 response the ingest returns for a recorded custom event, marked as simulated. This keeps the page honest without touching any real analytics.
  • Live mode. When a real sandbox tracking code is configured, the button posts the event to that one website and shows the real response. An unknown code returns a clean 404, so a mistyped value never creates stray data.

This page does not read analytics back. It shows the request and the ingest response, nothing more. To see recorded events, open your own dashboard for a website you own.

Live mode

A sandbox tracking code is configured. The send button posts a real event to that one website and shows the real response.

Used as event_name in the payload below. Edit it to see the request update.

Request

POSThttps://api.zenovay.com/api/events/uZE6xUOdwuEQ

Content-Type: application/json

{
  "event_type": "custom",
  "event_name": "signup_clicked",
  "session_id": "s_0000000000000000",
  "visitor_id": "v_0000000000000000",
  "url": "https://example.com/pricing",
  "referrer": "https://example.com/",
  "device_type": "desktop",
  "browser": "Chrome",
  "os": "macOS",
  "screen_width": 1512,
  "screen_height": 982,
  "language": "en-US",
  "user_agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36"
}

Response

Send the event to see the response here.

The request, explained

The tracker sends a POST to the events endpoint with the website tracking code in the path:

POST https://api.zenovay.com/api/events/<your-tracking-code>
Content-Type: application/json

The body is plain JSON. A custom event needs event_type, event_name, a session_id of at least 8 characters, the page url, and the basic client fields (device_type, browser, os, user_agent). The rest are optional context. The same endpoint also accepts /api/track/<code> and the short /e/<code> path.

A recorded event comes back as:

{
  "success": true,
  "data": {
    "type": "event_recorded",
    "event_type": "custom",
    "event_name": "signup_clicked"
  },
  "timestamp": "2026-06-20T00:00:00.000Z"
}

Next steps

Was this page helpful?