SOLVED

Marketo seems to be unable to recognize URLs any more

Go to solution
Anonymous
Not applicable
I just recognized that
  • no external URLs used as web page constraint in the “Clicks Link on Web Page” trigger is accepted,
  • none of my forms redirect anywhere – not to an external URL as well as not to another Marketo landing page.
Everything worked fine until yesterday. And I haven’t changed anything today. This is a serious issue.
Tags (1)
1 ACCEPTED SOLUTION
Anonymous
Not applicable
Problem solved.

Cause: The URL is not accepted because the Munchkin code is added via Google Tag Manager. This works perfectly. But when you want to use one of those pages as web page constraint in a trigger, Marketo scans the target page’s source code and doesn’t accept the URL if the Munchkin code is not physically present in the page’s source code.

Workaround: I rephrased my trigger.

And I filed an idea: https://community.marketo.com/MarketoIdeaDetail?id=08750000000K9v8AAC

View solution in original post

5 REPLIES 5
Dan_Stevens_
Level 10 - Champion Alumni
We use GTM across all of our sites to add the Munchkin code and we don't experience this issue.  We have several smart campaigns that have the "Clicks Link on Web Page" trigger and constrained to a specific web page URL.  Works as expected for us.
Anonymous
Not applicable
Problem solved.

Cause: The URL is not accepted because the Munchkin code is added via Google Tag Manager. This works perfectly. But when you want to use one of those pages as web page constraint in a trigger, Marketo scans the target page’s source code and doesn’t accept the URL if the Munchkin code is not physically present in the page’s source code.

Workaround: I rephrased my trigger.

And I filed an idea: https://community.marketo.com/MarketoIdeaDetail?id=08750000000K9v8AAC
Anonymous
Not applicable
Must have been a temprary server problem. The status 500 error message in the console screenshots would also indicate that.

I tested the forms this morning and everything works again.

But the problem with the URL which is not accepted as trigger constraint still exists:

0EM50000000Sii1.jpg
Anonymous
Not applicable
I opened a support ticket.

The form problem must be caused by something in the forms2.min.js – as the console error messages of different langing pages indicate.

0EM50000000Sigo.jpg

0EM50000000Sigt.jpg
Dan_Stevens_
Level 10 - Champion Alumni
I would raise a support ticket.  I just tested this in our instance and this works fine.