Events

Everything leadmaps measures starts as an event: a page opened, a button clicked, a form submitted, a purchase made. The Events page combines exact server totals with a recent-event list, newest first. It uses a durable live stream for new events and keeps polling the exact list so late commits and reconnects are reconciled instead of silently disappearing.

Think of it like the receipt printer at a shop counter. Every time something happens, a new line prints. You can watch the lines appear, and you can search back through them to find one specific thing.

What you see

• An exact activity pulse for the last 60 minutes, with one dense minute bucket and total, average, and peak activity.
• An event river showing the busiest paths in twelve five-minute buckets.
• A cursor-paginated recent-event list for the selected date range. Each entry shows the event name, time, URL, privacy-aware actor, and attached properties.
• A search box that matches event names or URLs, plus event-type chips.
• Shared source and dimension filters from the dashboard URL. They are enforced by the API before aggregates and rows are returned.
• A pause control. Because new events keep arriving, you can pause the feed to hold it still while you read, then let it run again.

How to read it

Let the feed run to see what is happening now, or search and filter to answer a specific question.

Here is a worked example. Say you just added a “signup” event to your site and you want to confirm it works. You type “signup” into the search box. The feed narrows to only signup events. You then complete a signup yourself, and within a few seconds a fresh “signup” entry appears at the top with your details on it. That is proof the event is firing and reaching leadmaps. If nothing appears after you signed up, the event is not being sent, so the problem is in how it is set up on your site, not in leadmaps.

The details on each event are what make it useful. A bare event name tells you something happened. The details tell you the rest: which page it happened on, which visitor did it, and any extra information your site attached, such as a plan name on a signup or an amount on a purchase.

Customize it

• Search by event name or URL. Type a name such as “purchase” or a path such as /pricing to narrow the loaded list.
• Filter by event type. Use the chips to show one event type without changing the underlying exact range totals.
• Use a shared source or dimension filter. A filtered link can narrow the API population by source, device, browser, operating system, country, region, city, or path. Use the Live stream when you specifically need to follow one anonymous visitor.
• Pause and resume. Pause the feed to freeze it while you read a specific entry, then resume to let new events flow again.

Use cases

• Confirm a new event is firing. After you add a custom event to your site, search for it here, then trigger it yourself. Action: if it appears within a few seconds with the right details, it works. If it does not, check how the event is set up on your site before assuming anything is wrong on the leadmaps side.
• Check that a purchase carries the right details. Search for your purchase event and make a test purchase. Action: open the newest entry and confirm the amount, currency, and any product details are present and correct, so your revenue reports downstream are accurate.
• Debug one strange session. When a visitor did something odd, filter the feed to that one visitor and read their events in order. Action: the sequence often shows exactly where they got stuck or what they clicked, which points you at the fix.

Tips

• This feed is for checking and debugging, not for totals. To count events or see trends, use the Overview, Pages, and other report pages. This page shows the raw stream.
• The live transport resumes from an opaque ingest-order cursor and deduplicates stable event IDs. Polling remains active as a reconciliation path, so a reconnect does not turn a temporary transport gap into missing history.
• If you want to read one entry carefully, pause first so the list does not shift under you.
• The details matter more than the name. Two events with the same name can carry very different information. Open an entry and read what is attached before you decide the event is set up correctly.
• If the feed is empty right after install, give it a moment and trigger an event yourself. A brand new site simply has not sent anything yet.