Listdom Directory Analytics helps administrators understand what people do inside a directory: which listings receive attention, what visitors search for, and which supported actions they take. Open Listdom → Analytics to review directory-wide activity and use the Stats add-on for detailed event collection and reporting.
The most useful report answers an operational question. Are visitors finding relevant services? Is a busy category sending people to useful listing details? Do contact actions follow that attention? This guide explains how to read the measures, check their coverage, and choose a next step without treating every click as a customer.
Start with a question your directory can answer
Choose a question before choosing a chart. “How many views do we have?” can be a useful starting point, but it rarely tells you what to improve. “Are people searching for services we have not covered?” leads to a clearer investigation.
A city guide might begin with search demand by location. A specialist service directory might compare detail-page attention and contact actions for its most important categories. A directory selling visibility may need to distinguish the exposure a placement receives from the actions that follow it.
Write down one question and the decision it could change. If more people search a neighborhood than your directory currently serves, you might recruit relevant businesses there. If many listings appear but few receive detail clicks, you might review card information. These are hypotheses to investigate, not conclusions a single total proves.
Understand Core Analytics, Stats, and the public element
Listdom → Analytics is the administrator’s reporting workspace. Listdom Core supplies the entry and overview; the Stats add-on supplies detailed event collection and reports. If detailed reporting is unavailable, follow the Webilia Connect prompt, connect the site, and install and activate the required add-on.
This is separate from displaying statistics on an individual listing. The public Stats listing element has its own display controls. Enabling a visible counter is not the same task as configuring directory-wide event collection, and hiding a public counter does not explain the entire state of your analytics configuration.
Owner workflows are another distinct audience. The frontend dashboard guide explains how owners manage their directory presence. Do not assume that an owner’s view provides every report available to a site administrator or that an administrator’s access proves an owner has the same permissions.
Configure collection before interpreting an empty report
In Analytics, choose Manage Stats settings. Review whether analytics collection is enabled, whether administrator activity is excluded, and which visitor, search, and engagement events you want to collect. Supported actions depend on the active integrations and their tracking switches.
Set a default reporting range appropriate to the decisions you make: the available defaults are 7, 30, or 90 days. Then choose event retention from 30, 90, or 180 days. These settings answer different questions. The report range selects what you view; retention limits how long event history remains available.
Check the collection start date before looking for historical patterns. Installing detailed reporting today does not create a complete event history for last month. Existing counters are not a substitute for events that were never collected.
For an initial validation, use a safe test process and distinguish intentional test activity from normal traffic. If administrator activity is excluded, browsing as an administrator may not produce the evidence you expect. That can be a correct configuration rather than a broken report.
Read the counting unit before comparing numbers
Analytics contains different kinds of measures. A card impression, submitted search, and contact click describe different events. They cannot automatically be combined into a person-level funnel.
The following figures are a hypothetical example, not measured Listdom results:
| Measure in one reporting period | Example count | What it tells you |
|---|---|---|
| Listing-card impressions | 1,200 | Recorded opportunities to see listing cards |
| Listing-card clicks | 110 | Recorded actions opening listings from cards |
| Detail views | 180 | Recorded views of listing detail pages, including other entry routes |
| Submitted searches | 80 | Deliberate search submissions |
| Zero-result searches | 12 | Recorded submissions that returned no results |
| Website clicks | 15 | Recorded clicks to supported website destinations |
The 180 detail views can include people arriving directly rather than through the 110 card clicks. A visitor can submit several searches. A website click can happen without a purchase. Calling the table “1,200 visitors became 15 customers” would change both the counting units and the meaning.
Track Unique Views estimates one view per browser, listing, and UTC day. One person using two browsers can contribute more than one estimated view. Several people sharing a browser can be represented differently. Use the measure as an estimate with a defined method, not a verified headcount.
Use search activity to investigate unmet needs
Search reports can show submitted searches, result totals, zero-result searches, filter use, and popular terms when term tracking is enabled. Counts represent deliberate submissions. Pagination, sorting, loading more results, and zooming a map should not be read as additional submitted searches.
Start with a recurring zero-result pattern. Suppose visitors repeatedly search for evening childcare in one district. There are several plausible explanations: you lack suitable providers, existing records lack a relevant field, the form encourages an unsupported combination, or a saved results restriction excludes useful listings.
Reproduce the query on the public search page before deciding to recruit more businesses. Inspect the target results configuration, then check representative listings. The Listdom search-form guide helps you trace the fields and destination involved.
A few zero-result searches can be normal in a specific directory. The useful distinction is whether a pattern reveals an avoidable failure or a deliberate scope boundary. A guide covering one city should not necessarily expand because someone searched another country.
Separate listing exposure from useful action
Popular listings can tell you where attention concentrates, but compare them in context. A listing shown more often has more opportunities to receive a click. A listing with a specialized service can be valuable with fewer views if it answers an important need.
Review listing-card information when exposure is high but opening activity looks weak. Does the title identify the service? Is the location clear? Is the image helpful? Check the detail page before interpreting low contact activity: an outdated phone number, an unclear offer, or missing practical information may be the real obstacle.
Supported engagement events include contacts, phone, email, website and WhatsApp clicks, directions, shares, favorites, and map-marker interactions. Availability depends on the integrations and tracking options active on your site. These actions express different intentions; saving a favorite is not equivalent to sending an inquiry.
If you sell featured exposure, the featured-listings guide provides the commercial context. Describe the exposure and recorded actions you can substantiate. A phone click does not prove that a call connected, and a directions click does not prove a shop visit.
Check coverage before comparing periods
Choose the reporting range, then inspect collection start dates, gaps, and partial-coverage notices. A seven-day report containing two days before collection began is not equivalent to seven fully tracked days.
Changes to event toggles matter too. If website-click tracking was enabled halfway through a period, a rise in recorded website clicks may reflect collection rather than visitor behavior. Retention can remove older event detail; it does not reconstruct deleted records when you later increase the setting.
Use periods with comparable coverage and note relevant site changes. A category reorganization, seasonal event, placement change, or different listing inventory can affect the comparison. Avoid assigning every difference to the most recent design edit merely because it is easy to remember.
The CSV export includes reporting dates, range, timezone, collection window, and coverage context. Keep that information attached when sharing a file. A colleague reading only a total may otherwise compare an incomplete period with a complete one.
Make two decisions from the hypothetical example
Return to the example table. The 12 zero-result submissions justify inspecting the repeated queries, not immediately redesigning the whole search form. If several involve a missing neighborhood category, examine whether the directory should cover it and whether suitable listings already exist under another label.
The 15 website clicks justify a different investigation. Open a selection of relevant listing destinations and confirm that the links lead to useful pages. If owners supplied generic homepages where visitors need booking or service details, consider improving the information your submission process requests.
Neither action requires claiming a conversion rate from incompatible counts. You are using observed activity to select a concrete inspection, then changing something only when the inspection supports it. The listing data-quality guide can help turn recurring content problems into an editorial routine.
After a change, collect a comparable period and look for the relevant behavior. Record the change and any limitations. Several simultaneous changes make it harder to understand which one helped.
Review privacy and public presentation separately
Track Search Terms stores bounded, normalized terms and excludes email-, URL-, and phone-like searches. Those protections do not establish blanket privacy or consent compliance for every site. Review the collection you enable against your own audience, policies, and applicable requirements.
Choose the events you actually need for directory decisions. Longer retention is not automatically better when your team cannot explain why it needs the additional history. The Directory Analytics reference explains collection and reporting controls.
If you want visitors to see listing statistics, enable Stats in the single-listing layout’s Listing Elements settings and choose the fields to display. The element is separate from the administrator’s Analytics workspace. The Stats add-on display guide covers that public presentation.
Keep a small, repeatable reporting habit
A weekly review can be straightforward: confirm coverage, inspect a meaningful search pattern, review one listing group, and record one justified action. Review categories and locations alongside individual listings so popular businesses do not conceal gaps elsewhere in the directory.
Keep the limits visible when reporting to owners or teammates. These reports concern activity inside the directory. They do not independently measure Google impressions, search rankings, AI citations, or sales completed on another website.
Start with a question you can answer using the events you collect. A modest report that leads to a defensible improvement is more useful than a large dashboard whose totals nobody can interpret.
FAQ
Is Listdom Analytics the same as the Stats listing element?
No. Analytics is the administrator’s directory-wide workspace. The Stats listing element displays selected statistics on a listing page and has separate presentation settings.
Why does an older directory have little recent event data?
Detailed collection may have started recently, been disabled, or had gaps. Retention may also limit the available history. Existing counters do not create a complete record of earlier events.
Do unique views count individual people exactly?
No. The estimate uses a browser, listing, and UTC-day basis. It is useful when interpreted consistently, but it is not a verified count of people.
Does changing pages in the results count as another search?
Search reporting concerns deliberate submitted searches. Pagination, sorting, loading more results, and map zooming should not be interpreted as additional submitted searches.
Can I treat phone or website clicks as sales?
No. They record interactions. Confirming answered calls, completed purchases, or other external outcomes requires evidence beyond those click events.
What should I include when sharing an export?
Preserve the date range, timezone, collection window, and coverage information. Explain changes in tracking or site configuration that materially affect a comparison.
