Formdownload URL Clarification | Community
Skip to main content
K
Karthick77
Level 3
April 1, 2024
Solved

Formdownload URL Clarification

  • April 1, 2024
  • 2 replies
  • 4719 views

In the trigger campaign setup, after a lead fills out the form, they should receive a confirmation email containing the on-demand webinar link. This link is represented by the token "{{lead.FormDownloadURL:default=edit me}}".

 

My query is:

How does this token capture the value? Does it extract the value from the URL of landing page and then redirect to the appropriate on-demand video?

Please let me know the thought on this.

#trigger campaign #lead tokens #formfillout #URL

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Darshil_Shah1

As said by others, this is a custom field on the person record, and if the person has a valid URL value in it, they will be redirected to it, otherwise, they’d not be! Do you have any processes in place that ensure that the person has value in this field before you send out an email. Also, you should probably use a fallback URL as the default value in the token if the field value is absent so people don’t see a invalid URL/404 page.

2 replies

SanfordWhiteman
SanfordWhiteman
Level 10
April 1, 2024
Well, that's a custom field. There's no field of that name by default.

So it doesn't do anything on its own.

If you want it to capture a special value and write it to a (hidden) field, you have to do that using JS! Perhaps you should be describing your requirements in detail instead.
    K
    Karthick77Author
    Level 3
    April 2, 2024

    Once X fills out the form, they should receive a confirmation email. In that email, we've included a CTA with the {{lead.FormDownloadURL}} token. When X clicks on the CTA, they will be directed to the related video.

     

    My question is:

    When the user clicks on the CTA button, how does it redirect to the correct video? Since we've placed a token related to the FormDownloadURL, and not any video links directly, is it because of the JavaScript written in the backend?

    Karthcik R
    SaurabhGoyal_GN
    SaurabhGoyal_GN
    Level 4
    April 2, 2024

    @karthick77 - As far as, I can understand, FormDownloadURL is a custom field and the same must be getting populated during the form the submission. JS must have been placed on Landing Page Level for the same. 

    It would be great if you can share the URL, we can tell you the same more confidently. 

      SaurabhGoyal_GN
      SaurabhGoyal_GN
      Level 4
      April 3, 2024

      @karthick77 - I was following this thread, was curious to know, how that field is getting populated. 

      I saw you marked a reply as solution but I am not able to grasp the answer in the whole thread. 

      It will be really helpful if you can post the final solution. 

      K
      Karthick77Author
      Level 3
      April 3, 2024

      Hi @saurabhgoyal_gn,

      Before I filled out the form, I noticed that some fields like FormDownloadURL, FormPageTitle, and FormTopic were blank. But after I filled out the form, I was redirected to the right on-demand page. I saw that the Vimeo video link was added to the FormDownloadURL field, and the FormPageTitle and FormTopic fields were filled too. However, after a couple of days, the field values disappeared again. So, once the person fills out the form, they're getting the correct URL value added to the custom field.

       

      Karthcik R
      SaurabhGoyal_GN
      SaurabhGoyal_GN
      Level 4
      April 3, 2024

      @karthick77 - But your question was this - 

      My query is:

      How does this token capture the value? Does it extract the value from the URL of landing page and then redirect to the appropriate on-demand video?

       

       I would like to know how does values for these fields are getting populated? - FormDownloadURL, FormPageTitle, and FormTopic

      I was looking for the answer to your question in the thread and the solution. 

      Terms & ConditionsAccessibility statement

      Loading footer...