Using webpage constraint for form fill out trigger on embedded forms

[Eben_Shapiro]

According to this post it's not possible to use the webpage constraint for form fill out trigger on embedded forms:

https://nation.marketo.com/community/champion/blog/2015/02/19/marketo-forms-which-application-is-rig...

I just ran a test where it seems like I got this to work. At first the web page constraint input field warned my that the page didn't exist, but after I submitted one lead on the page, then the warning went away and was able to activate the campaign.

First I submitted a test lead through the form on the non-marketo landing page specified in the web constraint, and the lead showed up in the campaign membership and went through the flow. Then I submitted a new test lead with the same form on a different page not specified in the web constraint and this lead correctly didn't show up in the campaign membership.

Is it only by some quirk that this worked? Is this a non-production safe technique?

[SanfordWhiteman]

It's not that it doesn't work at all, it's that it's not complete.

Unless it's been silently changed recently, it won't allow matches on query string, while Referrer does ("Referrer" here is the current page hosting the form, not the previous page).

[Eben_Shapiro]

Thank you Sanford and Dan, I found this other conversation you all had over here with more info about it:

https://nation.marketo.com/message/123143#comment-123143

That detail about the hash tag for non-Marketo landing pages is definitely worth noting.

It looks like the query string constraint needs to be used for the Marketo Landing pages too if one wants to isolate form submissions in that way. For the sake of argument, would it be safe to use the referrer value for Marketo Landing page form submissions too?

[SanfordWhiteman]

It looks like the query string constraint needs to be used for the Marketo Landing pages too if one wants to isolate form submissions in that way. For the sake of argument, would it be safe to use the referrer value for Marketo Landing page form submissions too?

Yep.

[Dan_Stevens_]

We've found this to be the most reliable setup for tracking form submits on non-Marketo LPs:

[Anonymous]

Good shout Dan.  We've also found that using 'Referrer is' didn't always work with non-Marketo landing pages; when we switched to 'Referrer contains' and just used unique elements of the landing page URL everything worked fine.

[SanfordWhiteman]

Good shout Dan. We've also found that using 'Referrer is' didn't always work with non-Marketo landing pages

An Is match is bound to miss some visits -- not because it doesn't work, but because it does work in creating a tight level of control.

When search engines append query params to the URL, for example (and you'll never be able to predict the exact values they append), the URL no longer matches your static value.  http:​//example.com/mylandingpage.html?myquery=value doesn't Is-match http:​//example.com/mylandingpage.html?myquery=value&searchinfo=0.3.53.aaaak.z.

So yes, Contains with your known URL will fix these cases.

(In the way-back of your mind, you might store some edge cases that can occur in the other direction, depending on quirks of your in-site navigation. http:​example.com/page2.html?prevpage=http:​//example.com/page1.html does Contain http:​//example.com/page1.html, for example!)