Per my initial posting, we noticed that progressive profiling wasn't working specifically for certain operating systems - we caught it in Windows 8, iPhone and Android, however Mac OS and Windows 10 were not impacted. Therefore, simply testing in incognito will not resolve my concerns, unless I'm missing something?
Given that Marketo did not alert us nor provide any documentation that progressive profiling was down for several days, we assumed it was something we did on our side - hence why I asked the community to see if anyone else experienced the same troubles. I did not intend for the community to go in and test our forms, that's what support is for (btw we do have test companies as well as a sandbox environment).
I'm less concerned with why it happened, I'm more asking about Marketo's best practices or how other customers go about testing forms on all browsers and devices since we were in the dark and there was no clear trend from our side.
Hope this helps.
The bug affected all platforms. I can assure you that if you performed cross-browser testing with all unprimed caches, you would've seen it everywhere.
Now, I'm not saying you should've had to do this testing -- obviously Mkto let a bug make it to release, and shouldn't -- but I don't know what other advice you need about how to perform your own testing, if you should feel that's necessary.
Looks like progressive profiling isn't working again for Windows. Once again, Marketo hasn't provided any bug reports on this issue and I've noticed this happening since yesterday. What's going on?
I'll QA it again. I'd also like to know your actual URL. By "Windows" do you actually mean "IE"? B/c browsers are too different for this to be a Windows-wide problem.
I just tested in Windows 7/IE 10 and Windows 10/Edge and had no problems. Can you respond with a URL on which you can reproduce the problem, and the browser you're using to test? Also include the fields on the form that are in the ProgPro group.
I want to be clear: my colleague and I both tested on Chrome - he's using Windows 7 and I am using Mac OS. Prog Prof is working fine for me, where for him it only showed the original 5 fields. Upon testing this morning it looks like it's working for both of us, but the fact that we've encountered this bug twice is concerning.
In case we find this issue again, here is the page with a form for reference: https://www.mulesoft.com/lp/whitepaper/api/protect-APIs (use a mulesoft.com domain to not get processed into lead nurture).
Upon first form submission:
The code hasn't changed since the bug fix the other week, so there's no reason for the behavior to differ.
Also, Chrome is going to execute the JS the same on every OS. I think you're looking at coincidence across platforms (just as the earlier bug demonstrably affected every platform equally).
Maybe there's another side you're not considering? The associated lead is not guaranteed to be known on the very next page view. 999/1000 times on an unloaded instance, it will be, but if your instance is under load the rate could be lower. I would have to capture the moment it apparently fails for you to be sure, though. And it can be *very* hard to troubleshoot unless you are patient, because the next attempt may well work and you have to try again and again to trigger it.
So after all this time, I've discovered the progprof is still erratic and I finally recorded the issue to prove it: Progressive Profiling Error Video
My colleague and I are both using the same version of Google chrome, and both filled out the same form in incognito - and while I had success with progprof, he did not. He is having the same issues with all of our forms and I am not. Sanford Whiteman why is this happening?
I'd need to look at the response from /getKnownLead and at other stuff on the wire when this is happening. Absent other evidence, I would assume he isn't waiting long enough between posting the form and refreshing the page. If the data is being posted successfully to /save2 it should be available via /getKnownLead quickly, though not immediately.
As I mentioned above, ProgPro is dependent on fetching the latest committed values stored on the server; it's not, by contrast, dependent on data actually stored in a cookie (which is why it's not necessarily immediately available). But it is deeply dependent on the tracking cookie existing in the browser, since that cookie is the "lookup key" by which the lead is located in Marketo. If your colleague has tracking protection turned on his browser, then cookies are not being set, so even the form fills will work the subsequent attempt to look up the lead will always fail.