This is a spike issue to research and finalize the engineering approaches for Phase 2: Form Infrastructure & Compatibility. Details are provided below
What We're Delivering
The backend foundation that makes per-form analytics possible, paired with a compatibility strategy that accounts for every type of form C1s use today — without disrupting any of them.
Why Not a New Form Builder?
A standalone form builder outside the block system would require us to maintain two separate form experiences, create confusion for C1s, and accumulate debt as WordPress continues evolving. The block system is where WordPress is going. We build there.
Key Capabilities
- Per-Form Data Layer: Each individual form instance gets its own tracking record — the direct prerequisite for Phase 3
- Stable Form Identifiers: Each block form gets a persistent ID that survives edits and page updates
Form Compatibility Strategy
The plugin supports two types of forms today. Each gets its own treatment:
Existing Block Forms Block forms already exist but lack per-form tracking. We migrate them to the new data layer automatically — C1s see no interruption and take no action. This should have little to no risk.
Shortcode Forms A meaningful portion of C1s — particularly those not using the modern block editor — built their forms using shortcodes. We do not force them to change. Shortcode forms remain fully supported.
- We also evaluate whether shortcode forms can participate in per-form analytics without requiring migration to blocks.
- C1s who want to move to block forms get a clear, assisted path to do so.
What doesn't change for any C1: No live form breaks. No forced migration. Every change is invisible or opt-in.
This is a spike issue to research and finalize the engineering approaches for Phase 2: Form Infrastructure & Compatibility. Details are provided below
What We're Delivering
The backend foundation that makes per-form analytics possible, paired with a compatibility strategy that accounts for every type of form C1s use today — without disrupting any of them.
Why Not a New Form Builder?
A standalone form builder outside the block system would require us to maintain two separate form experiences, create confusion for C1s, and accumulate debt as WordPress continues evolving. The block system is where WordPress is going. We build there.
Key Capabilities
Form Compatibility Strategy
The plugin supports two types of forms today. Each gets its own treatment:
Existing Block Forms Block forms already exist but lack per-form tracking. We migrate them to the new data layer automatically — C1s see no interruption and take no action. This should have little to no risk.
Shortcode Forms A meaningful portion of C1s — particularly those not using the modern block editor — built their forms using shortcodes. We do not force them to change. Shortcode forms remain fully supported.
What doesn't change for any C1: No live form breaks. No forced migration. Every change is invisible or opt-in.