Abstract: In some implementations, a computing device determines an event timeline that comprises one or more finance-related events associated with a person. A production classifier may be used to determine (i) an individual contribution of each event in the event timeline to a financial capacity of the person and (ii) a first decision regarding whether to extend credit to the person. A bias monitoring classifier may, based on the event timeline, determine a second decision whether to extend credit to the person. The bias monitoring classifier may be trained using pseudo-unbiased data. If a difference between the first decision and the second decision satisfies a threshold, the production classifier may be modified to reduce bias in decisions made by the production classifier.

Abstract: In some implementations, an event timeline that includes one or more interactions between a customer and a supplier may be determined. A starting value may be assigned to individual events in the event timeline. A sub-sequence comprising a portion of the event timeline that includes at least one reference event may be selected. A classifier may be used to determine a previous relative value for a previous event that occurred before the reference event and to determine a next relative value for a next event that occurred after the reference event until all events in the event timeline have been processed. The events in the event timeline may be traversed and a monetized value index assigned to individual events in the event timeline.

Abstract: Disclosed herein are methods, systems, and processes for distributed logging for securing non-repudiable transactions. Credentials, request information, response information, and action items generated and received by a requesting computing system and a responding computing system, and transmitted between the requesting computing system and the responding computing system are separately recorded and stored in a requestor log maintained by the requesting computing system and in a responder log maintained by the responding computing system.

Abstract: In some implementations, an event timeline that includes one or more interactions between a customer and a supplier may be determined. A starting value may be assigned to individual events in the event timeline. A sub-sequence comprising a portion of the event timeline that includes at least one reference event may be selected. A classifier may be used to determine a previous relative value for a previous event that occurred before the reference event and to determine a next relative value for a next event that occurred after the reference event until all events in the event timeline have been processed. The events in the event timeline may be traversed and a monetized value index assigned to individual events in the event timeline.

Abstract: In some implementations, an event timeline that includes one or more interactions between a customer and a supplier may be determined. A starting value may be assigned to individual events in the event timeline. A sub-sequence comprising a portion of the event timeline that includes at least one reference event may be selected. A classifier may be used to determine a previous relative value for a previous event that occurred before the reference event and to determine a next relative value for a next event that occurred after the reference event until all events in the event timeline have been processed. The events in the event timeline may be traversed and a monetized value index assigned to individual events in the event timeline.

Abstract: Disclosed herein are methods, systems, and processes for distributed logging for securing non-repudiable transactions. Credentials, request information, response information, and action items generated and received by a requesting computing system and a responding computing system, and transmitted between the requesting computing system and the responding computing system are separately recorded and stored in a requestor log maintained by the requesting computing system and in a responder log maintained by the responding computing system.

Abstract: Disclosed herein are methods, systems, and processes for distributed logging for securing non-repudiable transactions. Credentials, request information, response information, and action items generated and received by a requesting computing system and a responding computing system, and transmitted between the requesting computing system and the responding computing system are separately recorded and stored in a requestor log maintained by the requesting computing system and in a responder log maintained by the responding computing system.

Abstract: In some implementations, an event timeline that includes one or more interactions between a customer and a supplier may be determined. A starting value may be assigned to individual events in the event timeline. A sub-sequence comprising a portion of the event timeline that includes at least one reference event may be selected. A classifier may be used to determine a previous relative value for a previous event that occurred before the reference event and to determine a next relative value for a next event that occurred after the reference event until all events in the event timeline have been processed. The events in the event timeline may be traversed and a monetized value index assigned to individual events in the event timeline.

Abstract: In some implementations, a computing device determines an event timeline that comprises one or more finance-related events associated with a person. A production classifier may be used to determine (i) an individual contribution of each event in the event timeline to a financial capacity of the person and (ii) a first decision regarding whether to extend credit to the person. A bias monitoring classifier may, based on the event timeline, determine a second decision whether to extend credit to the person. The bias monitoring classifier may be trained using pseudo-unbiased data. If a difference between the first decision and the second decision satisfies a threshold, the production classifier may be modified to reduce bias in decisions made by the production classifier.

Abstract: In some implementations, a computing device may determine, from multiple data sources, multiple event timelines, with each event timeline associated with a customer. Each event in an event timeline represents an interaction between the customer and a vendor of goods and/or services. For N (N>1) marketing campaigns, N augmented timelines may be created for each timeline by augmenting each event timeline with the individual marketing campaigns. Thus, for M (M>1) customers, M×N augmented event timelines may be created. A trained machine learning model may perform an analysis of each augmented event timeline to predict results of executing each marketing campaign. The results may include total predicted revenue and total predicted cost resulting from executing each marketing campaign. A particular marketing campaign from the N marketing campaigns may be selected and execution of one or more marketing events may be initiated.

Abstract: In some implementations, a computing device determines an event timeline that comprises one or more finance-related events associated with a person. A production classifier may be used to determine (i) an individual contribution of each event in the event timeline to a financial capacity of the person and (ii) a first decision regarding whether to extend credit to the person. A bias monitoring classifier may, based on the event timeline, determine a second decision whether to extend credit to the person. The bias monitoring classifier may be trained using pseudo-unbiased data. If a difference between the first decision and the second decision satisfies a threshold, the production classifier may be modified to reduce bias in decisions made by the production classifier.

Abstract: In some implementations, an event timeline that includes one or more interactions between a customer and a supplier may be determined. A starting value may be assigned to individual events in the event timeline. A sub-sequence comprising a portion of the event timeline that includes at least one reference event may be selected. A classifier may be used to determine a previous relative value for a previous event that occurred before the reference event and to determine a next relative value for a next event that occurred after the reference event until all events in the event timeline have been processed. The events in the event timeline may be traversed and a monetized value index assigned to individual events in the event timeline.

Abstract: Disclosed herein are methods, systems, and processes for distributed logging for securing non-repudiable transactions. Credentials, request information, response information, and action items generated and received by a requesting computing system and a responding computing system, and transmitted between the requesting computing system and the responding computing system are separately recorded and stored in a requestor log maintained by the requesting computing system and in a responder log maintained by the responding computing system.

Abstract: Disclosed herein are methods, systems, and processes for distributed logging for securing non-repudiable transactions. Credentials, request information, response information, and action items generated and received by a requesting computing system and a responding computing system, and transmitted between the requesting computing system and the responding computing system are separately recorded and stored in a requestor log maintained by the requesting computing system and in a responder log maintained by the responding computing system.

Abstract: In some implementations, a computing device may determine, from multiple data sources, multiple event timelines, with each event timeline associated with a customer. Each event in an event timeline represents an interaction between the customer and a vendor of goods and/or services. For N (N>1) marketing campaigns, N augmented timelines may be created for each timeline by augmenting each event timeline with the individual marketing campaigns. Thus, for M (M>1) customers, M×N augmented event timelines may be created. A trained machine learning model may perform an analysis of each augmented event timeline to predict results of executing each marketing campaign. The results may include total predicted revenue and total predicted cost resulting from executing each marketing campaign. A particular marketing campaign from the N marketing campaigns may be selected and execution of one or more marketing events may be initiated.

Abstract: In some implementations, a computing device determines an event timeline that comprises one or more finance-related events associated with a person. A production classifier may be used to determine (i) an individual contribution of each event in the event timeline to a financial capacity of the person and (ii) a first decision regarding whether to extend credit to the person. A bias monitoring classifier may, based on the event timeline, determine a second decision whether to extend credit to the person. The bias monitoring classifier may be trained using pseudo-unbiased data. If a difference between the first decision and the second decision satisfies a threshold, the production classifier may be modified to reduce bias in decisions made by the production classifier.

Abstract: In some implementations, an event timeline that includes one or more interactions between a customer and a supplier may be determined. A starting value may be assigned to individual events in the event timeline. A sub-sequence comprising a portion of the event timeline that includes at least one reference event may be selected. A classifier may be used to determine a previous relative value for a previous event that occurred before the reference event and to determine a next relative value for a next event that occurred after the reference event until all events in the event timeline have been processed. The events in the event timeline may be traversed and a monetized value index assigned to individual events in the event timeline.