Using a Token in the Follow-Up URL setting of a form no longer working?

[Ilana_Guilfoyle]

Bad news folks: https://nation.marketo.com/ideas/2932#comment-16633 

To summarize, Marketo support said: "Using tokens into embedded form code does not conform to our new security policy."

Support​ Products and Support​

[Justin_Cooperm2]

This isn't true, I am fixing this issue. But, there are still functional limitations (see above). It has nothing to do with security.

[Abaran]

Hello Justin

Great to hear this is going to be fixed. It is a superb feature to use.

Do you know when it will be fixed and released?

Thanks

Axel

[Justin_Cooperm2]

This is now fixed. my.tokens are now allowed in External URL follow-up pages for forms.

[Edward_Unthank_]

Wooo! Thanks so much for championing and leading the change, Justin! Give this man a raise.

[Whitni_Freeman1]

Hey Justin,

I'm trying to use this now, but I can't seem to get it to work either. I've got a hidden checkbox on my form that I've set to prefill with data, which i'm setting from a smart campaign. For my advanced thank you page settings, i'm trying to use 2 different local tokens based on if the box is check or not. It seems like only the default value is working. Is this a limitation of the token usage in the advanced thank you page settings?

Thanks!

whitni

[SanfordWhiteman]

Are you comparing to a token, or using the token in the LP URL?

[Whitni_Freeman1]

Here's a few screenshots. The form lives in the Design Studio, tokens being set at the program level. The field "Possible Dupe" is a hidden field on the form.

[SanfordWhiteman]

If you switch the true and false case (i.e. Possible Dupe Is Not True) does it still only work for the Default choice? Also, what exactly do you mean by "not work" -- does the Thank You URL become the raw token code ("{{my.Possible...}}") or blank?