This preview of pull request 1639 is meant for internal use only.

journy.io Destination

journy io quick info

journy io is in beta, and accepts Track, Page, Identify, and Group calls. If you reference it in the Integrations object, call it “journy io”.

journy.io empowers your marketing, sales and support teams with actionable customer insights, needed to improve conversions, increase sales, and reduce churn, right in the tools they already use.

This destination is maintained by journy.io. For any issues with the destination, contact the journy.io Support team.

Note:

The journy.io Destination is currently in beta, which means that they are still actively developing the destination. To join their beta program, or if you have any feedback to help improve the journy.io Destination and its documentation, contact the journy.io support team!

Getting Started

  1. From the Destinations catalog page in the Segment App, click Add Destination.
  2. Search for “journy.io” in the Destinations Catalog, and select the “journy.io” destination.
  3. Choose which Source should send data to the “journy.io” destination.
  4. Go to the journy.io app, add Segment as source in the connections, choose “Manual setup” and copy the “API key”.
  5. Enter the “API Key” in the “journy.io” destination settings in Segment.

Page

If you aren’t familiar with the Segment Spec, take a look at the Page method documentation to learn about what it does. An example call would look like:

analytics.page()

Segment sends Page calls to journy.io as a pageview. Only page calls with anonymousId and properties.url are accepted.

Identify

If you aren’t familiar with the Segment Spec, take a look at the Identify method documentation to learn about what it does. An example call would look like:

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

Segment sends Identify calls to journy.io where they create a new, or update an existing user.

Track

If you aren’t familiar with the Segment Spec, take a look at the Track method documentation to learn about what it does. An example call would look like:

analytics.track('Login Button Clicked')

Segment sends Track calls to journy.io as a new events.

Set context.groupId to record the event and attribute it to a specific account. This is useful in B2B use cases where you need to attribute your non-group calls to an account.

Group

If you aren’t familiar with the Segment Spec, take a look at the Group method documentation to learn about what it does. An example call would look like:

analytics.group('groupId123', {
    name: "ACME"
});

Segment sends Group calls to journy.io where they create a new, or update existing accounts. If a userId is set, the user is linked to the account.

Personas

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

For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Personas sends an Identify call with the property order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it’s been more than 30 days since their last order), Personas sets that value to false.

When you first create an audience, Personas sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

Settings

Segment lets you change these destination settings from the Segment app without having to touch any code.

API Key

Add Segment as source in the connections and choose “Manual setup” to copy the API key.

This page was last modified: 12 May 2021



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