Move a website while keeping the same counter and history

A move to another host or domain does not require a new Stats4U counter. The counter number connects new measurements to the existing history. A reliable move preserves that number, the private management link and a single intended installation on each page. Old measurements are not rebuilt from the new website.

Before changing the website

1. Open the existing statistics and save the private management link securely. The public statistics address does not prove ownership. The guide to My counters explains where to find an owner link and how to connect an existing counter.
2. Copy the existing integration from the current template. Record its counter number and intended location. Check whether a plugin, shared footer or tag manager also inserts the same counter; the new site needs one intended installation, not overlapping copies.
3. Keep a copy of the current template and export any reports needed for the move. An export is a separate record for comparison; it does not import historical figures into another counter.

Check the new installation without adding artificial traffic

Publish the snippet in the new template with the same counter number. For JavaScript integration, keep the hosted s4u.js address. Do not replace it with an old downloaded copy. A change of host is not a reason to change the counter number or manufacture a new starting total.

Inspect the published HTML and the browser network panel during an authorised visit to the own test site. Check the counter number, a successfully loaded script or image, and blocked-request messages. Do not open or repeatedly reload the counting-image address as a diagnostic: that can add measurements. An ordinary page visit can also count.

Compare dates, domains and existing options

Use the same dates and the counter time zone for comparisons. A short interruption can leave a gap; Stats4U cannot reconstruct requests it never received. If old and new sites both remain open, their traffic can contribute to the same counter. Record the cutover date as a private chart note.

Review configured page groups, goals, funnels and campaign landing links. Rules involving a changed path may need updating. Historical page addresses keep their previous domain and path; renaming the website does not rewrite them. A new rule cannot invent visitor progress before that measurement existed.

Keep private links out of the public template

A public embed needs the counter number and design options. It does not need the owner token, a private management link or an API key. Keep those out of HTML, public repositories and screenshots. Update private bookmarks separately from the public installation.

If the counter stops, compare the published snippet with the saved working version and inspect blocking or duplicate integration before changing settings. Keep the old hosting available until the new pages have been checked. Avoid resetting data merely because the new site looks different.

Keep access to the existing counter

Find the private owner link and connect the counter to My counters before the move.

Read the owner-link guide