DISAMBIGUATION OF NOTIFICATION DELIVERY
In one embodiment, one or more computer systems of a social-networking system access a notification to be delivered to an identified user. The one or more computer systems of a social-networking system access registration data maintained by the notification-providing system and associated with the user. The one or more computer systems of a social-networking system identifies, based on the registration data, an endpoint associated with the user to which the notification will be delivered, wherein the endpoint includes a particular application installed on a client system associated with the user. The one or more computer systems of a social-networking system causes the notification to be sent to the identified endpoint.
1 . A method comprising:
by one or more computer server devices of a notification-providing system, accessing a notification to be delivered to an identified user;
by the computer server devices, accessing registration data maintained by the notification-providing system and associated with the user
by the computer server devices, identifying based on the registration data an endpoint associated with the user to which the notification will be delivered, wherein the endpoint comprises a particular application installed on a client system associated with the user; and
by the computer server devices, causing the notification to be sent to the identified endpoint.
2 . The method of claim 1 , wherein registration data comprises a list of endpoints associated with the user, wherein a subset of the endpoints associated with the user consists of the endpoints associated with the client system, and wherein the identified endpoint is included in the subset.
3 . The method of claim 2 , wherein the subset of endpoints comprises a plurality of Hypertext Transfer Protocol (HTTP)-based applications, and wherein for each of the HTTP-based applications, the registration data comprises user-agent information for each of the HTTP-based applications.
4 . The method of claim 3 , wherein the user-agent information for each of the HTTP-based applications is stored upon receiving an HTTP request from an application installed on the client system, wherein the HTTP request comprises information uniquely identifying the user.
5 . The method of claim 1 , wherein the endpoint is identified by a policy engine in accordance with a delivery policy.
6 . The method of claim 5 , wherein the policy engine incorporates historical notification information about:
the user's responses to past notifications; and
prior context/delivery patterns.
7 . The method of claim 6 , wherein information about the user's responses to past notifications comprises information about conversion rates associated with different notification/context/delivery patterns.
8 . The method of claim 5 , wherein the policy engine incorporates information associated with the user comprising:
demographic information for the user;
the user's location;
the user's available delivery channels and the status thereof;
the user's current delivery context; or
user profile information.
9 . The method of claim 5 , wherein the policy engine incorporates information associated with the notification comprising:
the source of the notification;
the content of the notification; or
the format of the notification.
10 . The method of claim 5 , wherein the policy engine incorporates social-networking information for the user, the social-networking information corresponding to information relating to a social graph, the social graph comprising one or more nodes, the nodes being connected by one or more edges representing relationships between the nodes, wherein the user is represented by one of the nodes.
11 . A method comprising:
by one or more computer server devices of a notification-providing system, accessing a notification to be delivered to an identified user associated with a client system having a plurality of installed HTTP-based applications;
by the computer server devices, accessing profile data maintained by the notification-providing system and associated with the user and the client system, wherein the profile data comprises a list of identifiers for the installed HTTP-based applications;
by the computer server devices, identifying based on the profile data one of the HTTP-based applications; and
by the computer server devices, causing the notification to be sent to the identified application.
12 . The method of claim 11 , wherein for each of the installed HTTP-based applications, the respective identifier comprises user-agent information for the HTTP-based application.
13 . The method of claim 12 , wherein the user-agent information for one of the installed HTTP-based applications comprises a browser name, a browser version, a rendering engine name, a rendering engine version, or device details.
14 . The method of claim 12 , wherein the user-agent information for each of the HTTP-based applications is stored in the profile data upon receiving an initial HTTP request from the HTTP-based application, wherein the initial HTTP request comprises authentication information uniquely identifying the user.
15 . The method of claim 14 , wherein the user-agent information for one of the HTTP-based applications is updated in the profile data upon receiving an indication from the HTTP-based application that an update to the HTTP-based application has been installed on the client system.
16 . The method of claim 11 , wherein the profile data further comprises historical usage information for each of the installed HTTP-based applications, and wherein the identified application is more frequently used than other ones of the installed HTTP-based applications.
17 . The method of claim 11 , wherein the profile data further comprises historical usage information for each of the installed HTTP-based applications, and wherein conversion rates for notifications delivered to the identified application is higher than conversion rates for other ones of the installed HTTP-based applications.
18 . The method of claim 11 , wherein the profile data further comprises information regarding functional capabilities for each of the installed HTTP-based applications, and wherein the identified application provides a particular functional capability lacking in other ones of the installed HTTP-based applications.
19 . The method of claim 11 , wherein the profile data further comprises resource usage information for each of the installed HTTP-based applications, and wherein the identified application conserves at least one resource more efficiently than other ones of the installed HTTP-based applications.
20 . The method of claim 19 , wherein the at least one resource comprises battery power, network bandwidth, memory, or data plan usage.