Once Candu is set up, you will not need a developer to create and publish content to your application. However, you will need a technical resource for the initial install.
In the first part of the installation, you will need to work with your developers to define where Candu content appears within your application. These windows are called Portals because your end-users will be able to interact with different onboarding experiences in these spaces. You can embed a Portal somewhere new within your application, like on a home page, or you can include it as a module within an existing page.
Before your technical team can embed a Portal in your application, you’ll need to create one on the Portals page. After creating your Portal, you can share the Portal’s
slug (a unique string to identify your Portal) with your developers, so they can specify where it will appear within your application.
Installation should be quick and painless.
Your technical team can get Candu up and running with our Quickstart Guide. Make sure your developer has a Candu login and can access the Settings page. The technical install involves installing Candu’s SDK, adding the Portal
slug, and whitelisting the sites where Candu content will appear. We also recommend syncing with your technical resources on Step 4 if you want to do any kind of user segmentation or eventing.
We’ve included a handy Notes for Developers section below for quick reference.
Once your Portal is created, build your first onboarding experience or “Tutorial.” With Candu’s drag-and-drop Editor, creating an onboarding flow is as simple as a few clicks.
Add content blocks, including media, text, gifs, etc., to build your first onboarding experience. You can further organize your content into containers, like checklists, cards, and carousels. See what's available:
Before setting your Tutorial live, you can Preview how it looks in your application, so there are no surprises once you publish.
After building your Tutorial, you can decide which end-users should be able to see it.
Candu allows you to create experiences as unique as your end-users. You can target different experiences at groups of end-users, Segments, using two types of data: events (first 30 days, clicked ‘sign up’) and traits (email domain, role, product tier).
With Segments, you can ensure that your end-users only access Tutorials that are relevant to their use case.
Last but not least, you’ll want to know how your end-users are responding to the onboarding you just created.
Set up Goals in Candu to track how different Segments interact with your Tutorials. Goals are tied to Candu’s Analytics Suite and are designed to help you understand how your Tutorials affect your end-users’ behavior.
Goals are event-based (‘create project’, ‘upgrade account’) and you can create as many Goals as you’d like.
Installing Candu: Developers should install the Candu SDK (see our Developer quickstart).
Setting up a Portal: Anyone can create the Portal in Candu, but whoever does so must pass the Portal
slug, so Candu knows where to render its content.
Metadata: In order to target content and understand its impact, you’ll want to pull in some information about your users in the form of events (actions your end-users take) and traits (end-user properties). Candu only begins tracking action after receiving the events, so it is important to set up relevant metadata during the installation.
Styling: Candu is designed to blend in with your application. In order to achieve a seamless product experience, developers must inject your application’s style guide. If a component does not have a defined style, Candu will provide a fallback design. See the React Style Guide for more information.
If you’re ready to Publish your Tutorial, full steam ahead! 🚂