# Walkthroughs

> End-to-end ClickClacks walkthroughs that follow one goal from zero to an answered question: browser events, the Node and PHP SDKs, identity, the HTTP API, activation funnels, retention, acquisition, tracking plans and weekly reporting.

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

Each walkthrough follows one realistic goal from nothing to an answered question, with numbered steps, what you should see at each checkpoint, and the mistakes people usually make. Pick the track that fits your job, or read both.

## The running example {#example}

Every walkthrough uses the same product, so the two tracks connect: **Acme CRM**, a small B2B CRM for sales teams.

- A marketing site on `acme.com` (and `www.acme.com`), with a pricing page and a blog.
- The product on `app.acme.com`, where people sign up, import contacts and create deals.
- A Node.js API behind the app, an older Laravel billing service that handles payment webhooks, and a small deal-pipeline service written in a language with no ClickClacks SDK.
- One ClickClacks project called _Acme_, with a source for each place events come from: _Marketing site_ and _Web app_ for the browser, and a server source for each backend.

The developers send events such as `Signed up`, `Contacts imported`, `Deal created`, `Plan upgraded` and `Invoice paid`. The analysts then use them to answer: where do new accounts get stuck, do they come back, and which campaigns bring the customers who stay? Swap in your own names as you go.

## Developer track {#developer}

Get the right events into ClickClacks, from the browser and from your servers, on the right people.

1. [Track your first custom events Install the script tag, name two events well, send them with properties, and see them in Realtime, Events and an insight.](https://clickclacks.io/docs/walkthroughs/first-events.md)
2. [Server-side tracking with Node A server source and key, @clickclacks/node in an Express API and a serverless function, flushing, and checking the result.](https://clickclacks.io/docs/walkthroughs/node.md)
3. [Server-side tracking with Laravel clickclacks/clickclacks-php in a Laravel app: the facade, a webhook, local development, queued sending and tests.](https://clickclacks.io/docs/walkthroughs/laravel.md)
4. [One person across browser and backend Anonymous visitor, identify at sign-in, server events with the same ID, sign-out, and the mistakes that split people in two.](https://clickclacks.io/docs/walkthroughs/one-person.md)
5. [Any language over HTTP POST /api/v1/batch with curl: a dry run, a real send, reading errors, strict mode and safe retries.](https://clickclacks.io/docs/walkthroughs/http.md)

## Analyst track {#analyst}

Turn the events into answers, keep them on a board, and hear about it when something moves.

1. [Find where signups drop off Build an activation funnel, find the biggest drop, see who dropped, break it down, save it and put it on a board.](https://clickclacks.io/docs/walkthroughs/activation-funnel.md)
2. [Are users coming back? Set a retention definition, read the grid and the curve, and compare cohorts by campaign and by segment.](https://clickclacks.io/docs/walkthroughs/retention.md)
3. [Where do our best users come from? Referrers, UTM tags and your own channels, compared by how well the people they bring activate and stay.](https://clickclacks.io/docs/walkthroughs/acquisition.md)
4. [Design a tracking plan What to track for a SaaS product and for a marketing site, how to name it, Lexicon, and a hand-off template.](https://clickclacks.io/docs/walkthroughs/tracking-plan.md)
5. [Weekly reporting A weekly board, alerts on the numbers that matter, and a Monday routine that takes ten minutes.](https://clickclacks.io/docs/walkthroughs/weekly-reporting.md)

## Before you start {#before}

- You need a ClickClacks project. The [quickstart](https://clickclacks.io/docs/quickstart.md) creates one and a website source in about five minutes.
- The developer walkthroughs assume you can deploy to a hostname you list on the source. The tracker doesn’t run on `localhost`.
- The analyst walkthroughs need a few days of real events. Reports such as Retention need at least two completed weeks before they show anything.
- The walkthroughs link to the reference and the product guides for every detail, rather than repeating them.