Forms
Lead tracking through the supported form plugins, and why it is server-only.
updated
Outline — facts still to be confirmed
This article is a structured outline. Its headings and scope are settled; the
specific values, screens and steps are marked TODO(owner: verify)
until they have been checked against the plugin itself. Blueprint §7 is explicit
that no article may state plugin behaviour that has not been verified.
Why Lead is server-only
Form plugins have no way to hand the server’s event ID to the page, so a browser-side Lead would carry a different ID and double every submission. A server-only Conversions API event is valid and counts. See Lead.
Supported form plugins
Contact Form 7, WPForms and Gravity Forms are integrated, with Fluent Forms added later.
TODO(owner: verify) — confirm the complete supported list in the shipped build, and the minimum version of each.
Outline still to fill
Mapping form fields to customer data
TODO(owner: verify) — how email, phone and name are located in a submission, and what happens when a form has several candidate fields.
Per-form control
TODO(owner: verify) — whether individual forms can be excluded, and how a form is identified in settings.
Verification status
TODO(owner: verify) — which form plugins have been confirmed end to end on a live site. Only Contact Form 7 has been verified in a controlled environment so far; the rest are unconfirmed.
Was this page helpful?