> ## Documentation Index
> Fetch the complete documentation index at: https://oneviewhub.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Cookieless Advertising
> Storing Click IDs in the cloud for simplified privacy compliance, more accurate data, and lightning-fast secure websites.
## Overview
OneView's Cookieless Advertising stores Click IDs server-side in your workspace instead of in advertising cookies. This architectural approach delivers:
* **[Simplified website](#simplified-website)** - Just 2 first-party cookies with centralized server-side consent enforcement
* **[Faster website](#faster-website)** - One script instead of multiple platform pixels, with typical 20-40 point Lighthouse improvements
* **[Improved accuracy](#improved-accuracy)** - Server-side storage eliminates data loss from browser blocking and cookie expiration conflicts
When someone clicks your ad, OneView captures the Click ID and stores it in your workspace database. You still use 2 first-party cookies for client and session identification, but all ad platform data lives server-side where it can be retrieved and consent can be properly [enforced](/docs/platform/features/collection/consent-enforcement).
## Benefits
### Simplified website
**OneView achieves simplified multi-vendor management** when you:
* Configure your **Consent Management Platform** (CMP) based on your **Data Protection Officer** (DPO) recommendations
* **Send data to OneView** in one of the [supported ways](/docs/guides/sending-events/overview)
OneView handles all tracking tags, consent enforcement, and enhanced conversion rules automatically.
**Understanding multi-vendor complexity:**
Managing a website with multiple tracking tags from different ad platforms typically requires:
* Setting up and maintaining multiple vendor scripts (Facebook Pixel, Google Tag, TikTok Pixel, etc.)
* Configuring a [Content Security Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CSP) (CSP) with custom rules for each vendor
* Managing [Google Tag Manager](https://tagmanager.google.com/) (GTM) configurations, either web or server-side
* Implementing consent enforcement logic for each individual tracking tag
* Maintaining data layer implementations for each platform's requirements
All while fighting **techincal details**, **privacy concerns**, **vendor documentation**, and **data loss** from browser blocking and cookie expiration conflicts.
| Category | Traditional | OneView |
| ----------------------- | ------------------------- | ------------------------ |
| **Cookies to Manage** | Multiple (one per vendor) | 2 (client + session) |
| **Consent Enforcement** | Per-cookie, client-side | Centralized, server-side |
| **Vendor Scripts** | One per platform | Single script (or none) |
OneView uses only 2 first-party cookies instead of multiple advertising cookies from different vendors. Consent is enforced server-side across all ad platforms automatically - no need to manage per-cookie consent logic in your client-side code.
This eliminates the complexity of managing tracking tags, consent enforcement for each tag, and custom CSP rules across multiple ad platforms, while fighting website restrictions, privacy concerns, and data loss from browser blocking and cookie expiration conflicts.
***
### Faster website
**OneView achieves optimal page speed** when you:
* Replace multiple vendor pixels with a single script that sends data to OneView
* Or use traffic mirroring to eliminate frontend scripts entirely
Typical improvements: 20-40 point Lighthouse score increase, 50-70% reduction in Total Blocking Time.
**Understanding page speed impact:**
The loading time of a website includes the time it takes for the browser to download the HTML, CSS, JavaScript, and other resources needed to display the page. Each tracking script adds:
* Network requests to third-party domains
* JavaScript execution time on the main thread
* Browser processing overhead
This is a key metric for user experience, measured by the [Lighthouse](https://developer.chrome.com/docs/lighthouse/overview/) tool.
| | **Traditional Tracking** | **OneView** |
| ----------------------- | ---------------------------- | ------------------------------------ |
| **Scripts Required** | Multiple (one per platform) | One (or none with traffic mirroring) |
| **Processing Location** | Browser (impacts page speed) | Server (no page speed impact) |
| **Lighthouse Impact** | Degraded by tracking scripts | Typical 20-40 point improvement |
OneView requires one frontend script, or none at all with traffic mirroring. Traditional tracking requires loading separate scripts for Facebook Pixel, Google Tag, TikTok Pixel, Snapchat, and every other platform. All processing happens server-side, eliminating page speed impact.
***
### Improved accuracy
OneView achieves **maximum attribution accuracy** because it eliminates dependency on browser cookie storage and **cookie expiration conflicts**.
**Understanding cookie restrictions:**
Browsers are deliberately restricting advertising cookie lifetimes to protect user privacy on websites where consent is poorly enforced, or not enforced by law:
* Safari: [Intelligent Tracking Prevention](https://webkit.org/tracking-prevention/)
* Firefox: [Enhanced Tracking Protection](https://support.mozilla.org/en-US/kb/enhanced-tracking-protection-firefox-desktop)
* Brave: [Query Stripping](https://brave.com/privacy-updates/5-grab-bag/)
Different platforms have different cookie expiration rules, creating attribution conflicts and data gaps.
| Challenge | Traditional Tracking | OneView |
| --------------------- | ---------------------------------------------------------------------------------------- | -------------------------------------- |
| **Cookie Expiration** | ❌ Different lifetimes per platform create conflicts | ✅ Synchronized retention policies |
| **Cookie Overwrite** | ❌ First-touch click IDs are lost when subsequent click IDs are overwritten by the script | ✅ Complete attribution chain preserved |
| **Attribution Gaps** | ❌ Data loss from expired or blocked cookies | ✅ Complete attribution chain preserved |
Traditional tracking loses attribution data when browsers block or delete advertising cookies. Different platforms have different cookie lifetimes, creating conflicts and data gaps.
OneView stores all Click IDs in your workspace with synchronized retention policies. No cookie expiration conflicts, centralized consent enforcement, no data loss.
## Common questions
OneView uses only 2 first-party cookies:
* **Client cookie** for client identification
* **Session cookie** for session tracking
Both are first-party cookies set by your domain. OneView does not use fingerprinting or other tracking methods.
Depends on how many tracking scripts you're currently running. Most customers with 5+ tracking pixels see:
* 20-40 point Lighthouse improvement
* 50-70% reduction in Total Blocking Time
* Significant Core Web Vitals improvements
Your actual improvement depends on the number of scripts you can remove and your existing optimization level.
OneView achieves full [ITP compliance](/docs/platform/guides/sending-events/advanced-setup/intelligent-tracking-prevention) because Click IDs are stored in your workspace, not in advertising cookies. The 2 first-party cookies OneView uses are exempt from ITP restrictions when set via same-origin domains.
Yes. Traditional tracking requires allowing multiple third-party domains in your CSP for each tracking script. OneView requires only one script (or none with traffic mirroring), dramatically simplifying your [Content Security Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP) configuration.
## Next steps
Implementation details for ITP compliance across all browsers
How consent preferences are enforced server-side across all platforms