CROzap Forms
| 开发者 | gyaner |
|---|---|
| 更新时间 | 2026年7月6日 15:08 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Contact Form 7 - connect any CF7 form. The plugin hooks the successful submission, maps the fields you choose (or auto-detects common ones), and forwards the lead. Your CF7 form keeps working exactly as before.
- WPForms - connect any WPForms form the same way.
- Captures
gclid(Google Ads) andfbclid(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, for 30 days.
- Reads the Meta pixel
_fbc/_fbpcookie 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.
安装:
- Upload the plugin files to
/wp-content/plugins/crozap-forms/, or install through the WordPress plugins screen. - Activate the plugin.
- Go to Settings, CROzap Forms.
- Paste your CROzap API key (in CROzap: Settings, Ad Connections, API Key) and save; the connection test runs automatically.
- Connect your Contact Form 7 and/or WPForms forms in the mapping tables and save.
常见问题:
Where do I get an API key?
Log in to your CROzap account and open Settings, Ad Connections, API Key. The key is stored on your server via the WordPress Options API and is never exposed to visitors' browsers. The settings page shows a short fingerprint (first and last characters) of the saved key so you can verify the right key is stored, and rejects values that are not CROzap-shaped keys.
Does the plugin load anything from CROzap or other external servers in the browser?
No. All scripts and styles are bundled locally. The only external communication is the server-side API call that delivers the lead.
What cookies does it set?
When a visitor lands on a URL containing ad parameters, the plugin sets first-party cookies to preserve attribution: crozap_gclid and crozap_fbclid (90 days) and crozap_utm_* (30 days). It also reads (never sets) the _fbc / _fbp cookies if your own Meta pixel created them.
What happens if CROzap is down when a form is submitted?
The visitor's Contact Form 7 or WPForms submission completes normally. The lead is queued locally and retried automatically (up to 3 attempts, deduplicated on the CROzap side), and a notice is shown on the settings page if delivery keeps failing.
Do phone numbers need a country code?
Yes, ideally (for example +91 98765 43210). CROzap normalizes numbers to E.164; a bare 10-digit number is assumed to be Indian (+91).
Does it work with caching plugins?
Yes. The integrations hook the server-side form processing of Contact Form 7 and WPForms, which page caching does not affect.
更新日志:
- Brand display name standardized to CROzap; add Plugin URI; update Author URI to webmonx.com.
- Bump tested-up-to to WordPress 7.0; remove manual textdomain loading (WP.org auto-loads translations).
- Filter out reCAPTCHA tokens and form-system fields from lead custom fields (g-recaptcha-response, hCaptcha, Cloudflare Turnstile, Contact Form 7 _wpcf7* internals). The exclusion list is filterable via crozap_excluded_fields.
- Fix: add concatenation guard to frontend script so it is safe when a JS optimizer combines scripts (prevents a theme/reCAPTCHA conflict on sites using Combine JS).
- Focus on Contact Form 7 and WPForms integrations; the built-in lead form (shortcode + block) is deferred to a future version.
- API key safety: values that are not CROzap-shaped keys (UUIDs) are rejected on save and the previous key is kept, so browser password-manager autofill can no longer silently replace a working key.
- Saved-key fingerprint on the settings page (first and last characters only) so you can verify which key is stored.
- The API key field defeats aggressive browser autofill (readonly until focused).
- The connection test runs automatically after saving a new key.
- Initial release: built-in lead form (shortcode + block), Contact Form 7 and WPForms integrations, click-id capture (gclid, fbclid, _fbc, _fbp), UTM capture, visitor IP forwarding, retry queue, Test connection.