TARKOP DSGVO COOKIE SHIELD
Tarkop DSGVO Cookie Shield translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what Tarkop DSGVO Cookie Shield does, but does not yet establish specific visitor-facing content values that REEID should translate.
AWAITING VERIFICATION
Translation scope is not yet established.
Plugin capabilities can be documented without treating structure, behavior, configuration or feature availability as translatable content.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
TRANSLATION SCOPE
No specific visitor-facing content values are currently approved for translation scope.
PLUGIN EVIDENCE
Plugin capabilities and distinctive features are documented separately from REEID translation support.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Prior-consent blocking for recognized third-party resources (e.g., Google Analytics, Facebook Pixel, YouTube, Vimeo, Google Fonts) by making them inactive before they reach the browser until consent is granted.
- Consent category controls for necessary, statistics, marketing, and external media services, with restoration of accepted script/stylesheet categories after consent.
- Recognition of supported third-party resources when integrated via WordPress mechanisms (enqueue, inline-script, content, widget, or oEmbed filters), and outputting recognized resources without an executable/loadable source before consent.
- Embedded video handling: embedded videos remain blocked until the visitor clicks a load button on that video.
- Consent persistence: visitor choices are stored in a cookie for 180 days and can be changed via a provided settings button/shortcode.
- Multilingual interface behavior: bundled German/English/Spanish/French/Portuguese/Italian translations follow the active WordPress locale in the dashboard and on the frontend (banner text is displayed as entered).
- Shortcode support for adding a “Cookie Settings” button via `[tarkop_dsgvo_button]` (e.g., in footer or privacy policy).
Distinctive features
Prior-consent blocking for recognized third-party resources (e.g., Google Analytics, Facebook Pixel, YouTube, Vimeo, Google Fonts) by making them inactive before they reach the browser until consent is granted. Consent category controls for necessary, statistics, marketing, and external media services, with restoration of accepted script/stylesheet categories after consent. Recognition of supported third-party resources when integrated via WordPress mechanisms (enqueue, inline-script, content, widget, or oEmbed filters), and outputting recognized resources without an executable/loadable source before consent. Embedded video handling: embedded videos remain blocked until the visitor clicks a load button on that video. Consent persistence: visitor choices are stored in a cookie for 180 days and can be changed via a provided settings button/shortcode. Multilingual interface behavior: bundled German/English/Spanish/French/Portuguese/Italian translations follow the active WordPress locale in the dashboard and on the frontend (banner text is displayed as entered). Shortcode support for adding a “Cookie Settings” button via `[tarkop_dsgvo_button]` (e.g., in footer or privacy policy).
Dynamic content
Dynamic or runtime content behavior remains limited to what is explicitly documented in the official plugin evidence.
SEO and metadata
SEO and metadata behavior is documented only where it is explicitly established by official plugin information.
URLs and navigation
URL and navigation behavior remains outside translation scope unless explicitly represented by the integration category.
Forms and commerce
Forms and commerce behavior is limited to factual capabilities documented for this plugin.
CONTENT BOUNDARY
Keep plugin capabilities separate from translation scope.
Current evidence documents what Tarkop DSGVO Cookie Shield does, but no specific visitor-facing content values have been approved as translation scope.
Structure, configuration, logic, integrations and runtime behavior are not translation claims.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Explore REEID Translate for multilingual WordPress workflows.
REEID separates factual plugin intelligence from evidence-backed translation scope.
No specific visitor-facing content values are currently approved for this integration.