CROZAP FORMS
CROzap Forms compatibility with REEID Translate
CROzap Forms compatibility with REEID Translate is being evaluated from available plugin evidence. Connects WordPress forms to CROzap for lead management and ad attribution. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for CROzap Forms.
Official documentation did not establish a visitor-facing content item within the supported scope for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
CROzap Forms is documented in the Forms category with 5 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How CROzap Forms compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Connects WordPress forms to CROzap for lead management and ad attribution.
- Sends captured lead data (including name, email, phone, message, and other submitted fields) to the CROzap API when a connected form is submitted.
- Captures and persists ad click identifiers (gclid, fbclid) and UTM parameters for attribution.
- Reads Meta pixel cookie values (_fbc / _fbp) when present and forwards them with the lead.
- Queues and retries lead delivery if CROzap is temporarily unreachable, without affecting the visitor’s form submission.
CONTENT BOUNDARY
CROzap Forms capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- No visitor-facing translation surface was established for this integration.
COMMON QUESTIONS
CROzap Forms and REEID Translate FAQ.
What does CROzap Forms do according to the available plugin evidence?
CROzap Forms has 5 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for CROzap Forms?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for CROzap Forms?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate CROzap Forms in a multilingual WordPress workflow.
REEID documents CROzap Forms functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.