7 Replies Latest reply on Jun 4, 2015 10:07 PM by Sanford Whiteman

    Show specific field or fields to Known Leads in custom HTML?

      Is there a useful/scalable method for showing a Known Lead at least one field via custom HTML in a 2.0 form? The use case would be this:

      Visitor to our site is a known lead, but we want them to be able to enter a datetime in an "Appointment date"  field for a sales consultation, and ensure it displays persistently as an editable field.
        • Re: Show specific field or fields to Known Leads in custom HTML?
          Hi Scott, am I right that you want to hide this field for unknow leads? Only to have it visible for know leads. If so I might be able to help. I only want to show our opt-in checkbox for people that are not opt-in yet. We don't want opt-in leads to uncheck the box. I have created an additional field in our database, which is auto-populated by a trigger to copy the value of the real opt-in field. In Forms2.0 I have the copy-field as hidden field and auto-populated with the database value of course. Next I set up a visibility rule for the real opt-in field to only show if the copy-field value is not true.
          • Re: Show specific field or fields to Known Leads in custom HTML?
            Thanks for your reply, Diederik.

            What I want to have happen is for this field to persistently show, regardless of whether the lead is known or not. An unknown lead would receive the full form, but a known lead would receive the "Welcome back, Lead Name!" salutation, along with the Appointment field.
            • Re: Show specific field or fields to Known Leads in custom HTML?
              Ahh, you're using the option "If Known Visitor, Show" to show Custom HTML in stead of the form. I had the same issue with my Email Preference Center. What I did is to create a new segmentation in Lead Database (Default: Email is not empty | Other segment: Email is empty). This kind of gets you two segments. On your landing page segment the form with this new segment. Next you show form1 to known lads and form2 to unknown leads. Form2 would be the full form. Form1 would just be your appointment field. It's a bit of a workaround, but it worked for me.
              • Re: Show specific field or fields to Known Leads in custom HTML?
                That's a great idea, Diederik. What about setting up a boolean field to test true/false on whether the form was filled out previously, and then using the logical flow you suggested? 
                • Re: Show specific field or fields to Known Leads in custom HTML?
                  That's a posibility too. But that does mean you wil lhave to create a field per form.
                  • Re: Show specific field or fields to Known Leads in custom HTML?
                    Jan Vacek

                    HI all,

                     

                    thanks for tips. Could you please advice me how can I recognize who is coming to my landing page whether it is unknown lead or known lead? Should I use any javascript that recognizes this or how?

                     

                    Thanks a lot,

                    Jan

                      • Re: Show specific field or fields to Known Leads in custom HTML?
                        Sanford Whiteman

                        There is no supported programmatic way to determine whether the current cookie is associated (there are undocumented methods but they are not guaranteed to work at later points in time).

                         

                        However, you can take advantage of the same Known Lead Substitute HTML feature we're discussing here to determine whether known/anonymous.  Load a hidden "detector" form that is set to use HTML if known.  Then check to see if the custom HTML element is present in the form or not.

                         

                        You can branch this same logic to solve your problem.  Load the detector form to see if the lead is known or not, and load the real form and hide/show fields based on the outcome of the detection.

                         

                        The way I see it, this task does not require segmentations.