Progressive Profiling

[Anonymous]

I'm trying to set up Prog Pro and seem to be running into trouble. I see your comments on every post I come across on the topic, so figured you may be a good resource! I've set up the form and put it on two test landing pages, but each time I go to the LP the form is still showing the same three fields and none of the prog pro fields are showing up for me. Any ideas on how to troubleshoot?

Here are our URLS

Test page 1 --> Certara | Form

Test page 2 --> Certara | Form

[Erik_Eaton]

Hey Megan,

It looks like it is working - I filled out the form and reloaded the page and job role showed up after the initial submission. What are you trying to get the form to do for progressive profiling? Can you get a screenshot of the set up? might help in determining how to achieve your goal with the progressive profiling.

[SanfordWhiteman]

Megan's form is set to show one empty ProgPro field from these fields, in order:

Company Name

Job Role

Department

Job Title, conditional on Department value

Phone

The VRs on Job Title will eventually cause confusion.  But, like you, I'd like to hear at which point Megan believes it isn't functioning.

[Anonymous]

Thank you both for looking into this! I tested multiple times and was getting the same three fields everytime I reloaded the page. Sanford, I agree that it's eventually going to cause confusion that Title is dependant upon Department. Do you have any suggestions on how to work around this?

[SanfordWhiteman]

Sanford, I agree that it's eventually going to cause confusion that Title is dependant upon Department. Do you have any suggestions on how to work around this?

Well... it's not just confusing as a setup, it flatly won't work as-is. (I was understating it. )

You can't have a 2nd field's visibility depend on a 1st field, where the 1st field may be skipped entirely by Progressive Profiling rules. (You can have a field that depends on a Hidden field, just not on a skipped field.)

What happens in this case is because the 1st field (Department) does not exist in the form when it's skipped, the 2nd field (Job Title) doesn't fulfill its dependency on the 1st. So the 2nd remains permanently in "pending Visibility Rule" state, where it is not visible. Yet because it is empty, the form will not progress beyond it.

You need custom JavaScript to solve this conflict.

[Anonymous]

Thanks, Sanford.

So say we want to keep our regular forms on some pages (say our contact us form) and put prog prof forms on other pages. Since I would still need the visibility rules on department and title for our normal form what would I do in order to get rid of it on the prog prof forms? Would that be custom JS as well? or am I completely missing something here?

Thank you!!

[SanfordWhiteman]

I don't get the question exactly. If you don't want the VRs in the ProgPro block... then remove the VRs from the ProgPro block.

[Denise_Greenb12]

Hi Megan,

Progressive Profiling is kind of tricky to test for yourself because you are a known user to Marketo. So to test PP properly what I tend to do is use a browser I don't ordinarily user and clear all the cookies and cache first. Then go to the test LP and fill in the form as a new test lead - and then do so again from that same browser, etc. If you make a change to the form start that process again.

Denise

[Anonymous]

Hi Denise,

I did just that! I cleared my cookies and also tried incognito, so i'm still unsure of why it wasn't working for me. But it is good to hear that it worked for everybody else. Thanks all for testing!

[Denise_Greenb12]

Hi Megan,

Did you also fill in the form with an email address that wasn't already in Marketo?

Denise

[Anonymous]

Hi Denise,

That's a great point. I don't think I did when I was doing my original testing. Thanks for pointing that out!

[SanfordWhiteman]

Incognito/Private/InPrivate's something you can use from your primary browser... a bit easier.

[Denise_Greenb12]

Yes but with Incognito/Private/InPrivate, it's not clear to me if all browsers behave the same way. If Incognito means cookies are blocked, doesn't that make you unknown again the second time you visit the LP?

[SanfordWhiteman]

Incognito means cookies are deleted when the Incognito session ends. Cookies are not blocked, rather they're both sent and received in Incognito mode. But they are all flagged as session cookies and are not stored permanently once the last Incognito tab has been closed.

[Denise_Greenb12]

Thanks for that explanation! Is that true of all browsers? It seems to me I have experienced inconsistency using incognito to get around the fact that I'm known - in testing other things besides progressive profiling - but I can't remember and specifics at the moment. That's why I have gone the route of using a different browser (which isn't that much more effort for than incognito since I have 2 other browsers installed and handy).

[SanfordWhiteman]

AFAIK the browsers all work the same w/r/t cookies as a whole in their corresponding private modes. But Firefox will block connections to known tracking services (including Munchkin) in Private Browsing mode, which in turn affects the Munchkin cookie (since if the JS can't load, the cookie can't be set).  But it doesn't block cookies in general, and you can turn off this functionality so it works like Chrome Incognito.

[Denise_Greenb12]

Firefox is my primary browser so that explains why I've had trouble with it in this regard. Thanks again, Sandy!

[SanfordWhiteman]

ProgPro works for me... here's a sequence of form views/submissions:

​