> For the complete documentation index, see [llms.txt](https://support.charlla.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.charlla.io/en/userguide/plan/intro.md).

# Understanding your Charlla subscription

## What counts as a player load <a href="#undefined" id="undefined"></a>

* Charlla bills by "player loads". A player load isn't a click to play a video. It's counted each time a Charlla player finishes loading and is ready to show on a store visitor's screen.
* When a shopper opens a page of your online store, the video player "loads". This counts as 1 load even if the video never plays. (It also counts as 1 load when autoplay is turned off in the player settings.)
* After the player loads once, it still counts as 1 load even if the video loops 100 times, as long as the page is not refreshed.
* When your store's Charlla player loads reach 80% and 100% of the loads included in your subscription, we notify you in the console.

⚠️ Note: Page views (PV) and loads are not the same! Even with only 1 visitor, a page with several videos can generate as many loads as there are videos.

## Overage charges <a href="#undefined" id="undefined"></a>

* You choose what happens when you go over the loads included in your Charlla plan. With **\[Allow]**, videos keep playing and overage charges apply. With **\[Block]**, videos stop playing and no overage charges apply. To set this up, see \[[Overage load settings](/en/userguide/plan/overage-control.md)].
* With overage loads allowed, we notify you in the console when your loads exceed 100% and overage charges start to apply.
* Overage charges are billed on your payment date **next month**. The overage charge and the plan subscription fee are charged separately, at different times.
* With an instant upgrade, the higher plan applies right away, so you can avoid overage charges on next month's payment date. To learn how, see \[[Instant upgrade](/en/userguide/plan/instant-upgrade.md)].

## How to keep unnecessary loads to a minimum <a href="#undefined" id="undefined"></a>

If you place several videos on a product detail page, turn on lazy loading. It prevents unnecessary charges and makes your page faster.

\[Example] Say your product detail page has 3 videos: one at the top, one in the middle, and one at the bottom.

|               | Without lazy loading                                                                                              | With lazy loading (recommended)                                                                              |
| ------------- | ----------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
| How it works  | All 3 videos load as soon as the visitor opens the page.                                                          | Each video loads only when the visitor scrolls down to it.                                                   |
| Loads counted | Even if the visitor only watches the top video and leaves, all 3 have already loaded, so **3 loads** are counted. | If the visitor only watches the top video and leaves, the other 2 never load, so only **1 load** is counted. |
| Result        | <p>Unnecessary costs<br>Slower page loading</p>                                                                   | <p>Cost savings (up to 1/3)<br>Faster page loading</p>                                                       |

{% hint style="info" %}
All code provided by Charlla has lazy loading applied.
{% endhint %}

{% hint style="info" %}
Video tags don't support lazy loading because of web technical standards.
{% endhint %}


---

# 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://support.charlla.io/en/userguide/plan/intro.md?ask=<question>&goal=<user_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.