Check an unexpected counter total without guessing

A stalled total, a sudden increase or a difference from another analytics tool can have several causes. Work through the checks in order. Keep the existing counter number and private management link; creating a replacement counter makes comparison harder and starts a separate set of statistics.

Start with the counter and the report

1. Read the counter number in the installed code and in the statistics address. They must refer to the same counter.
2. Check the metric label, selected dates and counter time zone. A running total, page views and daily visitors answer different questions.
3. Open the page template or integration settings and look for duplicate snippets. Keep the intended installation; do not delete code merely because a number differs.

If the number appears too low

On a website that belongs to the tester, inspect the browser’s network panel while opening one intended page. Check whether the Stats4U script and counter image are requested, whether they are blocked and which counter number they use. Do not call a counting address by hand: doing so creates another request rather than proving that the website integration works.

A successful script download alone does not prove that a counting request was completed. Browser extensions, Content Security Policy, an incorrect snippet or a platform that removes scripts can stop the next step. For an image-only installation, check the image request itself. Lazy loading can delay that request until the visitor scrolls close to the image.

For missing campaign data, first enable campaign measurement in the owner tools and use the UTM link generator. The final landing page must retain the campaign parameters. The JavaScript integration explicitly reports that address; image-only counting depends on the HTTP referrer or a manually supplied address, which may lack those parameters. The campaign guide explains the permitted labels and attribution limits.

If the number appears too high

Check for the same counter in both a theme and a plugin, or in both a global template and an individual page. Compare bot settings and the metric being displayed. Several page requests can belong to the same daily visitor; a page-view total should not be compared directly with another tool’s visitor total.

A preset starting value affects the counter total without adding earlier daily records. Historical retention also limits what a date-based report can show. Do not assume a lifetime total can always be reconstructed by adding the daily rows still retained.

Use diagnostics for the question they answer

The measurement debugger checks whether a proposed event would be accepted without increasing the statistics. It does not prove that a normal page view was counted or that a form or purchase succeeded. For a missing event, check its feature setting and event name there, then inspect the actual integration on the owned website.

If the issue remains, send support the counter number, page address, metric labels, dates and the observed error. Remove private management keys, share keys and personal form contents from screenshots and logs. Existing data should remain untouched while the cause is investigated.

Next step

Use the installation instructions for the website platform.

Open the installation guide