Osano Implementation Guide

Integrating Osano with Ours Privacy streamlines your consent management process by combining robust privacy compliance features with flexible data mapping. Osano is a leading consent management provider that supports both state-level and country-level privacy requirements, ensuring that your implementation meets diverse regional standards. This guide outlines the steps to integrate Osano with Ours Privacy for seamless consent handling.

Integration Overview

Before integrating Ours Privacy, ensure that your Osano Consent Management Platform (CMP) is fully configured and loaded. This guarantees that Ours Privacy can access the correct user consent status immediately upon initialization. Integration can be achieved through:

• Google Tag Manager (GTM): Configure Osano settings during the installation process.
• Web SDK: Set up Osano within the initialization call.

Important: Always load Osano before Ours Privacy. Failing to do so may result in missing consent information or conflicts from multiple initializations on the same page.

Additionally, within the mappers, you can determine which consent category the user has approved. This functionality enables you to selectively route data to various destinations—or withhold it entirely—depending on the level of consent granted.

Osano-Specific Configuration

When integrating Osano with Ours Privacy, ensure the following settings are properly configured:

Osano as the Consent Vendor

Specify Osano as your consent management provider. This configuration enables Ours Privacy to load Osano-specific logic and callbacks, ensuring that the system adheres to both state-level and country-level compliance requirements.

Enabling Consent Management

Activate consent management in your configuration so that Ours Privacy monitors Osano’s consent signals. With this enabled, the system dynamically adjusts data collection processes based on the user’s consent status.

Defining the Consent Strategy

Determine the strategy for when consent is considered granted to Ours Privacy. The available options include:

• Always: Consent is assumed granted regardless of the user’s explicit settings, useful for testing or when data collection is mandatory.
• Any: Consent is granted as soon as any of the consent categories is approved, suitable for general consent requirements.
• Specific Category: Consent is granted only if a particular category (for example, marketing) is explicitly approved. When using this option, you must specify the required category.

Mapping Consent Categories

Leverage the mapper functionality to access the specific consent category that the user has approved. This mapping is critical for:

• Routing data to appropriate destinations based on consent levels.
• Preventing data dispatch where the required consent has not been granted.

Best Practices for Osano Integration

• Load Order: Always load Osano 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 Consent Strategy: Choose the consent strategy that best fits your compliance and tracking needs. For instance, use the “specific category” option when strict control over particular data types is required.