HubSpot Testimonials: Add a Testimonial Slider, Module or Video Wall to Any HubSpot Page

Worth being precise, because the answer people give in forums is technically correct and practically misleading.

Can you put testimonials on a HubSpot page? Obviously yes. Content Hub gives you a rich text module, and a testimonial is text. The advice that circulates, in HubSpot community threads and in most of the third-party guides, is exactly that: open the page editor, add a Rich Text module where you want the proof, and type the quotes in. Some themes ship a purpose-built testimonial module, and the HubSpot Marketplace has a whole category of third-party testimonial slider and carousel modules, some free and some paid.

What none of that gives you is a testimonial content type. A blog post in HubSpot is an object. A contact is an object. A testimonial is not. It is field data belonging to the module instance you typed it into, which belongs to the page.

That sounds academic until you count. Below is what the same eight testimonials cost you in maintenance under each approach.

Note the third row honestly, because it gets skipped. A global module is a real option and it is free. If the exact same three testimonials belong in the exact same place on every page, make it global and stop reading. It breaks down the moment you want the SaaS onboarding quote on the onboarding page and the reporting quote on the reporting page, because a global module is one shared block, not a library you draw from.

If you are on Content Hub Professional already, this is the section that matters most, and the honest recommendation is to use HubDB rather than anything else, including us.

HubDB is a relational table inside HubSpot. You define columns once, quote, name, role, company, headshot, product line, and each testimonial becomes a row. A custom module then reads those rows in HubL:

{% for row in hubdb_table_rows(<tableId or name>, <filterQuery>) %}

Because the module holds a reference rather than a copy, editing one row updates every page that renders it, and the filter query lets a product page pull only the testimonials tagged to that product. That is real content modeling, and it is better than pasting quotes into modules by a wide margin.

Two things to know before you plan around it. First, the tier. HubSpot documentation lists HubDB availability as Marketing Hub Enterprise and Content Hub Professional and Enterprise, and adds a line that catches people out: Content Hub Professional or Enterprise is required to use HubDB for dynamic pages, while Marketing Hub Enterprise is required to use HubDB for programmable emails. So a Marketing Hub Enterprise account with a Content Hub Starter website can see HubDB and still not use it the way this page is describing.

Second, the price. These are the plans as listed on the HubSpot pricing page, checked August 2026. Confirm before you buy, because HubSpot repackages regularly.

The jump from Starter to Professional is the whole story. It is not a small upgrade, and nobody buys Content Hub Professional in order to manage testimonials properly. They buy it for the other things and inherit HubDB. If you are on Starter or Free and you want testimonials that update in one place, HubDB is not available to you at any effort level, and that is the situation an embed is actually for.

Third thing, and it is not a price problem: HubDB stores text and image URLs. A video testimonial in HubDB is a link to a video hosted somewhere else, which you still have to get out of your customer, which is the part that never happens. The same structural point applies to WordPress testimonial plugins and to the Elementor testimonial widget, where the storage question decides the maintenance cost in exactly the same way.

This is the section written for the people who searched something like how to automate testimonials in HubSpot, because a lot of the advice out there points you straight at Service Hub, and it does not survive contact with the details.

The pitch sounds unarguable. HubSpot can survey your customers, so send an NPS survey, filter for the promoters who scored 9 or 10, take the comments they left, and put them on the website. You have automated testimonial collection using a tool you already pay for.

Three problems, in increasing order of how much they matter.

It is a different subscription. HubSpot documentation lists feedback surveys as available with Service Hub Professional and Enterprise. On the HubSpot pricing page, Service Hub Professional is listed starting at $90 a month per seat on annual billing, with a one-time onboarding fee of $1,500. That is a real purchase, sitting in a different hub from the one that renders your website, and it exists to measure retention rather than to produce marketing copy.

The output is the wrong shape. An NPS response is a number from 0 to 10 plus an optional free-text comment, and the question that produced it asks how likely somebody is to recommend you. People answer that question diagnostically. The comments you get back are things like support took a while to get back to us but the product is solid. That is enormously useful for the roadmap. It is not a sentence you put next to a pricing table, because nobody wrote it to persuade anybody.

Nobody consented to publication. This is the one that should stop you. A survey response is collected under an internal-feedback expectation. The HubSpot survey flow captures a score and a comment. It does not capture permission to publish the comment, permission to attach the person name, title and company to it, or permission to keep it up next year. Publishing a customer sentence on your marketing site with their name on it is a different act from measuring their satisfaction, and it needs a separate, explicit ask.

None of this means the NPS survey is useless for testimonials. It is an excellent trigger. A promoter score is the clearest signal you will ever get about who to ask, and a HubSpot workflow can fire on it. Use the score to pick the person and the moment, then send them an actual testimonial request that asks a real question and records their consent. The difference between measuring sentiment and collecting proof is worked through on collect testimonials, and the questions that get a usable answer are on the testimonial form page.

There is a cost to manual entry that has nothing to do with hours, and it lands hardest on exactly the workflow HubSpot pushes you into.

You have the customer email open on one screen and a rich text module on the other. The quote runs long for the card layout, so you trim it. A qualifying clause muddies the point, so it goes. Two good sentences from different paragraphs read better joined, so you join them. Then you wrap the result in quotation marks, because that is what a testimonial looks like on a landing page.

The Federal Trade Commission Endorsement Guides at 16 CFR 255.1(b) say an endorsement may not be presented out of context or reworded so as to distort in any way the opinion or experience of the endorser, and that an advertisement need not present the message in the exact words of the endorser unless the advertisement represents that it is presenting the endorser exact words, such as through the use of quotation marks. The quotation marks raise the standard you are held to.

Every edit above is the ordinary, well-meant kind anyone makes in a page editor at the end of a long day. The problem is that once it is made, in a rich text module, there is no record anywhere of what the customer originally wrote. The original email is in somebody inbox, or it was in the inbox of a marketer who left. Keeping the submission with a timestamp and the consent attached does not make an edit legal by itself. It means the original still exists and you can check. Which edits are safe and which are not is worked through in the testimonial release form guide, and the federal rules generally are in FTC testimonial rules.

Placement first, because HubSpot sites are usually built by people who will actually act on this.

A slider earns its place in a tight horizontal strip on a long page where you have one row of vertical space to spend. On the page where somebody is hesitating, usually pricing or the demo request, a rotating carousel hides most of your proof behind a control almost nobody clicks. A full wall of testimonials does more work there, because the quantity is itself part of the argument. Video belongs on that page too, and the case for it is on video testimonials.

Two HubSpot-specific things that go wrong.

That last row is worth a sentence on its own, because HubSpot sites are often bought partly for performance. The metric a testimonial widget usually breaks is CLS rather than load time, and the details are in testimonial widgets and Core Web Vitals.

If HubSpot is one of several stacks you build on, the same embed renders in Webflow, Squarespace, Wix, Framer, WordPress and GoHighLevel, which means one library of approved testimonials across every property instead of a separate copy retyped into each builder. For the B2B approval politics that decide whether you can name the customer at all, see B2B testimonials.