Limits and plans

Testimonials has no price of its own. Each plan of Privatus Analytics includes a number of new testimonials a month and a set of features. A testimonial is never an event, so it does not count toward your monthly events, and your events do not count here.

What each plan includes#

Tags, manual collections, saved views, triage, bulk actions, mentions, duplicates, the brand kit, every widget layout, the API and MCP are part of every plan. Where a page of this section says a feature is part of Business, Enterprise has it too.

A feature your plan does not include is switched off and says so, with a link to the plans. What was made with it is kept and locked, never deleted: a smart collection, an auto-tag rule or a translation made on Business is still there after a downgrade and works again after an upgrade. Each feature's page says what a locked one does meanwhile.

What counts#

• A testimonial a customer sends through a form or a request link.
• A testimonial you add by hand.
• A testimonial added through the API or an MCP tool.
• What a scheduled re-sync of an import source brings in (Pro and up, see Automatic sync).

What never counts#

An import never counts, on any plan. A one-time import from a review platform or any page, a spreadsheet upload, a move from another testimonial tool and "find testimonials on my website" bring in everything they find, whatever your count is. They are never held and never refused for the limit.

The Free plan has a limit of a different kind for imports: one import a month that we fetch from a review platform or a page. Spreadsheet uploads and moves from another tool are not limited. See The Import tab.

Editing, approving, restoring from the trash and undoing never count either. A testimonial counts once.

At the limit#

Nothing a customer sends is dropped.

• A form submission is stored in full and waits. It stays pending with the badge Waiting. You can read every word, edit it, tag it and move it to the trash. It cannot be approved yet, so it is shown nowhere. The customer never sees an error for it.
• What you add yourself is refused until there is room: by hand, through the API or an MCP tool. The server responds with the code allowance_reached.

While any testimonial is waiting, the Inbox shows a strip above the list with how many are waiting, the date they become usable, See them and a link to the plans.

Once the month's number is used, the Forms tab says so too: "This month's allowance is used (5 of 5)", with how many are waiting and the date they are released. Your forms keep accepting answers.

When waiting testimonials are released#

Waiting testimonials are released oldest first:

• When a month starts. A job runs every day just after midnight UTC, and its run on the 1st finds a fresh month.
• When your plan changes, shortly after the upgrade.

Each released testimonial counts against the month it is released in, so a Free site with eight waiting on the 1st releases five and keeps three waiting. A released testimonial stays pending: you approve or reject it like any other.

API and MCP#

In the API, a waiting testimonial has waiting_for_allowance set to true, and testimonials_approve responds with the code waiting_for_allowance. List them with waiting=yes or the search is:waiting. The fields and codes are in the API reference.

Good to know#

• The number is per workspace, not per site: every site of the workspace draws on the same month.
• A testimonial counts once, in the month it arrives or is released. Trashing or deleting it does not give the place back.
• Recordings already stored keep playing after a downgrade to a plan with a shorter length or with text only. Only new recordings are held to the new plan.
• Request emails are sent through your own email provider (Business and up) and have a monthly number of their own for each site, shown on Email sending.