Missing analytics does not always mean your site had no visitors. Collection may be off, a report may have failed to load, or the activity may fall outside the page or period you are viewing. Two reports can also show different totals because they count different things.
Start with one specific question, such as “Why does this page show no clicks?” or “Why are this week's visitors lower here?” Check that measure before changing your tracking setup.
Separate an empty report from a loading problem
Read the message beside the figures before interpreting them.
- No visits in this window means no traffic was recorded for the selected period. Try a longer period and check Last activity on Site analytics Overview.
- Analytics data is unavailable means the report could not load. Select Retry analytics. It is not a zero-traffic result.
- Showing the last successful results means older figures remain visible after a failed refresh. Wait for a successful refresh before treating them as current.
- Updating… means a refresh is in progress. Let it finish before comparing figures or exporting them.
- Built-in off means built-in collection is disabled. Previously collected data can remain visible, even though new activity is not being added through that collection.
A page-level report uses Try again for a failed load. If only one report or panel fails, investigate that panel rather than assuming every analytics source is unavailable.
A blank speed measurement, missing revenue tile, or absent search comparison is also different from a measured zero. Read the nearby explanation and sample information.
Match the page and reporting period
- Open Dashboard → Insights → View full analytics for a site-wide view. For one page, post, or doc, open its analytics from the relevant content list.
- Check the selected period. Start with Last 30 days, then try a longer period if the site or page has little recent activity.
- For a page report, confirm the public route shown beneath its title. If the URL changed, do not assume visits to the old route moved into the new route's report.
- Wait for the selected period to load successfully. Keep both reports on equivalent dates before comparing them.
- Read chart subtitles, currency labels, and result timestamps as well as headline numbers.
Cedros's day ranges are rolling windows ending now. Daily charts use UTC calendar days, including the current, unfinished day. A chart's day boundaries therefore differ from the rolling headline window. Comparing an unfinished day with a complete day can make a normal total look unusually low.
All time does not always mean the chart shows every day. Site analytics headline totals use available history, while its daily trends show the most recent 366 days. In a single-page report, the All time headline can cover the full available history while the Traffic chart shows the most recent 30 days.
A report under Reports is a saved run result, not a continuously recalculated dashboard. Check which run you opened and when it finished. View latest returns from an earlier run to the latest result; Run now requests a new result when the report is active and you have access. See Scheduling reports and reviewing run history.
For more on the site-wide measures and windows, see Understanding your site analytics.
Check what the site is collecting
Open Analytics in the admin navigation and select Built-in. Check the specific event type you expected, such as Page views, CTA clicks, Click heatmap, Scroll depth, or Engagement time. Search collection has separate Site searches, Docs searches, and Blog searches controls.
Collecting means that event type is enabled. It does not prove anyone has performed the action or that an event reached the report. A page can have views without any recorded CTA clicks, form activity, or scroll measurements.
Analytics settings save automatically. If you change an intended setting, wait for saving to finish and resolve any error. Use Retry saving when offered, then reload the settings to confirm the saved state. A switch changing on screen is not enough.
Turning collection on does not recreate earlier activity. Check new visits after the change. Increasing how often a report runs cannot recover events that were never recorded.
When GDPR cookie notice is enabled, optional browser tracking waits for acceptance. A rejection or the browser's Global Privacy Control opt-out can explain missing optional activity. Browser extensions, blocked requests, connection failures, and restricted storage can also leave gaps. Do not treat an individual visitor's privacy choice as a site error.
Use Configuring analytics and tracking integrations for the collection switches, consent notice, saved-provider checks, and duplicate-tag setup.
Investigate the particular measurement
Views appear, but a heatmap is empty. A click heatmap needs recorded clicks and its own collection switch. Scroll depth and attention need their respective measurements. Confirm the page and period before changing anything. If the preview says the page did not render, use Try again and check the public page separately; a missing background is different from no recorded clicks.
Journeys are empty or shorter than expected. Journeys need session detail as well as events. Page-view totals alone do not guarantee a complete path. The journey list also shows a limited set of recent visits, so its visible row count is not the site's total visit count. Check filters and use additional-row controls when offered.
Search impressions or queries are missing. On-site searches, local Google landings, and Search Console performance are different sources. Google landings are visits recorded from Google referrals; they do not supply search-result impressions. In a page report, check whether search performance says Live, Not connected, Local fallback, or Unavailable, and read the reported dates. Use Connecting search-performance services to check the connection and property access.
Revenue is missing or differs from a payment report. Check the panel's access/setup message, period, currency, and whether you are reading gross revenue, net revenue, refunds, or purchase counts. Analytics outcomes and the Cedros Pay payment summary are separate views. In particular, Last 12 months uses a rolling year for analytics, while the Pay panel shows year to date. See Understanding journeys, attribution, and revenue before comparing them.
A new page or edit has no activity. Confirm that the intended page is published at the public address you are testing. Editing a draft or opening an editor preview does not establish that visitors saw the new content. An older published version can still be receiving visits.
Compare like with like
Use the same site, page, dates, timezone, metric, and filters in both reports. Then check how each number is defined.
Visitors, visits, and page views are different counts. Cedros Visitors represents distinct tracked identities, rather than verified individual people. One person using two browsers or devices can have separate identities. One visitor can have several visits, and one visit can include several page views.
Do not add daily visitor counts to obtain unique visitors for a month: the same visitor can appear on several days. The same overlap can occur across page or source rows. Ranked lists and exports of those lists also need not contain every event or every page.
A click is not a completed outcome. CTA clicks do not establish that someone submitted a form, completed a booking, or paid. Cedros's CTA click-through percentage uses tracked CTA impressions as its denominator, not all page views. Compare the same event and denominator before treating percentages as contradictory.
Source categories need interpretation. Direct can include visits without a usable external source. Paid & campaigns includes tagged traffic, so a tagged newsletter can appear there without advertising spend. Recognized crawler activity is reported separately from visitors; automated traffic handling can affect a comparison.
External tracking has its own setup. A saved provider ID does not prove delivery, and enabling a tracking integration does not import that provider's reports into Cedros. Check its destination account separately. If totals are unexpectedly high there, review whether the same destination is installed through both a direct integration and Tag Manager or custom code. Do not add two services' visitor totals together as if they represented different audiences.
Test a normal published visit
- Note one published page's public URL and the activity you want to test. Start with a page view or harmless navigation action.
- Open it in a normal browser profile whose consent and privacy settings you understand. Use the public address, not an editor or heatmap preview.
- If the consent notice appears, make the choice appropriate for your test. A previously saved choice may explain why no notice appears.
- Perform the action once and note the time and timezone. For attention measurements, keep the page visible and focused rather than leaving it in a background tab.
- Return to the matching report, select a period that includes the test, and refresh after allowing time for the event and report to update. Check an external provider separately if that is the destination you are testing.
Preview activity and automated browser tests can be excluded from analytics. They are not reliable substitutes for an ordinary visit. Repeatedly refreshing a public page can also add views without adding another distinct visitor, so avoid using repeated refreshes as a visitor-count test.
If the event still does not appear, compare the saved collection setting, consent choice, browser restrictions, route, and report state. Change one relevant factor at a time so you can tell what helped. A successful page-view check does not verify purchases, bookings, or every custom event.
Give the site owner a useful example
If you still need help, collect a small, specific example:
- The site and public page URL, plus the report or panel you opened.
- The metric you expected, selected period, and comparison service if there is one.
- The action's time and timezone, browser, and consent choice.
- The exact error or status message, including whether older results remain visible.
- A screenshot with sensitive details removed; for a saved report, include its run ID.
State what you expected and what appeared, such as “I visited this published page at 10:15, but its Last 30 days report still shows no views after a successful refresh.” That is more useful than “analytics is wrong.”
If you cannot open the report or edit collection settings, ask the site owner to review your feature and settings access. Access to analytics does not automatically include every payment report or content-editing action.