Set up your bannerConfigure Your ToolsAffiliate and Price Comparison

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.

  1. Configure the third-party service.
  2. Map the selected configuration in the Consenter Manager.
  3. 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.

ConfigurationSummary
Configuration A — Medium riskConsent Mode on; default denied via impactDataLayer; Consenter updates consent; no rewards exemption.
Configuration B — Higher riskAs A, plus rewards/loyalty links (im_rewards=1) tracked without consent.
Configuration C — Higher riskUTT 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 areaWhere to configure itConfiguration A — Medium riskConfiguration B — Higher riskConfiguration C — Higher risk
1Processing purposesOperator decisionSupport marketing analyticsSupport marketing analytics; Receive marketing offersSupport marketing analytics; Receive marketing offers
2Consent ModeSupport ticket; impactDataLayerOn; default deniedOn; default deniedOff
3Rewards exemptionim_rewards=1 on partner linksNot usedUsed—
4Customer identificationire('identify')Only after consent, no email hashOnly after consentCustomer 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 fieldConfiguration A — Medium riskConfiguration B — Higher riskConfiguration C — Higher risk
Processing purposesSupport marketing analyticsSupport marketing analytics, Receive marketing offersSupport marketing analytics, Receive marketing offers
Tracking methodFirst party tracking (cross-session)First party tracking (cross-session)Third party tracking (cross-session, cross-website, cross-device)
IdentifierDevice identifiersDevice identifiersDevice identifiers, Authentication-derived identifiers
Data categoriesDevice identifiers, Browsing and interaction data, e-commerce Activity, Privacy choicesDevice identifiers, Browsing and interaction data, e-commerce Activity, Privacy choicesDevice identifiers, Authentication-derived identifiers, Browsing and interaction data, e-commerce Activity
Legal role of data recipientProcessorProcessorProcessor
Personalisation modelNo personalisationNo personalisationProfile based
Maximum storage durationPer programme referral windowPer programme referral windowPer programme referral window
Processing locationUnited StatesUnited StatesUnited 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

On this page