> For the complete documentation index, see [llms.txt](https://docs.millimetric.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.millimetric.ai/recipes/recipes.md).

# Overview

End-to-end worked examples for the things people actually want to do.

Each page is a complete, copy-paste-ready walkthrough of a real-world flow: instrumenting it on the client, querying the resulting data, and the gotchas to watch for.

| Recipe                                                                | What it covers                                                                      |
| --------------------------------------------------------------------- | ----------------------------------------------------------------------------------- |
| [Track a signup funnel](/recipes/signup-funnel.md)                    | Page view → CTA click → form view → signup → activated. Drop-off math at each step. |
| [E-commerce events](/recipes/ecommerce.md)                            | Product views, cart, checkout, refunds. Revenue & AOV queries.                      |
| [Marketing attribution dashboards](/recipes/marketing-attribution.md) | The Facebook social-vs-paid split. First-touch vs last-touch. Channel ROI.          |
| [Server-side events from a backend](/recipes/server-side.md)          | When to emit from the server, how to thread `anonymous_id`, batching at scale.      |
| [Link anonymous → known users](/recipes/anonymous-to-known.md)        | Stitching pre-login activity to the post-login user. Multi-device.                  |
| [GDPR right-to-be-forgotten](/recipes/gdpr-delete.md)                 | The `/v1/forget` flow end-to-end, including audit-trail patterns.                   |
| [Funnel & retention analysis](/recipes/funnels.md)                    | SQL templates for n-step funnels, day-N retention cohorts, time-to-event.           |

If a flow you need isn't here, the [Quickstart](/quickstart.md) + [Events](/core-concepts/events.md) + [Properties](/core-concepts/properties.md) cover the building blocks.

## A consistent example app

The recipes share a fictional product to keep examples concrete: **Acme Notes** — a SaaS notes app with a free plan, a Pro plan ($49/month), and team workspaces. When you see `acme.com` or `plan: "pro"` in a snippet, that's why.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.millimetric.ai/recipes/recipes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.