> 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/partner/what-would-you-like-to-learn-about/platform-features/tracking/tracking-links/link-parameters/implement-tracking-for-rewards-programs.md).

# Implement Tracking for Rewards Programs

In some regions, privacy laws forbid the use of tracking cookies unless the user has provided consent. This means that a user’s interactions with your content cannot be tracked and attributed to you unless the user consents to being tracked. However, there are some circumstances in which the user is considered to have implicitly given consent to tracking.

Cookies that do not require consent are deemed "strictly necessary for the delivery of a service requested by the user". Examples include a shopping cart that keeps track of user purchases on an online shopping portal, and cookies that track purchases for a rewards program.

## Implement tracking for rewards programs

{% hint style="success" %}
This feature is only accessible to specific impact.com editions or add-ons. [Contact us](https://app.impact.com/support/portal.ihtml?createTicket=true) to upgrade your account and get access!
{% endhint %}

This article explains how, with a qualifying promotional model, you can implement privacy-compliant tracking, using the `im_rewards` tracking parameter. By using this parameter, you can ensure that your users' interactions are correctly tracked and attributed to your loyalty and rewards programs. This, in turn, ensures that:

* Users consistently receive the rewards they expect.
* You will be credited and paid for the conversions you drive.
* Brands gain a more accurate picture of the value you provide.

{% hint style="success" %}
**Note:** Changes to the `im_rewards` parameter may not immediately affect all your links due to adoption requirements by both you and the relevant brands. Implement now to capture increased attribution once more of your partnered brands adopt the functionality.
{% endhint %}

## Key considerations

* The `im_rewards` parameter indicates a cashback, loyalty, or rewards program that does not require explicit consent from the user.
* This parameter should not be used universally across all tracking links, only where the user participates in a cashback, loyalty, or rewards program.
* You should remain transparent about your tracking practices and ensure that they comply with [GDPR](https://en.wikipedia.org/wiki/General_Data_Protection_Regulation) and other relevant privacy regulations. This includes being clear about the use of tracking mechanisms for rewards and loyalty programs.

## Implement the `im_rewards` parameter

{% hint style="warning" %}
**Important:** This parameter is currently only available to eligible cashback, loyalty, or rewards partners.
{% endhint %}

* Update the relevant rewards tracking links with the `im_rewards` query string parameter. An example tracking link with `im_rewards=1` looks like this:

  `https://examplebrand.sjv.io/c/123/345?im_rewards=1&subid1=1234567`


---

# 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/partner/what-would-you-like-to-learn-about/platform-features/tracking/tracking-links/link-parameters/implement-tracking-for-rewards-programs.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.