Realtime
See the active audience, approximate locations, current pages, traffic sources, and a live activity stream. Pause the stream when you need to inspect an item.
| Site | Today | 7 days | 30 days |
|---|
to
All traffic
Event discovery
Scan your public website to find meaningful interactions that may be worth tracking as events. Review every suggestion before it becomes part of your tracking plan.
Event discovery combines page context with interaction details, helping you focus on business signals instead of collecting every available click.
How to use Event Discovery
- Choose where to begin. Use a public starting URL for the current property. The scanner follows eligible links up to 2 levels beyond that starting page. Under "Advanced", you can restrict the crawl to stay under that URL's path, or override the page/depth budget for just this scan — useful for a deliberate deep pass over one section, like
/products. - Add an optional label and focus. A label (e.g. "Add to cart sweep") helps you find this run later in the scan history. A focus note tells the AI which flow or outcome matters most, such as pricing, signup, or checkout — it only changes which crawled interactions get prioritized, not which pages get visited.
- Scan the website. LodyCDP examines the visited pages and proposes interactions with useful analytics meaning.
- Rerun scans freely. A new scan never redoes prior review work: interactions you already approved or rejected are remembered and skipped automatically, so you'll only be asked to review genuinely new candidates. Use this to progressively cover more of a site — scan the homepage first, then later rerun with a starting URL under a section like
/productsand a focus such as "add to cart" to surface interactions you haven't seen before. - Review the evidence. Check the suggested event name, page context, and matching interaction before approving or rejecting it. Use "Show events" to switch between everything discovered for this site and just the current scan's results.
- Publish approved events. Approved suggestions only begin automatic tracking after you publish the updated tracking plan.
Tip: Prefer events that represent intent or progress. A small set of clear signals is usually more useful than tracking every interface interaction.
Scanning only inspects publicly accessible pages. Existing historical analytics are not changed when you scan, approve, reject, or publish suggestions. "Reset all events" is the only action here that undoes prior review work — running a new scan never does.
Event catalog
Journeys
Build a journey from the pages and actions that matter to your business. Measure how visitors progress through each step, discover where they drop off, and understand how long it takes them to complete the journey.
Journeys analyze data LodyCDP has already collected, so you can investigate new hypotheses about past behavior without defining the journey in advance.
How to use Journey Builder
- Name the outcome. Use a clear goal such as “New customer activation” or “Checkout completion.”
- Add the starting point. Choose the page or event where the journey meaningfully begins.
- Add each milestone in order. A page matches its path, such as
/pricing. An event matches its tracking name, such assignup_started. - Choose a conversion window. This controls how much time a visitor has to reach the final step after entering the journey.
- Save and analyze. Select the journey to see progression, drop-off, completion rate, and median time between steps.
What drop-offs did next
Select Investigate drop-off on any journey step to see the first page or event recorded next for visitors who reached that step but did not continue to the expected next step. This can reveal alternative routes, distractions, or places where visitors leave the tracked journey. On the final step, See what happened next shows the first action recorded after visitors completed the journey.
Compare completion
Use this table to compare the full journey’s completion rate across devices, countries, or acquisition sources. For each group, Entered counts visitors who reached the first step, Completed counts those who reached the final step in order and within the conversion window, and Rate is the percentage who completed. Groups with fewer than five journey entrants are hidden.
Tip: Focus on meaningful milestones rather than every click. A journey with three to five steps is usually easiest to understand and act on.
Explore historical questions. You can create a journey today and apply it to previously collected data—for example, to test whether visitors who viewed pricing went on to create an account. No additional tracking setup or waiting period is required when the necessary pages and events were already recorded.
Visitors may take other actions between journey steps. Journey metrics treat each retained browser identifier as one user, so one person using multiple browsers or devices may be counted more than once. Historical sequence analysis is limited to the identifier retention period.
Statistics
Production traffic across all tracked sites. Local and development traffic is excluded.
Users
| Role | Domain access |
|---|
Help
Use this guide to choose a property, understand its traffic, investigate behavior, and manage the features available to your role.
Start with a property
Most pages in the console use the property picker at the top of the screen. Choose a tracked site there, then use the date range and filters on Sites to narrow the analysis. The displayed timezone controls day boundaries for presets and custom ranges.
The overview shows traffic trends, new and returning visitors, and engagement. Use the breakdown tabs for pages, landing pages, events, referrers, locations, devices, browsers, operating systems, and technology. Page details include views, entrances, exits, time, and scroll-depth distributions where enough data is available.
Filters combine with the selected date range.
A saved cohort lets you reuse a useful set of filters. Environment filtering keeps
development and staging traffic separate from production analysis.
Live and historical analysis
Journeys
Build an ordered path from pages and published events, choose a conversion window, then inspect completion, drop-off, time between steps, and comparisons by device, country, or source. Journeys can analyze previously collected data.
Reports
Editors and admins can schedule a weekly property report, choose recipients and delivery day, send a test, and review or resend earlier deliveries.
Statistics gives admins a production-only overview across all tracked properties. Unlike the property pages, it is not scoped by the property picker.
Discover and manage events
Event discovery sends the LodyCDP crawler through public, same-site pages and uses AI to propose meaningful click interactions. No additional event code is required on the website after the LodyCDP tracker is installed. Discovery is available to editors and admins, and never publishes a suggestion automatically.
Configure the scan
Confirm the starting URL and optionally add a label and focus. You can keep the crawler under the starting path and override the page or link-depth budget under Advanced. The URL must belong to the selected property.
Follow and review
Watch live progress, cancel if needed, and inspect visited pages. Review each new proposal's name, page context, matcher, rationale, and confidence. Use Show events to switch between this scan and all scans for the site.
Publish deliberately
Approve useful proposals, reject the rest, then select Publish approved events. Later scans remember prior decisions and skip already reviewed candidates instead of recreating them.
Event catalog combines discovered and observed events in one place. Use it to inspect activity and context, find possible duplicates, combine event names as aliases, split aliases again, and organize related events into conceptual groups.
Event status dictionary
- Proposed
- Discovery found a new candidate. It is waiting for an editor or admin to approve or reject it and is not active yet.
- Approved
- You accepted the suggestion. It is ready to be included when you select Publish approved events, but is not active until published.
- Rejected
- You decided not to track the suggestion. It is excluded from publishing and can be approved later if you change your mind.
- Published
- The event is included in the active tracking plan and can collect new matching activity.
- Observed
- The tracker has received this custom event, but it does not have a Discovery proposal. It appears in the Event catalog from recorded activity.
- Unpublished
- The event was removed from the active tracking plan, so it will not collect new automatic records. Records collected while it was published remain available.
- Reset all events
- Removes all automatically discovered events from the active tracking plan and returns them to a reviewable state. It does not delete any existing analytics records.
Historical data is preserved. Approving, rejecting, publishing, unpublishing, and resetting do not delete records that LodyCDP has already collected. Reset all events also clears prior Discovery review decisions; starting another scan does not.
Roles, access, and security
- Viewer
- Read-only access to assigned properties.
- Editor
- Access to assigned properties plus cohorts, journeys, Event discovery, tracking plans, and reports.
- Security Auditor
- Read-only access to assigned properties, the security audit log, and raw event details used for oversight. Two-factor authentication is required.
- Admin
- Access to all properties and features, including user invitations, role and domain assignments, and global Statistics. Two-factor authentication is required.
A person can hold more than one role; their permissions are combined. Admins manage roles and property access from Users. Security Auditors and admins can open detailed Realtime records, and every console change is recorded in the security audit log.