1. Option C: Consent or Pay Model (UK only)
This section covers the specific requirements that Utiq business customers’ pay or consent models must meet before Utiq consent can be integrated within such models.
Markets in scope
This section is applicable to the UK market only.
Pre-requisites
To use the “Consent or Pay Model”, Advertisers and Publishers must meet Utiq’s minimum standards listed below. If you cannot meet these requirements, you must use Utiq’s “Separate consent pop-up model” (see Option 1B.) or “Utiq Integrated Model” (see Option 1A.).
For any questions, please get in touch with our Customer Success team at csm@utiq.com.
These requirements focus only on Consent and Transparency aspects of the integration. Additional requirements will also apply which are covered separately (e.g. contractual).
Utiq Privacy Requirements (UPRs) for “Consent or Pay Model”
Core Requirements | Description | Specification/Checklist | Example |
---|---|---|---|
Users must be provided with the possibility of accepting cookies and tracking technologies and to just as easily refuse them. You must make it as easy for people to refuse consent as it is to accept consent. | “Accept” and “Pay” options presented on first layer. | The “Accept” and "Pay" options should be:
| ![]() |
Paying journey is functional and easy. |
| ||
Valid consent must be obtained for Utiq technology activation | It should be sufficiently clear that the use of Utiq technology is available on the website. |
| ![]() |
Correct configuration of accept and reject/pay functions | The CMP must be configured to ensure that Utiq calls are only triggered if user consents to the activation of Utiq technology. |
| ![]() |
Implement 1st layer Utiq opt-out function | A function to open the second layer of the CMP where the end users can granularly reject the activation of the Utiq technology (using the Utiq custom purpose) will be made available to end users in the “Accept” part of the CMP (within the Utiq consent text). |
| ![]() |
Main CMP title must be adequate | As per core requirement. |
| |
Configurable elements within the Utiq Consent text must be populated with the Data Controller information | The Utiq consent text (1st layer) contains the following configurable elements:
| Populate dedicated configurable elements with your details:
| ![]() |
Implement hyperlinks in clickable elements within Utiq consent text (1st layer and 2nd layer) | The Utiq consent text contains clickable elements:
| Implement hyperlinks that open in a new page for clickable elements within Utiq consent text:
| ![]() |
Implementation of telecom operators hyperlink | As per core requirement. |
| ![]() |
Implementation of a section within “Manage Utiq” page listing the cross domain websites in scope (i.e., all websites that would make use of the same martechpass value) | As per core requirement. |
| |
You must provide clear information about each of the options in your “consent or pay” model using concise, clear and plain language to enable people to make an informed decision. | Consent text must clearly explain what each options means, the consequences and the impact it will have on data processing. |
| |
You must provide clear information about how users can exercise their data protection rights. | Consent text must clearly explain how users can exercise their data protection rights. |
| |
Utiq technology purpose included in 2nd layer of CMP (as Utiq custom purpose) | It must be possible for users to view the purposes in a granular way. Specifically, users should be able to make granular choices for Utiq via distinct tick boxes. |
| ![]() |
The website’s main CMP must be easy to locate and resurface to facilitate withdrawal of consent at any time | You must give people an easy way to withdraw their consent and you must make this easily accessible on your service at all times. |
| ![]() |
The website should make its “Privacy policy/notice/statement” easily accessible at the bottom of all pages | As per core requirement. |
| ![]() |
Consent validity timeframe (the time after which consent should be re-requested) | The consent validity timeframe (the time after which consent should be re-requested) for Utiq consents is aligned with your CMP consent validity timeframe and up to a possible 13 month maximum period. martechpass TTL is 90 days. | Main CMP’s consent validity timeframe is no longer than 13 months. | |
Utiq shall not be enabled for users that have already consented unless consent is refreshed to cover Utiq consent | As per core requirement. |
| |
Evidence of consent | It should be technically possible for the Advertiser/Publisher to provide evidence of Utiq consents captured. It should be technically feasible for Utiq to monitor that each consent has effectively been provided. |
| |
Utiq consent withdrawal mechanism are in place | As per core requirement. |
| ![]() |
[1] Also known as “dark patterns”, are considered as interfaces and user journeys implemented on platforms that attempt to influence users into making unintended, unwilling and potentially harmful decisions, often towards a decision that is against the users’ best interests and in favour of the platforms interests, regarding the processing of their personal data (EDPB Guidelines 03/2022)
[2] ICO-CMA joint paper on Harmful Design in Digital Markets | DRCF
User testing
If you have any learnings or insights from user testings that could be beneficial also to Utiq consent and experience, we would greatly appreciate if you could share them with us.
Other Utiq Privacy Requirements
Please make sure you also comply with the other 2 requirements:
“2. Setup the dedicated “Manage Utiq” page linked via a footer hyperlink” → as per standard Utiq Privacy Requirements (UPRs) available here.
“3. Include reference to Utiq technology in the domain’s privacy statement” → as per standard Utiq Privacy Requirements (UPRs) available here.
Configuration in CMP console
Utiq’s consent text for the “Consent or Pay model”
The Utiq consent text has been carefully defined seeking to strike a balance between providing complete information on the processing and keeping the text brief and understandable for users as part of a layered approach to transparency. Specifically, the text addresses the purpose and scope of the processing, the nature of the personal data processed, retention periods, and the identity of controllers.
Utiq consent text to date (this may be subject to change):
Layer | Text |
---|---|
1st layer |
If you accept and use a supported internet connection, we, [DATA CONTROLLER], will use marketing identifiers provided by Utiq for advertising or analytics activities. To create the identifiers, Utiq works with your telecom operator, which will use your IP address against internal data (e.g. mobile number), without disclosing it. We use the identifiers to link the browsing activity across our property(ies) where Utiq consent is given, including of others using the same connection. You confirm that you are the connection account holder’ or have permission to activate Utiq. For more, visit Utiq's privacy statement. |
2nd layer (Utiq custom purpose) | Use of Utiq technology powered by your telecom operator If you consent, you agree to the following processing:
The Utiq technology is designed with privacy in mind: it uses minimal personal data, secure, temporary identifiers, and limits data sharing. Utiq also offers a privacy portal (“consenthub”) to exercise your privacy rights. For more details, visit Utiq’s privacy statement. |
Configurable elements and hyperlinks:
[DATA CONTROLLER] → Data Controller’s name and legal form → the legal entity that owns the website as mentioned on the website’s Privacy Policy page
[BUTTON WORDING FOR PAY OPTION] → label/wordings used for the “Pay” option button
consenthub → https://consenthub.utiq.com/
Utiq’s privacy statement → https://consenthub.utiq.com/pages/privacy-statement
supported internet connection → https://consenthub.utiq.com/pages/privacy-statement#telecom-operators
for advertising or analytics activities → this function will open the Advertiser/Publisher’s own privacy statement.
across our property(ies) → direct the user to the relevant section within the “Manage Utiq” page where there is the list of all such websites/apps in scope for the cross-domain martechpass sharing feature (i.e., all websites that would make use of the same martechpass value) (see “2. Setup the dedicated “Manage Utiq” page linked via a footer hyperlink“).
You can reject now → a function to open the second layer of the CMP.
Utiq logo → https://utiqcontent.com/website/logos/utiq-com.svg
1st layer

Utiq purpose displayed in the 2nd layer of the CMP
Utiq consent must be collected both for Utiq custom purpose and for Utiq custom vendor.

Utiq custom vendor
Utiq consent must be collected both for Utiq custom purpose and for Utiq custom vendor.
Field | Value |
---|---|
Vendor name | Utiq |
Privacy Policy | |
Purpose based on consent (2nd layer Utiq consent text) | Use of Utiq technology powered by your telecom operator If you consent, you agree to the following processing:
The Utiq technology is designed with privacy in mind: it uses minimal personal data, secure, temporary identifiers, and limits data sharing. Utiq also offers a privacy portal (“consenthub”) to exercise your privacy rights. For more details, visit Utiq’s privacy statement. |
Note:
If the website’s CMP is not listing any other vendors (and only listing the purposes), the configuration of “Utiq as vendor” can we omitted.
If the website’s CMP is listing other vendors, Utiq must be configured also as a custom vendor
Set up the functionalities in the Utiq Integrated Model text
Configurable elements
The Utiq consent text (1st layer) contains the following configurable elements:
[DATA CONTROLLER] → Data Controller’s name and legal form (i.e. the legal entity that owns the website as mentioned on the website’s Privacy Policy page)
[BUTTON WORDING FOR PAY OPTION] → label/wordings used for the “Pay” option button

Clickable elements
The Utiq consent text (1st layer and Utiq purpose displayed in the 2nd layer of the CMP) contains clickable elements:

You will need to implement hyperlinks that open in a new page for clickable elements within Utiq consent text:
consenthub → https://consenthub.utiq.com/
Utiq’s privacy statement → https://consenthub.utiq.com/pages/privacy-statement
supported internet connection → https://consenthub.utiq.com/pages/privacy-statement#telecom-operators
for advertising or analytics activities → this function will open the Advertiser/Publisher’s own privacy statement.
across our property(ies) → direct the user to the relevant section within the “Manage Utiq” page where there is the list of all such websites/apps in scope for the cross-domain martechpass sharing feature (i.e., all websites that would make use of the same martechpass value) (see “2. Setup the dedicated “Manage Utiq” page linked via a footer hyperlink“).
You can reject now → a function to open the second layer of the CMP.

Consent synchronization with CMP-consenthub-“Manage Utiq” withdraw function
There are 3 ways for users to withdraw Utiq consents:
via the CMP: by re-opening the CMP and changing the Utiq preferences, the users can withdraw Utiq consent.
via the consent revocation dedicated functionality in the “Manage Utiq” page: users can revoke their Utiq consent directly through the site. The revocation will only apply to that site in this case.
via consenthub
The above should be implemented in accordance with Utiq technical requirements to ensure correct synchronisation with consenthub.
Utiq SDK should be loaded on all site pages, to be able to ensure consent synchronisation of the user.
How to integrate it
You can find the documentation to integrate it at the Tag Integrations section.
For any technical query on the implementation, you can reach out to our Customer Success team at csm@utiq.com.