> For the complete documentation index, see [llms.txt](https://doc.commandersact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.commandersact.com/fr/developpeurs/tracking-and-integrations/tracking/events-reference/campaign-analytics-module-events.md).

# Événements de Campaign Tracking

## ad\_view

Cet événement est associé à l'affichage de votre annonce, peut être utilisé pour suivre le touch point "impressions" dans le module Campaign Analytics

## ad\_click

Cet événement est associé à un clic sur votre annonce, peut être utilisé pour suivre le touch point "clicks" dans le module Campaign Analytics

#### Paramètres <a href="#parameters_35" id="parameters_35"></a>

<table><thead><tr><th width="161">Nom</th><th width="100">Type</th><th width="85">Obligatoire</th><th width="153">Valeur d'exemple</th><th>Description</th></tr></thead><tbody><tr><td><code>ad_cost_id</code></td><td><code>string</code></td><td>Non</td><td>1254965</td><td>remplacez le <code>tclid</code> de MixCommander</td></tr><tr><td><code>user</code></td><td><a href="#user"><code>Object&#x3C;User></code></a></td><td>Oui</td><td><p><code>{</code><br><code>id: '12345',</code><br><code>email: 'toto@domain.fr',</code></p><p><code>consent_categories: [1,3]</code></p><p><code>}</code></p></td><td><p><code>consent_categories</code> est la liste des consentements de l'utilisateur. Elle est remplie automatiquement à partir des sources web si vous utilisez Commanders Act CMP.</p><p>Vous devriez également ajouter toutes les propriétés de l'utilisateur dans cet objet user, en particulier la clé de rapprochement (id, email).</p></td></tr><tr><td><code>ad_format</code></td><td><code>string</code></td><td>Non</td><td>image</td><td>Type/format de l'annonce</td></tr><tr><td><code>campaign</code></td><td><code>string</code></td><td>Non</td><td>my_campaign</td><td>nom de campagne</td></tr><tr><td><code>keyword</code></td><td><code>string</code></td><td>Non</td><td>t-shirt</td><td>mots-clés de la campagne</td></tr><tr><td><code>medium</code></td><td><code>string</code></td><td>Oui</td><td>seo</td><td>medium du touch point</td></tr><tr><td><code>source</code></td><td><code>string</code></td><td>Oui</td><td>my_source</td><td>source du touch point</td></tr></tbody></table>

**Exemple**

{% tabs %}
{% tab title="JavaScript" %}

```javascript
cact('trigger','ad_click', { /*ou ad_view*/
    "medium": "seo",
    "campaign": "my_campaign",
    "source": "my_source",
    "keyword": "t-shirt",
    "ad_format": "image"
}
  user: {
    id: '12356',
    email:'toto@domain.fr',
    consent_categories: [1,3]
  }
});
```

{% endtab %}
{% endtabs %}

## page\_view and purchase

Pour créer les touch points 'sites' et 'orders', vous pouvez utiliser les événements suivants :

* 'page\_view' pour créer un touch point 'sites'
* 'purchase' pour créer un touch point 'orders'


---

# 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://doc.commandersact.com/fr/developpeurs/tracking-and-integrations/tracking/events-reference/campaign-analytics-module-events.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.