Topics

Overview

Each business has its own unique way of evaluating accounts and users that are using their platform. A most common need would be to define ideal customer profiles (ICP) or users/accounts that have specific characteristics for your business which you want to monitor. journy.io therefore features Segments.

journy.io allows its subscribers to create as much Segments as needed.

Let us show you how it's done... 🚀

Segment anatomy

When accessing Settings → Segments, you can see existing Segments already created, for either users or accounts.

Open

Hoovering over an existing Segment, or pressing the [+] button in the top-right corner, will allow you to update or create a new Segment, where one will be asked to provide:

• A name: Segment name that will appear as value in the computed property 'Segments'.

• A set of conditions which defines the Segment. Each user/account meeting these conditions will be part of the Segment; and thus hold the name of this Segment as one of the values of its computed property 'Segments'

Open

Use of Segments throughout journy.io

Once Segments defined, each account/user will be processed and the 'Segments' computed property will hold the names of all Segments the account/user is part of.

There are 3 use cases for segments:

Use Segments as condition element for views and playbooks

Simply create a new playbook, or press filter in your list/stage view and you will see our default condition builder. When pressing '+ Add condition', you'll see 'Segments' as one of the condition elements.

Condition rules can be that a user/account will be in/not in a segment.

Use Segments as filter for sync'ing users/accounts to destinations

If you open a connector — e.g. HubSpot — and navigate to the Destination tab, you can see that optionally, you can filter users/accounts. Simply select the segments you want to be sync’d to select destination. Not filling in anything means every user/account will be sync’d.

Sync property 'Segments' downstream your connected apps

Every user/account in at least one Segment, will have the computed property 'Segments' filled in.

When navigating to a connection's destination tab, you can sync that computed property 'Segment' to a destination property, typically typed List or Multi-Line Text.