Ingest Streaming Event
Send vendor events from a whitelisted domain to the Monita streaming ingestion service. This endpoint expects the exact payload that the Monita tag emits (see example) and requires a valid token (t), vendor name (vn) and event (e).
Body
Raw payload accepted by the streaming ingestion endpoint. The Monita browser tag sends this body verbatim.
Issued ingestion token used to authorize the event.
Event/action name such as PAGE_VIEW.
Human readable vendor identifier.
Source of the payload (for example script).
Version of the Monita script that produced the event.
Version of the customer deployment.
Epoch timestamp with millisecond precision provided by the browser.
HTTP method used when contacting the vendor endpoint.
Full URL of the vendor endpoint that fired.
URL of the monitored page.
Path portion of the monitored page.
Flexible event data emitted by the vendor. Each object may contain arbitrary keys that describe the vendor payload.
Optional list of transient diagnostic values.
System or tag template that triggered the event.
Internal release identifier.
Deployment environment string.
Identifier for the monitored container (for example GTM-M7L6DD5).
Execution duration in milliseconds.
Optional vendor specific identifier.
Consent state encoded by the customer.
Client session id (UUID).
Optional customer identifier.
Response
Event accepted and normalized. The resulting record is persisted with fields such as event_id, event_timestamp, vendor, vendor_name, domain, session_id, deployment_method, browser metadata, and more (see data warehouse schema).