The Events page is where you go to see exactly what your tracking is sending and to document what each event means. It pairs a live, searchable stream of incoming events with a structured data dictionary so your whole team shares one definition of every event.
If you just want to confirm your setup is firing correctly, start with Verify events. This page is for going deeper once data is flowing.
The event stream
The event stream lists incoming events newest-first, so you can watch real activity arrive and inspect any single event in detail.
Each row shows the event name, the profile and user it belongs to, the anonymous (device) identifier, the timestamp it was received, the custom properties sent with it, and the automatic context (browser, device, session, page). Click any row to expand it and see the full property and identity detail.
To find what you're looking for:
- Search by event name, anonymous ID, user ID, or canonical ID.
- Filter to a single event name using the event dropdown.
- Refresh to pull in the latest events.
- Use the pagination controls to browse older events.
Debugging during setup?
The stream is great for spot-checking live data. While you're still wiring up tracking, Verify events walks through the basics of confirming events arrive as expected.
The data dictionary
The dictionary is your catalog of every event UMAP360 knows about — what it means, who owns it, and what parameters it should carry. You can search it by name, description, or parameter, filter by category, and export the whole catalog to CSV.
Events are grouped into three sections:
- UMAP360 events — automatically tracked by the SDK.
- Custom events — events your team defines and sends.
- Undefined events — events seen in your data but not yet documented. These are worth reviewing: an unexpected event can signal a bug, bot traffic, or unplanned tracking.
UMAP360 system events
UMAP360 tracks a standard set of system events automatically or treats them as having special meaning. Their names start with $:
| Event | What it means |
|---|---|
$pageview | A page view — captured when someone visits a page (URL, path, title, referrer). |
$identify | User identification — links anonymous activity to a known user and their traits. |
$screen | A screen view — the mobile-app equivalent of a page view. |
$alias | A user alias — maps one user ID to another and merges their activity histories. |
$group | A group association — links a user to a group or organization for account-level (B2B) analytics. |
Element Clicked | Captured when someone clicks a link, button, or any element you've marked for tracking. Records the element type, text, ID, and class (plus the link URL and target for anchors). |
Scroll and CTA tracking aren't automatic
Events like scroll depth or CTA clicks are not auto-tracked. If you want them, send them as your own custom events.
Custom events
Any event you track yourself is a custom event. It appears in the dictionary automatically the first time it's received — you don't need to register it in advance.
Defining and documenting events
Open Events → Dictionary and click an event to view or edit its definition. For each one you can set:
| Field | What it's for |
|---|---|
| Display name | A human-readable label (e.g. "Product Viewed" for a product_viewed event). |
| Description | What the event represents and when it should fire. |
| Category | A logical grouping such as Commerce, Navigation, or Engagement. |
| Expected parameters | The properties this event should include, each with a description. |
| Owner | The team member responsible for this event's data quality. |
Assigning owners and writing clear descriptions turns the dictionary into a shared contract: everyone knows what each event means, who to ask about it, and which properties it should carry.
Define before you build
Define your events in the dictionary before implementing them, so engineering and analytics agree on names and parameters up front.
Discovery and parameter stats
UMAP360 keeps running statistics on every event so you can judge data quality at a glance.
For each event you can see its lifetime total count, when it was last seen, its volume per day, and where it ranks among your most frequent events. This is the fastest way to spot which events are most active — or to notice something firing that shouldn't be.
For each parameter on an event, open the event and scroll to the Parameters section. There you'll find:
- Presence count — how many instances of the event include this parameter.
- Top values — the most common values being sent.
- Description — your own note explaining what the parameter is.
Use this to confirm that required properties are actually being sent consistently.
Next steps
- Verify events — confirm your tracking is firing correctly.
- Analytics and funnels — turn events into trends and conversion paths.
- Alerts — get notified when key events spike or drop.
- Developer documentation — the full SDK reference for sending custom events.
Last updated 2026-06-11