Trigger based on Fills out Form: central form + Constraint: Webpage doesn't always fire | Community
Skip to main content
Gerard_van_den_
Level 3
November 24, 2016
Solved

Trigger based on Fills out Form: central form + Constraint: Webpage doesn't always fire

  • November 24, 2016
  • 3 replies
  • 3971 views

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

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Gerard_van_den_

To keep you posted: after a couple of rounds at regular support, they have finally escalated it to development. Support couldn't explain why the activity log was incomplete. Awaiting further information. I've shared my concerns as form fills are at the very core of Marketo's functionality.


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]

3 replies

Grégoire_Miche2
Level 10
November 24, 2016

Hi Gerard,

This is weird. Please look at the activity log of one of these missing leads and focus there on the fills out form event. display the acitvity details and provide here a screenshot.

-Greg

Gerard_van_den_
Level 3
November 24, 2016

see also my observation below, it seems to be related to a merge activity.  The Activities simply stop with the top most entry: Change Program Status, whereas for leads that are not merged (bottom screenshot), you see a couple more activity entries, including, most importantly: Fill Out Form.

Grégoire_Miche2
Level 10
November 24, 2016

Hi Gerard,

The merge activity occurs because the lead that fills out the form was already in your database, together with an anonymous leads that had a cookie on the visitor's browser. So, when this anonymous lead filled out the form and Marketo recognized the email address, the anonymous and previously known leads were immediately merged.

The fills out form event has been fired, as you can see at the top of the activity log.

Check the qualification rules of the smart campaign, to see whether it is not set to "run only once" or "run only once every XX" and also check if this lead has not already filled out that form in the past.

-Greg

Emmanuelle_Biss
Level 4
November 24, 2016

Hey @Gerard van den Akker​,

Try to take a look at some of the activity log of the contacts who are members of program but not registered. Maybe there is a trigger that impeded the member to be registered. And see if there is any differences with the contacts who are registered. Do you notice anything that could explain the difference?

Emma

Gerard_van_den_
Level 3
November 24, 2016

Thanks for your suggestions. I've revamped the form to be a local form but that didn't help.

I'm starting to see a pattern though: all problematic leads show in their activity log they've been merged, and the merge takes place before the Fills out form is showing up in the Activity log. So I guess that's somehow why it doesn't trigger. Still I don't fully understand...

SanfordWhiteman
Level 10
November 24, 2016

Can you show us the SLs and Flows that you are using?

Gerard_van_den_
Level 3
November 24, 2016

Sure, but I think this is pretty straightforward: