# Recipes

> Common analytics questions answered step by step in ClickClacks: activation, attribution with visit referrer and UTM, checkout drop-off, feature adoption, rage-click triage, retention, alerts, and a weekly board for a client.

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

Real questions, answered step by step. Each recipe uses the controls you will see in the app and links to the guide with the details.

Event names such as `Signed up` are examples. Use the names your product sends. [Lexicon](https://clickclacks.io/docs/guides/lexicon.md) lists them all. To add the event a question needs, such as a FAQ opened or a form started, see [Examples](https://clickclacks.io/docs/examples.md).

## What share of sign-ups activate in their first week? {#activation}

Pick the action that means “got value”, such as creating a first project.

1. In [Funnels](https://clickclacks.io/docs/guides/funnels.md), click **New funnel** and start from the _Signup → activation_ template, or add `Signed up` then `Project created`.
2. Set **Conversion window** to **7 days** and **Count** to **Unique people**. Save.
3. Read **Overall conversion** and **Median time to convert**.
4. Click the drop and open **What they did instead** to see where the others got stuck.

Then check whether activated people stay: in [Retention](https://clickclacks.io/docs/guides/retention.md), set the starting event to `Project created` and read the weekly curve.

## Which campaigns and referrers bring sign-ups? {#attribution}

ClickClacks gives every event in a visit the visit’s referrer and UTM values. So a sign-up three pages after landing still counts toward the campaign that brought the visit.

1. In [Insights](https://clickclacks.io/docs/guides/insights.md), chart `Signed up` as **Unique people**.
2. Click **Add breakdown** › **Event property** › **UTM campaign**, **Top 10**.
3. Switch the chart to **Bar** to rank them over the range. Save it as _Sign-ups by campaign_.
4. For untagged traffic, change the breakdown to **Referrer**.

Need the referrer of one event itself, such as the page that linked to your pricing page mid-visit? Use **Referrer (this event)** under **Show advanced properties**. See [Referrer and UTM](https://clickclacks.io/docs/guides/filters.md#referrer).

## Which pages lead to sign-up? {#signup-paths}

1. In [Flows](https://clickclacks.io/docs/guides/flows.md), choose `Signed up` as the anchor.
2. Set the direction to **Before** and **Steps** to 3. Keep **Pageviews by path** on.
3. Switch to **Table** and read **Top paths**.
4. Click **Open as funnel** on the top path to measure how many who start it finish.

## Where do people drop out of checkout? {#checkout}

1. Build a checkout [funnel](https://clickclacks.io/docs/guides/funnels.md): `Added to cart` → `Checkout started` → `Payment submitted` → `Order completed`, 7-day window.
2. Read **Biggest drop-off** and click it.
3. In the drawer, **Where they were** shows the page they stopped on.
4. Open that page in [Heatmaps](https://clickclacks.io/docs/guides/heatmaps.md) on **Mobile** and **Desktop**, and check [Friction](https://clickclacks.io/docs/guides/friction.md) for findings on it.
5. Choose **Break down by** › **Device** to see whether one device is the problem.

## Is anyone using the new feature? {#adoption}

1. In [Events](https://clickclacks.io/docs/guides/events.md), pick the feature’s event, such as `Export created`, over **Last 30 days**.
2. Read **Feature adoption**: unique people and uses per person, by week.
3. Choose **Break down by** and a property the event carries, such as `plan`, to see who uses it.
4. For stickiness, set Retention’s starting and returning events both to `Export created` with **Came back every week since**.

## What % of new visitors come back in week 1? {#week-one}

1. In [Retention](https://clickclacks.io/docs/guides/retention.md), click **Edit definition**.
2. Set the starting event to a pageview and the returning event to **Any event**, with **Came back in that week**. Apply.
3. Read the **Week 1 retention** card, and the W1 column cohort by cohort.

## Why did sign-ups drop on Tuesday? {#drop}

1. If you have an [alert](https://clickclacks.io/docs/guides/alerts.md) on sign-up conversion, open the fired alert and read **What changed**: which segment holds the gap?
2. If not, chart `Signed up` in [Insights](https://clickclacks.io/docs/guides/insights.md) and break it down by **UTM source**, then **Browser**, then **Country**. Look for the one value that fell.
3. Check each source’s health in [Sources](https://clickclacks.io/docs/guides/sources.md). A source that stopped sending looks exactly like a drop.
4. Look at [Friction](https://clickclacks.io/docs/guides/friction.md) for anything new that day.
5. Then set up an alert so you hear about it next time.

## Rage-click triage {#rage}

1. Open [Friction](https://clickclacks.io/docs/guides/friction.md) on **Happening**. Start with _Getting worse_, then most people affected.
2. Read **What we saw**: did people give up afterwards?
3. Ask the [investigator](https://clickclacks.io/docs/guides/friction-investigator.md) _Is this concentrated in a saved segment?_
4. Fix it and **Link an outcome** to measure the fix, or **Mute** it if it is expected.

## Did the redesign work? {#redesign}

1. Mark the release date with an [annotation](https://clickclacks.io/docs/guides/boards.md#annotations) so it shows on every line tile.
2. Open the page in [Heatmaps](https://clickclacks.io/docs/guides/heatmaps.md) and click **Compare periods**: the weeks before against the weeks after.
3. Compare the relevant funnel’s conversion for the same two windows.
4. Before-and-after shows change, not cause. For a fair answer next time, run an [experiment](https://clickclacks.io/docs/guides/experiments.md).

## Follow visitors from our site into our app {#cross-domain}

1. Add the site and the app as [sources](https://clickclacks.io/docs/guides/sources.md) in one project.
2. In [Identity](https://clickclacks.io/docs/guides/identity.md), turn on **Carry identity between these domains**.
3. Call identify in the app after sign-in (see [Events and identify](https://clickclacks.io/docs/events.md)).
4. After a day, check **Kept the same ID across a hop** is 80% or more. Then build the funnel from pricing page to sign-up.

## Count renewals and invoices, not only clicks {#backend}

1. Add a **Server** source in [Sources](https://clickclacks.io/docs/guides/sources.md) and create a key.
2. Send `Invoice paid` from your billing code with the same user ID your app identifies with. See [Server-side tracking](https://clickclacks.io/docs/api.md).
3. Build a funnel from `$pageview` on `/pricing` to `Invoice paid`, with a 30-day window.

## Is my tracking working? {#install-check}

1. Open [Realtime](https://clickclacks.io/docs/guides/realtime.md) and, in another tab, click around your site. Events should appear within seconds.
2. For a custom event, pick it in [Events](https://clickclacks.io/docs/guides/events.md), expand a row and read **Your properties**.
3. In [Sources](https://clickclacks.io/docs/guides/sources.md), each source should say **Receiving**.

## A weekly board for a client {#client-board}

1. Switch to the client’s project with **⌘J**.
2. Click **New board**, name it _Weekly report_, and start from **Acquisition**.
3. Add the client’s key funnel from **Saved reports**, and a **Note** for your commentary.
4. Set **Last 7 days**, turn on **Compare**, and click **Save as default**.
5. Invite the client to the project as a [Member](https://clickclacks.io/docs/guides/members.md), so they can open the board themselves.

More in [Boards](https://clickclacks.io/docs/guides/boards.md).

## Monday morning across every client {#monday}

1. Turn on the [Weekly digest](https://clickclacks.io/docs/guides/weekly-digest.md) in the agency alerts inbox, once.
2. On Monday, read the email for visitors changes, firing alerts and stopped sources.
3. Open the [agency home](https://clickclacks.io/docs/guides/agencies.md) and click **Needs attention**.
4. Hop between clients with ⌘J. Your date range and filters come along.

## Related {#related}

- [All product guides](https://clickclacks.io/docs/guides.md)
- [Filters, dates and comparisons](https://clickclacks.io/docs/guides/filters.md)
- [Boards](https://clickclacks.io/docs/guides/boards.md): Keep the answers on a board.
- [MCP server](https://clickclacks.io/docs/mcp.md): Ask these questions from an AI client.