What image-only counting and JavaScript each measure
Technically reviewed:
About the content and its review
In this article
Stats4U can count through a plain image or through its JavaScript integration. Those methods do not supply the same information. A counter can increase while the page report contains only a domain or no usable address. An image request may carry page information, but does not automatically describe the full surrounding page.
Understand the image-only installation
An image, Markdown or BBCode installation requests the counter image. The server can use the HTTP referrer as page information, but cross-origin browser policies often reduce it to the origin rather than the full page address. The supported p= parameter can supply a page address manually. The image does not run page JavaScript or observe form events and completed purchases.
A missing page address or N/A therefore need not mean that counting failed. A domain-only entry may reflect the information the browser actually sent. Check the installation and any manually supplied address before interpreting an empty or incomplete page report. The referrer of the image request describes the embedding page, not the earlier website that referred the visitor.
Use JavaScript where the platform permits it
- Open the Stats4U installation guide and choose the website platform. Use the generated code for the existing counter number.
- Place the JavaScript snippet in the template used by the pages to be measured. Avoid adding the same counter again through another plugin or widget.
- On the owned website, check whether the platform preserved the script and whether the browser requested it. A preview inside an editor may behave differently from the published page.
The JavaScript integration can supply the page and referrer information used by the page and source reports. This still depends on successful execution and the information the browser makes available. A missing referrer is not reliable proof that a visitor typed the address directly.
Enable extra measurements deliberately
Campaign reports require campaign measurement to be enabled and a valid marked landing link. Automatic contact and form events require the corresponding setting. A form submission signal does not establish that processing succeeded; confirmed success must be reported from the application’s success path.
Funnels use configured page or event steps in order after the funnel is created. Shop reports require a connected integration that reports completed purchases. Merely installing the basic counter or switching on an option cannot reconstruct those outcomes from old page-view totals.
When scripts cannot run
If a forum or website platform removes scripts, use its supported image, Markdown or BBCode option. Keep the limitations visible when interpreting reports. Do not paste unsupported JavaScript repeatedly or promise campaign and form reports from an image-only counter.
For an image counter, load the counting image when the visit should be counted. Adding loading="lazy" can delay the request until the image approaches the viewport. A footer image that is never approached may never be requested. Preserve generated dimensions to reserve space without delaying measurement.
Next step
Find the supported integration for the website platform.
Open the installation guide