Quickbase pricing is based on an entitlement called “Reads”. Depending on the contract-type that you’re on, you will have either 1 or 2 components to your Reads. Customers on User-based contracts, only Integration Reads count towards their entitlement. Customers on Usage-based contract have both Integration Reads and User Reads count towards the "Read" entitlement allocation.
Q: What are User Reads?
A: User Reads measure the number of times that users view forms, reports/charts, homepages, and dashboards.
Q: How are User Reads counted?
A User Read is:
- A Dashboard view, regardless of the number of charts/tables/widgets
- A Homepage view, regardless of the number of charts/tables/widgets
- A Form/Record view, regardless of the number of tables on the Form
- A Report/Page view regardless of the number of records in a report
A User Read is NOT:
- Using the Web or Mobile Interface to…
- Create, Edit, or Delete Quickbase Data
- Build or Improve Quickbase Applications
- Manage or Administrate the Quickbase Platform
- Any type of view that is not a Dashboard, Form, or Report View
Q: What are Integration Reads?
A: Integration Reads measure the number of times software services read data from Quickbase and deliver it externally.
Q: How are Integration Reads counted?
An Integration Read is:
- An API call sent from a 3rd party system, that involves a read of data from Quickbase
- An API call that requests record information from Quickbase, whether 1 record, 100 records, or 1M records
- A Pipelines Step that results in data being delivered to a third-party system would be counted as an Integration Read.
- Assuming a V3 Plan:
3rd Party -> 3rd Party = Billable Read
Quickbase -> 3rd Party = Billable
3rd Party -> Quickbase = Non-billable
Quickbase -> Quickbase = Non-billable
- Assuming a V3 Plan:
- Additionally, User Read activity and Integration Read activity from the “Everyone On the Internet” feature all accrues towards Integration Reads (since there is not 1 specific person/license that activity can be attributed to). In Platform Analytics, EOTI users will show as "Anonymous," since they are users who were not signed in.
An Integration Read is NOT:
- An API Call or Pipeline Step Run that…
- Creates of Edits Quickbase Data
- Builds or Improves Quickbase Applications
- Manages or Administrates the Quickbase Platform
- Receive data from external systems.
API Calls from Quickbase Sync, Quickbase Automations, and Quickbase Webhooks
Q: If I am on a user-based plan, do I have to worry about User-Reads? Will I see User Reads on my contract?
A: No, customers on User-based plans receive unlimited User Reads because they have a User License entitlement instead. The Reads entitlement for these customers only includes Integration Reads.
Q: If I am on a usage-based plan, do both my User Reads and my Integration Reads have limits? Are the limits the same?
A: For customers on usage-based plans, there is only 1 combined limit (Reads); there is not 2 separate, individually measured entitlements. Usage-based customers can use whatever mix of User Reads and Integration Reads they desire, as long as the total stays under the purchased amount.
Q: What happens when I hit the limit of my Reads entitlement?
A: We want your business workflows to remain intact without any disruption. As a result, Quickbase will not stop any workflow or functionality (including Pipelines) if your usage reaches the purchased amount. This is a soft-limit and will trigger a conversation with your Quickbase Account team about the options to purchase more entitlements.
Q: How do I know if I’m on a User or Usage-based plan?
A: In Platform Analytics (a tab within the Admin Console), customers on Usage-plans have their Total Reads tile as a gauge, to indicate there is a capped limit on that metric (the combination of User Reads and Integration Reads)
In Platform Analytics, customers on User-based plans will have the Integration Reads tile as a gauge, to indicate that only this type of Read is a capped entitlement.
Q: What if I do not use all my allocated Reads during my contract term?
A: Entitlements are a limit and are not something that carry over from one contract term to the next. We would encourage you to make the best of what you have purchased to deliver maximum value to your business. There are a variety of use cases and workflows that Quickbase helps 5000+ customers across the globe. Please talk to your AE / CSM if you need help building applications on Quickbase.
Q: How are User Read and Integration Read allocations calculated?
A: For existing Quickbase customers, we use your current usage of the platform in order to help you determine your Read(s) allocation(s). For new customers, we summarize usage data across accounts with similar profiles to yours in order to determine your Read(s) allocation(s).
Q: How do I monitor usage of my Reads?
A: Realm & Account Admins can see how many Reads have been consumed in the contract-period via our new feature in our Admin Console called Platform Analytics. Admins are able to see all major entitlements & value metrics via 1 concise dashboard, with the ability to drilldown into each metric to see the top Apps & Users (and their trends over time). To learn more about this feature, Platform Analytics.
Q: What if I need more Reads during my contract term?
A: Add-On Read packages are available for add-on purchase throughout your contract term. Quickbase will not stop any product/workflow functionality if you exceed your capped entitlement. When usage reaches certain levels, the Quickbase account team will contact you about adding entitlements to your contract.
Q: Is there a way to account for anticipated growth within my account in order to avoid increased add-on costs later?
A: Yes, in Platform Analytics you can compare how far you in your Days into Contract Period tile (let’s say 33%), to your Integration Read tile (let's say its 20%). By comparing these 2 tiles, you can make estimates on how much you will use in your contract period. In this example, the projected usage of Reads in the Contract Period is 60% of your total purchased amount.
Q: Can I self-service add-ons?
A: Not currently, if you do want to purchase any type of Add-On packages, contact your Account Executive.
Q: Are Quickbase to Quickbase Step-Runs counted toward the billable entitlements?
A: No. Quickbase to Quickbase Step-Runs are not counted toward the billable Integration Read entitlement. They are unlimited.
Usage Based Pricing: Scenario Based
Q: What if I have more than 1 report or widget on a homepage, will it count ALL the reports?
A: No, it only counts the 1 dashboard view
Q: When I am on a homepage and I want to make a report larger, I usually click the display in full window button… Will this consume an additional User Read?
A: No, this does not incur an additional User Read.
Q: When I am on a homepage sometimes, I like to go to the full report by clicking the Full Report button … Will this consume an additional User Read?
A: Yes, this does incur an additional User Read because you are going to a separate view of the report
Q: When I am on a homepage sometimes, I like to customize the report by clicking the Customize Report button … Will this consume an additional User Read?
A: No, this does not incur a User Read because you are performing an edit action. All editing actions are unlimited.
Q: Do building activities (creating a form, editing a field name, adding a new, etc) count toward User Reads?
A: No, this does not incur a User Read. These activities are unlimited. We want you to build the best apps that you can for you & your users
Q: Does Quickbase Sync, Automations, Webhooks, or Actions count towards my Integration Read allocation?
A: No, we do not count these internal features towards your Integration Read allocation
Q: What language is written in our contract on User Reads and Integration Reads?
A: Here is the legal language in contracts…
Read Request means delivery of data by the Quickbase Service (such as records, reports, forms and dashboards) in response to an individual User request... For clarity, creating records and reports, adding and editing data, building applications, changing settings, and adding users are not considered a Read Request and therefore do not count against a Customer’s Read Request limits
API Read means delivery of data by the Quickbase Service to an external system in response to an API call. For clarity, creating records and reports, adding and editing data, building applications, changing settings, and adding users are not considered an API Read and therefore do not count against a Customer’s API Read limits.
Q: Do Grid Edit reports count as User Requests and/or Integration Reads?
A: Yes, accessing a Grid Edit report will count as 1 user read. If you do edit within the grid, it will not incur additional User Reads. If you save after editing and reload the page, it will incur an additional User Reads
Q: Does printing reports count as a User Requests and/or Integration Reads?
A: No, it does not incur any Reads
Q: If a table report has multiple pages, and a user brings up the report, then clicks to the second page, is that two reads or just one?
A: For the legacy table report, we count one User Read per page. So if you go from page 1, to page 2, to page 3 in the legacy Table Report, it will count as 3 User Reads. For the default table report, there is only 1 User Read for the entire report. So you can sift through pages as you like, and it only counts as 1 User Read
Q: How do default table reports get counted for User Reads and Integration Reads?
A: We count 1 User Read per default table report. When you select the next Page, that does not incur an additional User Read. When you add column Filters and use them, that does not incur another User Read.
Q: How do Dashboards get counted for User Reads and Integration Reads?
A: There is one User Read per Dashboard view (regardless of how many Reports are on there). This is how Homepages get counted today.
Q: Why are there null User IDs that are accruing Reads?
A: There are a few reasons:
- If your app is open to EOTI (everyone on the internet), the activity from these users will not be associated to a User ID. They may show up as “User ID = 1” for some customers
- Additionally, when a user is not logged in and tries to view a dashboard (generally via a saved URL), it triggers an no-UserID Read. Then once they log-in, the subsequent User Reads are associated to their name.
- Lastly, User Reads within the Reports and Forms category get triggered via Notifications, Subscriptions, and Reminders that fire in the tables They do not fire against a User ID, therefore they are null. They may show up as “User ID = 3000” for some customers.
Q: Do User Reads and Integration Reads in a Sandbox app count against a client's allotment?
A: Yes. Customers are using, testing, and interacting with our platform, therefore we count test/sandbox application User Reads and Integration Reads.
Q: If my Pipeline is Quickbase to Quickbase, but I have clock or other built in tools as part of it, will those be considered free or charged? Currently only items under the Quickbase channel are considered free.
A: See this section to see which Steps are free vs. Billable.