CookieYes pageview limit: What happens and what it costs

The CookieYes pageview limit can make your consent banner disappear when your monthly allowance runs out and extra pageviews are unavailable or disabled. On Basic and Pro, enabling extra pageviews keeps the banner active at $0.30 per 1,000 additional pageviews.

What happens when a CookieYes site reaches 100% of its pageviews?

At 100% of its monthly allowance, CookieYes stops displaying the banner and stops tracking new pageviews if extra pageviews are disabled. If extra pageviews are enabled on an eligible paid plan, the banner stays active and additional usage is billed, as CookieYes explains in its Pageview Pricing guide.

Your website may load normally without displaying a consent banner. Open it in a fresh private browsing session. With no existing consent choice, you should expect the configured prompt to appear if the banner is active.

If the banner is missing, check CookieYes usage, the extra pageviews setting and whether its code is present. A missing prompt alone does not identify the cause.

The Free plan does not offer extra pageviews. For Basic and Pro, the extra pageviews setting determines whether exceeding the allowance generates an overage charge or interrupts the banner. Reaching the limit does not trigger an automatic upgrade.

How does CookieYes count a pageview?

CookieYes counts a pageview whenever a webpage containing its code loads or reloads, according to the CookieYes pricing page. The CookieYes Pageview Pricing guide confirms that a reload counts even if the visitor never clicks the banner.

One visitor can generate several pageviews by opening different pages. CookieYes filters recognized crawlers and known malicious bots. Valid page loads still count when a visitor accepts, rejects or ignores the consent prompt.

Unique visitors and sessions cannot substitute for pageviews. Analytics reports may also differ from CookieYes usage because of different counting rules and consent settings.

Use your CookieYes dashboard's pageview figure when checking your remaining allowance. Before a campaign, compare that figure with traffic from a previous busy period, and check the usage dates. A calendar-month analytics report may cover a different period.

What do extra pageviews cost?

CookieYes charges Basic and Pro accounts $0.30 per 1,000 extra pageviews when the extra pageviews option is enabled. Usage is billed in 1,000-pageview blocks, with partial blocks rounded up under the published billing rules.

For example: A Pro site on a $25 monthly subscription records 400,000 pageviews in its usage month. Its plan includes 300,000 pageviews.

• Extra usage: 400,000 - 300,000 = 100,000 pageviews.
• Billable blocks: 100,000 / 1,000 = 100 blocks.
• Extra charge: 100 × $0.30 = $30.
• Monthly plan plus extra usage: $25 + $30 = $55.

That example assumes extra pageviews were enabled throughout the overage. The fee is based on the extra pageviews, not every pageview recorded that month.

For monthly subscribers, CookieYes adds those charges to the next monthly invoice. On annual subscriptions, CookieYes tracks overages monthly and invoices them when accumulated charges reach $10. Smaller balances carry forward, with any remaining charges collected at renewal.

If extra pageviews are off, the banner stops at the allowance. Free users cannot opt into paid extra pageviews. Estimate spike traffic before enabling paid usage.

How many pageviews does each CookieYes plan include?

CookieYes lists 5,000 monthly pageviews on its standard Free plan, 100,000 on Basic and 300,000 on Pro. Ultimate offers unlimited pageviews subject to a fair usage policy, while Enterprise pricing is custom, according to its plan comparison.

Plan	Monthly price	Annual price	Pageviews per month	Extra pageviews available?
Free	$0	$0	5,000	No
Basic	$10	$100	100,000	Yes, $0.30 per 1,000
Pro	$25	$250	300,000	Yes, $0.30 per 1,000
Ultimate	$55	$550	Unlimited, subject to fair usage	Not applicable (unlimited)
Enterprise	Custom	Custom	Not specified	Not specified

Websites already on the Free plan before July 1, 2025 continue to receive 15,000 pageviews a month. If you have an older account, use the quota shown in your dashboard rather than assuming the standard Free row applies.

CookieYes lists Global Privacy Control (GPC) and geo-targeting from Pro, with branding removal on Ultimate. Compare these features when considering a cheaper plan.

For comparison, CookieConsentHQ offers these monthly allowances:

Plan	Monthly price	Pageviews per month
Free	$0	25,000
Starter	$8	150,000
Growth	$18	750,000
Business	$39	5,000,000
Agency	$79	10,000,000 pooled across 25 sites

Annual billing costs ten times the monthly price. See CookieConsentHQ's pageview pricing for the plan breakdown.

CookieConsentHQ includes GPC and Google Consent Mode v2 on Free. Custom geo-targeting rules by country, US state and Canadian province, along with branding removal, start at Starter.

How do you keep a banner running through a traffic spike?

To keep a CookieYes banner active through a traffic spike, confirm that paid extra pageviews are enabled before reaching your allowance. If you cannot enable them, upgrade manually or switch to a tool that keeps its banner running beyond its pageview allocation.

Check the extra pageviews setting

For Basic or Pro, follow these steps:

1. Open CookieYes and click the profile icon at the top right.
2. Select Billing & Invoices.
3. Find the Billing Details panel.
4. Scroll to Extra usage.
5. Select Enable Extra Pageviews and confirm.

These are the steps in CookieYes's setup instructions.

Eligible paid accounts created after December 23, 2025 have extra pageviews enabled by default. Earlier accounts have them disabled by default. Check the current setting, especially if more than one person manages billing.

Watch the dashboard and warnings

Review pageview usage before a newsletter, campaign or expected traffic surge. CookieYes displays a dashboard warning at the limit and sends email warnings beforehand. Make sure someone responsible for billing receives them. During the campaign, check usage and projected overage costs.

Check the monthly reset date

CookieYes does not necessarily reset pageviews on the first day of a calendar month. Its older Pageviews help page describes a reset tied to website registration. The newer Pageview Pricing guide clarifies that Free uses the registration date, while paid plans use the subscription start date. An upgrade from Free to paid starts a new billing cycle. Verify the applicable date for your account.

Upgrade if you need more room

CookieYes does not automatically upgrade your plan. If your allowance runs out with extra usage disabled, a manual upgrade reactivates the banner.

For a short spike, extra pageviews may be cheaper than upgrading. For sustained growth, compare expected traffic with the next plan's allowance and features. Make changes before traffic arrives.

Consider a banner that stays active above its allowance

CookieConsentHQ keeps its banner running after the plan's pageview limit, without overage fees. On its Free plan, new consent records stop being stored until the following month. The banner and automatic blocking of known trackers keep operating. Paid plans show an upgrade prompt in the dashboard.

The CookieYes alternative that never switches off explains that difference.

When switching any client-side consent tool, check tracking code pasted directly into the website. A hardcoded script or iframe with a src address in the page HTML can start loading before the consent script runs. Every client-side consent tool shares this limitation. Finding cookies set before consent walks through that check.

Test the consent prompt and tracker requests in a fresh browser session after making changes. If an interruption raises questions about your legal obligations, ask a qualified lawyer.