Testing your content

Two ways to preview your content, and best practices before launch.

✅ Testing overview

👋Questions about your upcoming launch? Team Candu team is here to help. Reach out any time to support@candu.ai.

Candu integrates with your app to create native product experiences, so no end-user can tell the difference between what your front-end team has coded and what Candu renders.

There is no better test than going live with your target audience, and seeing how they respond, but it can feel more secure to test a few important things before you launch:

  • First, is your content clear? Do you have any typos you’d prefer to have a colleague ahem mention before a client notices? As with any copy, it’s in your best interest to get a second pair of trusty eyes on your content.

  • Second, does it look and feel the way you intended across all browsers and screen sizes? Candu supports desktop, but your extra-large monitor may look different than a 14 inch laptop, and Safari sometimes does things that Chrome does not.

  • Third, if you’ve created unique content for different Segments, it’s good to double-check how your Tutorials appear to each group of end-users.

Testing approaches

We’ve seen a two approaches work for testing Candu:

With an internal audience (“dogfooding”)

Your internal audience is useful for quick, candid feedback from people who understand your brand and goals. They can give you feedback on how different elements should look, or how to improve your explanations, since they’re closest to your product.

With an external audience of beta-friendly clients

Beta-friendly clients are great for almost the opposite reason as your internal audience—they aren’t as close to your product, so they’ll be able to give you fresh insights into issues that people on the inside may overlook.

Since you are launching an onboarding workflow, if you launch with beta-friendly clients, you should decide if you want to start with new end-users at those accounts, or with people who have already onboarded but who give good feedback (or both).

Testing best practices

Testing with both audiences

Testing with both internal and external audiences means you’ll get lots of feedback from people who know your product and from people who don’t.

Keep in mind that this feedback can slow down your launch, and muddy the waters as you balance varying opinions.

Communication cannot be overstated

Regardless of who you select to test your onboarding, it’s a great idea to communicate as much as possible.

Let internal testers know what persona they’re playing, and have them try to get in that audience’s frame of mind. Are they testing an admin flow, or a new end-user flow? Tell them which perspective is most useful for approaching the testing.

Raw feedback from new end-users will give you a sense of your Tutorial’s impact, but it may be insightful to tap a few veteran customers who can compare their original onboarding with the new one.

Plan your test

To streamline an effective launch, we recommend the following:

  • Create a timeline, so testers know when to provide feedback.

  • Ask for feedback on specifics actions and components—see examples in What to Test.

  • Remaining focused on publishing. Your onboarding will not be perfect the first time. Your goal is to launch with a great first draft and then iterate.

What to test

Tutorial Content: Content, Containers and Integrations

Content: Are your concepts clear? Do people understand the flow they are supposed to follow?

  1. Copy: Does the person testing understand the message you are trying to convey? Are there any copy edits to make? Any typos to fix?

  2. Media: Does embedded media render properly? If there is a video, gif, or embedded component, does it start playing correctly?

  3. Buttons / Interactions: Do the buttons work, and do they link to the correct pages? Do the interactions improve the flow of the onboarding?

Containers: Are you organizing your content into containers such as tabs, carousels, or modals? Does the flow and the layout make sense? Are there steps that are missing? Is it easy and logical to move through your content?

Integrations: If you’ve set up integrations such as guides, are they operating as expected?

Testing Portals

Does the content look good on the page? If these are working correctly, they really shouldn’t stand out to people at all!

  1. Look and feel: Does your content properly map your app’s styles? Do all the elements look like they are integrated into your interface? Can they tell where your Candu content starts and ends?

  2. Across devices: How does your content look with different browsers and screen sizes?

Testing Segments

Are the right people seeing the right content? If your end-users fall into multiple buckets, have you set up the hierarchy such that your end-users see the most relevant content?

Testing eventing

Do you have the data you need to create the right Segments? When your end-users interact with Candu, are you properly receiving the data in your Event Stream.

Testing requires the use of custom Segments. Ensure that you have created the Segments you need before asking users to test!

The results of your test

Something amiss? Contact support@candu.ai or see our Developer Testing and Troubleshooting guide