Review: MetForm and its integrations

This is a test site for several services. It shows the draft templates of four ClickUp tickets around the form plugin MetForm, grouped by ticket below, so all of them can be checked in one go. Every template is created on this site (Cookies > Services and Cookies > Content Blocker). Each page holds one MetForm form and tests one rule or function. Open a page in a private window to see the visitor’s view: the cookie banner first, then the page before and after consent.

1. MetForm (ticket)

Service „MetForm“ for the form functions and its content blocker, which holds every MetForm form until consent.

PageRuleBefore consentAfter consent
Store Entries and Redirect Form Datadiv[class*="mf-form-wrapper"]Content blocker „MetForm“ instead of the formSending stores the entry, sets the 15-minute cookie bWYtY29va2ll and opens the thank-you page with name and e-mail in the address
Save Form Progressdiv[class*="mf-form-wrapper"] and *metform-pro/build/frontend/form-builder/save-progress.js*Content blocker, save-progress.js not loaded, nothing in local storageTyped values in local storage under metform-<form id>
Count viewsdiv[class*="mf-form-wrapper"]Content blocker, no request to /forms/views/One request to /wp-json/metform-pro/v1/forms/views/<form id> per display (form built with Elementor, the only kind Count views reaches)
Google Map Location fielddiv[class*="mf-form-wrapper"] and the existing content blocker „Google Maps“ (*maps.googleapis.com*)Content blocker „MetForm“, nothing from Google MapsWith „MetForm“ only: the form, the address field without suggestions, the map area empty, still nothing from Google. With „Alle akzeptieren“: map and address suggestions
Control: form without consent-relevant functionsdiv[class*="mf-form-wrapper"] onlyContent blocker „MetForm“: whether Store Entries is on cannot be seen before sending, so every MetForm form waits (see the page)Sending sets no MetForm cookie and sends nothing to Google, IPinfo or MetForm’s statistics

2. MetForm Statistics (ticket)

Service „MetForm Statistics“ for the form statistics of MetForm Pro and its content blocker, which holds the statistics script in the background.

PageRuleBefore consentAfter consent
Form Analytics*metform-pro/build/frontend/analytics/tracking.js*Content blocker „MetForm“, no tracking.js, no mf_analytics_*, no track_viewWith „MetForm“, „MetForm Statistics“ and „IPinfo“: cookie mf_analytics_<form id>, mf_session_<form id> and the track_view request. Without „IPinfo“: nothing is sent

3. MetForm with Google reCAPTCHA (ticket)

Integration content blocker of the service „Google reCAPTCHA“ for MetForm’s reCAPTCHA field (v2 and v3).

PageRuleBefore consentAfter consent
Google reCAPTCHA v2 checkboxdiv[class*="mfb-recaptcha__wrapper":visualParent(value=form),confirm(),…]Content blocker „MetForm“, nothing from GoogleAfter „MetForm“ only: form without reCAPTCHA, a click into it asks for „Google reCAPTCHA“, then the checkbox. „Alle akzeptieren“: checkbox at once
Google reCAPTCHA v3same ruleContent blocker „MetForm“, nothing from GoogleSame as v2, with the reCAPTCHA badge, sending passes Google’s check

4. ipinfo.io with MetForm (ticket)

Integration content blocker „MetForm with IPinfo“ of the service „IPinfo“: the country lookup that MetForm Pro’s Form Analytics script makes on page load.

PageRuleBefore consentAfter consent
Form Analytics: IPinfo country lookup on page load*metformAnalyticsTracking*No request to ipinfo.io, also after consent to „MetForm“ and „MetForm Statistics“ aloneAfter consent to „IPinfo“ as well: one request to ipinfo.io/json when the page loads, then the statistics request with the country

Placeholders and test setup

Placeholder: Every form waits behind the content blocker „MetForm“. „MetForm Statistics“ and „MetForm with IPinfo“ have no placeholder of their own, because they hold back a background script with nothing visible to replace, and the form itself is held by „MetForm“. „MetForm with Google reCAPTCHA“ shows the form and asks for consent on the first click into it.

Test setup: Save Form Progress, Form Analytics and the reCAPTCHA version are site-wide MetForm settings. A small test plugin on this site switches each of them on only on its own page above, so every page shows one function. In wp-admin the settings show what is stored: Save Form Progress on, Form Analytics on, reCAPTCHA v2. Elementor is active only because Count views reaches only forms built with it.

Scanner

The Real Cookie Banner scanner (Cookies > Scanner) finds „MetForm“ on every test page and on no other page (not on this index, the thank-you page, the start page, the privacy policy, the imprint or the sample post). It finds „MetForm with Google reCAPTCHA“ only on the two reCAPTCHA pages, „MetForm Statistics“ and „MetForm with IPinfo“ only on the analytics and IPinfo pages, and „Google Maps“ only on the Google Map Location page. The other suggestions on this site („WordPress Emojis“ on every page, „WordPress Comments“ on the sample post) come from WordPress itself.