How Ours Privacy Works with Consent

Ours Privacy has always supported user consent—and now it does so better, deeper, and easier than ever before.

As a healthcare-focused customer data platform (CDP), we understand the critical importance of compliance and user privacy. We work seamlessly with both state-level and country-level consent vendors, ensuring that our approach adapts to varied regional privacy requirements. This guide explains how to integrate and configure consent management with Ours Privacy so that your data collection adheres to user preferences while remaining flexible and robust.

Integration Overview

Before integrating Ours Privacy, load your Consent Management Platform (CMP) first. This ensures that when Ours Privacy starts up, it can immediately access the user's consent status. Ours Privacy can be loaded via either:

• Google Tag Manager (GTM): Configure consent settings during the installation process.
• Web SDK: Configure consent settings during initialization.

Important: If you do not configure consent during initialization, the system will not operate in consent mode. Also, avoid initializing the SDK multiple times on the same page to prevent conflicts.

Additionally, within the mappers, you can access which consent category the user has approved. This functionality enables you to determine which data should be sent to specific destinations—or withheld entirely—depending on the level of consent granted.

Configuring Consent

When starting the SDK, you can pass several consent-related options that control how and when events are tracked based on user consent. Here is a breakdown of the available settings:

Consent Vendor

• Type: Text
• Description: Specifies the third-party consent management provider you are using (for example, OneTrust, Cookiebot, or Osano). This setting allows the SDK to load vendor-specific logic and callbacks as needed.

Consent Enabled

• Type: Yes/No
• Description: A flag to turn consent management on or off within the SDK. When enabled, the system monitors and reacts to the user’s consent status.

Consent Granted To Ours

• Type: Choice (Options: "always", "any", or "specific category")
• Description: Defines the strategy for when consent is considered granted to Ours Privacy:
  • Always: Consent is assumed granted regardless of the user’s explicit settings. This option is useful for testing or when data collection is mandatory.
  • Any: Consent is granted as soon as the user approves any of the tracked categories. Ideal for situations where general consent is sufficient.
  • Specific Category: Consent is granted only if a particular category is explicitly approved. When using this option, you must also specify the required category.

Consent Granted Category

• Type: Text
• Description: Only Required if you choose the "specific category" option. This setting specifies which consent category (such as marketing) must be approved for the system to begin processing and dispatching events.

Consent Categories To Track

• Type: List of Categories
• Description: Defines the categories that the SDK will monitor. Common categories include analytics, marketing, and personalization. This mapping helps the system determine which events to queue or send based on the user’s consent preferences.

Best Practices for Consent Management

• Load Order: Always load your CMP before initializing Ours Privacy to ensure that the consent status is available immediately.
• Single Initialization: Avoid initializing the SDK multiple times on the same page to prevent conflicts.
• Tailored Strategies: Choose the consent strategy that best fits your compliance and tracking needs:
  • Use "always" for testing or mandatory data collection.
  • Use "any" for general consent requirements.
  • Use "specific category" when you need to enforce approval for a particular data category.
• Stay Updated: Regularly check our documentation to take advantage of the latest features and compliance standards.

Conclusion

With enhanced consent management, Ours Privacy continues to provide robust, compliant data collection for the healthcare sector. By integrating your CMP and properly configuring the consent settings during initialization, you ensure that your data collection process respects user privacy preferences while maintaining flexibility and accuracy in event tracking. Additionally, by leveraging the mapper functionality, you can precisely control data flows based on the consent categories approved by your users.

For more detailed instructions and troubleshooting tips, please refer to our comprehensive documentation.