Using a Token in the Follow-Up URL setting of a form no longer working? | Community
Skip to main content
Ilana_Guilfoyle
Ilana_Guilfoyle
New Participant
August 12, 2015
Solved

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

  • August 12, 2015
  • 5 replies
  • 6350 views

Hello,

For a long time now I've been able to use a local token as the value for a form's follow-up URl setting. As of recently this will no longer validate:

I've also tried using the token at the form level (form defined) but that results in the page just reloading on form submit, instead of redirecting to the follow-up page. Is this something anyone else is experiencing/found a solution for (aside from having to manually choose for every landing page). Ideally, My team shouldn't have to be editing the form settings for every landing page they create.

Thanks!

    Best answer by Justin_Cooperm2

    We're aware of this issue and are going to be fixing this very soon. This broke because more stringent validation logic was added to the platform to avoid potential problem scenarios. This is an area that has historically allowed tokens to be used, but it's never been an "officially" supported feature. The reason for this is that there are several potential issues that customers may not have been aware of when using tokens in follow-up URLs. As we work on rolling out support again, we have made some improvements to solve some of the previous issues. That said, there are still some significant consequences that need to be understood (and we will add a note to the UI to indicate this):

    1. This will break if you are embedding the form on an external page.
    2. Only program tokens (my.token) will be allowed.
    3. This will break if you use a program token that isn't a "text" token.

    ETA for rollout is ~3 weeks.

    Justin

    5 replies

    Justin_Cooperm2
    Justin_Cooperm2
    New Participant
    August 28, 2015

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

      Edward_Unthank_
      Edward_Unthank_
      New Participant
      August 29, 2015

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

        Ilana_Guilfoyle
        Ilana_GuilfoyleAuthor
        New Participant
        August 13, 2015

        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
        Justin_Cooperm2
        New Participant
        August 13, 2015

        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
          Abaran
          New Participant
          August 18, 2015

          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
          Justin_Cooperm2Accepted solution
          New Participant
          August 13, 2015

          We're aware of this issue and are going to be fixing this very soon. This broke because more stringent validation logic was added to the platform to avoid potential problem scenarios. This is an area that has historically allowed tokens to be used, but it's never been an "officially" supported feature. The reason for this is that there are several potential issues that customers may not have been aware of when using tokens in follow-up URLs. As we work on rolling out support again, we have made some improvements to solve some of the previous issues. That said, there are still some significant consequences that need to be understood (and we will add a note to the UI to indicate this):

          1. This will break if you are embedding the form on an external page.
          2. Only program tokens (my.token) will be allowed.
          3. This will break if you use a program token that isn't a "text" token.

          ETA for rollout is ~3 weeks.

          Justin

            Ilana_Guilfoyle
            Ilana_GuilfoyleAuthor
            New Participant
            August 13, 2015

            Thanks! I really appreciate your quick response and explanation!

            Edward_Unthank_
            Edward_Unthank_
            New Participant
            August 12, 2015

            Oh no!! I severely dislike this. This is core to the setup we've been using for all landing pages and forms, everywhere.

            Marketo has been putting in more guard-rails to tokens behind the scene—about a month ago, they started throwing up error messages if you try to delete tokens that are used by program assets which is another example of a safety guard-rail at the expense of power users.

            I don't know how to escalate this, or to whom we can escalate this. Any Marketo employees able to jump in and offer a solution?

            Edward

              SanfordWhiteman
              SanfordWhiteman
              New Participant
              August 12, 2015

              In fairness, this can be accomplished using a token in the LP + the Forms 2.0 onSuccess event, no?

              Ilana_Guilfoyle
              Ilana_GuilfoyleAuthor
              New Participant
              August 13, 2015

              Yes, i could write some custom onSuccess javascript, but that seems like a pretty large lift for something that was once super simple. And thats not a viable solution for teams that don't have a dedicated developer. Plus, there's this unanswered question I unearthed in these forums: Token encoding in Follow-Up URL

              Josh_Hill13
              Josh_Hill13
              New Participant
              August 12, 2015

              What is the URL itself you are using? You cannot use "" in a token.

              But that's probably not the issue here. Ask Support directly.

              Ilana_Guilfoyle
              Ilana_GuilfoyleAuthor
              New Participant
              August 13, 2015

              Yeah, I've tried both with and without http, neither has worked.

              Terms & ConditionsAccessibility statement

              Loading footer...