Before you build dashboards or campaigns on your data, make sure it's actually arriving. There are two easy ways to confirm.

In the setup wizard

Step 3 of the welcome wizard ("Verify") watches for incoming data live. It shows a checklist that lights up as each signal is detected:

MilestoneWhat it confirms
First event receivedThe tracker reached UMAP360 — you're connected
User identifiedAt least one visitor was tied to a known identity
Connector linkedA data source (ads, store, payments) is connected
Revenue event capturedRevenue data is flowing in

You only need the first event to move on — the wizard unlocks Continue as soon as it arrives, and the other three are informational. If nothing shows up after about ten minutes, an in-app troubleshooting link appears. You can also Skip verification and confirm later.

In the Events stream

Any time after setup, open Events to watch raw activity arrive in real time, newest first. It's the definitive place to confirm tracking is working.

Each row shows the event name, the profile and user it's tied to (or Anonymous), and when it was received. Click a row to expand its full detail, including every property and the automatic context (browser, device, session, page).

To find a specific event:

  • Search the stream by event name, anonymous ID, or user ID.
  • Filter to a single event name with the dropdown.
  • Click Refresh to pull the latest.

Trigger an action on your site (load a page, click a tracked button) and you should see the matching event appear within a few seconds.

If you don't see events

Check these first

Most "no events" issues come down to one of these:

  • The tracker isn't on a live, public page yet — a snippet that only runs on localhost won't send real traffic.
  • The write key in your snippet doesn't match the one in your workspace. Copy a fresh snippet from Settings → API Keys.
  • The page didn't actually load the snippet. Open your browser's developer tools, go to the Network tab, and look for UMAP360 requests when the page loads.

If events still aren't arriving, developers can turn on the tracker's debug logging to see what's happening in the browser console — see the developer verification guide. For anything else, head to Troubleshooting & support.

Next step

Seeing events? You're ready to read your data — head to Your first dashboard.

Last updated 2026-06-11

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.