
INDIETECH POPUP BUILDER
IndieTech Popup Builder compatibility with REEID Translate
IndieTech Popup Builder compatibility with REEID Translate is being reviewed using official plugin documentation. Gutenberg editor-based popup content creation with WordPress blocks (content configured in the document sidebar). No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What IndieTech Popup Builder 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
IndieTech Popup Builder is documented in the Other category with 8 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 IndieTech Popup Builder 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
- Gutenberg editor-based popup content creation with WordPress blocks (content configured in the document sidebar).
- Multiple popup trigger modes including page-load immediate, time delay, scroll-percentage, exit intent, and click-to-open via a CSS class on elements.
- Targeting rules with include/exclude logic by page/post IDs and URL prefixes, plus options for all pages, homepage, and CPT single; exclusions are applied first and popup shows only when include matches and no exclude matches.
- Cookie-based frequency control with configurable duration (days) and cookie set timing (on close or on seen).
- Popup behavior controls including closing when clicking outside the overlay and an option to disable page scroll while the popup is open.
- Styling and layout options including a 9-position matrix placement, max width, overlay opacity, and close-button placement (inside/outside/hidden).
- Optional analytics tracking for popup open/close/CTA clicks supporting direct GA4 (gtag.js) and Google Tag Manager (dataLayer).
- Optional Gravity Forms integration to set a permanent cookie and auto-close the popup after a successful form submission inside it.
TRANSLATION BOUNDARY
IndieTech Popup Builder 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 context. Visitor-facing translation scope is not listed for this category.
FREQUENTLY ASKED QUESTIONS
IndieTech Popup Builder and REEID Translate FAQ.
What does IndieTech Popup Builder do?
IndieTech Popup Builder has 8 documented features listed in its official documentation. See the Plugin Information section for details.
Does IndieTech Popup Builder 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 IndieTech Popup Builder?
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 IndieTech Popup Builder in a multilingual WordPress workflow.
REEID documents IndieTech Popup Builder 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.