Datareporter WebCare Integration

By datareporter

100+ active installationsVersion 1.2.0

Integrate the Datareporter WebCare cookie consent banner, privacy policy, and imprint into your WordPress site.

Description

Datareporter WebCare Integration integrates your Datareporter WebCare cookie consent banner, privacy policy, and legal imprint into WordPress. WebCare is a consent management platform from Austria. You configure your consent banner, privacy policy, and imprint in WebCare, and this plugin delivers them to your WordPress site.

What the Plugin Does

  • Cookie Consent Banner: Adds the WebCare consent banner to your site. The banner collects cookie consent and includes a tag manager that controls tracking scripts based on visitor consent.
  • Privacy Policy: Displays your WebCare privacy policy on any page or post using the [drwc_privacy] shortcode. When you update the privacy policy in WebCare, the changes are reflected on your site automatically.
  • Imprint: Displays your legal imprint using the [drwc_imprint] shortcode. Like the privacy policy, it stays in sync with your WebCare account.
  • Embed Blocker: Blocks third-party embeds (YouTube, Vimeo, Twitter/X, TikTok, Google Maps, Calendly) until visitors give consent. An overlay prompts visitors to allow content per provider, or content unlocks automatically once the WebCare banner reports consent for statistics or marketing. Any other third-party widget is covered by a service you define (found automatically by CSS class, element id or iframe domain) and by the Consent box block or shortcode that editors wrap around content (Feature requires WordPress 6.9 or later).

Key Technical Features

  • Local Caching: Cache banner assets, privacy policy, and imprint content on your server for fewer external requests.
  • Subresource Integrity (SRI): SRI support for the banner script, verifying that the banner loader has not been tampered with.
  • Scheduled Cache Sync: An hourly background sync keeps cached content up to date with your WebCare account.
  • WP Rocket Compatibility: WP Rocket is detected automatically. The WebCare scripts and stylesheets are excluded from its JavaScript and CSS optimizations, and its page cache is purged when the plugin changes your pages.

Shortcodes

  • [drwc_privacy]: Displays your privacy policy.
  • [drwc_imprint]: Displays your imprint.

Both accept an optional lang attribute (ISO code, e.g. lang="de") that selects the language. Without the attribute the page language is used (in cache mode the WordPress locale, which WPML and Polylang switch per page) and a ?lang= URL parameter overrides both; English is the fallback when a language is not available.

If you migrated from the old “Datareporter Webcare” plugin, its shortcodes keep working unchanged and are officially supported: [datareporter type="privacynotice"] renders exactly like [drwc_privacy] and [datareporter type="imprint"] exactly like [drwc_imprint]. Use the drwc_ forms for new pages.

Requirements

This plugin requires an active WebCare license. You can get one at the Datareporter Store. The integration key from your WebCare account is needed during setup.

Documentation & Support

The plugin help page walks through setup, caching, the embed blocker and the expert settings step by step. For WebCare itself visit the WebCare Help Center.

External services

This plugin connects to the Datareporter WebCare CDN (Content Delivery Network), an external service operated by Datareporter GmbH (Austria). The CDN is a network of servers that hosts and delivers the cookie consent banner, privacy policy, and legal imprint content to your WordPress site. Because this content is created and managed in your WebCare dashboard, the plugin must fetch it from the CDN — it cannot be generated locally.

The content served by the CDN (including the cookie banner text, privacy policy, and imprint) is dynamically generated based on the settings you configure in your individual WebCare license via the WebCare dashboard. When you update your settings there, the CDN-served content updates automatically.

What the CDN is used for

The plugin uses the Datareporter WebCare CDN for three purposes:

  1. Cookie consent banner: The banner JavaScript, CSS, and configuration are loaded from the CDN so your consent banner appears on every page.
  2. Privacy policy and imprint: The plugin fetches your privacy policy and legal imprint content from the CDN and displays it on pages where you place the [drwc_privacy] or [drwc_imprint] shortcodes.
  3. Integration key verification: When you enter or save your integration key in the WordPress admin panel, the plugin sends a request to the CDN to verify that the key is valid so your WebCare content is reachable.

CDN domains

The plugin communicates with the following domains. The exact domain used depends on your WebCare configuration:

  • webcachex-eu.datareporter.eu
  • webcachex.datareporter.eu
  • webcache-eu.datareporter.eu
  • webcache.datareporter.eu

For example, a request to load the banner design (stylesheet) would look like this:
https://webcachex-eu.datareporter.eu/c/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/yyyyyyyyyyyyyyy/zzz/banner.css
where xxxx..., yyy..., zzz are parts from your individual integration key.

When data is sent

Your visitors’ browsers make no requests to the CDN until a site administrator has entered an integration key and enabled the banner. Your server contacts the CDN only in the cases listed below.
Once active:

  • CDN mode (default): On every page load, your visitors’ browsers send requests directly to the CDN domains listed above to load the banner script, styles, privacy policy, and imprint content.
  • Hourly background sync: Once an integration key is stored, your WordPress server fetches the banner script, its stylesheet, the privacy policy, the imprint and their language files from the CDN once an hour (WP-Cron) into wp-content/uploads/drwc-cache/, whether or not a cache mode is enabled, so that cache mode can be switched on without delay. The integration key is part of the URL; the request carries WordPress’ default User-Agent header, which includes your site URL.
  • Cache mode (optional): Your WordPress server serves those synced files locally to visitors instead of the CDN.
  • Admin panel: Your server verifies the integration key against the CDN with a single request when you save it, and again at most once every five minutes while an administrator has the plugin’s settings page open. On activation, when the settings of the old “Datareporter Webcare” plugin hold a complete key and this plugin has none yet, one request verifies that key before it is imported.

What data is sent

Each request to the CDN transmits the following data:

  • The IP address of the requesting party (the visitor’s browser in CDN mode; your server for the hourly sync, the key checks and cache mode).
  • Standard HTTP headers: User-Agent, Referer, and Accept-Language.
  • Integration key components (client ID, organization ID, and website ID) included in the request URL.

Service provider

This service is provided by Datareporter GmbH (Austria): privacy policy.

About Datareporter

Datareporter GmbH is an Austrian company specializing in privacy and consent management. Their WebCare platform helps website operators meet GDPR requirements with automatically updated consent banners, privacy policies, and legal imprint management.
More info about us can be found at datareporter.eu/company/info.

Installation

  1. Install the plugin in the Plugins section of your WordPress admin dashboard.
  2. Activate the plugin in the Plugins menu.
  3. Go to Settings > Datareporter WebCare and enter your WebCare Integration Key (see the plugin help page for where to find it).
  4. Enable the cookie consent banner.
  5. Add the [drwc_privacy] and [drwc_imprint] shortcodes to the relevant pages on your site.
  6. Configure caching and embed blocker settings as needed.

FAQ

Do I need a WebCare account to use this plugin?

Yes. The plugin requires a valid integration key from an active WebCare license. You can obtain one at store.datareporter.eu.

What content does the plugin load from external servers?

The consent banner script, privacy policy data, and imprint data are loaded from the Datareporter WebCare CDN. Local caching can be enabled to reduce external requests.

How do I block a widget that is not one of the built-in providers?

Go to Settings > Datareporter WebCare > Embed Blocker > Custom Services (Advanced) and add a service: give it a title, list the widget’s scripts and stylesheets under “Blocked Scripts and Stylesheets” (open any page with ?drwc_debug=1 and read the console report for ready-to-paste values) and either let it be found automatically by a CSS class, element id or iframe domain, or wrap the widget in a Consent box (block, or shortcode [drwc_consent_box service="<slug>"]…[/drwc_consent_box]) where you place it. A Consent box without a service blocks its content as generic third-party content. A step-by-step guide is on the plugin help page.

The Embed Blocker is enabled but embeds are not being blocked. What can I do?

Some page builders (e.g. Elementor) switch off the WordPress template buffer that the Embed Blocker reads every page through. Go to Settings > Datareporter WebCare > Expert Settings > Compatibility > Page builders: the table shows whether the buffer is active, and the button forces it on when another plugin switched it off. Stop forcing it if it causes issues with that plugin.

Does the plugin work with WP Rocket?

Yes. When WP Rocket is active, the WebCare scripts and stylesheets are excluded from Delay JavaScript, Defer, Minify and Combine, Remove Unused CSS and Load CSS asynchronously, and WP Rocket’s cache is purged whenever the plugin changes your pages. Settings > Datareporter WebCare > Expert Settings > Compatibility shows which optimizations are on; no manual exclusions are needed.

I am migrating from the old “Datareporter Webcare” plugin. Do I have to change my pages?

No. The [datareporter type="imprint"] and [datareporter type="privacynotice"] shortcodes of the old plugin are permanently supported and render exactly like [drwc_imprint] and [drwc_privacy]. On activation the plugin imports the integration key from the old plugin’s settings if they are complete and can be verified against the WebCare CDN; otherwise the Setup tab offers a button to import it while the key field is empty. Enable the banner on the Setup tab first, then deactivate the old plugin: while both are active the old plugin keeps rendering its shortcodes and loads a second cookie banner (a warning is shown on the Plugins page), and this plugin takes the shortcodes over the moment it is deactivated. Any other type value renders nothing and is recorded in the plugin’s debug log. See also the migration section of the plugin help page.

Where can I get help?

The plugin help page documents every setting of this plugin. Visit the WebCare Help Center for documentation and support on WebCare.

Screenshots

Changelog

1.2.0

Every feature is described on the plugin help page.

  • New: embed blocker services for any third-party widget, plus the Consent box block and shortcode.
  • New: blocked content loads automatically once the banner has consent for statistics or marketing.
  • New: diagnostic report (?drwc_debug=1) and dry run (?drwc_noblock=1) for the embed blocker.
  • New: WP Rocket compatibility with automatic exclusions and cache purge.
  • New: migration from the discontinued “Datareporter Webcare” plugin, its shortcodes keep working.
  • New: redesigned Embed Blocker tab and a Compatibility section on the Expert tab.
  • Improved: privacy policy and imprint follow the page language in cache mode; several shortcodes per page in CDN mode.
  • Security: hardened restore of blocked content against markup planted by untrusted users.
  • Fixed: embed blocker edge cases (lazy-loaded iframes, TikTok, UTF-8 BOM, inline UTF-8, framework attributes, shared nomodule scripts).
  • Fixed: banner initialisation and the “Cookie Settings” link in cache mode.
  • Fixed: PHP 8.1+ deprecation notice on pages with legal-text shortcodes while no key is set.
  • Fixed: settings validation for the banner and SRI switches and for services.
  • Changed: debug log under a random per-site file name, emptied at 10 MB; CDN script URLs carry the plugin version.
  • Requirements: banner loader v6, WordPress 6.4 or later, tested up to 7.1.

1.1.1

  • Fixed embed blocker compatibility with Elementor and other page builders that disable the WordPress template enhancement output buffer. A new opt-in option is available under the Troubleshooting section in the Embed Blocker tab.
  • Fixed Vimeo iframe sizing in Elementor after consent.

1.1.0

Initial public release with the following features:
* Cookie consent banner integration with CDN and local cache modes.
* Privacy policy and imprint shortcodes ([drwc_privacy] and [drwc_imprint]).
* Embed blocker for YouTube, Vimeo, Twitter/X, TikTok, Google Maps, and Calendly with per-provider consent overlays (requires WordPress 6.9 or later).
* Local caching of banner assets, privacy policy, and imprint content with hourly scheduled sync.
* Subresource Integrity (SRI) support for the banner loader script.
* Debug logging with configurable log levels.
* Full internationalization with German and English translations.