CookieYes Implementation Guide

CookieYes and Ours Privacy work together to provide a comprehensive consent management solution that supports healthcare, GDPR, CCPA, and other privacy regulations. This guide explains the capabilities, operating modes, and integration patterns available when using CookieYes as your Consent Management Platform (CMP).

Overview

CookieYes controls when the Ours Privacy SDK loads and provides granular consent data that flows through your entire data pipeline. This approach delivers:

• Regulatory Compliance: Supports GDPR-, CCPA-, CPRA-, LGPD-, and HIPAA-aligned deployments
• Granular Control: Category-based and vendor-specific consent management
• Complete Audit Trail: Visibility into every consent decision and change
• Flexible Integration: Works with any CookieYes configuration or consent strategy

Operating Modes

Ours Privacy supports two distinct operating modes for consent management with CookieYes, each offering different levels of data collection and consent enforcement:

Mode 1: Strict Consent Mode (Zero Data Collection)

Ours Privacy SDK is not loaded until explicit consent is granted through CookieYes, ensuring zero data collection before user permission.

Can I ensure nothing is sent to Ours Privacy if someone opts out? Yes. If someone opts out, nothing is sent to Ours Privacy.

How it works:

• CookieYes controls when the Ours Privacy SDK loads
• No data is sent to Ours Privacy until consent is granted
• Complete control over tracking initiation
• Zero data collection before user permission

Mode 2: Mapper-Controlled Mode

Ours Privacy loads immediately and collects all events, but the mapping layer stops dispatch to destinations based on consent conditions.

How it works:

• Ours Privacy SDK loads immediately and collects all events
• Events are sent to Ours Privacy regardless of consent status
• Consent status is passed as event properties
• Ours Privacy mappers conditionally route events to destinations based on consent
• Events without proper consent are filtered out at the mapping layer (not sent to destinations, but still collected by Ours Privacy)

Important: In this mode, data is still sent to Ours Privacy even if users opt out. Only the forwarding to destinations is controlled. If you need to ensure no data is sent to Ours Privacy when users opt out, use Mode 1 instead.

Choosing the Right Mode

The choice between these modes depends on your organization's privacy requirements, compliance needs, and technical architecture. We recommend:

• Consult with your privacy officer and/or legal team to determine the appropriate consent management approach for your use case
• Reach out to us to start a conversation about privacy and consent management strategies

Our team can help you evaluate your specific requirements and recommend the best approach for your organization.

Implementing Consent Events and Mapping

We recommend firing a "consent_change" event when consent is granted or changed. This allows you to track consent decisions and use them in your mapping logic.

Firing Consent Events

Use CookieYes's web SDK to get the consent status or grab their cookie string if it contains the allowed/denied categories. Then pass this information into event properties and visitor properties:

// Get consent status from CookieYes
const consentStatus = {
  marketing: true,
  analytics: false,
  functional: false,
  necessary: true,
}; // Example object grab the real one with the CookieYes web sdk.

// Track consent change event
ours(
  'track',
  'consent_change',
  {
    // Event properties
    ...consentStatus,
    cmp_vendor: 'cookieyes',
  },
  {
    // Visitor properties - consent object
    consent: consentStatus,
  }
);

Conclusion

Integrating CookieYes with Ours Privacy enables:

• Regulatory Compliance: Supports GDPR-, CCPA-, CPRA-, and HIPAA-aligned deployments
• Granular Consent Control: Category-based and vendor-specific consent management
• Complete Audit Trail: Visibility into every consent decision and change
• Flexible Integration: Works with any CookieYes configuration or consent strategy

The Ours Privacy platform respects these consent properties throughout your data pipeline, helping you maintain data integrity and user privacy alongside your consent strategy.

Next Steps

• Consent Overview: How consent flows through Ours Privacy end-to-end
• Ours Privacy CMP: Use the built-in CMP if you don't already have CookieYes
• Mappings: Conditionally route events to destinations based on consent
• Need help?: Reach out at support@oursprivacy.com