About this plugin
CROzap Forms connects your WordPress site to CROzap, a lead management and ad attribution platform. Every lead a connected form captures is sent to your CROzap account, together with the ad click identifiers that let CROzap fire conversion signals back to Google Ads and Meta when the lead qualifies.
Seven form integrations:
- Contact Form 7
- WPForms
- Gravity Forms
- Fluent Forms
- Forminator
- Ninja Forms
- Elementor Forms (part of Elementor Pro)
Connect any form from any of these builders. The plugin hooks the successful submission, maps the fields you choose (or auto-detects them), and forwards the lead. Your form keeps working exactly as before, and a CROzap failure never affects the visitor’s submission.
Each integration stays completely dormant unless its form plugin is active. These are third-party plugins owned by their respective authors; this plugin is not affiliated with or endorsed by any of those projects. A built-in lead form (shortcode + block) is planned for a future version.
Field auto-detection that actually works
For each connected form you can set which field holds the name, email and phone, or leave the mapping blank. When it is blank the plugin first looks for a field of the matching type, and then falls back to matching the field’s visible label (for example a label containing “phone”, “mobile” or “whatsapp”). That second step matters: many forms are built from plain text fields rather than the builder’s dedicated Name/Email/Phone fields, and a type-only lookup finds nothing in those forms.
If a connected form is submitted and no name, email or phone can be identified, the settings page now tells you so instead of failing quietly.
Ad attribution built in (the reason this plugin exists):
- Captures gclid (Google Ads) and fbclid (Meta) from the landing page URL and persists them in first-party cookies for 90 days, so a visitor who lands on one page and submits a form on another still carries the click id.
- Captures UTM parameters (utm_source, utm_medium, utm_campaign, utm_content, utm_term) the same way.
- Reads the Meta pixel _fbc / _fbp cookie values when your site’s own Meta pixel has set them (the plugin loads nothing from Meta).
- Forwards the visitor’s real IP address so attribution and consent records in CROzap reflect the visitor, not your hosting server.
With those click ids stored on the lead, CROzap fires the matching conversion signal (Google offline conversion or Meta CAPI event) back to the originating ad network when your team qualifies the lead – closing the ad optimization loop for leads captured on your WordPress site.
Resilient by design: if CROzap is temporarily unreachable, the visitor’s form submission completes normally and the lead is queued and retried automatically. Nothing external is ever loaded in the browser; the only outbound connection is the server-side API call to CROzap.
External Services
This plugin connects to the CROzap API, an external service operated by WebMonx Solutions LLP. You need a CROzap account and API key to use it.
com): name, email, phone, message and any other submitted form fields (sent as custom fields), the campaign name you configured, UTM parameters (utm_source, utm_medium, utm_campaign, utm_content, utm_term), ad click identifiers (gclid, fbclid, and the Meta pixel _fbc / _fbp cookie values when present), the URL of the page the form was submitted from, the consent status, the visitor’s IP address, and a site platform label (source_detail, default “wordpress”).
The “Test connection” button on the settings page sends an empty authentication check to the same API. No data is sent to CROzap on any other page view.
Why: CROzap is a lead management and ad attribution platform; this data is required to create the lead in your CROzap account and attribute it to the ad click that produced it.
- CROzap Terms of Service: https://crozap.com/terms/
- CROzap Privacy Policy: https://crozap.com/privacy/
Disclose this data flow in your own site’s privacy policy, and use the per-form consent option where your jurisdiction requires consent.