✦ Cookieless analytics, built around daily rotating IDs
☰
All featuresWeb AnalyticsCustom EventsCookieless AnalyticsIntegrationsPricingDocumentationComparisonsFree toolsBlogGlossary
Installation guide

Install cookieless analytics on Webflow

Add the browser bundle through Webflow’s site-wide custom code and verify it on the published site. There is no native Webflow app required for this manual installation.

Prepare the SDK from source

The SDK package is currently private and unpublished. Clone its repository and build the browser bundle. The source repository uses pnpm; application integration examples below use npm. Pin a reviewed commit for a production deployment.

Build the source and a local package archive

git clone https://github.com/yosriady/untitled-analytics-sdk.git
cd untitled-analytics-sdk
pnpm install
pnpm build
pnpm pack

Host the built bundle

Upload dist/snippet.global.js to a static host you control. Use its HTTPS asset URL in the script tag. Register your published Webflow domain as the site origin; your preview and custom domains may need separate registration.

Add site-wide custom code

Use Webflow’s site settings custom-code area, typically its footer/before-body section. Your plan must support custom code. Add the snippet once and publish the site; designer previews and staging behavior can differ from the published origin.

Site-wide footer code

<script src="https://assets.your-domain.com/snippet.global.js"
  data-write-key="YOUR_SDK_WRITE_KEY"
  data-endpoint="https://api.your-domain.com"
  defer></script>

Track a completed action deliberately

Basic pageviews do not require form-field capture. If you need a named conversion, invoke track from your confirmed completion behavior after the tracker loads. Avoid recording every typed input or guessing that a click equals a successful submission.

If a custom interaction changes pages without a full navigation, call window.untitledAnalytics.page after the navigation. The public SDK key is safe for this browser integration; private MCP keys are not.

Verify pageviews and custom events

Register your actual site origin and use its public SDK write key. The endpoint is your deployed API origin, not a Tinybird URL. Open the published site, check that the bundle loads, and inspect successful collector requests and the project activity feed. Collection is queued, so allow for delivery latency.

Trigger a second page and a custom event. Confirm one expected pageview per navigation. Disable duplicate analytics installations. Identify an account only after login and clear the SDK user ID at logout. Review campaign fields, properties, and optional replay on a non-sensitive page first.

Frequently asked questions

Is the npm package public?

No. Build from source and install the local archive, or host the built browser bundle. Do not assume npm install @untitled-analytics/web resolves yet.

Which endpoint do I use?

Use your deployed analytics API origin, such as https://api.your-domain.com. Do not expose Tinybird or database credentials in browser code.

How do I check installation?

Verify bundle loading and successful collector requests, then inspect the project activity feed for the page and a named test event.

Sources and implementation