Last modified: 2023-03-24

In-App Reporting

The In-App Reporting feature became available in OneSpan Sign 11.41. It provides customers with additional ways of accessing reports about the activity on their OneSpan Sign accounts.

Before In-App Reporting was introduced, New User Experience customers with sufficient permissions could access the following option from the Reports menu on the Navigation Bar:

  • Usage Summary — This option enables users to run an Account Summary Report that creates, for each sender on an account, the number of associated transactions, grouped by status.

In-App Reporting enables customers to access from the Reports menu two additional options:

  • Transaction Reports — These system-created reports provide data about transactions on the account (information about senders, signers, key events, etc.).

  • Account Reports — These system-created reports provide information about actions on the account (e.g., when specific users joined the account).

Before In-App Reporting, customers who wanted to view the kinds of data in Transaction Reports and Account Reports had to request it from our Support Team, or they had to build their own event-collection system using OneSpan Sign’s REST API. In-App Reporting enables customers to access this information directly from the New User Experience or relatively simple API calls.

Note that:

  • The system provides monthly snapshots for Transaction Reports and Account Reports. For the current month, those reports are updated daily. Moreover, Transaction Reports carry every transaction forward into the next month unless the transaction is deleted.

  • Transaction Reports and Account Reports are updated daily at midnight UTC. The time required to generate an update varies. It may occasionally take more than 24 hours for an event to appear in a report.

  • Reports will record only activities that occur after In-App Reporting is enabled. For example, if a transaction was In Progress when In-App Reporting was enabled, a Transaction Report will record subsequent activity on that transaction, but prior activity on the transaction will not be recorded. Reports are thus expected to be missing at least some information about transactions that were created before In-App Reporting was enabled.

  • The system retains Transaction Reports and Account Reports for one year. Although they are then deleted, the underlying data about a transaction is deleted only when the transaction itself is deleted.

  • We recommend setting a retention period of 3 months for transactions. This should help limit Transaction Reports to a manageable size, and make them easier to maintain.

  • In-App Reporting is not available for US FedRAMP, or via OneSpan Sign’s SDKs.

In-App Reporting is a valuable tool for customers, for it enables them to easily:

  • Track account-related costs (e.g., transactions, documents, KBA, SMS), so they can better manage their budgets.

  • Calculate their Return on Investment, which can be used to champion the solution and thus increase its adoption.

  • Track the adoption rate, which could provide insights into actionable improvements.

  • Track the Transaction Cycle Time, which could enable customers to improve process efficiency and thereby lower costs and increase revenue.

  • Calculate the Transaction Completion Rate, which could enable customers to increase the completion rate and thereby increase sales.

  • Monitor the status of transactions for follow-up with signers, which should lower the Transaction Cycle Time.

To activate In-App Reporting for your account, please contact our Support Team. Once this feature is activated, your account's Admins and Managers can use In-App Reporting. The account's senders cannot, unless they have been assigned a role for which Reports are enabled.


Was this information helpful?