-
Re: Different form requirements for known vs unknown people?
Let's be specific about "the lead is known." Do you mean
- their tracked Munchkin session is already associated with a known lead in your database due to previous activity (earlier form fillout, clicked Marketo email)
or
- their session is anonymous, but they begin to enter data that, if posted, would be merged with a known lead
-
Re: Different form requirements for known vs unknown people?
The second option, we would be looking for them to complete their existing profile.
-
Re: Different form requirements for known vs unknown people?
If their session is anonymous, you cannot know until they've filled out the form that they would be merged with an existing record.
Hence you have no idea, at the time they first see the form, how many fields to display.
Forms can switch fields depending on the characteristics of an existing associated session (hiding the form if the session is associated, for example, or displaying only empty fields). This is what Progressive Profiling and other features are all about. But it can't work when the server hasn't seen the person yet. Does this make sense?
-
Re: Different form requirements for known vs unknown people?
Yes, that does make sense, thank you!
Can you explain how to only display empty fields?
-
Re: Different form requirements for known vs unknown people?
Read up in the docs and previous Community posts on Progressive Profiling.
-
-
-
