Send Segments from Journey Manager

   Journey Analytics Previously known as Transact Insights.  |   Analytics User |  18.05 This feature was introduced in 18.05.

Overview

Segmentation analysis is a powerful tool that helps you to understand the behavior of specific groups of users who share a common trait. It allows you to slice and dice Insights data to provide more granularity and identify usability issues that may impact onboarding performance for specific groups of users. In short, you can identify "what group of users" abandon the application, and "at what stage" of the journey. This capability helps businesses increase ROI by focusing investments on optimizing journeys for specific groups of users.

Segmentation analysis is powered by segment events data sent to Insights. Segments are custom events that can be sent via Segment APIs from a Maestro, Composer or Open UX application or from a groovy/fluent service on Journey Manager, to Journey Analytics. Each segment event lets Insights know to which segment a transaction belongs to. A transaction can only belong to one segment or group. For instance, transactions can be grouped by gender, age or age brackets, products selected, or Exchange package used to complete an application, such as LinkedIn prefill or Mitek drivers license scan.

It is important to make sure each segment name and value sent as part of the segment event do not contain any PII (data that could identify an individual user, such as an address, telephone number or account number). For more information on PII, see Data Privacy and Security.

As a safeguard against unintentionally sent personally identifiable information (PII), a segment whitelisting mechanism has been introduced to Journey Analytics. No segments are stored in Journey Analytics unless they have been whitelisted under Preferences > Whitelist segments first. For more information on the Segment Whitelist, see Preferences

Segment compatibility

  • Journey Manager - From 18.05.

Example

Most commonly, Applications may have a review step prior to approval or declination if the Applicant doesn't get automatically Approved or Declined. Typically, a review step will involve a manual review of the Application before making a decision. If you want to study bottlenecks in the backend processing of the application, you can use Segmentation in combination with Milestones.

  • Send Approved, Declined or Review milestone when an application moves to one of those states.
  • When an application moves to Approved or Declined status, send a Segment event whether the Approval or Declination was Instant or Reviewed.

Approved


		TxnUpdater(txn)
		.addMilestone("Approved"
		.update()
		TxnUpdater(txn)
		addSegment("Approval Type", "Instant")
		.update()
				or
				.addSegment("Approval Type", "Reviewed")
				.update()

			

Declined


			TxnUpdater(txn)
			.addMilestone("Declined")
			.update()
				new TxnUpdater(txn);
				.addSegment("Decline Type", "Instant")
				.update()
				or .addSegment("Decline Type", "Reviewed")
		

Review


			TxnUpdater(txn)
			.addMilestone("Review")
			.update()
		

For Journey Analytics to store these segment names and values they need to be added to the Segment Whitelist as shown below.

The Segment Whitelist is shared across all Journey Manager environments (DEV, UAT, TEST, STAGING, PROD). Changes to the Segment Whitelist in one environment will be reflected in all environments.