For web testing: Visitor quota is consumed as and when visitors become part of the tests running on your website. Each visitor can become part of multiple tests and is counted only once towards the monthly billing cycle. For example, if three tests are running on your website and a visitor becomes part of all three tests in the same month, then the visitor quota consumed is counted as one.
For server-side testing: Visitor quota is consumed as and when visitors become part of the tests running on your a/b testing platform. Each visitor can become part of multiple tests and is counted only once towards the monthly billing cycle. However, the same user ID needs to be passed for the visitor in multiple campaigns to be counted as one. For example, if three tests are running on your platform and a visitor becomes part of all three tests in the same month, then the visitor quota consumed is counted as one (if the same user ID is passed for that visitor).
For mobile app testing: Visitor quota is consumed as and when visitors become part of the tests running on your mobile app. Each visitor can become part of multiple tests and is counted only once towards the monthly billing cycle. For example, if three tests are running on your mobile app and a visitor becomes part of all three tests in the same month, then the visitor quota consumed is counted as one.