There are two ways to feed a bridge from a form, and you should pick based on how the form was built.
The easy way, Forms Connect:
If your form was built with a WordPress form plugin, install Forms Connect from the Pro Pack and select the form as the bridge source. There is no code at all. Gravity Forms, WPForms, Contact Form 7, Elementor Pro, Ninja Forms and Fluent Forms are all supported, and submissions fire instantly.
The advanced way, a raw HTML form:
For a hand coded squeeze page, post directly to your site's admin-post.php file. You need two hidden fields: one named action with the value ws_optin, and one named rule set to the ID of the bridge you want to feed. The visitor's details go in the normal named inputs.
The fields the endpoint accepts:
- email is required. The endpoint also accepts the alternative names e and Email.
- first_name is optional. It also accepts firstname, firstName and fname.
- last_name is optional. It also accepts lastname, lastName and lname. A single field named name is split into first and last automatically.
- redirect sets where the visitor lands afterwards. A redirect_fail value handles the error case.
Which redirect wins:
If the bridge itself has a Form Redirect URL saved in its Filters and options step, that value wins over the one posted by the form.
The AWeber Legacy exception:
When a destination on the bridge is AWeber Legacy, WP Sync returns a small auto submitting form so AWeber records the opt in correctly in the visitor's own browser, and your redirect runs immediately afterwards.
Checking it worked:
Form submissions are recorded in the Activity Log with the type optin, so you can confirm every field arrived as expected.