Last updated

Cookie Consent Flags

Rokt supports cookie opt-outs so you can align your implementation with user consent preferences. This helps ensure compliance with privacy regulations and provides consistent, respectful experiences when customers opt out of different levels of tracking.

Types of Tracking Technologies

Rokt distinguishes between two categories of tracking technologies. Each serves a different purpose and has different implications for user consent flags.

Functional Tracking Technologies

Functional tracking technologies enhance the usability and performance of a site or app. They are used to remember language or region settings, keep a user logged in during a session, save items in a shopping cart, and support analytics that measure performance or detect errors.

In short, functional tracking focuses on making the core experience smoother and more reliable.

Targeting Tracking Technologies

Targeting tracking technologies enable advertising, retargeting, and marketing personalization. They collect browsing behavior and interactions to build user profiles, such as tracking which sites a user visits to serve relevant ads, measuring ad performance with social media pixels, or using third-party cookies for retargeting campaigns.

In short, targeting tracking focuses on profiling users to deliver personalized marketing and advertising.

Configurable flags for managing cookie preferences

The Rokt Web SDK provides two configurable flags for managing consent preferences:

• noFunctional — Controls the use of browser identifiers for functional tracking.
• noTargeting — Controls the use of browser identifiers for targeting tracking.

Both flags align with terminology used by common Consent Management Platforms (CMPs) for ease of implementation.

noFunctional: true

• Prevents the use of browser identifiers for functional tracking.
• No new identifiers are created.
• Existing identifiers are ignored but not removed.
• Other identifiers (e.g., email, phone number) continue to work if provided.

noTargeting: true

• Prevents the use of browser identifiers for targeting tracking.
• Cross-site personalization and advertising identifiers are disabled.
• Functional identifiers remain active unless noFunctional is also set.

If a flag is omitted, set to false, or given any other value, the SDK will use identifiers as configured.

Behavior Comparison

Flag Configuration	Functional Tracking	Targeting Tracking	Other Identifiers (e.g. email, phone)
Default (no flags / false)	Browser identifiers are generated, stored, and used to enable personalization and checkout features (e.g. Upsells).	Browser identifiers may be used for personalization across sites (when applicable).	Always accepted if provided.
noFunctional: true	Browser identifiers are not generated or used. If already present, they are ignored for this session.	Targeting tracking behaves according to the noTargeting flag (default is enabled).	Always accepted if provided.
noTargeting: true	Functional tracking operates normally (unless noFunctional is also set).	Browser identifiers are not used for targeting or cross-site personalization.	Always accepted if provided.
noFunctional: true and noTargeting: true	Browser identifiers are not generated or used for functional purposes.	Browser identifiers are not used for targeting across sites.	Always accepted if provided.

Example

To set the noFunctional or noTargeting flags, include the following within your SDK initialization script:

windiow.mParticle.config.launcherOptions = {
    noFunctional: true, // Disables functional tracking
    noTargeting: true,  // Disables targeting tracking
};

note

These flags apply only to browser-based identifiers. Other identifiers (such as email addresses or phone numbers) may still be passed at your discretion and will continue to be used in accordance with your configuration.