Everything you need to build on UMAP360. Send behavioural events to a single endpoint, and the platform handles identity resolution, attribution, and the triggers that power your engagement and recovery campaigns.

New here

Start with the basics, then go as deep as you need:

  • Introduction — how the integration model works, end to end.
  • Quick start — send your first verified event in ten minutes.

Build with

Glossary

  • anonymousId — a stable per-browser/device id you (or the SDK) generate and reuse on every event; ties a visitor's activity together before they're known.
  • userId — a known user's id, attached via identify once they sign in.
  • profile — the single record UMAP360 resolves per person by stitching anonymousId / userId / email / phone.
  • session — a window of activity that ends after a period of inactivity.
  • write / read / admin key — API keys scoped to send / read / manage; the prefix (uk_live_ / uk_read_ / uk_admin_) tells you which.

Need a hand

These docs are versioned alongside the product. If something here doesn't match what you see in the dashboard, treat the dashboard as the source of truth — and tell us so we can fix the doc.

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.