To keep form maintenance under control, we thought it was wise to create a central form for (e.g.) webinar registrations that lives in the Design Studio. In the webinar program we've created a local Landing Page with the central form on it. We then listen to this central form being filled out (Trigger: Fills out Form), with Form name = 'central form' and Constraint: Web page = 'local Marketo LP'. People who will out the form will be marked as Registered as a result.
I now see that half of the members is Member of the program, but not Registered. So it seems the Trigger as described above doesn't work in all cases. I vaguely recall having met this problem before, and adding a second trigger Fills out Form, with Constraint: Referrer = 'local Marketo LP' may solve the problem (I'm monitoring it as we speak).
However, I just don't understand whether my setup is simply incorrect or what else may be causing this.
Any insights much appreciated!
Gerard
Solved! Go to Solution.
So, after some perseverance, I got the answer to this disturbing behavior: it was a bug that resulted from the move to project Orion. Patch should have been applied on 20 Dec 2016.
[quote]
The issue you were seeing was caused by a flaw in the Munchkin v2 element. This flaw caused by an incorrect directory naming convention in the web file info table, when migrating anonymous leads during the merge lead activity. This caused the form fill out activity to fail to be added to the lead's activity log.
Our developers had learned this after customers such as yourselves had reported the issue. They had created a patch and it was pushed out to all customers yesterday. So although you will not see the past Form Fill Out activities during the period of the outage, you should start seeing them now. Again this is only for leads that have merged and anonymous lead with a known lead.
[quote ends]