Raptive’s consent management platform, or CMP, helps visitors in GDPR-covered regions make privacy choices related to Raptive ads and participating advertising partners.
The CMP manages consent signals for Raptive advertising technology. Creators can also configure certain publisher-installed analytics tools, plugins, pixels, widgets, and other scripts to respond to those signals.
What is GDPR?
The General Data Protection Regulation, or GDPR, is a European privacy law that governs how organizations collect, use, store, and share personal data.
GDPR applies to organizations established in the European Union and may also apply to organizations outside the EU based on their audience and activities.
I’m not located in Europe. Does GDPR apply to my site? GDPR may apply to sites outside Europe when they process personal data from visitors in GDPR-covered regions. This means your site may still be subject to GDPR requirements even if only a small percentage of its traffic comes from those regions.
What visitors see and how consent is handled
Visitors in the European Economic Area (EEA), UK, and Switzerland see a consent modal that allows them to accept, decline, or customize their cookie and advertising preferences.
Raptive’s GDPR CMP supports the IAB Europe Transparency & Consent Framework, or TCF. This advertising-industry framework provides a standardized way to collect visitors’ privacy choices and communicate them to participating vendors.
When a visitor makes a choice, the CMP sends the applicable consent signals to Raptive’s ad stack and participating advertising partners. These signals help determine how Raptive ads and participating partners may process data for personalized advertising and related ad purposes.
The exact wording, buttons, and available settings may vary based on the visitor’s location and your site’s CMP configuration.
Connecting non-Raptive tools to Raptive’s CMP
Raptive’s CMP manages consent signals for Raptive advertising technology by default. It does not automatically control publisher-installed analytics tools, pixels, plugins, widgets, or other scripts.
You can use Google Tag Manager to configure supported non-Raptive tags to respond to consent signals from Raptive’s CMP. This is especially important for tools that should not load or process data until the applicable consent has been provided.
Raptive can help explain the consent signals available through our CMP, but you remain responsible for configuring and managing the non-Raptive tools you use.
Google Analytics and consent
Raptive’s CMP does not automatically prevent publisher-installed Google Analytics tags from loading or setting cookies before consent. The appropriate configuration depends on how Google Analytics is installed on your site.
If you use Google Tag Manager, follow our consent mode tag-blocking instructions to configure your Google Analytics tags. Other Google Analytics installations may require a different method to delay Analytics until the visitor provides consent.
Read more: Delaying Google Analytics until user consent
Before changing your Analytics implementation, confirm how Google Analytics is currently installed and make sure it is not loading from multiple sources, such as both a WordPress plugin and Google Tag Manager.
Frequently asked questions
How can visitors change their choices?
Visitors can reopen the CMP through the Update Privacy Preferences link when that link is available for their location. They can then review or change their previous choices.
Can I customize the GDPR CMP?
Contact Support if you want to change the CMP’s wording, appearance, or vendor configuration. We can review your request and confirm which adjustments are supported.
Because these changes may affect your site’s privacy experience, we recommend reviewing requested customizations with your legal counsel.
Can I use my own CMP instead of Raptive’s?
Raptive’s CMP is included by default and is the simplest option for most creators. Select third-party CMP integrations may also be supported.
Contact Support before replacing Raptive’s CMP so we can confirm compatibility and configure Raptive ads to receive the appropriate consent signals.
Learn more about using your own CMP instead of Raptive’s.
Can I run another CMP alongside Raptive’s CMP?
No. Running multiple CMPs can create conflicting consent signals, duplicate privacy experiences, and prevent vendors from receiving accurate visitor choices.
If you want to use a supported third-party CMP instead, contact Support before making changes.
Do I need a separate cookie notification?
Raptive’s CMP provides the consent experience used by Raptive ads in GDPR-covered regions, so you should not add a separate cookie or consent platform alongside it.
Publisher-installed tools may require additional configuration to respond to visitors’ consent choices. Review those tools with their providers and your legal counsel to determine the appropriate setup.
Raptive cannot provide legal advice or confirm whether your site meets every applicable privacy requirement. We can explain how Raptive’s consent tools work and help with supported technical configurations.