Skip to content
Monita Docs

Server-side monitoring overview

Client-side monitoring sees what leaves the browser. If part of your marketing stack runs server-side — Adobe Event Forwarding, a server GTM container, Tealium EventStream, Segment, or your own backend — you can stream those events to Monita too, and get the same anomaly detection, validation rules and alerting across your whole pipeline.

Every server-side integration is the same one-endpoint pattern:

POST https://collect.monita.ai/api/v1/
token: <your property token>
Content-Type: application/json

A 204 No Content response means the event was accepted. See Direct HTTP for the full payload contract, and the platform guides for click-by-click setup:

Set up the Monita side first

Section titled “Set up the Monita side first”

Whichever platform you send from, the Monita setup is identical:

  1. Create a property in the app (or reuse an existing one — use the same property if you want web, mobile and server events grouped together).

  2. Add a vendor entry for each vendor whose server-side events you’ll report (for example Meta Conversions API, GA4 Measurement Protocol). For server-side sources you can add the vendor and save — the request-matching fields only apply to client-side capture.

  3. Turn on Monita Collect for those vendors. The code icon next to each vendor shows the exact vendor name to send in the vn field — matching it exactly gives you the vendor’s logo and grouping in dashboards.

  4. Copy your property token from Manage → Installation guide.

What’s different server-side

Section titled “What’s different server-side”

Verifying

Section titled “Verifying”
  1. Check your platform’s own logs show 204 responses from collect.monita.ai.
  2. Open the property’s Visualisation view — events appear grouped by the vn vendor name and e event name within a minute or two.
  3. No data? See Deployment troubleshooting.