Abstract: An example method for delivery of push notifications includes receiving a push notification including a message and a destination, creating a send token, sending a push notification derived from the received push notification and the send token, and receiving push information concerning a processing of the sent push notification which is identified by the send token. An example system for delivering push notifications includes a server system having a processor, memory, and a network interface, where the memory stores program instructions including code segments for receiving a received push notification via the network interface. In this example, the program instructions further includes code segments for creating a send token, code segments for sending a sent push notification derived from the received push notification and the send token via the network interface, and code segments for receiving received push information concerning a processing of the sent push notification are provided.

Abstract: A system for updating a digital wallet installation is disclosed. Event information is received. The received event information is evaluated against a set of rules. A digital wallet asset logical instance to be updated is identified based at least in part on the evaluation. The identified instance is updated. An installation of a digital wallet asset associated with the identified instance is identified. An update instruction is provided to a device associated with the installation.

Abstract: Installing digital wallet assets is disclosed. A distribution channel is received. A notification message indicating that a digital wallet asset is available for installation is generated. The notification message is distributed based at least in part on the distribution channel. A callback is received. The digital wallet asset is provided. The digital wallet asset is constructed based at least in part on an associated digital wallet asset logical instance.

Abstract: Generating a digital wallet asset logical instance is disclosed. A template is received. A set of data values is received. The digital wallet asset logical instance is generated at least in part by merging the received data values with the received template. The generated digital wallet asset logical instance is associated with metadata tags. A digital wallet asset is constructed based at least in part on the generated digital wallet asset logical instance.

Abstract: A push notification delivery system includes a server system including a processor, a network interface, and memory storing program instructions having code segments for receiving a received push notification, code segments for determining at least one of a favorable push time and a favorable message format based upon a database of received push information developed from a plurality of prior sent push notifications, and code segments for pushing the message to the destination in accordance with the at least one of a favorable push time and a favorable message format. A method for delivering push notifications includes receiving a received push notification including a message and a destination, sending a sent push notification derived from the received push notification to the destination in accordance with at least one favorable condition, receiving received push information related to the sent push notification, and storing the received push information in a database.

Abstract: Push reporting is disclosed. A first payload comprising feature reporting information and meta information is received from a first device at a first time. A second payload comprising feature reporting information and meta information is received from a second device at a second time. At respective third and fourth times, respective third and fourth payloads are received from the first and second devices, respectively. The third and fourth payloads include additional feature reporting information and meta information. The processing of the information received from the first and second devices is coordinated. A request for information is received. Metrics are provided as output. The metrics are based at least in part on the processing of the information received from the first and second devices.

Abstract: Disclosed is a mobile event streaming system that receives customer application lifecycle and user events including a message, event source and a destination then processes data for consumption by one or more customers, generating a secure data stream and sending the processed data over the generated data stream. An example system for receiving, processing, and delivering customer application lifecycle and user engagement data includes a server system having at least one processor, memory and a network interface where the memory stores program instructions for receiving, storing, processing and transmitting messages via the network interface. The mobile event streaming system may be a distributed content delivery service wherein the content delivered via the service is processed. Processing the data comprises the addition of metadata, one or more identifiers such as user, and event identifiers including predictions of future user engagement to enable real-time data consumption by customers.

Abstract: Disclosed is a mobile event streaming system that receives customer application lifecycle and user events including a message, event source and a destination then processes data for consumption by one or more customers, generating a secure data stream and sending the processed data over the generated data stream. An example system for receiving, processing, and delivering customer application lifecycle and user engagement data includes a server system having at least one processor, memory and a network interface where the memory stores program instructions for receiving, storing, processing and transmitting messages via the network interface. The mobile event streaming system may be a distributed content delivery service wherein the content delivered via the service is processed. Processing the data comprises the addition of metadata, one or more identifiers such as user, and event identifiers including predictions of future user engagement to enable real-time data consumption by customers.

Abstract: An example method for delivery of push notifications includes receiving a push notification including a message and a destination, creating a send token, sending a push notification derived from the received push notification and the send token, and receiving push information concerning a processing of the sent push notification which is identified by the send token. An example system for delivering push notifications includes a server system having a processor, memory, and a network interface, where the memory stores program instructions including code segments for receiving a received push notification via the network interface. In this example, the program instructions further includes code segments for creating a send token, code segments for sending a sent push notification derived from the received push notification and the send token via the network interface, and code segments for receiving received push information concerning a processing of the sent push notification are provided.

Abstract: Disclosed is a mobile event streaming system that receives customer application lifecycle and user events including a message, event source and a destination then processes data for consumption by one or more customers, generating a secure data stream and sending the processed data over the generated data stream. An example system for receiving, processing, and delivering customer application lifecycle and user engagement data includes a server system having at least one processor, memory and a network interface where the memory stores program instructions for receiving, storing, processing and transmitting messages via the network interface. The mobile event streaming system may be a distributed content delivery service wherein the content delivered via the service is processed. Processing the data comprises the addition of metadata, one or more identifiers such as user, and event identifiers including predictions of future user engagement to enable real-time data consumption by customers.

Abstract: A push notification delivery system includes a server system including a processor, a network interface, and memory storing program instructions having code segments for receiving a received push notification, code segments for determining at least one of a favorable push time and a favorable message format based upon a database of received push information developed from a plurality of prior sent push notifications, and code segments for pushing the message to the destination in accordance with the at least one of a favorable push time and a favorable message format. A method for delivering push notifications includes receiving a received push notification including a message and a destination, sending a sent push notification derived from the received push notification to the destination in accordance with at least one favorable condition, receiving received push information related to the sent push notification, and storing the received push information in a database.

Abstract: A system for updating a digital wallet installation is disclosed. Event information is received. The received event information is evaluated against a set of rules. A digital wallet asset logical instance to be updated is identified based at least in part on the evaluation. The identified instance is updated. An installation of a digital wallet asset associated with the identified instance is identified. An update instruction is provided to a device associated with the installation.

Abstract: Disclosed is a mobile event streaming system that receives customer application lifecycle and user events including a message, event source and a destination then processes data for consumption by one or more customers, generating a secure data stream and sending the processed data over the generated data stream. An example system for receiving, processing, and delivering customer application lifecycle and user engagement data includes a server system having at least one processor, memory and a network interface where the memory stores program instructions for receiving, storing, processing and transmitting messages via the network interface. The mobile event streaming system may be a distributed content delivery service wherein the content delivered via the service is processed. Processing the data comprises the addition of metadata, one or more identifiers such as user, and event identifiers including predictions of future user engagement to enable real-time data consumption by customers.

Abstract: Push reporting is disclosed. A first payload comprising feature reporting information and meta information is received from a first device at a first time. A second payload comprising feature reporting information and meta information is received from a second device at a second time. At respective third and fourth times, respective third and fourth payloads are received from the first and second devices, respectively. The third and fourth payloads include additional feature reporting information and meta information. The processing of the information received from the first and second devices is coordinated. A request for information is received. Metrics are provided as output. The metrics are based at least in part on the processing of the information received from the first and second devices.

Abstract: Selecting a geolocation using a polygon is disclosed. User input is received. One or more polygons used to define an audience are determined based at least in part on the received user input. At least one polygon is displayed. Content is sent to the audience defined by the polygon in response to a received confirmation of the at least one polygon.

Abstract: An example method for delivery of push notifications includes receiving a push notification including a message and a destination, creating a send token, sending a push notification derived from the received push notification and the send token, and receiving push information concerning a processing of the sent push notification which is identified by the send token. An example system for delivering push notifications includes a server system having a processor, memory, and a network interface, where the memory stores program instructions including code segments for receiving a received push notification via the network interface. In this example, the program instructions further includes code segments for creating a send token, code segments for sending a sent push notification derived from the received push notification and the send token via the network interface, and code segments for receiving received push information concerning a processing of the sent push notification are provided.

Abstract: Querying for devices based on location is disclosed. A request to send a push notification to a location is received. One or more bucket indexes to search for the presence of a device identifier are determined. The one or more bucket indexes are searched for the presence of the device identifier. One or more device identifiers are received in response to the search. The push notification is sent to one or more devices associated with the received one or more device identifiers.

Abstract: Delivering push notifications is disclosed. A message and destination information are received. The destination information represents a destination to which a current push notification including the message should be sent. At least one of a push time and a message format are determined. The determination is based at least in part on push information associated with at least one previously sent push notification. The current push notification is sent to the destination in accordance with the determination.

Abstract: Composing a push notification is disclosed. A first selection comprising at least an operating system of a first device is received. An interface configured to receive, from a user, instructions associated with the push notification is provided. At least a portion of the instructions is used to graphically render to a user how a display interface of the first device would display the push notification, in a first state, if it was received by that instance.

Abstract: Push Reporting is disclosed. A first payload comprising feature reporting information and meta information is received from a first device at a first time. A second payload comprising feature reporting information and meta information is received from a second device at a second time. At respective third and fourth times, respective third and fourth payloads are received from the first and second devices, respectively. The third and fourth payloads include additional feature reporting information and meta information. The processing of the information received from the first and second devices is coordinated. A request for information is received. Metrics are provided as output. The metrics are based at least in part on the processing of the information received from the first and second devices.