# Product guides

> How to use every part of ClickClacks: traffic, insights, funnels, flows, retention, friction, alerts, experiments, boards, segments, people, sources, teams and agencies, with step-by-step recipes.

- Canonical URL: https://clickclacks.io/docs/guides
- Section: Product guides
- Last updated: 2026-09-26

How to use every part of ClickClacks, from your first look at traffic to a board you share with a client. Each guide walks through the real controls, then answers a few concrete questions step by step.

New here? Start with [Filters, dates and comparisons](https://clickclacks.io/docs/guides/filters.md). The same filter bar sits on top of almost every report, so learning it once pays off everywhere. Prefer to follow one goal from start to finish? Try the [analyst walkthroughs](https://clickclacks.io/docs/walkthroughs.md#analyst).

## Understand your traffic {#traffic}

Who came, from where, and what they did on the page.

- [Overview The page we picked for you: active people, pageviews, sessions, bounce rate, top pages, referrers and countries.](https://clickclacks.io/docs/guides/overview.md)
- [Realtime Who is on your site right now, and what they are doing, second by second.](https://clickclacks.io/docs/guides/realtime.md)
- [Heatmaps Where people click and how far they scroll, drawn over a real screenshot of the page.](https://clickclacks.io/docs/guides/heatmaps.md)

## Analyze behaviour {#behaviour}

Count things, find where people drop off, and see who comes back.

- [Insights Chart any event over time, split it by a property, and save it for later.](https://clickclacks.io/docs/guides/insights.md)
- [Funnels Line up the steps to a goal and see how many people make it through each one.](https://clickclacks.io/docs/guides/funnels.md)
- [Flows Pick one event and see the paths people take before and after it.](https://clickclacks.io/docs/guides/flows.md)
- [Retention Group people by when they started and see how many come back, week after week.](https://clickclacks.io/docs/guides/retention.md)

## Find problems {#problems}

Let ClickClacks tell you when something is wrong.

- [Friction Rage clicks, dead clicks and abandoned retries, found for you every night and ranked by how many people they hit.](https://clickclacks.io/docs/guides/friction.md)
- [Alerts Watch a number and hear about it when it leaves its usual range.](https://clickclacks.io/docs/guides/alerts.md)

## Experiment {#experiment}

Test a change and know when the answer is real.

- [Experiments Run A/B tests with a goal, guardrails and results you can check at any time.](https://clickclacks.io/docs/guides/experiments.md)

## Organize {#organize}

Keep the reports that matter, and keep your data tidy.

- [Boards Assemble your own page of tiles from saved reports, and arrange it the way you read it.](https://clickclacks.io/docs/guides/boards.md)
- [Segments Save a group of people once and apply it to any report.](https://clickclacks.io/docs/guides/segments.md)
- [Lexicon Describe, verify, tag, hide and merge events and properties, so every picker reads the same way.](https://clickclacks.io/docs/guides/lexicon.md)

## People {#people}

Go from a number to the humans behind it.

- [People and profiles Find a person, read their timeline, and see every event they sent across your sources.](https://clickclacks.io/docs/guides/people.md)
- [Events explorer Query the raw event stream, pick your columns, and watch new events arrive live.](https://clickclacks.io/docs/guides/events.md)

## Data {#data}

Where your events come from, and how people are stitched together.

- [Sources Add a website, web app or server, install it, and check that data is arriving.](https://clickclacks.io/docs/guides/sources.md)
- [Identity Follow one person across your domains and devices, and check how well it is working.](https://clickclacks.io/docs/guides/identity.md)
- [Custom domain Serve the tracker and its events from a subdomain you own, such as cc.acme.com.](https://clickclacks.io/docs/guides/custom-domain.md)

## Teams and agencies {#teams}

Bring your team in, or run analytics for many clients from one place.

- [Members and roles Invite people, choose what each role can do, and keep access tidy.](https://clickclacks.io/docs/guides/members.md)
- [Agencies The agency home, switching between clients, staff access and the cross-client alerts inbox.](https://clickclacks.io/docs/guides/agencies.md)
- [Weekly digest One email every Monday with each project’s visitors, biggest change, alerts and stopped sources.](https://clickclacks.io/docs/guides/weekly-digest.md)

## AI {#ai}

Ask questions in plain language, and track your own AI agents.

- [Friction investigator Ask questions about a friction finding and get answers that cite their evidence.](https://clickclacks.io/docs/guides/friction-investigator.md)
- [Traces Every run of your own AI agents: steps, outcomes, duration and cost, with model prices.](https://clickclacks.io/docs/guides/traces.md)
- [MCP server Connect Claude, Codex or any MCP client to your analytics. Developer docs.](https://clickclacks.io/docs/mcp.md)

## Recipes {#recipes}

Have a question rather than a feature in mind? The [recipes page](https://clickclacks.io/docs/guides/recipes.md) answers common ones step by step: activation, attribution, checkout drop-off, feature adoption, rage-click triage and a weekly board for a client.