For newsletters
Nothing in an email runs a script
Email has not run JavaScript for twenty years, and that is a good thing. A testimonial in a newsletter is a picture or it is nothing — so it has to be a good picture.
No password. You get a private dashboard link right after this — bookmark it, that's your login.
Why it is hard here specifically
Newsletter operators try to embed a widget in an email, discover it does not work, and end up pasting a grey screenshot of a tweet.
What Kudobox does about it
The quotation, drawn as an image
With your colour and your mark on it, at the size the post wants. Paste it in like any other picture.
A wall to link to
A page of its own, at your own address, for readers who want the rest.
Ask your readers, not just your customers
A reader who replies to say an issue changed their mind has written you a testimonial. That is what the “Email” source is for.
The questions worth asking
Copy these into your form and change them to sound like you. Each one is written to produce a sentence you could actually publish — which is the whole difference between a testimonial and a compliment.
- What made you subscribe?
- Which issue do you still think about?
- What have you done differently because of something you read here?
- Who do you forward it to?
- How would you describe it to them?
Where to put them
The layouts that suit this trade. All twenty-three are on every plan, on as many pages as you like.
And what you already have
You are probably not starting empty. These are the places this trade usually finds its first ones.
The limit, said plainly
Substack posts and email clients will not run the widget. That is on the page about it rather than in a support article you would find afterwards.
Other trades
Your customers already wrote the words
Send one link and their words arrive here instead — with the date, with the permission, and read for risk before you publish.
Everything it does