- 1. Getting Started
- 2. What's New
- 3. Dashboard
- 4. Contacts
- 5. Components
- 6. Channels
- 7. Campaigns
- 8. Reports
- 9. Points
- 10. Stages
- 11. Categories
- 12. Plugins
- 13. Use Cases
- 14. Cron Jobs
- 15. SAML SSO
- 16. Themes
- 17. Translations
- 18. Tips & Tricks
- Published with GitBook
This feature was added in Mautic 2.1.0.
Progressive profiling makes your forms smarter by asking for the most important information that you don't have yet. This way your contacts won't feel overwhelmed by long forms and saves time by answering questions Mautic already knows the answer to. Progressive Profiling lets you improve the form conversion rate.
There are 2 possible ways that you can configure a form field to display only when needed. The configuration is in the Behavior tab in the field configuration form. The Behavior (Progressive Profiling) can be configured for all field types except the button field. We recommend use email field visible because it is the identifier of a contact. The button field must be always visible because otherwise the form couldn't be submitted.
It's recommended to use the email field in each form. From Mautic 2.9 email can be hidden, but be aware of that. Email as identifier of a contact could be unusable if same PC is used by more people (public library, schools...).
1. Display field only if the value is not known yet
Mautic will search for a value in 2 places before the form is rendered for the current contact:
1.1 Former form submissions
Mautic will search for the field value in the former form submissions of the current contact. If a value is found, the field might be hidden if configured so. There are limitations of the search history. Read about them below.
1.2 Contact profile values
If the form field is linked with a contact field, Mautic will check if there is a value in the contact's profile and hides the field if configured so.
2. Display field only after X submissions.
If you want to ask a contact additional questions on the second form load, you can specify so for each lead. It works nicely with hiding fields which you already know the answer to. For the first submission, the contact can be asked to fill in the First and the Last name. When she comes the second time, the First and the Last name fields will be hidden and instead she'll be asked to fill in her Company and Phone.
Limits of Progressive Profiling
The search history limit
The Mautic forms without progressive profiling are as fast as it can be. The HTML of the form is rendered once, stored and this "cached" HTML is used for the next form loads. When a progressive profiling configuration is turned on on any of the form fields, the form HTML might be different for each contact. It can even change for each contact after each submission. That's why the caching technique cannot be used anymore and the form load time will be slower for a progressive profiling form.
There is limit of 200 submissions from which Mautic searches for existing form values. This limit was added to prevent possible slow form loads or even hitting the server time or memory limits when a contact has several thousands of form submissions. This limit might cause Mautic to display/hide the wrong fields.
The embed type limit
Progressive Profiling forms will not work if you embed your form as static HTML. It will work at form preview, form public page, form embedded via JS, form embedded via iframe.
The kiosk mode limit
Progressive Profiling features are turned off if you switch the form to the Kiosk Mode. The form always creates a new contact on each submission in the Kiosk Mode. It doesn't track the device from which the form was submitted.
The Progressive Profiling options under the Behavior tab will still be accessible in the Form Builder so you could easily switch the Kiosk mode off and use the Progressive Profiling features again.