Raptive ads include a consent management platform, or CMP, by default. For many creators, this is the simplest path because Raptive manages the ad-related consent experience and related ad stack configuration.
If you prefer to use and manage your own CMP, Raptive can support that for select CMP platforms. In this setup, your CMP remains responsible for collecting and managing visitor consent, and Raptive ads read the applicable consent signals from your CMP so ads can respond appropriately.
Supported CMP platforms
Raptive currently supports integrations with the following CMP platforms:
- Consentmanager
- Ketch
- OneTrust
- Osano
At this time, Raptive ads are only compatible with supported CMP integrations. If you want to use a CMP that is not listed, contact Raptive before implementing it. We can review the request, but compatibility is not guaranteed and may require additional engineering work.
Before you switch to your own CMP
Before adding or replacing a CMP on your site, we recommend doing the following:
- Confirm your CMP is on Raptive’s supported list
- Review your intended CMP setup with your privacy or legal counsel
- Confirm that the appropriate consent signal frameworks will be enabled for each region’s requirements
- Confirm that your CMP’s required stub script will be installed as part of the implementation
- Contact Raptive before launching or replacing the CMP
Do not add a second CMP without coordinating with Raptive first. In many cases, Raptive will need to disable the Raptive-provided CMP and configure ads to listen for your CMP’s signals.
What you’re responsible for when using your own CMP
When you choose to use your own CMP, you are responsible for the CMP itself, including:
- Vendor relationship and costs
- CMP setup and configuration
- Ongoing maintenance
- Determining which regions, regulations, and consent experiences apply to your site
- Working with your privacy or legal counsel on compliance requirements
Raptive cannot provide legal advice or confirm whether your CMP setup complies with every applicable law or regulation. Raptive can help validate whether the expected technical consent signals are present and whether Raptive ads are able to read those signals.
Setting up your self-managed CMP
Before adding or changing a CMP on your site, please contact Raptive.
Running more than one CMP on your site can create conflicting consent signals, duplicate privacy experiences, or other compliance risks. Letting us know before implementation helps us disable the Raptive-provided CMP where appropriate and configure Raptive ads to listen for consent signals from your CMP.
Install the CMP stub script
When using your own CMP, its required stub script must be installed on your site. The stub initializes the CMP early in the page-loading process, so Raptive ads and other participating technologies can access the applicable consent interface while the full CMP loads.
Work with your CMP provider or developer to confirm that the correct stub script is included in your implementation. Without it, the CMP may not initialize properly, and Raptive ads may be unable to read the expected consent signals.
Required signal frameworks
To help Raptive ads receive the expected privacy signals in applicable regions, your CMP must be configured to expose the appropriate framework signals.
| Region | Framework to enable | Expected outcome |
| GDPR-covered regions | IAB Europe Transparency and Consent Framework (TCF) | CMP exposes TCF consent signals for GDPR visitors. |
| United States, Canada, and any other countries you choose to manage this way | IAB Tech Lab Global Privacy Platform (GPP) | CMP exposes GPP signals for these visitors. |
The exact list of countries, states, provinces, or regions your CMP should cover should be confirmed by your privacy or legal team. Raptive can help validate whether the expected TCF or GPP signals are present after your CMP configuration is published.
Frequently Asked Questions
Can I use a CMP not on your list?
At this time, Raptive ads are only compatible with supported CMP integrations.
If you want to use a CMP that is not listed, contact Raptive before implementing it. We can review the request, but compatibility is not guaranteed and may require additional engineering work.
We’re continuing to evaluate additional CMP integrations, so please let us know if there’s a CMP you’d like to use that isn’t currently supported.
Can I run my CMP alongside Raptive’s CMP?
We do not recommend running your own CMPs alongside Raptive’s.
Multiple CMPs can create conflicting consent signals, duplicate privacy experiences, or other compliance risks. Contact Raptive before adding or replacing a CMP so we can review the setup and configure Raptive ads appropriately.
Can Raptive confirm if my CMP is compliant with all available regions and regulations?
No. Raptive cannot provide legal advice or assess the overall compliance of your CMP.
Raptive can help validate whether expected technical consent signals, such as TCF or GPP signals, are present in applicable regions and whether Raptive ads are able to read those signals.