usageAllowed and the page-view gate

How page views are counted, how the gate returns usageAllowed false, and what the embed does when the plan limit is reached.

Every Hubbo plan includes an allowance of page views. The embed checks that allowance on boot. This article explains the semantics so you can predict and debug behavior.

What a page view is

A page view is one unique browser session (session UU), not one page load. The API sets an httpOnly cookie named hubbo_pv_* (one per account) on api.hubbo.io the first time a session loads the embed. While that cookie exists, further loads and widget interactions in the session do not add to the count. Closing the browser and coming back later starts a new session and counts again.

Plan	Page views per period	NPS responses per month
Free	10,000	50
Standard	1,000,000	5,000
Premium	50,000,000	50,000

Which hosts count

Your own site: counts.
hubbo.io and www.hubbo.io (this marketing site): count.
Public pages on app.hubbo.io (notification page, roadmap, status): count, once per browser session — same gate as your site.
Admin previews only are skipped, and only when a signed-in team member loads Hubbo from a Hubbo preview host (for example the editor on app.hubbo.io). A spoofed Origin header alone does not skip counting.

The gate

The first client_getCurrentAccount call counts the session and returns usageAllowed. It is false when the plan allowance is exhausted. When it is false, the embed does not mount notifications, NPS or surveys and does not start subscriptions. After the session cookie is set, later checks in that session only read the current usage and do not increment it.

query {
  client_getCurrentAccount {
    usageAllowed
  }
}

Do not work around the limit

The session cookie is httpOnly and lives on the API host precisely so that page scripts cannot forge it. Setting your own cookies, storage keys or headers does not bypass the limit and is not supported. Upgrade the plan or wait for the next billing period.

How the limit resets

Upgrading a plan or a successful subscription invoice resets the page-view counter for the period.
Downgrading or cancelling does not grant a free reset. If usage is above the new plan limit it is capped at that limit.
On the Free plan the counter starts over after 30 days once the limit has been reached.

What visitors see

Nothing. When usageAllowed is false the widgets simply do not appear, client_getAllNotifications returns an empty list, and the public roadmap and status pages answer as “not found”. The gate uses the count before the current session is added, so the session that reaches the limit is still served. Account owners can opt in to an email warning that the page-view limit is about to be exceeded.