Candu Destination


Candu is the first Editor for your app. Instead of overlaying an experience layer, Candu’s embedded components inherit your style guide, so they look like a native part of your interface. Candu helps you build, iterate, and personalize native onboarding experiences that guide your end-users from basic to expert-level fluency.

This destination is maintained by Candu Labs. For any issues with the destination, please reach out to their team.

NOTE: The Candu Destination is currently in beta, which means that they are still actively developing the destination. This doc was last updated on February 18th, 2020. If you are interested in joining their beta program or have any feedback to help improve the Candu Destination and its documentation, please let their team know!

Getting Started

The first step is to make sure Candu supports the source type and connection mode you’ve chosen to implement. You can learn more about what dictates the connection modes we support here.

Web Mobile Server
📱 Device-mode
☁️ Cloud-mode
  1. From your Segment UI’s Destinations page click on “Add Destination”.
  2. Search for “Candu” within the Destinations Catalog and confirm the Source you’d like to connect to.
  3. Drop in the “API Key” into your Segment Settings UI which you can find from your Candu Settings page.

Page

If you haven’t had a chance to review our spec, please take a look to understand what the Page method does.

An example call would look like:

analytics.page()

Page calls will be sent to Candu as a page event. You will be able to use page events to ensure content is displayed in the right context.

Screen

If you haven’t had a chance to review our spec, please take a look to understand what the Screen method does.

An example call would look like:

[[SEGAnalytics sharedAnalytics] screen:@"Home"];

Screen calls will be sent to Candu as a screen event.

Identify

If you haven’t had a chance to review our spec, please take a look to understand what the Identify method does.

An example call would look like:

analytics.identify('userId123', {
  email: 'john.doe@example.com'
});

identify calls will be sent to Candu as an identify event. The identify call is used to record the identity of an end-user, which enables you to send them the most relevant content.

Track

If you haven’t had a chance to review our spec, please take a look to understand what the Track method does.

An example call would look like:

analytics.track('Clicked Login Button')

track calls will be sent to Candu as a track event. You will be able to measure how well your content is performing by measuring uplift with any track events.

Personas

You can send computed traits and audiences generated through Segment Personas to this destination as a user property. To learn more about Personas, reach out for a demo.

For user-property destinations, an identify call will be sent to the destination for each user being added and removed. The property name will be the snake_cased version of the audience name you provide with a true/false value. For example, when a user first completes an order in the last 30 days, we will send an identify call with the property order_completed_last_30days: true, and when this user no longer satisfies we will set that value to false.

When the audience is first created an identify call is sent for every user in the audience. Subsequent syncs will only send updates for those users which were added or removed since the last sync.

Settings

Segment lets you change these destination settings from your Segment dashboard without having to touch any code.

API Key

This page was last modified: 09 Mar 2020

Get started with Segment

Segment is the easiest way to integrate your websites & mobile apps data to over 300 analytics and growth tools.
or
Create free account