The Four Map Data To Options
Where each answer ends up, and how to choose
Every field that asks a question has a Map Data To setting in its settings panel. It decides where that answer goes once the form is submitted.
There are four options. The one that matters most is the first, because it is the only one that produces something you can filter and segment on.
The four options
| Option | What happens to the answer | Choose it when |
|---|---|---|
| CRM Field | Written into a named field on the contact — a standard field like email or city, or one of your custom fields. A second dropdown appears so you can pick which. | You will filter, segment, report on, or use the answer in a merge tag. This is the only option that gives you that. |
| Contact Notes | Gathered into the readable note Zyntro writes on the contact. | The answer is worth reading but not worth a field — an open comment, a bit of background. |
| Profile Data | Also gathered into the readable note on the contact. | As above. In practice this and Contact Notes reach the same place. |
| Do Not Map | Nothing. The answer is kept with the completion and goes no further. | The answer only matters at the moment of submission — a confirmation, an internal routing question, something you are gathering in aggregate. |
Important: Contact Notes and Profile Data both end up in the same place: the contact's note. Zyntro reads the whole submission and writes one note in readable prose, and answers mapped to either of these two options are gathered into it. Neither puts an answer into a named, filterable field — that is what CRM Field is for. Choose either of them when you want an answer kept as readable context, and CRM Field when you want to filter, segment or report on it.
Info: Several field types ship set to Do Not Map — text, multi-line text, number, range and calculated fields among them. If you add one of these and do not change the setting, the answer will not reach the contact. This is the most common reason an answer appears to go missing.
Field types with no mapping setting
Heading
display only
optional
Asks nothing, so there is nothing to map.
Content
display only
optional
Asks nothing.
Image
display only
optional
Asks nothing.
File upload
attachment
optional
Uploads are attached to the contact record rather than mapped to a field, so no setting is needed.
Tip: A useful test for any field: would you ever want a list of everyone who answered this a particular way? If yes, it needs a CRM field. If you would only ever read it on one person's record, a note is fine.
Warning: Zyntro also fills in CRM fields nobody asked about. When a contact or custom field exists but the form did not collect it, Zyntro infers a value from the rest of the answers where it reasonably can — working out a country from a phone number, for example. This fills records out usefully, but it means a field can hold an inferred value rather than something the person actually told you. Treat anything business-critical as needing an explicit question rather than relying on inference.
Worked choices
| Question on the form | Map Data To | Why |
|---|---|---|
| What is your email address? | CRM Field → email | Identity. It is how Zyntro recognises a returning person and how anything reaches them. |
| How many employees do you have? | CRM Field → a custom field | You will segment on company size. |
| What are you hoping to solve? | Contact Notes or Profile Data | Free text, different every time. Valuable to read and to reason over, useless to filter. |
| Which service are you interested in? | CRM Field → a custom field | A list of everyone interested in one service is immediately useful. |
| How did you hear about us? | CRM Field → a custom field | Only if the options are fixed. As free text it belongs in a note. |
| Do you agree to our terms? | CRM Field → a custom field | You may need to evidence consent, which means being able to find it. |
| Anything else we should know? | Contact Notes or Profile Data | Open-ended by design. |
| Confirm you are over 18 | Do Not Map | A gate at the point of submission, not a lasting attribute — unless you need to evidence it, in which case map it. |
