> For the complete documentation index, see [llms.txt](https://docs.yoplanning.support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yoplanning.support/yoplanning-academie/yoplanning-parametrage/module-de-reservation/integration-du-module-de-reservation/doc-technique-agence-web/suivi-de-la-source-de-trafic-avec-les-parametres-utm.md).

# Suivi de la source de trafic avec les paramètres UTM

## Suivi de la source de trafic avec les paramètres UTM

Pour suivre efficacement les performances de vos campagnes marketing, Yoplanning prend en charge les **paramètres UTM** dans les URLs menant vers le module de réservation.

***

### 🔧 Comment ça fonctionne ?

Lorsque l’utilisateur arrive sur une URL contenant des UTM, comme :

```
https://reservation.yoplanning.pro/oxygene?utm_source=google&utm_medium=cpc&utm_campaign=promo_ski
```

Google Analytics attribue la session à la bonne source / medium / campagne.

***

### 📌 Conseils

* Ajoutez toujours les paramètres UTM dans vos liens de newsletters, publicités, sites partenaires, etc.
* Le module lit et transmet automatiquement ces paramètres au Data Layer.
* Le système est compatible avec GA4 et l’envoi des événements e-commerce associés.

***

### ✅ Exemple complet

Lien dans votre site :

```
https://reservation.yoplanning.pro/votreteam?utm_source=facebook&utm_medium=social&utm_campaign=ete2025
```

Dans GA4, les conversions seront attribuées à la source correcte.


---

# 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.yoplanning.support/yoplanning-academie/yoplanning-parametrage/module-de-reservation/integration-du-module-de-reservation/doc-technique-agence-web/suivi-de-la-source-de-trafic-avec-les-parametres-utm.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.