EMP has integrated with Othot!


The EMP team is excited to announce that we have integrated with Othot!

Othot field category and fields:

The EMP team has made it possible to invest in the campaigns or events that will generate the greatest impact on your enrollment funnel.

EMP users who have an Othot subscription can now use the Othot fields we have added to act upon the campaigns or events expected to create the largest impact on your enrollment funnel.

You can find your Othot fields in the "Field Categories" section of EMP Settings:

Here is a list of descriptions and sample values for the Othot fields in your EMP account:

Field

Description

Example

Date Provided

When the calculation was last refreshed

11/27/2021

Outcome Name

The outcome for which likelihood is calculated

Enroll

Division Name

The name of a customer’s subpopulations

Campus A, Law School Campus

Likelihood

The predicted percentage that the outcome will occur

77.58%

Decile

The categorical ranking of a student’s Likelihood

3

Othot Student Record URL

A url string that can be used to redirect a user to the individual view of the student in Othot. This would enable the user to do individual prescription analysis if desired.

Most Impactful Feature

The most impactful prescription that could be done for that individual student.

Campus Visit: Inquiry

Most Impactful Value

The value of the most impactful feature.

YES

Most Impactful Impact

The increase the most impactful prescription would have on the students likelihood score.

23.45%

Likelihood Factor

The factor that represents how much more or less likely the individual is compared to the average for this lifecycle phase

2.3

Action

Name of prescribed action which will impact the outcome

”Visit type 6”; “Visit type 13”

Expected Impact

The predicted percentage increase to the likelihood of the Outcome if the action is taken

11.58%


Bug Fixes:

  • Improved performance for import missing options page

  • Fix for duplicate field names in some circumstances

  • Fix for duplicate email open interactions in some circumstances

Did this answer your question?