Skip to content
Monita Docs

Send data from Adobe Event Forwarding to Monita

Adobe Experience Platform Event Forwarding (server-side Launch) can forward the events flowing through your Edge Network property to Monita, so your server-side vendor calls get the same monitoring as your client-side tags.

The integration is a standard Event Forwarding rule that makes an HTTP call to Monita’s collect API — no Monita-specific extension required.

Before you start

Section titled “Before you start”
  • An Event Forwarding property with the Cloud Connector extension installed (Adobe’s generic HTTP extension), or any extension that can send a custom fetch/HTTP request.
  • Your Monita property token and vendor names — see the Monita-side setup.

Create the rule

Section titled “Create the rule”

  1. In your Event Forwarding property, go to Rules → Create New Rule. Give it a name like Forward to Monita, and choose the event trigger you want to monitor (typically Core – All Events, or a condition scoped to specific event types).

  2. Add an action: Cloud Connector → Make Fetch Call.

  3. Configure the call:

    • Method: POST

    • URL: https://collect.monita.ai/api/v1/

    • Headers:

      Header Value
      token your Monita property token
      Content-Type application/json

    • Body: a JSON template mapping your data elements into Monita’s event fields:

      {
        "s": "adobe",
        "dm": "tms",
        "e": "{{arc.event.xdm.eventType}}",
        "vn": "Adobe Analytics",
        "u": "{{arc.event.xdm.web.webPageDetails.URL}}",
        "do": "www.your-domain.com",
        "sid": "{{arc.event.xdm.identityMap.ECID.0.id}}",
        "dt": [
          {
            "event": "{{arc.event.xdm.eventType}}",
            "pageName": "{{arc.event.xdm.web.webPageDetails.name}}"
          }
        ]
      }

      Adapt the data-element paths to your schema. The three fields Monita requires are the token (already in the header), vn and e; everything else improves grouping and lets data validation rules inspect your payloads.

  4. Save and build the library, then promote it through your environments — Event Forwarding changes don’t take effect until the library is published, exactly like client-side Launch.

Field mapping guide

Section titled “Field mapping guide”
Monita field What to map Why it matters
e Your event name/type Groups traffic by event in every dashboard and detector
vn The vendor this call represents Use the exact spelling from Monita Collect for logos and grouping
u / do Page URL / your site’s hostname Server-side calls have no page context — set these explicitly
sid / cid Session ID / customer ID Joins server events with client-side sessions
cn Consent state Feeds consent posture
dt An array with one object of the parameters you care about This is what data validation alerts evaluate

One rule can represent one vendor (vn fixed per rule) or you can drive vn from a data element if you forward on behalf of several vendors.

Verify

Section titled “Verify”
  1. Use your Event Forwarding property’s monitoring tools to confirm the fetch calls return 204.
  2. A 401 means the token header is missing or wrong — recheck it against Manage → Installation guide in Monita.
  3. In Monita, open Visualisation on the property — events appear under the vn vendor within a couple of minutes.