
SP LEAD INSIGHTS FOR CONTACT FORM 7
SP Lead Insights for Contact Form 7 compatibility with REEID Translate
SP Lead Insights for Contact Form 7 compatibility with REEID Translate is being reviewed using official plugin documentation. Tracks Contact Form 7 form views and submissions per form, with conversion rate calculated and shown in the WordPress dashboard No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What SP Lead Insights for Contact Form 7 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
SP Lead Insights for Contact Form 7 is documented in the Analytics 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 SP Lead Insights for Contact Form 7 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
- Tracks Contact Form 7 form views and submissions per form, with conversion rate calculated and shown in the WordPress dashboard
- Provides a dashboard widget showing the top 5 forms by conversion rate (including views and submissions)
- Stores a full submission log including date, form name, and delivery status
- Implements an email domain blocklist that rejects submissions from blocked domains with a validation error and records blocked attempts with timestamps and reasons
- Uses honeypot spam protection that is enabled by default
- Stores only event metadata (e.g., form ID, event type, delivery status) and stores IPs as one-way HMAC-SHA256 hashes keyed to the site’s `AUTH_SALT` (raw IPs are not saved)
- Uses a lightweight async JavaScript beacon for view tracking that fires after page load and does not block rendering
- Claims zero outbound HTTP (“nothing phones home”) and no Google Analytics/API keys/data leaving the server
TRANSLATION BOUNDARY
SP Lead Insights for Contact Form 7 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
SP Lead Insights for Contact Form 7 and REEID Translate FAQ.
What does SP Lead Insights for Contact Form 7 do?
SP Lead Insights for Contact Form 7 has 8 documented features listed in its official documentation. See the Plugin Information section for details.
Does SP Lead Insights for Contact Form 7 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 SP Lead Insights for Contact Form 7?
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 SP Lead Insights for Contact Form 7 in a multilingual WordPress workflow.
REEID documents SP Lead Insights for Contact Form 7 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.