UMAP360 is a Growth Operating System for modern businesses — analytics, attribution, and automated engagement in one platform. For developers the integration surface is deliberately small: you send behavioural events to a single endpoint, and UMAP360 handles the rest — identity stitching across devices, click-ID attribution, and the triggers that fire your engagement and recovery campaigns.

How integration works

Every UMAP360 integration is built on one HTTP contract:

  1. Send events to the ingestion endpoint (POST /v1-batch) as a JSON batch, authenticated with a write key.
  2. UMAP360 resolves identity — anonymous visitors are stitched to known users by anonymousId, userId, and traits such as email or phone.
  3. The platform reacts — attribution is computed, conversions are forwarded to ad platforms, and engagement rules evaluate in real time.

You can talk to that endpoint directly with any HTTP client, or use the Web SDK, which batches, retries, and enriches events for you in the browser.

Send your first event

The fastest way to see data land is a single curl — no SDK required:

curl -X POST https://YOUR_PROJECT_REF.supabase.co/functions/v1/v1-batch \
  -H "Authorization: Bearer uk_live_your_write_key" \
  -H "Content-Type: application/json" \
  -d '{
    "batch": [
      {
        "type": "track",
        "event": "Signup",
        "messageId": "msg_0001",
        "timestamp": "2026-06-08T10:00:00.000Z",
        "anonymousId": "anon_demo"
      }
    ]
  }'

A successful request reports how many events were accepted:

{ "success": true, "processed": 1, "failed": 0, "duration_ms": 24 }

Where to go next

  • Quick start — get a write key and send a verified event in ten minutes.
  • REST API reference — the full ingestion contract: event shapes, batch limits, and error handling.
  • Web SDK — drop-in browser tracking with batching, retries, and identity resolution built in.

Last updated 2026-06-10

We use cookies for analytics — to understand how visitors use UMAP360 and improve the product. Essential cookies (session, forms) always run; analytics cookies wait for your call. See cookie policy.