Abstract: Systems and methods for determining whether a user is part of a defined segment of all users makes use of a database of user information that includes rapidly searchable field values. Predetermined segment definitions can be evaluated using information from a user's record in the database to rapidly determine if the user is a member of the segment.

Abstract: Systems and methods for throttling requests submitted to a database are designed to maximize the rate at which information can be obtained from the database. In the throttling methods, the time required for the database to perform a certain operation is monitored. If the time required to perform the operation exceeds a threshold time period, a request limit is imposed on the database, the request limit limiting the number of data read and/or write requests that can be submitted to the database per unit of time.

Abstract: Systems and methods for determining whether to send a message to a user take into account a pressure score for the user that is indicative of how receptive the user is to receiving messages. The user's pressure score can vary depending on user behavior. Multiple pressure scores relating to different respective topics or subjects may be maintained for the user.

Abstract: Systems and methods for determining whether to send a message to a user take into account a pressure score for the user that is indicative of how receptive the user is to receiving messages. The user's pressure score can vary depending on user behavior. Multiple pressure scores relating to different respective topics or subjects may be maintained for the user.

Abstract: Systems and methods for sending a message to a plurality of a client's users prioritize delivery of the message first to those users who are most engaged with the client. A user's degree of engagement with the client may be determined based on a variety of factors, including how recently the user interacted with the client. A database query of user contact information may result in query results being streamed to a message sending unit, and the streamed results may be ordered based on the user's degree of engagement.

Abstract: Systems and methods for determining whether a user is part of a defined segment of all users makes use of a database of user information that includes rapidly searchable field values. Predetermined segment definitions can be evaluated using information from a user's record in the database to rapidly determine if the user is a member of the segment.

Abstract: Systems and methods for controlling contacts with a client's users make use of segment-based contact limits. A contact limit sets a maximum number of contacts that a client can have with a user within a predetermined time window. A segment-based contact limit only applies the contact limit to a subset of all the client's users. The type of contact being limited could include messages that are sent to the user or advertising or sales campaigns that are conducted for the user. A segment is a subset of all of the client's users, and a segment may be defined based on one or more filters.

Abstract: Systems and methods for determining whether a user is part of a defined segment of all users makes use of a database of user information that includes rapidly searchable field values. Predetermined segment definitions can be evaluated using information from a user's record in the database to rapidly determine if the user is a member of the segment.

Abstract: Systems and methods for determining whether to send a message to a user take into account a pressure score for the user that is indicative of how receptive the user is to receiving messages. The user's pressure score can vary depending on user behavior. Multiple pressure scores relating to different respective topics or subjects may be maintained for the user.

Abstract: Systems and methods for determining whether to send a message to a user take into account a pressure score for the user that is indicative of how receptive the user is to receiving messages. The user's pressure score can vary depending on user behavior. Multiple pressure scores relating to different respective topics or subjects may be maintained for the user.

Abstract: Systems and methods for determining whether to send a message to a user take into account a pressure score for the user that is indicative of how receptive the user is to receiving messages. The user's pressure score can vary depending on user behavior. Multiple pressure scores relating to different respective topics or subjects may be maintained for the user.

Abstract: Systems and methods for controlling contacts with a client's users make use of segment-based contact limits. A contact limit sets a maximum number of contacts that a client can have with a user within a predetermined time window. A segment-based contact limit only applies the contact limit to a subset of all the client's users. The type of contact being limited could include messages that are sent to the user or advertising or sales campaigns that are conducted for the user. A segment is a subset of all of the client's users, and a segment may be defined based on one or more filters.

Abstract: Systems and methods for determining whether a user is part of a defined segment of all users makes use of a database of user information that includes rapidly searchable field values. Predetermined segment definitions can be evaluated using information from a user's record in the database to rapidly determine if the user is a member of the segment.

Abstract: Systems and methods for determining whether to send a message to a user take into account a pressure score for the user that is indicative of how receptive the user is to receiving messages. The user's pressure score can vary depending on user behavior. Multiple pressure scores relating to different respective topics or subjects may be maintained for the user.

Abstract: Systems and methods for sending a message to a plurality of a client's users prioritize delivery of the message first to those users who are most engaged with the client. A user's degree of engagement with the client may be determined based on a variety of factors, including how recently the user interacted with the client. A database query of user contact information may result in query results being streamed to a message sending unit, and the streamed results may be ordered based on the user's degree of engagement.

Abstract: Systems and methods for controlling contacts with a client's users make use of segment-based contact limits. A contact limit sets a maximum number of contacts that a client can have with a user within a predetermined time window. A segment-based contact limit only applies the contact limit to a subset of all the client's users. The type of contact being limited could include messages that are sent to the user or advertising or sales campaigns that are conducted for the user. A segment is a subset of all of the client's users, and a segment may be defined based on one or more filters.

Abstract: Methods and systems for collecting and analyzing application usage are disclosed. A usage analytics module is integrated within an application. The application is deployed to a device. Usage analytics are received, at a server, in response to usage of the application at the device. The usage analytics are provided to the developer, wherein the usage analytics includes at least one of: information identifying a user of the application or information linking the usage analytics to an existing user identity.

Abstract: Methods and systems for collecting and analyzing application usage are disclosed. A usage analytics module is integrated within an application. The application is deployed to a device. Usage analytics are received, at a server, in response to usage of the application at the device. The usage analytics are provided to the developer, wherein the usage analytics includes at least one of: information identifying a user of the application or information linking the usage analytics to an existing user identity.

Abstract: Methods and systems for collecting and analyzing application usage are disclosed. A usage analytics module is integrated within an application. The application is deployed to a device. Usage analytics are received, at a server, in response to usage of the application at the device. The usage analytics are provided to the developer, wherein the usage analytics includes at least one of: information identifying a user of the application or information linking the usage analytics to an existing user identity.

Abstract: Methods and systems for collecting and analyzing application usage are disclosed. A usage analytics module is integrated within an application. The application is deployed to a device. Usage analytics are received, at a server, in response to usage of the application at the device. The usage analytics are provided to the developer, wherein the usage analytics includes at least one of: information identifying a user of the application or information linking the usage analytics to an existing user identity.