Install Stats4U on a static website without exposing private access

A static website can load a Stats4U counter without running PHP or maintaining a visitor database on its own host. The browser loads the integration from Stats4U and the counting happens there. Successful setup still depends on the published HTML, the host policy and the visitor browser allowing the required requests.

Prepare the public integration

1. For a new counter, choose a design and copy the generated code. For an existing counter, keep its counter number. Save the private management link securely before editing the site. A counter can work without an account while its owner access still needs protection.
2. Put only the public embed in the shared HTML template where the counter should appear. A static-site generator must carry that template into the published pages. Check the generated HTML after deployment; editing a source component does not prove that the live page contains it.
3. Keep the owner token, management link and API keys out of public HTML and repositories. The counter number and public design options are sufficient for the normal embed. Review the complete copied text before committing it; do not publish private bookmarks as installation instructions.

Use the integration supported by the host

Where external scripts are allowed, use the generated JavaScript snippet and the hosted s4u.js address. This allows updates to reach the integration. A downloaded copy stays at its copied version unless it is updated separately; changing the website does not update that file automatically.

Where only images, Markdown or BBCode are accepted, use the matching generated integration. It can count image requests, while page details depend on the HTTP Referer or an explicitly supplied address. Optional automatic events require JavaScript; a picture alone cannot observe a confirmed form result.

Check the published result safely

Inspect an own authorised test page in the browser network panel. Check the counter number, duplicate snippets and blocked resources. Content Security Policy, editor filtering or a browser extension may prevent the script or image from loading. Do not disable broad security protections merely to make a badge appear.

A normal page visit can count. Do not manually open the counting-image address or repeatedly refresh it to diagnose the installation. An invisible design can load correctly without showing a badge; inspect requests and the corresponding report instead of adding another snippet just to make something visible.

Know what a counter cannot observe

The counter reports requests and supported measurements that reach Stats4U. It does not see every request handled by the static host, server errors, failed downloads or bandwidth. Those require the host logs or its own monitoring where available. Static hosting does not guarantee that such information is unavailable.

A static site still needs maintained content, a protected publishing account and an appropriate privacy notice. A counter does not remove those responsibilities. Enable optional campaign or event measurements only when their setup is understood; installing the basic snippet does not populate every advanced report.

Choose and publish the correct integration

The installation guide explains the available code formats and checks after embedding.

Open the installation guide