How to use continue later with email session when the form is embedded on a page on my website?

  • Profile Image
    Asked on March 17, 2015 at 09:18 AM
    When I create a form with you, I can access it via the jotform link. When I use the carry on later option, I'm still using the jotform link + their email. If I'm embedding it onto my own website, in this instance it would be found at If I added the email bit to the end of my web address, it wouldn't pull through the form, I'd have to send them the jotform link for this to work.
  • Profile Image
    Answered on March 17, 2015 at 09:41 AM

    I understand what you mean, but there should be 2 ways to go do this with your website being used both times Thom.

    1. First one is to change the DNS to have jotform shown as if it is a page of your own website:

    How to use Custom Domains with Jotform

    - Downside: can not be used over HTTPS

    - Upside: the URL now shows your website instead of jotform website, while it is still direct link to jotform

    2. Second one is to pass the URL session to your form.

    For example, if you have PHP scripting on your website you can do the following:

       $url_session = false;
       if(isset($_GET, $_GET['session']))
           $url_session = $_GET['session'];

    That should be placed before the form code and then when you embed code you add following code:

    <iframe src="linkToForm<?php echo ($url_session) ? '?session='.$url_session : ''; ?>" ></iframe>

    * You should keep all the data in the iframe code that you get from our system, but just add the bold part in the src attribute after the link to the jotform

    Hope this helps, but do feel free to give us a link to your page Thom and we can provide you with the full code that you should embed.

    * The only code that changes is the iframe embed code, the first part is always the same.

    - Downsides: You need to set it up properly

    - Upsides:

    1. You can have multiple jotforms on the page and pass the session to both or to only one
    2. works equally on HTTP and HTTPS3. copy paste type of implementation - no need to be familiar with DNS