` tag are un-styled by default. To ensure they match your website's design, apply custom styles using the `
` ID to target only these elements. Specify the styles as follows:
CSS
/* Example Manage Utiq CSS Styles */
/* Set the font family for the elements */
/* These can also be set one by one if needed */
#utiq-manage-page h2,
#utiq-manage-page p,
#utiq-manage-page a,
#utiq-manage-page li {
font-family: "Poppins", "Century Gothic", "Arial", sans-serif;
}
#utiq-manage-page h2 {
font-size: 1.5em;
}
#utiq-manage-page a {
color: #db214f;
}
#utiq-manage-page a:hover {
color: #7a0320;
}
#### Putting it all together
The following is a minimal example. Depending on your setup, you may need to add custom configuration for the `utiqLoader` script.
HTML
Manage Utiq
Manage your Utiq technology consents
---
language: "en"
---
# MarTech Integration
This section contains integration guides with other MarTech platforms, like Web Analytics and CDPs.
* [Web Analytics Integration](https://docs.utiq.com/docs/web-analytics-integration.md)
* [CDP Integration](https://docs.utiq.com/docs/cdp-integration.md)
* [CDP Data Export](https://docs.utiq.com/docs/cdp-data-export.md)
Utiq's MarTech Integration guides are designed to help you connect the **Utiq martechpass** (mtid) with third-party marketing technologies, including **Web Analytics platforms** and **Customer Data Platforms (CDPs)** , and how to configure **CDPs to export audiences**. These integrations enable better identity resolution, improve measurement accuracy, and support effective first-party data activation.
Inside this section, you'll find:
* [Web Analytics Integration](https://docs.utiq.com/docs/web-analytics-integration.md): How to pass `martechpass` as a user identifier to analytics tools like Google Analytics, Marfeel and Piano.
* [CDP Integration](https://docs.utiq.com/docs/cdp-integration.md): How to ingest `martechpass` as a declared ID into CDPs such as Permutive, Adobe CDP and ADEX.
* [CDP Data Export](https://docs.utiq.com/docs/cdp-data-export): How to configure your CDP to export audiences (containing martechpasses and audience metadata) into a Utiq-issued S3 bucket for activation.
Each guide starts with the rationale and value of integrating the `martechpass`, followed by step-by-step instructions for each supported vendor, complete with platform-specific code samples, documentation references, and testing guidelines.
---
language: "en"
---
# Mobile App Integration
There are numerous ways to integrate Utiq into your Mobile App, based on how a Mobile App is developed, we choose the best way for integration.
* Native [Android SDK](https://docs.utiq.com/docs/android-sdk.md), if your Android Application is built with Kotlin or Java.
* Native [iOS SDK](https://docs.utiq.com/docs/ios-sdk.md), if your iOS Application is built with Swift.
## Consent Experience on Mobile App
To enable the Utiq technology in your app, we require all the items listed in the [Consent Experience on Mobile App](https://docs.utiq.com/docs/consent-experience-on-mobile-app.md) page to be implemented ahead of go-live.
Note, regarding Apple ATT, the responsibility of if / what identifiers are used is with the wrapping application. The Utiq SDK will not return adtechpass when the user opted in for ATT.
## Mobile App Checklist
This is a checklist to show you the onboarding process for a native app.
Note that examples of Android have been used within links, as demonstration. Please relate to the similar functions on iOS operating system.
1. Implement [++Utiq Consent Experience++](https://docs.utiq.com/docs/consent-experience-on-mobile-app#ConsentExperienceonMobileApp-1.ImplementoneofthetwooptionsforUtiqConsentExperience) on your CMP
2. Create a native [Manage Utiq](https://docs.utiq.com/docs/consent-experience-on-mobile-app#ConsentExperienceonMobileApp-2.Setupthededicated%E2%80%9CManageUtiq%E2%80%9Dpagelinkedviaafooterhyperlink) page and add menu link leading to the page
3. In Manage Utiq page, use [++Utiq.rejectConsent()++](https://docs.utiq.com/docs/android-sdk#AndroidSDK-Rejectconsent) on one-click-revoke feature
4. Include Utiq text in [++Privacy Policy++](https://docs.utiq.com/docs/consent-experience-on-mobile-app#ConsentExperienceonMobileApp-3.IncludereferencetoUtiqtechnologyinthedomain%E2%80%99sprivacystatement) page
5. [++Install++](https://docs.utiq.com/docs/android-sdk#AndroidSDK-Installation) Utiq SDK within your app, with the API **token** provided by Utiq
6. If CMP consent exists for Utiq, [Get Utiq IDs \& Consent Sync](https://docs.utiq.com/docs/android-sdk#AndroidSDK-FetchUtiqdata), using `STUB_TOKEN`
7. If CMP consent does not exist for Utiq, or revoked later, '[++Reject++](https://docs.utiq.com/docs/android-sdk#AndroidSDK-Rejectconsent)' Utiq consent
8. [++Test++](https://docs.utiq.com/docs/consent-experience-on-mobile-app#ConsentExperienceonMobileApp-Testing) the integration with [++UtiqOptions().enableLogging()++](https://docs.utiq.com/docs/android-sdk#AndroidSDK-Initializingwithcustomoptions) and monitor for [++errors++](https://docs.utiq.com/docs/android-sdk#AndroidSDK-Errorhandling)
9. On production build **remove** `STUB_TOKEN` and **remove** `enableLogging()`
10. Make sure you always use the **latest Utiq SDK** following our **release notes**
**Notes**:
* We need you to provide us with a desired **app friendly name** , as it will appear on
* After we configure your app in our platform, we will provide an **SDK Token** which is needed for [initializing](https://docs.utiq.com/docs/android-sdk#AndroidSDK-InitializingtheSDK) the SDK
* For testing, we will provide you with a **Stub Token** to use when [fetching Utiq data](https://docs.utiq.com/docs/android-sdk#AndroidSDK-FetchUtiqdata), to mimic eligible Telco connection
Please review the detailed [Mobile SDK Integration Guide](https://docs.utiq.com/docs/mobile-sdk-integration-guide.md).
---
language: "en"
---
# Mobile SDK Integration Guide
## Overview
This document describes how app developers should synchronize their Consent Management Platform (CMP) with the Utiq Mobile SDK consent state.
It is intended for developers integrating Utiq alongside a CMP such as Didomi, OneTrust, or another consent solution that manages vendor and purpose choices.
## Flows to be implemented
* if CMP consent exists for Utiq, call `fetchIdConnectData(...)` to get Utiq IDs
* if CMP consent does not exist for Utiq, whether never given or revoked later, call `rejectConsent(...)` and do not call `fetchIdConnectData(...)`
* if `fetchIdConnectData(...)` returns `UserOptedOutFromUtiqException`, switch off Utiq in the CMP
* if consent is revoked via the Manage Utiq page/screen, switch off Utiq in the CMP and call `rejectConsent(...)`
## What this means in practice
The CMP is the source of truth for Utiq consent in the app.
The app must keep the Utiq SDK aligned with the CMP:
* CMP says Utiq is enabled: use `fetchIdConnectData(...)`
* CMP says Utiq is disabled: call `rejectConsent(...)`
* SDK says the user opted out in Utiq consenthub: update the CMP so Utiq is disabled there too
* Manage Utiq page/screen is used to revoke Utiq: disable Utiq vendor/purpose in the CMP and call `rejectConsent(...)`
## Recommended app behavior
### When CMP consent exists for Utiq
The app should:
* call `fetchIdConnectData(...)` when Utiq IDs are needed
* use the returned values from `dataCallback(...)`
### When CMP consent does not exist for Utiq
This includes:
* the user rejected Utiq in the CMP
* the user revoked previously granted consent in the CMP
The app should:
* call `rejectConsent(...)`
* clear any app state that depends on previously fetched Utiq IDs
* do not call `fetchIdConnectData(...)`
### When `fetchIdConnectData(...)` reports Utiq opt-out
If `errorCallback(...)` receives `UserOptedOutFromUtiqException`, the app should:
* switch off Utiq in the CMP (reject Utiq purpose and vendor)
* clear any app state that depends on previously fetched Utiq IDs
This is the main path for synchronizing a consent change that happened outside the app, for example through consenthub.
## Minimal examples
++**Disclaimer**++: This integration examples below are directional, and come with owner of the app responsibility - so test thoroughly before going to production.
### Android
Kotlin
// Utiq consent exists in the CMP
Utiq.fetchIdConnectData(
stubToken = stubToken, // <-- only for testing, DO NOT SET FOR PRODUCTION
dataCallback = { ids ->
renderIds(ids)
},
errorCallback = { error ->
if (error is UserOptedOutFromUtiqException) {
cmp.disableUtiq()
clearUtiqUiState()
}
}
)
// Utiq consent is not given or was withdrawn
Utiq.rejectConsent(
successCallback = {
clearUtiqUiState()
},
errorCallback = { error ->
showError(error.message)
}
)
### iOS
Swift
// Utiq consent exists in the CMP
Utiq.shared.fetchIdConnectData(
dataCallback: { ids in
self.renderIds(ids)
},
errorCallback: { error in
let nsError = error as NSError
if nsError.code == UserOptedOutFromUtiqException().code {
self.cmp.disableUtiq()
self.clearUtiqUiState()
}
}
)
// Utiq consent is not given or was withdrawn
Utiq.shared.rejectConsent(
successCallback: {
self.clearUtiqUiState()
},
errorCallback: { error in
self.showError(error.localizedDescription)
}
)
## Error handling
Only one `fetchIdConnectData(...)` error should automatically update the CMP:
* `UserOptedOutFromUtiqException`
Other errors are normally technical or eligibility errors and should not automatically switch off Utiq in the CMP.
## App lifecycle note
The app may be resumed from memory or restarted from scratch when the user returns to it.
Because of this:
* do not rely on in-memory state alone
* always derive Utiq behavior from the current CMP consent state and current SDK state
## Testing
The App SDK integration should be validated using the testing principles described here: [Mobile SDK Testing Guide](https://docs.utiq.com/docs/mobile-sdk-testing-guide.md)
## Disclaimer
This guidance describes how to keep SDK and CMP states technically aligned. It does not replace the developer's responsibility to configure their CMP, vendor disclosures, purposes, legal text, and jurisdiction-specific consent experience in accordance with their legal and compliance requirements.
---
language: "en"
---
# Mobile SDK Testing Guide
## Overview
This page explains how to validate a Utiq Mobile SDK integration before moving to production.
The goal of testing is to confirm that:
* consent handling works as expected
* Utiq identifiers are only requested when the user has the correct consent status
* consent changes are reflected correctly in the app
* the integration continues to behave correctly across normal app usage, including app close and reopen
## Before You Start
Before testing, please make sure that:
* the Utiq Mobile SDK has been integrated into the app
* the app is connected to a Consent Management Platform (CMP), where applicable
* you have access to a suitable test build
* you can observe app behavior, logs, and network traffic if needed
## What Should Be Validated
The following areas should be covered during integration testing:
* SDK initialization
* consent-enabled behavior
* consent-disabled behavior
* consent changes made outside the app
* repeat usage and app relaunch behavior
* cached and refreshed identifier handling
## Recommended Test Scenarios
* The exact test steps may differ depending on the app's consent flow and UI.
* If the app has a custom consent experience, the scenarios below should still be validated in the equivalent user journey.
### 1. First launch and SDK initialization
**How to test**
1. Install the app on a test device.
2. Open the app for the first time.
3. Let the SDK initialize.
4. Close and reopen the app.
**Expected result**
* the app starts normally
* the SDK initializes successfully
* reopening the app does not cause errors or unexpected behavior
### 2. Consent granted -\> identifiers can be requested
**How to test**
1. Open the app in a clean state.
2. Grant the relevant Utiq consent in the CMP.
3. Trigger the app flow that uses the Utiq SDK.
**Expected result**
* the app is able to request Utiq identifiers successfully
* the expected Utiq-enabled app behavior becomes available
* no errors are shown to the user
### 3. Consent not granted -\> identifiers are not requested
**How to test**
1. Open the app in a clean state.
2. Do not grant Utiq consent, or explicitly reject it.
3. Trigger the same app flow that would normally use the Utiq SDK.
**Expected result**
* the app does not continue with Utiq identifier usage as if consent had been granted
* the app behaves correctly for a non-consented user
* no Utiq-enabled functionality is activated incorrectly
### 4. Consent withdrawn after previously being granted
**How to test**
1. Grant Utiq consent and complete a successful identifier-related flow.
2. Afterwards, withdraw Utiq consent.
3. Return to the app and repeat the relevant flow.
**Expected result**
* the app recognizes that consent is no longer valid
* the app no longer behaves as if Utiq consent is active
* any Utiq-dependent state is updated accordingly
### 5. Consent withdrawn outside the app
This scenario is important for cases where the user revokes their Utiq consent outside the mobile app, e.g. using [consenthub](https://consenthub.utiq.com/)
**How to test**
1. Grant consent in the app and complete a successful flow.
2. Revoke the Utiq consent using [consenthub](https://consenthub.utiq.com/) (make sure you use the same network connection).
3. Return to the app and trigger the same flow again.
**Expected result**
* the app detects that the Utiq consent was revoked
* the app switches off the Utiq consent in the CMP
* the app does not do try to fetch Utiq IDs
### 6. Repeat use and network behavior
When testing repeated identifier requests, developers should be aware that network activity may vary depending on how much time has passed since the previous fetch.
For example:
* if the next fetch happens within a short period, such as less than 10 minutes, the SDK may reuse previously available valid data
* if more time has passed, the SDK may perform network calls again to refresh the data
**How to test**
1. Complete a successful Utiq-enabled flow.
2. Repeat the same flow again shortly afterwards.
3. Repeat it again after a longer interval, based on your test setup.
**Expected result**
* the integration should continue to work correctly in both cases
* it is expected that the user may or may not see network calls, depending on the time between fetches
* differences in network activity alone should not be treated as an issue if the functional result is correct
### 7. App close, reopen, and resume behavior
**How to test**
1. Grant consent and complete a successful Utiq-enabled flow.
2. Put the app into the background and bring it back.
3. Fully close the app and open it again.
4. Repeat the same flow.
**Expected result**
* the app continues to behave correctly after resume
* the app also behaves correctly after a full restart
* consent status and Utiq behavior remain aligned across normal app lifecycle events
### 8. Clean-state recovery
**How to test**
1. Use the app and complete a successful Utiq-enabled flow.
2. Reset the app state using your normal QA approach.
3. Start the app again and repeat the integration flow.
**Expected result**
* the app can recover cleanly from a reset state
* the SDK continues to work correctly after reset
* the integration behaves like a fresh installation where expected
## Minimum Recommendation Before Production
Before going live, Utiq recommends confirming at least the following on both Android and iOS:
* the SDK initializes successfully
* the app behaves correctly when consent is granted
* the app behaves correctly when consent is not granted
* the app responds correctly when consent is later withdrawn
* the integration still works correctly after app close and reopen
* repeat usage remains stable and consistent
---
language: "en"
---
# Native Mobile SDK
The Utiq Mobile SDK for [Android SDK](https://docs.utiq.com/docs/android-sdk.md) and [iOS SDK](https://docs.utiq.com/docs/ios-sdk.md) provides a simple means of integration with the Utiq service.
The SDK is published for Android via JitPack and iOS via Swift. You can use this SDK in [Android SDK](https://docs.utiq.com/docs/android-sdk.md) and [iOS SDK](https://docs.utiq.com/docs/ios-sdk.md) projects; for Android projects, Kotlin and Java languages are both supported, in the case of iOS, Swift is currently supported.
## The Native Mobile SDK provides:
Access to handlers that control and provide access the consent status for the service as well as Utiq "passes" supporting MarTech, AdTech and Analytics use cases. For more information please refer to [How Utiq Technology works](https://docs.utiq.com/docs/utiq-technology.md).
For any questions, or if you need assistance, please contact [++onboard@utiq.com++](mailto:onboard@utiq.com)
---
language: "en"
---
# Onetag
Onetag Smart Curation provides your co-pilot for better media quality and performance.
Our Smart Curation Platform and AI-powered technology deliver more effective digital advertising for the open internet, harnessing deeper placement level intelligence to achieve your business outcomes. We feed every DSP with curated, high performing impressions from over 2,000 directly integrated publishers, using real-time AI. We filter out all the wastage and optimize to deliver only high attention and uncluttered inventory, contextual relevance and engaged users.
**Intuitive and ease of use**
The Smart Curation Platform and its dedicated DealCurate section is your clear and intuitive UI to create the programmatic Smart Deals you need, the way you want. Maximise user matching, ad relevance, attention, and performance, including Onetag's proprietary semantic engine for rich contextual data.
**Powered by proprietary AI**
Onetag Smart Curation technology optimizes your inventory before you even see the impressions. DealCurate targeted deals also benefit from our AI capabilities focused on advanced traffic shaping and dynamic optimisation. These effortlessly increase your media curation efficiency and performance.
**Leverage rich cookieless data**
Onetag is at the forefront of cookieless advertising solutions. Through innovative identity frameworks and partnerships, Onetag helps publishers maintain audience addressability and deliver personalized advertising experiences while respecting user privacy. Its first-party data activation capabilities enable brands to continue engaging with their audiences effectively, even in a post-cookie environment.
Onetag's proprietary semantic engine also gives you immediate access to unique rich contextual data powered by our knowledge graph, harnessing large language models (LLMs) to read all content on web pages and go deeper than traditional keyword technology.
DealCurate also leverages a vast pool of ad placement level data beyond what DSPs typically access, to enable greater real-time optimisation.
**Risk free control and flexibility**
DealCurate is completely free for curators with no hidden costs. DealCurate provides your risk free solution for programmatic deal creation and management.
The new Discovery forecasting view in the right-hand pane shows you the immediate impact of deal criteria on weekly forecast impressions, giving you even greater control of your Deals.
**Future proofed and privacy-first**
DealCurate is 100% cookieless, enabling curators to fully embrace the now and future of programmatic advertising.
DealCurate also supports all leading Universal IDs and is fully compliant with privacy legislation.
---
language: "en"
---
# Onetag Use Case 1: Reach & Frequency
**2 Different objectives:**
* **Targeting UTIQ-enabled Impressions:** Ensure that your campaigns only reach impressions tied to UTIQ tokens, aligning with privacy-compliant targeting.
* **Additionally you can set up Frequency Capping:** Limit the number of times a user is exposed to an ad, based on a frequency cap defined by the advertiser.
**Implementation Steps:**
1. **Set UTIQ as the Targeting Filter:**
1. Login the[OneTag Platform](https://platform.onetag.com/)
2. Navigate to[++Deal Curate++](https://platform.onetag.com/deal/deals) and click on "Create a Deal" and apply the UTIQ token filter under Data Marketplace and then Alternative ID provider. *This ensures the campaign delivers ads exclusively to UTIQ-enabled impressions.*
2. **To apply a Frequency Cap:**
1. Select Utiq ID in the Audience Data section of deal settings. Real-time decryption enabled via Utiq and Apply frequency capping to the Utiq ID on each deal. Define the maximum number of times a single user can see your ad.
For example, if the cap is set to "3" per day, no individual will see the ad more than three times during the campaign's duration.
This helps prevent overexposure and ensures a balanced user experience.
3. **Activate the Campaign:**Once the reach \& Frequency rules are in place, you can launch your deal filling the info regarding the DSP that is receiving the deal to activate the campaign.
---
language: "en"
---
# Optimized Reporting with UTIQ: Standard Insights and Advanced Analytics
Every adtech (SSP \& DSP) has reporting functionality that provides **comprehensive and real-time insights** into ad performance, empowering publishers and advertisers to optimize their strategies with precision. Typically, through a **customizable and intuitive dashboard**, users can access key metrics such as revenue, fill rate, bid activity, and audience engagement, enabling them to make data-driven decisions that enhance campaign effectiveness. The platform's ability to process large volumes of data quickly ensures that users can monitor trends and adjust their strategies proactively.
With increasing emphasis on **transparency and accountability** in digital advertising, adtech partner 's reporting functionality ensures that publishers and advertisers maintain full visibility into their inventory performance.
When it comes to reporting within **adtech partner in combination with UTIQ** , there are two distinct options that cater to different levels of granularity and insight. **The default report provided by adtech partner** offers a high-level overview of campaign performance, including key metrics such as impressions, fill rate, and revenue. This built-in reporting serves as a reliable baseline for publishers and advertisers to track their monetization efforts and ensure smooth campaign execution.
For those requiring **deeper insights into user engagement and audience dynamics** , **UTIQ provides a more detailed report** that enhances adtech partner's standard analytics. This advanced reporting includes unique UTIQ-specific metrics such as **Unique UTIQ Users vs. Impressions** and **frequency dispersion analysis**, offering a clearer view of audience reach and engagement in a cookieless environment. By leveraging UTIQ's detailed data, advertisers can fine-tune their targeting strategies, optimize campaign performance, and gain a more comprehensive understanding of how their ads are resonating with users.
By combining adtech partner's reporting framework with UTIQ's granular insights, publishers and advertisers can achieve **a more transparent, data-driven approach to programmatic advertising**. This synergy not only enhances performance measurement but also enables more strategic decision-making, particularly in a privacy-first landscape where user identification and segmentation are becoming increasingly complex.
[Next Page](https://docs.utiq.com/llms-full.txt/1)