Understand form structure and actions

A POM form has two complementary parts: a visual layout that collects values and a configuration that decides what happens after validation.

Read the layout hierarchy

Form
└── Step
    └── Row
        └── Column
            └── Field

• A Step is one stage. Even a single-screen form has a step.
• A Row keeps related columns together.
• A Column controls responsive width.
• A Field collects a value or adds structural content.

Fields are stored separately from their placement in the layout. Every field must belong to a column to appear on the frontend.

Separate labels from identifiers

The visible Label explains the question to visitors. The Name is the stable identifier used by submissions, merge tags, conditions, notification recipients, webhooks, and post mappings.

For example:

Label: Email address
Name: contact_email
Merge tag: {{field:contact_email}}

Use unique lowercase names with underscores. Changing the label is presentational; changing the name changes the references that consume the answer.

Know which fields collect data

Text, Email, Phone, URL, Number, Textarea, choice, date/time, upload, and Hidden fields can contribute values. Heading, HTML, and Submit Button are structural and do not provide field merge tags.

A Hidden field is browser-submitted context, not proof of identity, authorization, price, or payment.

Understand the AJAX action pipeline

With AJAX (No page reload) selected under Messages/Behavior → Submission Behavior, POM Forms:

1. Resolves conditional field visibility.
2. Validates and sanitizes visible values.
3. Processes verified uploads.
4. Stores the submission when enabled.
5. Evaluates notification routes.
6. Sends the webhook when enabled.
7. Creates WordPress content when enabled.
8. Returns the success message and optional redirect.

Values belonging to fields hidden by conditional logic are removed before storage, notifications, webhooks, or post creation.

Webhook, notification, storage, or post-creation delivery is a separate result from field acceptance. Monitor every required destination instead of treating the visitor’s success message as proof that an external system completed its work.

External action modes are different

Form Action URL (GET) and Form Action URL (POST) forward validated values to another endpoint. They bypass internal submission storage, notifications, the Webhook tab, Google Drive uploads, and post creation.

Use an action mode only when the receiving endpoint owns the workflow. Use AJAX mode for normal POM Forms processing.

See Form fields, Notifications and storage, and Integrations.