Abstract: Systems and methods disclosed herein relate to utility based selection of inquiries in a streaming data pipeline. An indication of user identification data and a data source may be received by a server in communication with a distributed streaming data pipeline. This pipeline may be in communication with asynchronous event processing services. Those event processing services may determine an inquiry rule that includes an inquiry threshold. This rule may be based on the data source and retrieval of information related to that data source from memory in a database server. The rule may prompt a comparison of an inquiry count to an inquiry threshold. If the count is below the threshold, an inquiry may be sent to a user based in part upon expected utility that is itself based upon several indications of expected utility calculated by an event processing service.

Abstract: Systems and methods disclosed herein relate to utility based selection of inquiries in a streaming data pipeline. An indication of user identification data and a data source may be received by a server in communication with a distributed streaming data pipeline. This pipeline may be in communication with asynchronous event processing services. Those event processing services may determine an inquiry rule that includes an inquiry threshold. This rule may be based on the data source and retrieval of information related to that data source from memory in a database server. The rule may prompt a comparison of an inquiry count to an inquiry threshold. If the count is below the threshold, an inquiry may be sent to a user based in part upon expected utility that is itself based upon several indications of expected utility calculated by an event processing service.

Abstract: Data is received that specifies at least one beacon associated with a first account and a first validity window specifying a time period during which the at least one beacon is to be associated with an additional account. Thereafter, a first entitlement is generated which, when registered by a second account, causes the at least one beacon to be associated with the second account until expiration of the first validity window. Prior to registration of the first entitlement and additionally outside the first validity window the at least one beacon is associated solely with the first account. After the registration of the first entitlement, the at least one beacon is caused to be associated with the second account during the first validity window. Other types of sharing parameters are also available such as sequencing, subsets of beacons, and the like.

Abstract: Data is received that specifies at least one beacon associated with a first account and a first validity window specifying a time period during which the at least one beacon is to be associated with an additional account. Thereafter, a first entitlement is generated which, when registered by a second account, causes the at least one beacon to be associated with the second account until expiration of the first validity window. Prior to registration of the first entitlement and additionally outside the first validity window the at least one beacon is associated solely with the first account. After the registration of the first entitlement, the at least one beacon is caused to be associated with the second account during the first validity window. Other types of sharing parameters are also available such as sequencing, subsets of beacons, and the like.