Last modified: 2024-03-28

In-App Reporting

In-App Reporting provides customers with additional ways of accessing reports about the activity on their OneSpan Sign accounts.

New User Experience customers with sufficient permissions can access the following options 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.

  • 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).

OneSpan Sign provides a sample integration tool which pulls a list of transactions from within a given time frame and allows you to export these results to an easily modifiable CSV report. For more information, see Transaction Export and Download Tool.

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. Each Transaction Report update captures all the day's transaction events up to when the update starts at 24:00 UTC. Each Account Report update captures all the day's account events up to 23:30 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. USE THIS BULLET TO REPLACE THE PRECEDING ONE WHEN WE PUBLISH 11.47.

  • 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.

Fixing Character-Display Issues

When you use Microsoft Excel to open a CSV report that contains diacritics (e.g., a report in Spanish), certain characters may not display properly. This happens because: (1) the reports are saved using UTF-8 source encoding; (2) Microsoft Excel does not use that encoding. Instead, it uses Windows-1252 encoding.

To avoid this issue, open your reports as follows:

  1. Open a blank document in Microsoft Excel.

  2. In the Search field, enter Get Data from Text.

  3. Navigate to the report you want to open, and click Import.

  4. In the Wizard that appears, select Delimited as the data type.

  5. Select the option My data has headers, and click Next.

  6. Select Comma as the delimiter, and click Next.

  7. Select the General column data format, and click Finish.

  8. You will be asked how you want to view this data. Accept the default values, and click OK.

Was this information helpful?
X