Totallytics is now Clicktag

Totallytics is now Clicktag

Totallytics has a new name: Clicktag. Along with this new name, we have introduced a clean green interface and organized our web addresses into two distinct locations. Our public website and documentation now live at clicktag.io, while your analytics dashboard and site settings live at clicktag.app.

While the look and web addresses have updated, your day-to-day experience remains uninterrupted. Everything you have already set up continues to work as expected. You do not need to rewrite your tracking scripts, migrate your data, generate new tokens, or rebuild existing dashboards. Your historical analytics, site verifications, API keys, and custom setup carry directly into Clicktag.

Summary of changes

Here is a quick look at what has moved and what remains completely unchanged across your setup:

Client-side tracking and your websites

You do not need to reinstall or edit your existing tracking snippets. Scripts loaded from previous endpoints continue to collect pageviews and custom events without disruption.

If you manage scripts on your site, here is what you need to know about compatibility:

• Global configurations through window.tt_settings and HTML attributes like data-hostname and data-verify work exactly as before. For a complete guide to setup options, check our installation guide.
• Custom event tracking through window.tt_event(name, metadata) continues to record actions as outlined in our events documentation.
• Automatic tracking for single-page applications monitors standard browser navigation by listening for pushState and popstate events that change the URL pathname. It does not automatically track replaceState calls or URL changes that only affect search query parameters.
• If you disable automatic tracking by setting data-auto-collect="false", you can trigger pageviews manually by calling window.tt_pageview(path).

Backend libraries and API analytics

If you monitor your backend services with our libraries, your server code does not require changes. Our packages continue to aggregate request metrics, such as request counts, status codes, and response latency, across your backend endpoints.

You can continue using the existing library releases:

• Node.js, Bun, and Deno applications continue using the totallytics package from npm.
• Go services continue importing github.com/bitgate/totallytics-go in their modules.
• Existing backend deployments continue reading your API key from the TOTALLYTICS_API_KEY environment variable.

To review middleware setup and metric summaries, visit our API analytics documentation.

Signing in to clicktag.app

When you are ready to check your metrics or manage your site settings, head to clicktag.app.

Our dashboard authentication relies on Firebase client-side storage, which web browsers isolate by web origin. Because browsers do not share origin-scoped browser storage between different domains, your existing login state cannot carry over automatically to the new domain.

When you visit clicktag.app for the first time, simply sign in using the same Google account you have always used. Once you log in, you will find all your websites, verified tokens, historical stats, and site settings exactly where you left them.

Optional three-step checklist

You do not need to change anything today to keep your analytics running smoothly. However, if you would like to tidy up your tools and workflows, here is an optional checklist:

1. Update your browser bookmarks to point directly to https://clicktag.app for quick dashboard access.
2. Update internal team runbooks or onboarding notes to reference https://clicktag.io for public product documentation.
3. If you decide to update your site script tags to the new domain later, review your Content Security Policy (CSP). Merge the new domain into your existing script-src (and script-src-elem if present), img-src, and connect-src directives as needed. No changes are required for your existing working legacy configuration.

Frequently asked questions

Do I need to reinstall my website tracking code right now?

No. Your existing tracking script tags continue to capture page visits and custom events without issue. Existing ingestion endpoints remain active, so your data collection carries on without interruption. You can update your script tags whenever you next update your website.

Why am I asked to sign in again on the new dashboard?

Authentication uses Firebase origin-scoped browser storage rather than shared session cookies. Because modern browsers keep storage strictly isolated to each web origin, clicktag.app cannot read the login data stored under the previous domain. Signing in with your existing Google account immediately connects you to your account.

Are the backend library names or environment variables changing?

No. Backend packages will remain totallytics on npm and github.com/bitgate/totallytics-go for Go. Your servers should also continue using the TOTALLYTICS_API_KEY environment variable to authenticate metric delivery.

Will my existing site tokens or historical data be affected?

No. All historical stats, site verification tokens, API keys, and site settings are preserved in full. Everything is linked to your existing Google account and appears in your dashboard at clicktag.app.