Keep these limitations and best-practice notes in mind when building and distributing forms.
Permissions
If you cannot see Forms in the sidebar, you may not have the required permission. Contact your administrator.
Submit button is required
Without a Submit block as the last action, the form will not be finalised or processed. Always confirm a Submit button is in place before publishing.
Contact matching
Matching relies on First Name + Last Name + Email. Missing or mismatched data creates a new profile instead of updating an existing contact. Encourage accurate entry of these fields, or use per-individual links / tracked email links to attribute submissions automatically.
Email-sourced responses
When a form is distributed via the email builder with tracking, an Add/Update Contact block is not required — the unique link identifies the recipient.
Subscription plans
If no plans appear in the Subscription block, they must be set up in your SwiftFox account first. Once configured, they appear under Available Plans.
Membership Data block — do not use
Do not use the Membership Data block. Use the Subscription, Payment Method and Account Payment blocks for membership and finance flows instead.
Iframe embeds
When embedding via iframe, you may need to increase the height to remove scrollbars. For Umbraco, prefer the Form ID with the SwiftFox Form block for cleaner, site-styled embedding.
Zero-total payments
You can skip payment details when the total is $0 using the Payment Method → Advanced option "Don't ask for payment details if total is $0".
Best practice
- Preview the form (and conditional logic) before publishing.
- Use Conditional Settings to keep forms short and relevant.
- Use the global Style controls for consistent typography and colours rather than styling blocks individually.
- Set a Form Expiry and closed message for time-limited campaigns.
- Clone an existing form to reuse a proven layout as a starting point.