Pause and Resume

  • Updated

With long, involved decision trees, authors may want to allow end-users to complete the entire tree in separate sessions. So an end-user could start using the tree, go to lunch, and reopen the tree at a later time and finish the session. The state of the tree is saved at all times.

To make this work, the URL that opens the tree needs to have a unique identifier attached to it, in the session_id parameter of the URL. So when you launch the tree, you will need to provide this parameter. And when the end-user relaunches the tree, the same URL needs to be used.  

Important: The session_id needs to be unique across all Zingtree customers and sessions.

For example, if your URL is this:


You would create a unique session ID (like 141112232-xyz), and launch the URL like this:


Please Note: In order for Pause and Resume to work properly, the tree ID must be the same in both the initial URL and the resumed URL.


Resuming a Session from a Different Node

You can move a session to a new node by simulating a click on the tree. You need to provide some "click text" as if a button was clicked, and a new node number where the session will resume. The click text will appear in the session history and button click reporting.

For example, to move a session to node #99, as if a button named "Next" was clicked, you would add this to the URL along with the session ID:


Note that any spaces in the click text need to be replaced with + .


Was this article helpful?

1 out of 1 found this helpful

Have more questions? Submit a request

Didn't find what you need?

Our friendly customer support team is here to help

Submit a Ticket

Looking for help or advice?

Reach out to our knowledgeable community of users.

Zingtree Community