CX Journeys Spring 2020 Release Notes

Export Segment

The Export Segment enables exporting a set of users from Journey Analytics 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, contact Professional Services.

So how can I export a segment? Under the segments section, clicking on the three-dots menu (on the right corner for each segment) will open a dropdown list. The third option is Export.

Options menu.

After clicking on export, the following screen appears:

Export popup.

  • Supported formats are CSL and JSON (with an option to Gzip the file).

  • In the export attributes option, users will have to pick the desired user attributes to be exported.

You can now move on to the second step.

Destination.

In the second 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
    • Journey Analytics Service Account Address – In the following approach users will
    • have to copy Journey Analytics 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

S3

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

SFTP (SSH)

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.

Scheduling.

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 Journey Analytics 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:

Upload file.

  • 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.

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

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.

Verify field mapping.

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 third and final step.

Scheduling.

The user will need to complete the following steps:

  • Enter Segment Name.
  • Enter scheduling/one time operation (Manual).
  • Enter notification details if failure occurs.
  • Click either Save or Save and Run.

Roles

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

Roles.

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? Yes. 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).