CX Journeys Spring 2021 Release Notes

Released starting June 2021.

Experience Cloud Connector

CX Journeys can now ingest respondent data directly from Medallia Experience Cloud. Experience Cloud writes the respondent event data to a CSV file. Using this connector, CX Journey periodically collects the CSV file(s) and adds that data to the CX journey for each identified respondent.

Note: This feature is only available to super users (Medallia Professional Services).

To implement the connector use the Medallia Experience Cloud Integration wizard to:

  1. Identify the CSV file to ingest, and identify the CX Journey fields that uniquely identify the respondent (users). The default fields are Phone and Email.
  2. Map the fields in the CSV file that identify the respondent (user) to their corresponding CX Journey fields.
  3. Define the events to collect. For each define:
    • Event name — The name of the event, such as “page_load” or “add_to_cart”.
    • Event timestamp — Date/time when the event occurred, which is usually the time when the event record was created: “Creation Date”
    • Additional properties included in the event file and which need to be recorded as part of the event in CX Journeys.
  4. Specify a name for the connector and define the schedule of when to collect events. Optionally include an email for whom to notify if an error occurs during the ingestion.

Amazon S3 & SFTP Integrations

Project administrators (and above) can now connect their data to CX Journeys integration table using Amazon S3 & SFTP as the data source.

CX Journeys Fall 2020 Release Notes

Released starting 3 September 2020

Path Builder

Path Builder now has these enhancements

Expand events (Events breakdown by properties)

Users can now choose to expand the results of path analysis by a particular property to see how it may impact customer journeys. Each event can be expanded by a single property. For example, users can break down the “add_to_cart” event by the “item_name” property to see the most common items added to cart.

To to do so, under path analysis click the “Expand Events” button, and choose the desired event:

Reverse order

Users can create Sankeys that appear in reverse order to focus on the end of the path and present the results from right to left. To enable reverse order, on the report settings turn on the “Reverse order” toggle: 

Hide drop offs

For some of the journeys use cases, the focus is more on the journey’s side and less on the drop-offs. Now, with a simple click (under visualization settings) users can hide drop offs from the Path report visualizations. 

CX Journeys Spring 2020 Release Notes

In this product update you will find updates on:

  • Export Segment
  • Import Segment
  • Roles

Export Segment

The Export Segment enables exporting a set of users from CX Journeys platform to different destinations such as Google Bucket, S3, and SFTP (SSH).

Which formats are being supported?
The supported formats are CSV and JSON.

Who can export segments?
Each project user can export segments.

Which projects support import segment
At the moment, we provide the solution for new project architecture. To check whether your project supports the export please contact Professional Services.

So how can I export a segment?
Under the segments section, clicking on the 3 dots button (on the right corner for each segment) will open for you a drop down list, the 3rd option will be Export.

After clicking on export, the following screen appears:

  • Supported formats are CSV and JSON (with an option to Gzip the file)
  • In the export attributes option the users will have to pick the desired user attributes to be exported

Now you’re ready to move to the 2nd step!

In the 2nd step, the user will be able to choose one of the following options:

  • Google bucket
  • S3
  • SFTP (SSH)

Google Bucket

  • Destination URI – the location address of the bucket destination
  • Google bucket connection approach
    • CX Journeys Service Account Address – In the following approach users will
    • have to copy CX Journeys Address and paste it in the relevant bucket. In the bucket browser (in GCP) Under permissions tab, click add members, and pick a role for the permission. The minimum role needed is “Storage Legacy Bucket Owner”.
    • Another approach that can be used is creating a custom role (under roles section) with the following permissions:
      • storage.buckets.get
      • storage.buckets.getIamPolicy
      • storage.objects.delete
      • Storage.objects.create
    • After the role has been created, click add members, and pick the role created for the permission.
    • Service Account Key – In this approach, the user will have to create a service account in Google Cloud
      • Under IAM & Admin click Service Account, and then create service account
      • After completing step 1 and 2 (no need to add permission), In the last stage of the user will need to create the key in JSON format, and upload it to the wizard


The following fields should be filled:

  • Destination URI – The location address of the bucket destination
  • Region (default is US East N. Virginia)
  • Access Key ID – The user identifier for the bucket destination
  • Secret Access Key – The user password for the bucket destination


This option is fully customizable by the user, depending on the location of the address. The following fields should be filled:

  • File Path – The required folder for the SFTP file
  • Host Name – The location address of the SFTP server
  • Port (usually 22)
  • Username
  • Password

Once the configurations have been set, the user will be able Test the connection, and/or move to the last step.

The user will have to save two last preferences regarding the process:

  • Scheduling/one time operation (manual)
  • Notification to email whether the import failed for any reason
  • Save/Save and run now

Import Segment

The Import Segment enables importing a set of users to the CX Journeys platform, using manual file upload or the project Google Bucket source.

Which formats are being supported?
The supported formats are CSV and JSON, however different extensions (json, jsn, csv, txt, gzip, zip & no extension) are being supported as well

Who can Import segments?
Each project user can import segments

How can I import my own segment?
Under the segments section, clicking on the + button (on the top right corner) will open you a drop down list, the 3rd option will be Import. User will be able to choose from two options

  • Import from Google Cloud Storage
  • Upload local file

Google Bucket

Choosing the Google cloud storage shows the following screen:

  • File: clicking on the browse button will allow the user to choose the desired file from the account source bucket. If you don’t have access to the source bucket please reach your account admin or professional services.
  • Creating new user option allows the user to import new users to the platform
  • Update users option allows the user to update the users existing attributes
  • Unify users allows the user to unify multiple users records to a single user, according to the identity source logic. (Recommended state is No)

Manual upload:

Manual upload approach holds the same functionality, the only difference is the size limit of 50MB.

After completing the 1st step, steps 2 are completely equal, between two options the user will reach to the mapping step.

On the left side the source file properties will be shown, while on the right side the tool will recommend the desired fields (properties) that will be mapped. In addition, for each property the platform will recommend the property expected type, which can be modified by the user (only for new properties).

For each property the user can choose the following options:

  • Add the property as a new property (whether there’s no existing property in the platform)
  • Ignore the property
  • Map the property to an existing property

Note: In the mapping stage the user has to map at least one identifier field (in the mapping fields)

Once the mapping have been set, the user will be able to reach the 3rd and final step.

The user will have need for last couple of preferences regarding the process:

  • Segment name
  • Scheduling/one time operation (manual)
  • Notification to email whether the import failed for any reason
  • Save/Save and run now


Roles are a group of users who hold the same permissions, either for a project or dashboard. Once you add a role to the dashboard (or project), all the users of that role immediately get the same permissions.

Who can manage Roles?
Roles are being managed by the Account Admin.

What is an Account?
Account is the new parent hierarchy for project management. Means that one account can hold several projects which can be easily navigated between (Settings -> Active Project).

As a result, “Account Admin” user level has been added. For each account, only account admins will be able to create new roles.

How can I create a new role? 
Click on User icon -> Roles -> + Button

Each role can be related to several projects and/or several dashboards (left side). On the right side the account admin can add all the relevant users that will be part of the role.

Can I share a dashboard to roles?
Sure, clicking on the dashboard share button will allow users to manage their share preferences for users and roles.

If I’m a project admin, can I provide a role permission?
Yes. A role permission to a project can be provided (or removed) via the permissions section (Settings-> Permissions -> Roles Tab).