Form Pages settings (slug, headline, sub-headline, CTA, theme) live in postmeta on the wpforms form post. SleekView reads the form post's meta as part of the join. Entries don't carry this data directly; they carry the form_id, and the join surfaces the page settings.

UTM parameters arrive on the landing-page URL. To make them attributable per entry, the form must capture them as hidden fields. WPForms supports this via field defaults referencing query parameters. SleekView's pivot of wpforms_entry_fields exposes those captured values as filterable, sortable columns.

If the form captures referrer to a hidden field (configured via custom code or a tracking add-on), SleekView surfaces it as a column. WPForms doesn't capture HTTP referrer by default; this is a form-setup choice. Once captured, it joins the same pivoted columns as any other entry field.

No. Form Pages is a rendering mechanism; submissions hit the same wp_wpforms_entries, wp_wpforms_entry_fields, and wp_wpforms_entry_meta tables as inline-form submissions. The only Form-Pages-specific data is on the form post, in the page settings postmeta.

If you've created two Form Pages (two different forms with different slugs and copy), each entry's form_id identifies which one was submitted. SleekView's grouping on form_id with a custom variant-label column shows side-by-side conversion. WPForms doesn't have native A/B testing; the comparison happens at the entry-aggregation level via SleekView.

Conversational Forms is a rendering add-on like Form Pages; submissions still land in the same entry tables. SleekView's view works the same; if both Form Pages and Conversational Forms are active on different forms, a single SleekView can show entries from both with a rendering-mode column indicating which add-on rendered each.

Yes. Add a SleekView-managed lead-status column ("Hot", "Warm", "Cold", "Disqualified") and edit cells inline. Writes go to wp_wpforms_entry_meta with audit logging. Bulk updates iterate via the WPForms admin API so registered hooks fire normally.

wpforms_entries filters on form_id are indexed; the per-page count is fast even with millions of rows. The Form-Pages slug join is a single lookup against the form post. SleekView's per-page report is real-time; no separate aggregation table or scheduled rebuild is involved.