If you're wondering how Uptrends determines the cost of a particular transaction monitor, you're in the right place. Before we get into the credit calculation, let's review some terms frequently used when discussing transaction monitors.

Transaction: A transaction is a user’s journey to complete a task on your website. Transactions include tasks like logging in, making a purchase, submitting a form, requesting a document, setting up an account, requesting a password reset, and more. A single transaction consists of two or more steps.

Transaction credit: Think of a transaction credit like cash. You have an allotted number of transaction credits based on your plan (You can always buy more.). A transaction monitor carries a "costs" of a certain number of credits based on multiple factors that we discuss in a moment. While your monitor is in development mode, no credits are used or needed. You use the credits by putting the monitor in staging or production mode (Learn more about monitor modes.). You can find the number of credits available to you in your account settings.

User actions: A user action is a user's interaction with the page. Examples of user actions include clicks, text input, hover actions, and content checks.  

Step: A step is an arbitrary grouping of user actions. You can group your actions into steps that make the most sense to you and help you with troubleshooting and reporting. Uptrends reports timings on a step-by-step basis (something to consider when setting up your steps). Our recommendation is to end each step with a navigation action.

How does Uptrends determine the number of credits a transaction monitor uses?

You may have heard someone say that we base the price of a transaction monitor on the number of steps in a transaction. That isn't quite right. We determine how many transaction credits a transaction uses based on a couple of different factors:

The number of user actions resulting in a server request. Each user action (see the definition above) in a transaction monitor that results in a server request uses one transaction credit. Each transaction monitor uses a minimum of two credits: one for the navigation and one for the user action resulting in a server call such as clicking a submit button.

Transaction waterfalls and screenshots: Each transaction waterfall or screenshot used in your transaction uses a transaction credit.

The transaction monitor calculation

If you want a formula for calculating the number of credits required for a single transaction, try this:

Number of actions with server requests + number of waterfall charts + number of screenshots = total number of transaction credits used

Although most of the time, the above formula works, as stated earlier, other less obvious factors may increase or reduce the total number of credits needed.

Conclusion

If you find yourself scratching your head wondering how we made the transaction credit use calculation, contact support. Our support team reviews the transaction with you to clear up any confusion.