Journey Manager (JM) Previously known as Transact Manager (TM). | System Manager / DevOps | 5.1 & Higher This feature is related to 5.1 and higher.
A transaction can be abandoned in several ways:
It is a balancing act to optimize conversion rates whilst keeping your database as lean as possible. As with the case of a saved form, it is hoped that the user will soon resume, complete, and submit it. We advise that sufficient time is allowed for all users to resume their forms before automatically abandoning them. According to the strict policy, the Saved Transactions setting gives the user 30 days to return to a previously saved form.
The image below illustrates an example where a transaction, that was previously saved, is abandoned automatically after a period of inactivity (based on the Saved Transactions setting).
The following steps describe this process:
In most cases, abandoned transactions are deleted according to the Finished Transactions setting. The only exception is where a user opens the form and leaves it open without having saved it (this includes any background saving). In this case, the transaction is automatically abandoned one day after first opened and then it’s deleted 2 days after being abandoned.
Data for abandoned submissions is delivered if the abandoned delivery channel is configured in TM.
Next, learn about submission categories.