Systems and methods for reliably using ping to account for interactions with electronic content

• US 9,083,676 B2
• Filed: 07/15/2013
• Issued: 07/14/2015
• Est. Priority Date: 07/15/2013
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Sarat, Sandeep, Gagne, Mathieu, Kleber, Michael, Shienbrood, Eric
• Primary Examiner(s): SALL, EL HADJI MALICK
• Application Number:
  US13/942,289
• Publication Number:
  US 20150019690A1
• Time in Patent Office: 729 Days
• Field of Search: 709/203, 709/206, 709/219, 709/226
• US Class Current: 1/1
• CPC Class Codes: G06F 40/134 Hyperlinking
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/535 Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34

Abstract

A method for reliably using ping to account for interactions with electronic content includes receiving a request for a content item from a user device, selecting a content item in response to the request, determining whether the user device is ping enabled, and generating a hyperlink for inclusion with the selected content item. The hyperlink has a target URL and a ping attribute. At least one of the target URL and the ping attribute is based on a result of the determination whether the user device is ping enabled. The method further includes distributing the content item and the hyperlink to the user device and receiving a ping request from the user device. The ping request includes the target URL and an identifier of the distributed content item. The method further includes accounting for the interaction in response to receiving the ping request from the user device.

Claims

1. A method for reliably using ping to account for interactions with electronic content, the method comprising:

receiving, at one or more servers, a request for a content item from a user device and selecting a content item in response to the request;

determining, by the one or more servers, whether the user device is ping enabled;

generating, by the one or more servers, a hyperlink for inclusion with the selected content item, the hyperlink having a target URL and a ping attribute, wherein at least one of the target URL and the ping attribute is based on a result of the determination whether the user device is ping enabled;

distributing, by the one or more servers, the selected content item and the generated hyperlink to the user device;

receiving, at the one or more servers, a ping request from the user device, wherein the ping request is received at the one or more servers in response to an interaction with the distributed content item if the user device is ping enabled, wherein the ping request includes the target URL and an identifier of the distributed content item; and

accounting for the interaction with the distributed content item in response to receiving the ping request from the user device.

2. The method of claim 1, further comprising:

causing the user device to store a ping identifier in a local memory of the user device in response to the detected interaction with the distributed content item, wherein the ping identifier is associated with the ping request received from the user device if the user device is ping enabled;

receiving, at the one or more servers, a second request for a content item from the user device, wherein the second request includes the stored ping identifier;

determining whether the ping request associated with the ping identifier was previously received from the user device; and

identifying the user device as ping enabled in response to a determination that the associated ping request was previously received.

3. The method of claim 1, further comprising:

receiving, at the one or more servers, a redirect request from the user device; and

determining whether to account for the interaction using the ping request or the redirect request.

4. The method of claim 1, further comprising:

storing, in a profiles database, an indication that the ping request was received from the user device in response to receiving the ping request,

wherein determining whether the user device is ping enabled includes retrieving information from the profiles database.

5. The method of claim 1, wherein the target URL is based on a result of the determination whether the user device is ping enabled,

wherein if the user device is determined to be non-ping enabled, the target URL directs the user device to a resource associated with the one or more servers for recording the interaction with the distributed content item using a redirect-based accounting technique.

6. The method of claim 1, wherein the target URL is based on a result of the determination whether the user device is ping enabled,

wherein if the user device is determined to be ping enabled, the target URL directs the user device to a landing page associated with the distributed content item without directing the user device to a resource associated with the one or more servers.

7. The method of claim 1, wherein the target URL is based on a result of the determination whether the user device is ping enabled,

wherein if the user device is determined to be not ping enabled, the target URL includes both a URL associated with the accounting server and a URL associated with a landing page for the distributed content item.

8. The method of claim 1, wherein the ping attribute is based on a result of the determination whether the user device is ping enabled,

wherein if the user device is determined to be ping enabled, the ping attribute includes a URL associated with the one or more servers for recording the interaction with the distributed content item using a ping-based accounting technique.

9. The method of claim 1, further comprising:

removing the ping attribute from the hyperlink in response to a determination that the user device is not ping enabled.

10. A system for reliably using ping to account for interactions with electronic content, the system comprising:

one or more servers configured to

receive a request for a content item from a user device and select a content item in response to the request;

determine whether the user device is ping enabled;

generate a hyperlink for inclusion with the selected content item, the hyperlink having a target URL and a ping attribute, wherein at least one of the target URL and the ping attribute is based on a result of the determination whether the user device is ping enabled;

distribute the selected content item and the generated hyperlink to the user device;

receive a ping request from the user device, wherein the ping request is received in response to an interaction with the distributed content item if the user device is ping enabled, wherein the ping request includes the target URL and an identifier of the distributed content item; and

account for the interaction with the distributed content item in response to receiving the ping request from the user device.

11. The system of claim 10, wherein the one or more servers are further configured to:

cause the user device to store a ping identifier in a local memory of the user device in response to the detected interaction with the distributed content item, wherein the ping identifier is associated with the ping request received from the user device if the user device is ping enabled;

receive a second request for a content item from the user device, wherein the second request includes the stored ping identifier;

determine whether the ping request associated with the ping identifier was previously received from the user device; and

identify the user device as ping enabled in response to a determination that the associated ping request was previously received.

12. The system of claim 10, wherein the one or more servers are further configured to:

receive a redirect request from the user device; and

determine whether to account for the interaction using the ping request or the redirect request.

13. The system of claim 10, wherein the one or more servers are further configured to:

store, in a profiles database, an indication that the ping request was received from the user device in response to receiving the ping request,

wherein determining whether the user device is ping enabled includes retrieving information from the profiles database.

14. The system of claim 10, wherein the target URL is based on a result of the determination whether the user device is ping enabled,

wherein if the user device is determined to be non-ping enabled, the target URL directs the user device to a resource associated with the one or more servers for recording the interaction with the distributed content item using a redirect-based accounting technique,

wherein if the user device is determined to be ping enabled, the target URL directs the user device to a landing page associated with the distributed content item without directing the user device to a resource associated with the one or more servers.

15. The system of claim 10, wherein the target URL is based on a result of the determination whether the user device is ping enabled,

wherein if the user device is determined to be not-ping enabled, the target URL includes both a URL associated with the accounting server and a URL associated with a landing page for the distributed content item.

16. The system of claim 10, wherein the ping attribute is based on a result of the determination whether the user device is ping enabled,

wherein if the user device is determined to be ping enabled, the ping attribute includes a URL associated with the one or more servers for recording the interaction with the distributed content item using a ping-based accounting technique.

17. The system of claim 10, wherein the one or more servers are further configured to:

remove the ping attribute from the hyperlink in response to a determination that the user device is not ping enabled.

18. One or more computer-readable storage media having instructions stored therein, the instructions being executable by one or more processers to cause the one or more processors to perform operations comprising:

receiving a request for a content item from a user device and selecting a content item in response to the request;

determining whether the user device is ping enabled;

generating a hyperlink for inclusion with the selected content item, the hyperlink having a target URL and a ping attribute, wherein at least one of the target URL and the ping attribute is based on a result of the determination whether the user device is ping enabled;

distributing the selected content item and the generated hyperlink to the user device;

receiving a ping request from the user device, wherein the ping request is received at one or more servers in response to an interaction with the distributed content item if the user device is ping enabled, wherein the ping request includes the target URL and an identifier of the distributed content item; and

accounting for the interaction with the distributed content item in response to receiving the ping request from the user device.

19. The computer-readable storage media of claim 18, wherein the instructions are executable by the one or more processors to cause the one or more processors to perform operations further comprising:

causing the user device to store a ping identifier in a local memory of the user device in response to the detected interaction with the distributed content item, wherein the ping identifier is associated with the ping request received from the user device if the user device is ping enabled;

receiving a second request for a content item from the user device, wherein the second request includes the stored ping identifier;

determining whether the ping request associated with the ping identifier was previously received from the user device; and

identifying the user device as ping enabled in response to a determination that the associated ping request was previously received.

20. The computer-readable storage media of claim 18, wherein the instructions are executable by the one or more processors to cause the one or more processors to perform operations further comprising:

receiving a redirect request from the user device; and

determining whether to account for the interaction using the ping request or the redirect request.