What happens if I exceed the number of dynamic requests included in my plan? - Help Center

At Servebolt we have a soft approach to request limits. We will not take down your site because you exceed the included pageviews. If you exceed the amount of dynamic requests included in your plan, we will get in touch and find a solution that fits your case. We can set you up with an add-on which includes more dynamic requests for a set price per month. Other solutions could be to improve your cache hit ratio, or to add Cloudflare and setup caching at Cloudflare's edge.

What are Dynamic Requests? - Help Center

A dynamic request is a request that was not served by any cache, and therefore reaches the origin webserver (Apache). In other words, all requests that are served from a cache, including our own Nginx cache and Cloudflare edge cache, do not count as a dynamic request. All our plans come with a set amount of dynamic requests included. The usage of dynamic requests is measured by counting the number of requests that reach Apache. Dynamic requests will also includes all requests that cannot be cached in the first place, like POST requests. Typical examples of POST requests are ajax and API requests. When a Bolt environment (your website) is configured correctly, most page views will be delivered from a cache and are therefore not counted as dynamic requests. How do I know how many Dynamic Requests I need? To get a rough estimate, for most regular sites, you can use the Google Analytics monthly page view number and divide it by 4 (~80% cache hit rate). If you know your site's cache hit rate, multiply your number of page views by 1 - your cache hit rate (the example for an 80% cache hit rate is 1 - 0.8 = 0.2 dynamic request rate) to get an estimated amount of dynamic requests needed. All our plans come with a fixed number dynamic requests included. We count Dynamic Requests by counting requests made to all the sites on the Bolt, that are not a request to static assets like CSS, JavaScript or images. We do include requests to API endpoints, AJAX endpoints and similar. Frequently Asked Questions about Dynamic Requests My page view count in Google Analytics is HIGHER than your count! Why? If you use a cache in front of our servers we do not count dynamic requests that hit cache. We only count requests that hit our server. So if you use a cache feature like Cloudflare APO, all requests that is served from Cloudflare's cache is not counted. My page view count in Google Analytics is LOWER than your count! Why? For Google Analytics (GA) – and most other analytics tools – to count a pageview, the client/visitor/requestor needs to run the Google Analytics JavaScript on the page they are requesting. The GA JavaScript doesn't run in many situations. For instance when:– The request is an API request– The browser is blocking the JavaScript– The site doesn't run the JavaScript because consent is not given (GDPR)– The JavaScript isn't present on the page– The request is coming from some sort of bot (i.e Semrush, Ahrefs) that doesn't run the Google Analytics JavaScript snippetThere may be more reasons Google Analytics can't measure all hits, but these are the most common ones. What about the information in Cloudflare's analytics? Cloudflare's analytics information will be in most cases a more accurate portrayal of actual traffic being processed by your site. It's still not the same, but those numbers match our calculation more accurately. Why is there a difference between a page view and your dynamic request? Page views are just that, a view of someone watching a particular page. It's counting the number of views of the HTML being rendered for a specific page by your browser. A URL if you will. Our dynamic requests is about the number of assets such a particular HTML page needs to present itself as you site has defined them. That means that all the assets that are required to generate that HTML page counts as a dynamic request. And that's not even counting AJAX implementations such as add to cart or certain search solutions or API, feed or commenting. All those require some sort of dynamic process on the server and counts towards the total.

My page view count in Google Analytics is HIGHER than your count! Why?

If you use a cache in front of our servers we do not count dynamic requests that hit cache. We only count requests that hit our server. So if you use a cache feature like Cloudflare APO, all requests that is served from Cloudflare's cache is not counted.

My page view count in Google Analytics is LOWER than your count! Why?

For Google Analytics (GA) – and most other analytics tools – to count a pageview, the client/visitor/requestor needs to run the Google Analytics JavaScript on the page they are requesting. The GA JavaScript doesn't run in many situations. For instance when: – The request is an API request – The browser is blocking the JavaScript – The site doesn't run the JavaScript because consent is not given (GDPR) – The JavaScript isn't present on the page – The request is coming from some sort of bot (i.e Semrush, Ahrefs) that doesn't run the Google Analytics JavaScript snippet There may be more reasons Google Analytics can't measure all hits, but these are the most common ones.

What about the information in Cloudflare's analytics?

Cloudflare's analytics information will be in most cases a more accurate portrayal of actual traffic being processed by your site. It's still not the same, but those numbers match our calculation more accurately.

Why is there a difference between a page view and your dynamic request?

Page views are just that, a view of someone watching a particular page. It's counting the number of views of the HTML being rendered for a specific page by your browser. A URL if you will. Our dynamic requests is about the number of assets such a particular HTML page needs to present itself as you site has defined them. That means that all the assets that are required to generate that HTML page counts as a dynamic request. And that's not even counting AJAX implementations such as add to cart or certain search solutions or API, feed or commenting. All those require some sort of dynamic process on the server and counts towards the total.

Billing Documentation

Invoice Fees

Servebolt moved to an automated billing system in the fall of 2019. During this process, all customers were informed several times before the switch, and encouraged to move from manual bank payments (or for Norway EHF) to the three new free invoice payment options. The three free ways to pay […]

More than a year agoJune 10, 2021

How Servebolt Billing works for Accountants

All self-served customers on Servebolt can view the billing history and download all previous invoices from the billing section on their account page. Sometimes we receive requests from accountants that ask for information regarding customer accounts and invoices. There are several reasons for why Servebolt can not provide such information […]

More than a year agoJune 8, 2021

How we bill up- and downgrades

Upgrades and downgrades that are done through the Admin Panel effectuated immediately. On downgrades, credits will be issued for the period from the time of upgrade and until the end of the billing period. These credits are automatically recorded to your account, and will automatically be used for payment in […]

More than a year agoJune 10, 2021

Billing

Invoice Fees

How Servebolt Billing works for Accountants

How we bill up- and downgrades

Payment methods we support

Servebolt Invoices Explained

Why use Direct Debit (SEPA / Autogiro)