How do you use Marketo forms in WordPress right now?
Are you embedding Marketo froms within WordPress page?
are you using any WordPress plugin?
Are you using iframe?
Is there any URL you can share?
This sort of information can be useful to be able to help effectively.
Hey Rajesh, I can't message you directly. Could you either follow me or share your email address so I can send you one of the URLs? Thanks.
Are the URLs not public URLs? If we don't see them here, it will obscure the solution for other Community users.
We use this same approach across hundreds of our programs. Since we use a common form on our gated content pages (on our website, not Marketo LPs), we need to constrain this by the landing page, e.g.:
I just checked some active campaigns and it's working fine. I've never heard that the constraint for "Web Page is" is only for Marketo landing pages.
7 of 7 people found this helpful
-Why is this suddenly an issue?
-Why does it seem to work for some leads?
-What is the actual difference between these two constraints?
Without looking at your actual URLs, I can't say whether anything unexpected happened. But I agree with Support that Referrer is the preferred constraint for embedded forms.
This is not to say that Web Page does not also work, but for non-Marketo URLs it enforces an exact match on the hostname+pathname+hash, which is not so for Marketo LPs For example, the constraint
Web Page [is] s.example.com/mypage.html
but it will not match
Contrast this with a constraint by Marketo LP friendly name
Web Page [is] My Landing Page 02
which will match
and will also match if you change the URL.
In other words, even though it's expressed as an [is] match, with a Marketo LP it's flexible across branding domains and hashes.
Referrer, on the other hand, treats the entire referrer URL as an opaque string and allows for partial matches. So
Referrer [starts with] http://s.example.ccom
will not match
Referrer [contains] mypage.html
They both have their uses, but I don't find an exact page match without the query string to be something I run into too often. More often I want to catch a certain form across an entire domain, or the query string itself, or something within the path (like a language).
Sanford Whiteman, there's one scenario that you didn't illustrate:
Referrer [is] s.example.com/mypage.html
will it match a URL containing a URL parameter?
Similarly, when we use "LINK is" for a "clicks link in web page" trigger, that Marketo only evaluates the base URL without the URL parameters (unless you add in a "query string" constraint).
Referrer does consider the entire URL, including query string.
In that case, if we have a central campaign landing page that's used across multiple channels - meaning there could be all sorts of combinations of UTM parameters attached to the URL, resulting in 25+ URLs - the best approach would then be to use a "referrer" [CONTAINS] "http://mainURL.com" contraint, correct?
1 of 1 people found this helpful
1 of 1 people found this helpful
'Referrer starts with' would also work and may be slightly faster.
If your base URL is the same for all channels and the only differences in the links are the query parameters, you should be able to use a 'Web Page is' constraint. The key with the Web Page constraint is it must exactly match the base URL including trailing slashes (or not) and hashes. You can typically see the base URL (not including www.domain.xxx) in the Webpage URL field of a Visit Web Page activity for that page (screen shot below). You can also see the Webpage ID field value in the Visit Web Page activity, which should match the Webpage ID field value in the Fill Out Form activity.
If your page has sections, you will need to add the base URL and the base URL with its hash values in the multiple value chooser field as in the following examples.
Thanks Sanford Whiteman. Your explanation makes sense for the most part.
The form was split up into a multi-step form, so each step appended #step-1 to the URL. This is relatively new for us, so that's probably why we hadn't seen this issue previously. The other versions of our multi-step forms have triggers based on the form ID alone without any other constraints, and that's why we don't see this issue for those trigger campaigns.
It still throws me off that there were some leads who had the #step-4 referrer url and still qualified for the trigger (form ID+Web Page constraint). But since there are inconsistencies, I won't be relying on this constraint anymore.
I've since built a patch campaign to wait 5 minutes after leads fill out the form + referrer then go through the necessary flow steps if it hasn't already, and it seems to be working. After monitoring for a few days, all leads are going through the patch campaign without issue so it does seem like referrer is the better constraint for non-Marketo LPs.
Lesson learned. (Is this noted in the product docs already?)
The form was split up into a multi-step form, so each step appended #step-1 to the URL. This is relatively new for us, so that's probably why we hadn't seen this issue previously.
I had a gut feeling it was the hash that was causing confusion. I like to exploit the hash-awareness in other contexts w/Marketo, so I keep an eye out for it. Switching to Referrer will both solve this problem and give you more flexibility in the future.