> For the complete documentation index, see [llms.txt](https://cmp.docs.sirdata.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cmp.docs.sirdata.net/en/faq/pricing/what-is-a-load.md). # What is a load? The unit used to apply the caps and to price the Business plan: definition, counting, tracking and estimating. A **load** is a page, or any other remote resource, on which the ABconsent tag of one of your configurations is executed or loaded. In practice, a load is counted each time a page that contains the tag opens in a visitor's browser. It does not matter whether the visitor sees the choice interface or not, or whether they accept or refuse. Bots count too, as soon as the tag runs. A load is therefore not exactly a "page view": any page or resource on which the tag runs counts, and your audience measurement tools may count differently. {% hint style="info" %} Some ABconsent screens, and older pages of this documentation, speak of **hits**: these are loads. {% endhint %} ## How loads are counted * **Per site.** A load is counted for the site of the configuration whose tag ran. A site is a configuration of the choice interface created in your account. If a configuration covers several domains, their loads add up. * **Per calendar month, in UTC.** The counter starts again from zero on the 1st of each month at 00:00 UTC, which is 1 a.m. Paris time in winter and 2 a.m. in summer. * **No carry-over.** Unused loads of a month are not carried over to the following month. {% hint style="info" %} **Account opened before 1 November 2026:** the plan applies to the whole account. The loads of all its sites then add up for the cap. {% endhint %} ## What loads are used for * On **Starter** and **Pro**, they are compared with the cap of the plan: 25,000 and 250,000 loads per month. See [What happens when a site reaches its cap?](/en/faq/pricing/what-happens-when-a-site-reaches-its-cap.md) * On **Business**, they set the price for the month. See the grid in [Pricing](/en/faq/pricing.md). * On **Essentials**, they affect neither the price nor the service: Essentials is free of charge and has no cap. ## Tracking your loads * In ABconsent, the site list (menu **My CMP configurations**) shows the loads of the month against the cap, up to the previous day: on the line of each Starter or Pro site, or at the top of the list for an account opened before 1 November 2026. * The menu **Statistics > Hit statistics** ([www.abconsent.com/sites/analytics/hits](https://www.abconsent.com/sites/analytics/hits)) gives your loads day by day, up to the previous day. * On Starter and Pro, Sirdata sends you an email when a site reaches 80%, then 100% of its cap. Consent statistics (acceptance rate, refusal rate…) are described in [Access to Statistics](/en/faq/statistics/access-to-statistics.md). ## Estimating your loads before choosing a plan The safest way is to measure: once the tag is installed, note the total of a full month in **Hit statistics**. Before installation, start from the number of page views of your site over a month, and keep a margin. Your audience measurement tool may count only the visitors who accept it, whereas a load is counted each time the tag runs, whatever the visitor's choice. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://cmp.docs.sirdata.net/en/faq/pricing/what-is-a-load.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.