> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/de/what-would-you-like-to-learn-about/platform-features/tracking/set-up-tracking/accept-clicks-on-landing-pages.md).

# Partner-Tracking für Comparison Shopping Service (CSS) aktivieren

Mit dem Klick-Tracking über Landingpage-URLs können Ihre Partner impact.com-URL-Parameter an Ihre Landingpage-URL anhängen. So lässt sich das Klick-Tracking nutzen, ohne zuerst über impact.com weiterzuleiten. Das ist besonders nützlich, wenn Partnerplatzierungen herkömmliche Weiterleitungen über Tracking-Links einschränken oder umgehen – etwa bei Preisvergleichspartnern, die Produkte in Suchergebnissen bewerben und Interessenten direkt zu Ihrer Landingpage leiten müssen.

## Tracking-Einstellungen aktivieren

So verwenden Sie das Klick-Tracking über Landingpage-URLs:

1. Wählen Sie in der oberen Navigationsleiste  ![](https://1698965099-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2F210dEQa93qyQgoJDkieL%2FUser%20profile.svg?alt=media\&token=f84c5b17-fae4-4a30-990a-9de5e57a150b) **\[Benutzerprofil] → Einstellungen**.
2. Wählen Sie rechts unter *Tracking*die Option [**Allgemein**](https://app.impact.com/secure/advertiser/fr/general-tracking-settings.ihtml)**.**
3. Aktivieren Sie unter *Attribution* die Option **impact.com-Klickparameter auf Landingpages akzeptieren**.
4. Wähle **Speichern**.

## Voraussetzungen

* Ihre Landingpage muss über eine kompatible Landingpage-Integration verfügen, z. B. über [UTT-Tracking](https://help.impact.com/brand/de/what-would-you-like-to-learn-about/platform-features/tracking/javascript-tag-tracking/tracking-with-universal-tracking-tag-utt.md), [PageLoad API](https://integrations.impact.com/brand-api-reference/reference/page-load) oder eine kompatible E-Commerce-Integration.
* Weitere Informationen finden Sie unter [Best Practices für das Tracking](https://help.impact.com/brand/de/what-would-you-like-to-learn-about/platform-features/tracking/tracking-best-practices.md#landing-page-tracking) .

## Partner einrichten

Informieren Sie Ihre Partner, wenn Landingpages um zusätzliche Analytics-Parameter ergänzt werden müssen. Weitere Informationen zur Einrichtung von Partnern finden Sie unter [Google Ads & impact.com – CSS-Partner-Tracking](https://help.impact.com/partner/de/was-mochten-sie-lernen/platform-features/tracking/google-ads-and-impact.com-css-partner-tracking.md).

{% hint style="info" %}
**Hinweis**: Wenn das bestehende standardmäßige Direct-Link-Tracking aktiv ist, hat es weiterhin Vorrang vor dem Klick-Tracking über Landingpage-URLs.
{% endhint %}


---

# 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://help.impact.com/brand/de/what-would-you-like-to-learn-about/platform-features/tracking/set-up-tracking/accept-clicks-on-landing-pages.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.
