NODD CONSENT
nodd Consent compatibility with REEID Translate
nodd Consent compatibility with REEID Translate is being reviewed using official plugin documentation. Blocks Google Analytics, Tag Manager, Ads, Meta Pixel, LinkedIn, TikTok, Hotjar, and Microsoft Clarity scripts until user consent is granted. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What nodd Consent does
Official plugin information supports the compatibility context documented for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
nodd Consent is documented in the Analytics category with 6 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How nodd Consent compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- Blocks Google Analytics, Tag Manager, Ads, Meta Pixel, LinkedIn, TikTok, Hotjar, and Microsoft Clarity scripts until user consent is granted.
- Injects a consent banner on all front-end pages before any tracker loads to manage cookie preferences.
- Sends Google Consent Mode v2 signals based on the visitor's recorded choices.
- Integrates with WordPress privacy policy links (footer, registration, checkout) to point to the nodd Privacy Center.
- Provides a shortcode `[nodd_privacy_settings]` to allow visitors to update their consent choices post-initial-load.
- Requires an external nodd account and site key for functionality; does not operate independently without this connection.
TRANSLATION BOUNDARY
nodd Consent capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility. No specific content shown to visitors is confirmed for translation in this category.
FREQUENTLY ASKED QUESTIONS
nodd Consent and REEID Translate FAQ.
What does nodd Consent do?
nodd Consent has 6 documented features listed in its official documentation. See the Plugin Information section for details.
Does nodd Consent have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from nodd Consent?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate nodd Consent in a multilingual WordPress workflow.
REEID documents nodd Consent functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.