Entities and Custom Fields from Forms
Populating the organisation as well as the person
A contact is a person. An entity is the organisation they belong to. A single submission can populate both, and which record an answer lands on depends on how the field was defined rather than anything you set on the form.
Which record an answer lands on
| Kind of field | Where it goes |
|---|---|
| A standard contact field | The contact — name, email, phone, address, timezone and the rest. |
| A standard entity field | The linked entity — its name, label, location, website, tags and social profiles. |
| A custom field defined against the contact | The contact. This is set when you create the custom field, not on the form. |
| A custom field defined against the entity | The entity. |
Info: You do not choose contact or entity on the form. The CRM Field dropdown lists both kinds, and each field already knows which record it belongs to from how it was defined. If an answer is landing on the wrong record, the custom field's own definition is what to change.
How CRM mode affects submissions
| CRM mode | Effect on a form submission |
|---|---|
| B2B | Entity data from the form is used, and an entity is created or matched alongside the contact. |
| Hybrid | The same as B2B. Entity data is used where the form collected it. |
| B2C | Entity creation is skipped. Any entity data the form collected is not written, because the mode says you deal with individuals. |
Warning: In B2C mode, entity answers collected by a form are discarded. The submission still succeeds and the contact is still created — the organisation data simply is not written. If you are in B2C mode and want to record something about where somebody works, use a contact custom field rather than an entity field.
What else Zyntro sets on the contact
Source
text
required
The form's name. This is how you tell which form produced a contact, and it is also what the lead rotation counts — so renaming a form restarts those counts.
Tags
text
optional
Taken from a tag answer if the form collected one, otherwise the form's name.
Email verified
flag
optional
Set when the submission supplied an email address, with a note recording that it came from a form completion.
Phone verified
flag
optional
Set when the submission supplied a phone number, recorded the same way.
Owner
member
required
Decided by the form's allocation. An existing contact keeps the owner they already had.
Attachments
files
optional
Uploaded files, attached to the contact and labelled with the form and field they came from.
Tip: Create the custom fields you need before building the form. The CRM Field dropdown can only offer fields that already exist, and adding them afterwards means revisiting every field you wanted to map.
