Compare Publishing Options 

Use FormAssembly hosted form

• This is the easiest and quickest option. After saving your form in the Form Builder, it is available at the public link found in the form's Publish tab.
• The public form link remains the same even after changes are made in the Form Builder, so the public form link will always direct respondents to the most recent version of your form.

• The form will be accessed at the FormAssembly hosted link with tfaforms.com as the domain name.
• The form will be separate from your external webpage.

Yes

Embed HTML

• You can make very specific changes to your form's HTML, which can also complicate things down the road. 

• You must be comfortable working with HTML.
• You must re-publish after all Form Builder changes.
• Saved forms and failed CAPTCHAs will load at the FormAssembly-hosted form.
• Form CSS can clash with the parent site's CSS.

No

iFrame

• The iframe will protect the form's CSS from inheriting the parent site's CSS.
• Changes made in the Form Builder will update automatically.

• You should be comfortable working with HTML.
• Saved forms and failed CAPTCHAs will load at the FormAssembly-hosted form.
• Prefilling will not work with an iframe unless you add the prefill parameters to the source link.
• When using iFrame and Pardot together, iFrame will prevent collecting visitor data.

Yes
_{*See Note}

Server-Side Script (API) /

WordPress Plugin

• Doesn't need to be republished every time you make changes in the Form Builder. 
• Appears as part of the page, as opposed to iframe where it looks like a separate page on the page.
• Save and Resume, as well as a failed CAPTCHA, return to your site.

• Form CSS can clash with the parent site's CSS.
• You should have an understanding of web servers.
   

Yes
_{*See Note}