BrowserHawk To-Go: Monthly pricing calculator

Estimate your monthly cost with this calculator
Detect and log 120+ browser and system settings or dynamically render site content.
Estimated service requests (monthly):
Estimated service requests: A service request occurs when a visitor to your site requests a page that includes the CORE JS library. The JS is cached for 24 hours so if your visitor hits several pages it only counts as one request. If you will only use CORE from select pages, base your estimate on the number of visitors that will hit those pages. Otherwise base your estimate on the number of monthly visits your site receives.
Instantly add a self-help, automated browser troubleshooting and analysis page to your site.
Estimated service requests (monthly):
Estimated tests executed (monthly):
Estimated emailed results (monthly):
Estimated service requests: A service request occurs when a visitor to your site requests a page that includes the RET JS library. The JS is cached for 24 hours so if your visitor hits several pages it only counts as one request. If you will only use RET from select pages, base your estimate on the number of visitors that will hit those pages. Otherwise base your estimate on the number of monthly visits your site receives. Estimated tests per month: Enter the number of times you anticipate a browser troubleshooting test will be executed during the month. A good rule thumb is a small fraction of one percent of total requests if used as a general 'submit a bug' page. If used more proactively, such as screening users before they log in, the number will be significantly higher. Estimated emailed result: Enter the number of times you anticipate a user will select the option within the browser troubleshooting page to email their test results back to your help desk for further assistance. A good rule of thumb is 10% of the number of tests executed. Depending on how you use this tool this percentage could be significantly higher.
Monitor the actual page load times as experienced by each visitor to your site.
Estimated service requests (monthly):
Estimated page views (monthly):
Estimated service requests: A service request occurs when a visitor to your site requests a page that includes the PLT JS library. The JS is cached for 24 hours so if your visitor hits several pages it only counts as one request. If you will only use PLT from select pages, base your estimate on the number of visitors that will hit those pages. Otherwise base your estimate on the number of monthly visits your site receives. Estimated monthly page views: Enter the number of page views your site receives per month for the pages or sections of your site that will use PLT. Or if you will use PLT across your full site, enter your total monthly page views. This field is only relevant if you log to the BHTG network. Unlike with service requests, repeat page views for the same visitor should be counted.
Automatically log all JavaScript errors that users encounter on your site.
Estimated service requests (monthly):
Estimated errors (monthly):
Estimated service requests: A service request occurs when a visitor to your site requests a page that includes the ERR JS library. The JS is cached for 24 hours so if your visitor hits several pages it only counts as one request. If you will only use ERR from select pages, base your estimate on the number of visitors that will hit those pages. Otherwise base your estimate on the number of monthly visits your site receives. Estimated errors per month: Enter the number of JavaScript errors you estimate users could encounter on your site. A good rule of thumb is 0.5% of your service requests. Keep in mind that multiple JS errors can occur on a single page. This field is only relevant if you log to the BHTG network.
Log data to BHTG network for real-time reporting and analysis.
Overview: Select Yes if you want to log the results from any of the libraries to the BHTG network for analysis and reporting. Each record logged uses one row of database storage. Typical storage for each library: CORE uses one row per visit; PLT uses one row per page view; ERR users one row per error; RET users one row per test executed. If you will log to your own network or will not perform any logging select No.