Docs
ClickClacks docs
ClickClacks runs from a single browser script. These guides cover installing it, sending your own events, following people across domains, and exactly what it collects.
- Install the tracker One script tag in your document head. What data-key and data-domains do, framework placement, and checking the first event arrives.
- Events and identify What is captured automatically, how to send your own events, and how to tie a visitor to a user in your product.
- Domains and identity Allowed domains, following one person from your marketing site into your app, and serving the tracker from your own domain.
- Privacy What the tracker stores and sends, what it strips before anything leaves the browser, and how to opt a visitor out.
How the pieces fit
Five words come up throughout these guides. Each one contains the next.
- 01OrganizationYour team. It owns the data and the subscription.
- 02ProjectOne product. Every surface of it reports here, so a funnel can cross from site to app.
- 03SourceOne place events come from, such as a website or a web app. Each has its own browser key.
- 04PersonOne human, assembled from events across the project’s sources.
- 05EventOne recorded action: a name, a time and properties.
Ready to add a source? Open the app or start with the install guide.