> For the complete documentation index, see [llms.txt](https://docs.exads.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.exads.com/advertisers/campaigns/conversion-tracking.md).

# Conversion Tracking

Conversion tracking shows which ad clicks lead to valuable customer actions. Track events such as landing page visits, sign-ups, purchases, and subscriptions.

Create a **Goal** for each action you want to measure. Goals connect conversions to your campaigns. They also provide conversion data for reporting, ROI calculations, and campaign optimization.

Choose the tracking method that fits your setup:

* **Conversion Tracking API — S2S**: Send conversions from your server. This is the recommended method.
* **Pixel Tracking**: Add a tracking script to the page where the conversion occurs.
* **Google Tag Manager**: Deploy and manage the conversion pixel through your container.
* **Voluum**: Pass conversion data through Voluum using a postback.

Start by [creating a conversion tracking goal](/advertisers/campaigns/conversion-tracking/setting-up-conversion-tracking.md). Then configure your chosen integration:

* [Set up Google Tag Manager](/advertisers/campaigns/conversion-tracking/conversion-tracking-gtm.md).
* [Track conversions with Voluum](/advertisers/campaigns/conversion-tracking/conversion-tracking-voluum.md).


---

# 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.exads.com/advertisers/campaigns/conversion-tracking.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.