impact.com
How to configure impact.com at different risk levels and map it in the Consenter Manager.
This work is licensed under CC BY-SA 4.0
Typical processing purposes: Support marketing analytics, Receive marketing offers
Overview
This guide explains how to implement different privacy configurations for impact.com's Universal Tracking Tag (UTT) on a brand website and how to reflect them in the Consenter Manager.
- Configure the third-party service.
- Map the selected configuration in the Consenter Manager.
- Update your privacy policy to reflect the actual implementation.
The configurations are comparative examples, not guarantees of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.
At a glance
Scope. impact.com UTT and Consent Mode for brands.
What the service does in this scope. The UTT uses first-party cookie tracking and runs on every page. The UTT sets first-party cookies on your domain storing a UUID and timestamp to identify the customer later. Consent Mode (beta) is enabled via a support ticket; the default consent status should be declared via impactDataLayer before the UTT loads. Partners can append im_rewards=1 to loyalty or rewards links. UTT version 3 can read consent directly from a standard-framework CMP; the Publisher Tag withholds identifyUser until consent and hides values such as customerEmailHash.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Medium risk | Consent Mode on; default denied via impactDataLayer; Consenter updates consent; no rewards exemption. |
| Configuration B — Higher risk | As A, plus rewards/loyalty links (im_rewards=1) tracked without consent. |
| Configuration C — Higher risk | UTT without Consent Mode; identify with customer IDs/email hash. |
⚠ Recommendation. Tracking rewards traffic without consent (B) relies on a regulator position on cashback/loyalty cookies. Have your DPO assess whether it applies to your programme and jurisdiction.
Step 1 — Configure impact.com
| # | Configuration area | Where to configure it | Configuration A — Medium risk | Configuration B — Higher risk | Configuration C — Higher risk |
|---|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Support marketing analytics | Support marketing analytics; Receive marketing offers | Support marketing analytics; Receive marketing offers |
| 2 | Consent Mode | Support ticket; impactDataLayer | On; default denied | On; default denied | Off |
| 3 | Rewards exemption | im_rewards=1 on partner links | Not used | Used | — |
| 4 | Customer identification | ire('identify') | Only after consent, no email hash | Only after consent | Customer ID and email hash |
Step 2 — Map the configuration in the Consenter Manager
Processing location. impact.com is a US enterprise; list the United States.
Legal role. Confirm the role in your impact.com agreement; the table uses Processor for the brand-side tag.
| Consenter Manager field | Configuration A — Medium risk | Configuration B — Higher risk | Configuration C — Higher risk |
|---|---|---|---|
| Processing purposes | Support marketing analytics | Support marketing analytics, Receive marketing offers | Support marketing analytics, Receive marketing offers |
| Tracking method | First party tracking (cross-session) | First party tracking (cross-session) | Third party tracking (cross-session, cross-website, cross-device) |
| Identifier | Device identifiers | Device identifiers | Device identifiers, Authentication-derived identifiers |
| Data categories | Device identifiers, Browsing and interaction data, e-commerce Activity, Privacy choices | Device identifiers, Browsing and interaction data, e-commerce Activity, Privacy choices | Device identifiers, Authentication-derived identifiers, Browsing and interaction data, e-commerce Activity |
| Legal role of data recipient | Processor | Processor | Processor |
| Personalisation model | No personalisation | No personalisation | Profile based |
| Maximum storage duration | Per programme referral window | Per programme referral window | Per programme referral window |
| Processing location | United States | United States | United States |
How is this guide?
Shape Consenter Together
Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.
Need Help?
Last updated on