The Candu SDK has two components that need to be set up: the Candu Provider and Portals.
The Candu Provider takes four inputs (see inputs), and fetches Segment membership for the end-user via the Candu API. This information feeds into a Portal component, which determines which Tutorial to render for each end-user.
To ensure fast caching and high uptime, the Portal and Tutorial components fetch content from Candu’s CDN, respectively.
As your end-users interact with your Tutorials, eventing data is created and returned via the Candu API.
To make any changes to your application, your content, or to see how your content is performing, login to Candu’s Dashboard.
As your page renders, Candu’s SDK uses four inputs to build in-product experiences:
User ID – The identification for each end-user whom you wish to track.
(Optional) Traits – End-user properties you can use to tailor your content. These properties are tracked with an Identify call.
(Optional) Styleguide – A library of the UI components you’ve chosen to render.
(Optional) Variables – A means to provide additional flexibility and privacy, variables can be calculated from end-user traits, such as API keys, or provided at runtime to render dynamic content, such as custom components.
Once you’re ready to start with Candu, head over to the Developer Quickstart, which guides you through installing the SDK.