Forms
Workflows

Pre-filling forms for targeted contacts

Auto‑fill targeted SwiftFox forms, manage field display and avoid unwanted contact overwrites.

July 7, 2026
ID:
373

When SwiftFox already knows who is completing a form — a targeted form — it can automatically pre-fill that contact's details. This removes the need to ask for basic identity information such as name and email, and ensures the submission is linked to the right Contact profile.

Targeted forms are recognised whenever the respondent's identity is known: through Emails sent to a known contact, through per-individual preview and publish links, and through the Login portal where the user is signed in. In all of these cases SwiftFox can identify the respondent and apply the response to the correct profile.

What this feature does

  • Automatically pre-fills contact details on targeted forms.
  • Controls how contact fields appear using display settings on the Add/Update Contact block.
  • Supports multiple targeted entry points — email, per-individual links and the Login portal.
  • Prevents accidental overwriting of contact details when a form is forwarded.
  • Allows a new profile to be created when the respondent is not the targeted contact.

Targeted form entry points

A form is treated as targeted when SwiftFox already knows the respondent. This includes:

  • Forms opened from an email sent to a known contact.
  • Forms generated for a specific individual via Preview and Publish (per-individual links — see Success page & publishing).
  • Forms accessed inside the Login portal, where the user is signed in.

In these cases, responses automatically apply to the contact profile and do not require an Add/Update Contact block to identify the person.

Block display Settings

When you edit an Add/Update Contact block, a Block display Settings section appears on the right-hand side. This controls how contact details are shown to the targeted contact (the recipient of an email, or a logged-in Login portal user). There are three display options.

Option 1 — Show all contact fields (default)

This is the default behaviour.

  • All contact fields are shown.
  • First name, last name and email are pre-filled.
  • The respondent can see exactly which profile they are submitting as.

Option 2 — Show contact name only

This option displays a single line showing the contact name, for example: Name Test Profile, not you click here to add your details.

  • The respondent can confirm whether they are the targeted person.
  • If they indicate it is not them, they can enter new details.
  • A new contact profile is created instead of overwriting the original one.

This is especially useful for event RSVP forms that are forwarded, preventing unintended updates to the original contact record.

Option 3 — Hide all contact fields

  • No contact details are shown on the form.
  • Only the form questions are visible.
  • SwiftFox still records which contact submitted the form.

Login portal form behaviour

Forms embedded in the Login portal are automatically targeted because the user is logged in. Auto-fill ensures:

  • Contact details are already known.
  • No duplicate forms are needed for portal versus public use.
  • A single form can be reused across email, Websites and Login portal contexts, adapting based on whether the respondent is known or anonymous.

FAQs

What is a targeted form?

A form where SwiftFox already knows who the respondent is — for example via an email link or Login portal sign-in.

Can a forwarded form create a new contact instead of overwriting one?

Yes. Use the Show contact name only option so the respondent can indicate it is not them and create a new profile.

Does hiding contact fields stop profile matching?

No. SwiftFox still matches the submission to the correct contact behind the scenes.

Can the same form be used for the Login portal and a website?

Yes. Auto-fill lets one form adapt based on whether the respondent is known or anonymous.