Targeting

Your data decides what each user sees.

Use traits, events and form answers to choose what each user sees.

No credit card required

Candu segment builder: a form-answer condition changes from Onboard new signups to Announce a feature.

Ask once

Use the answers people give you.

Candu form answers become user traits you can target content with.

ShopifyOne question shapes the setup that follows.

Answers become traits.

Each question becomes a trait you can segment on. Turn the sync off per form if you’d rather not.

Keep the data too.

Download responses as a CSV, or send them on by webhook.

Candu user traits: Onboarding Survey answers with Source Forms, beside traits from the Candu SDK.
The form-answer trait
Its source
Candu. The answer, saved as a trait.

Know who’s who

Build an audience from what you know.

Combine traits, events and form answers with AND or OR.

Candu segment builder with segment membership and a form-answer condition joined by AND.
Segment membership
Matching form answer
Candu. Segment membership and a form answer, combined with AND.

Traits.

Role, plan, company: whatever you pass when they sign in.

Events.

What they did, and when.

Form answers.

The question from above, now a trait like any other.

Account traits.

Plan or size at the company level, so a whole account moves together.

First visit.

Brand new, or here for months.

A list.

Upload a CSV of user IDs when the list lives somewhere else.

Make a segment of one (“Only me”) and see exactly what it sees, in your product, before anyone else does.

Show the right thing

A different welcome for each audience.

Give new users a setup checklist and invited teammates a place to start.

Getting live

Candu Getting live editor view: Welcome to Candu. Let’s get you live, with a setup checklist and plan.
A plan for getting live

Invited teammates

Candu Invited teammates editor view: Welcome to your team’s Candu, with live-content review and a first-job checklist.
A first job for a teammate
Candu. Getting live and Invited teammates views in the editor.

Who

Choose the segment that sees each experience.

When

Set a start date, an end date, or both.

Which language

Add language-specific views, with the original as a fallback.

Built with Candu

Resource Guru app navigation with the Getting Started Guides checklist open.
The open getting-started guide
Resource Guru Getting started guides in the app.
The banner’s next step
Gorgias A plan-usage banner in a Candu draft.
HoneyBook project pipeline with the Candu tour step Track each project end-to-end.
A guide to the project pipeline
HoneyBook A project-pipeline tour.

Inside one experience

Change content by audience.

Create audience-specific versions of headings, steps and buttons within one experience.

Candu editor: the block’s view picker changes from Getting live to Invited teammates.
Candu. One home experience, two editor views.

Name each view by who sees it.

“Owners”, “Invited teammates”, “Enterprise”. The first match wins, top to bottom.

Fill copy with traits.

“Welcome, {company_name} team”, with a fallback for users who have none.

A card can hand off to the assistant.

A checklist card shown to a segment can open the assistant on that user’s step.

See what the assistant does

Data in, results out

Use your data. See what works.

Choose an audience with your user data, then measure views and interactions.

  1. 01

    Your data

    User traits, events and form answers.

  2. 02

    Audience rules

    Choose who sees each experience.

  3. 03

    Views and results

    Measure views, clicks and completions.

Connect your data.

Pass traits and events with the JavaScript SDK, REST API or an integration.

Send results to your tools.

Send views, clicks and checklist completions to your analytics tools. Use webhooks for interactions and form responses.

Compare audiences in Candu.

Views, interactions and conversion for each experience, split by the segment that saw it. Goals count a user once they see the experience and do the thing within 7 days.

Test with a control group.

Run an A/B test for one segment against a control group that sees nothing.

Experiment availability depends on your plan.

See every integration
Candu Views by Segment chart and segment list. Labels were changed on screen for the source capture; numbers are unchanged.
Audience
Views
Views by segment, with the matching audience totals.

Before you start

FAQ

How do form answers become traits?
Each answer syncs to segments as a user trait when the form is submitted. It’s on by default, and you can turn it off per form.
What data do segments need?
An identify call with a unique user ID and traits. Events alone can’t build a segment. Traits can come from the SDK, the REST API or an integration.
What if a user matches more than one segment?
Segments on an experience are read left to right, and the user sees the first one they match. Drag to reorder.
Can I target anonymous users?
To build segments, identify users with a unique user ID and traits. Without a user ID, Candu tracks users anonymously and segmentation won’t work.
How does scheduling handle time zones?
Times show in the time zone of whoever sets them. If your team is spread out, check the zone before saving.
How many segments can I have?
Segment limits depend on your plan. See pricing for plan details.

Use what you know.
Show each user the right thing.

Start free

Once we agree access and the journey.

Map your first journey

We map one journey in your app. Within 48 hours of agreeing access and the journey.

Capture

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.