> For the complete documentation index, see [llms.txt](https://docs.saas.haut.ai/haut.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.saas.haut.ai/haut.ai/guides/lead-generation-for-clinics/measure-and-optimize.md).

# Track App Performance with Google Analytics

Track how your clinic's lead-generation funnel performs with Google Analytics and UTM campaigns, and use returning-visit results to show treatment progress.

Once leads are flowing, this step shows you where they come from and where they drop off, so you can spend effort on what works. Your [Consumer App for Clinics: From Setup to Follow-Up](/haut.ai/guides/lead-generation-for-clinics.md) reports its activity to Google Analytics, and the UTM labels you set when sharing the app let you compare channels.

***

## Connect Google Analytics

Add your GA4 measurement ID to the app to track visitor behavior end to end. Follow [Connect Google Analytics to Your Consumer App](/haut.ai/haut.ai-features/consumer-apps/connect-google-analytics-to-your-consumer-app.md).

The app reports events across the whole journey — session start, analysis completed, recommendations shown, and more. The full list is in [Google Analytics Events Reference](/haut.ai/haut.ai-features/consumer-apps/connect-google-analytics-to-your-consumer-app/google-analytics-events-reference.md).

***

## Watch the funnel

With events flowing into GA4, follow how many visitors move from one stage to the next:

* **Started** — opened the app.
* **Analyzed** — finished the skin analysis.
* **Captured** — completed the survey (your lead).
* **Converted** — booked, tracked in your CRM or booking system.

The biggest drop between two stages is where to focus first. A steep drop at **Captured**, for example, usually means the survey is too long or asks for too much too soon.

***

## Compare your channels

In the previous step you gave each channel its own `utm_campaign` value (for example, `reception_qr` or `instagram_bio`). Use those campaign labels in GA4 to see which channels bring the most leads, and which bring the ones that book. If you embed the app, make sure UTM parameters pass through from your page — see [Forward Parent Page UTM Parameters to the Consumer App](/haut.ai/haut.ai-features/consumer-apps/connect-google-analytics-to-your-consumer-app/forward-parent-page-utm-parameters.md).

***

## Show progress to bring clients back

For a clinic, the follow-up visit is where treatment results show. Turn on the **returning user experience** so a client who returns within 90 days sees how their skin parameters have changed since their first analysis. Seeing measured progress is a strong reason to continue treatment. See [Configure Advanced Settings](/haut.ai/haut.ai-features/consumer-apps/configure-advanced-settings.md#returning-user-experience).

***

## You're done

Your Consumer App now runs as a full lead-generation funnel: it attracts prospects, analyzes their skin, captures them as leads, follows up automatically, and reports how each channel performs. Return to the overview at any time: [Consumer App for Clinics: From Setup to Follow-Up](/haut.ai/guides/lead-generation-for-clinics.md).

***

{% hint style="warning" %}
Not a Haut.AI client yet?
{% endhint %}

<a href="https://haut.ai/book-a-demo?utm_source=referral&#x26;utm_medium=saas_docs&#x26;utm_campaign=Docs_SaaS_HautAI" class="button primary" data-icon="user-vneck">Book a demo</a> <a href="https://haut.ai/product/ai-skin-analysis?utm_source=referral&#x26;utm_medium=saas_docs&#x26;utm_campaign=Docs_SaaS_HautAI" class="button secondary" data-icon="external-link">Platform overview on haut.ai</a>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.saas.haut.ai/haut.ai/guides/lead-generation-for-clinics/measure-and-optimize.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.