Quickbase pricing is based on an entitlement called reads. Depending on your plan type, you have either 1 or 2 components to your reads:
User-based plans—only integration reads count towards your read entitlement
Usage-based plans—both integration reads and user reads count towards your read entitlement
User reads
User reads measure how often users view data within Quickbase. The following table describes actions that count and do not count as user reads:
User read | Not a user read |
|---|---|
Viewing a dashboard | Creating, editing, or deleting data |
Viewing a homepage | Building or managing apps |
Viewing a form or record | Administrative actions |
Viewing a report or page | Printing a report |
Additional scenarios:
Viewing a homepage with multiple widgets—1 user read
Opening a full report from a homepage—1 additional user read
Saving and reloading a report—1 additional user read
Expanding a report to full screen—not an additional user read
Integration reads
Integration reads measure the number of times software services read data from Quickbase and send it externally.
An integration read occurs when:
A third-party system sends an API call that reads Quickbase data
A Quickbase API call retrieves any number of records
This includes generateDocument, which is used to generate documents according to templates built in the app. Find more details in Technical summary of User and Integration Reads.
A Pipelines step delivers data to an external system
3rd Party -> 3rd Party = Billable Read
Quickbase -> 3rd Party = Billable
3rd Party -> Quickbase = Non-billable
Quickbase -> Quickbase = Non-billable
Additionally, user read and integration read activity from the Everyone On the Internet (EOTI) feature all accrue towards integration reads. This is because there is not 1 specific person/license that activity can be attributed to. In Platform Analytics, EOTI users will display as Anonymous, since these are users who were not signed in.
Integration reads do not include:
An API call or Pipeline step run that…
Creates or edits Quickbase Data
Builds or improves Quickbase apps
Manages the Quickbase platform
Receives data from external systems.
API Calls from Quickbase Sync, Quickbase Automations, and Quickbase Webhooks
Printing a report
Manage your read usage
Admins can monitor read usage on the Account summary and Platform analytics pages in the Admin Console. Here:
Usage-based plans show a Total reads gauge that tracks both user and integration reads.
User-based plans show an Integration reads gauge to track integration read usage.
You can view usage trends by app and user.
Read limits and add-ons
Quickbase doesn’t stop your workflows when you reach your read limit. Instead, your account team will contact you to discuss options for purchasing more entitlements.
If you need additional reads, contact your Account Executive to purchase an add-on package. Add-ons are available any time during your contract term.
Entitlements reset with each new contract term and don’t carry over.
Estimate and optimize usage
On the Platform analytics page, compare your Days into contract period tile to your Reads tile to estimate usage for the remainder of your contract. For example, if you’re 33% through your contract and have used 20% of your reads, your projected usage is about 60% of your total allowance.
Legal language in your contract
Your contract defines reads as follows:
Read request—the delivery of data (such as records, reports, forms, or dashboards) in response to a user request. Creating or editing data, building apps, or adding users doesn’t count as a read request.
API read—the delivery of data to an external system in response to an API call. Creating or editing data, building apps, or adding users doesn’t count as an API read.
Support
If you’re unsure which plan you’re on or need help understanding your read metrics, contact your Account Executive or Customer Success Manager.