Testimonial
Use Testimonial to show customer reviews, quotes, ratings, and social proof.
Content settings
| Setting | What it controls |
|---|---|
| Testimonial items | Add, remove, reorder, and edit testimonials. |
| Customer name | Name shown for the author. |
| Social handle | Optional handle or short identifier. |
| Stars | Rating from 1 to 5. |
| Testimonial text | Quote or review content. |
| Image | Avatar or customer image. |
| Customer name tag | HTML tag used for the customer name. |
| Content tag | HTML tag used for the testimonial text. |
Style settings
| Style area | What you can adjust |
|---|---|
| Layout type | Grid, list, or slide. |
| Slide speed | Timing for slide layouts. |
| Item card | Background, shadow, border, radius, padding, and spacing. |
| Avatar | Size, background, border color, and spacing. |
| Stars | Filled and empty star colors. |
| Text | Customer name, handle, and content colors and typography. |
Best practices
- Use real testimonials and accurate ratings.
- Keep testimonial text short enough for mobile.
- Test slide layouts so users have time to read each item.
FAQ
When should I use this page?
Use this page when you need a quick reference for this Atomicat feature and want to understand what it changes before editing or publishing. It is especially useful while reviewing a page, funnel, quiz, lead flow, product setup, video configuration, or account setting. For Testimonial, keep a short checklist of the fields you changed and test the result in the same browser session.
Do I need to configure this before publishing?
Configure it before publishing whenever the feature affects visitor behavior, tracking, SEO, forms, embeds, checkout, or access. If the feature only changes internal organization, review it before launch so your team can manage the campaign consistently. For Testimonial, keep a short checklist of the fields you changed and test the result in the same browser session.
Can this affect live pages?
Yes, some settings can affect live pages after saving or publishing. Always preview the page, test the main action, and confirm desktop and mobile behavior before sending paid traffic or sharing the URL. For Testimonial, keep a short checklist of the fields you changed and test the result in the same browser session.
What should I check if something looks wrong?
Check the page status, project access, saved revisions, browser cache, connected domain, and any related integrations. If the feature depends on a plan, permission, or enabled module, confirm that your workspace has access. For Testimonial, keep a short checklist of the fields you changed and test the result in the same browser session.