Data Machines
...
Models Supported by Data Machi...
Activity Models
Churn Prediction
6min
this model will provide the likelihood of churn for a user of a digital app, based on the activity of the user collected data ingestion through qualetics api is required for this model to return results the prediction of churn is based on the activity of the user, calculated in the form of the user engagement docid\ xrcxo3v4pxmwgc5kkzcbv at least 3 iterations of user engagement needs to run to provide an accurate prediction note data streaming docid\ vku08owje1j2 quxcf6 k integration is required for this model please complete the integration setup, verifying data connection docid 4iiuungko4l0wf64u ywk and ensure that the streaming is going live docid\ yuos evgre81ztel8fwdi before using this model model input parameters parameter name parameter type required example actor text yes rest api example var settings = { "url" "https //mlapi qualetics com/api/datamachine/init?id=\<datamachine id>", "method" "post", "timeout" 0, "headers" { //add authorization headers here "content type" "application/json" }, "data" json stringify({ "actor" "\<actor id>" }), }; $ ajax(settings) done(function (response) { console log(response); }); model output result parameter name parameter type example churn rest api output example if churn is likely the following output is returned { "churn" "churn likely" } if churn is not found the following output is returned { "churn" "churn not detected", } if insufficient data is present the following output is returned { "churn" "insufficient data to predict churn" } standard output parameters every model consists of the following mandatory standard output parameters input the input string required for the model to extract the categories original input this is the input provided to the first step in model which is retained across multiple steps in a data machine workflow final result the result of the model executed in the final step of the data machine workflow sessionid a unique session id that is generated for every execution of a data machine which can be used to retain results across multiple sessions status the result of the data machine execution if all of the steps in a sequence are successfully executed, a value of "completed" is provided if the execution is interrupted at any point, a value of "terminated" is provided with the reason for termination