Data delivery

• US 10,284,441 B2
• Filed: 02/07/2017
• Issued: 05/07/2019
• Est. Priority Date: 11/03/2010
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google LLC (Alphabet Inc.)
• Inventors: Savage, Jesse, Kuhn, Brian N., Wogulis, James L.
• Primary Examiner(s): Yohannes, Tesfay
• Application Number:
  US15/426,401
• Publication Number:
  US 20170163500A1
• Time in Patent Office: 819 Days
• Field of Search: 709203, 709223, 709227, 1 1
• CPC Class Codes: G06Q 10/063 Operations research, analysis or management
• CPC Class Codes: G06Q 10/0637 Strategic management or analysis, e.g. setting a goal or target of an organisation; Planning actions based on goals; Analysis or evaluation of effectiveness of goals
• CPC Class Codes: G06Q 50/40 Business processes related to the transportation industry shipping G06Q10/083
• CPC Class Codes: H04L 43/04 Processing captured monitoring data, e.g. for logfile generation
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for support dependent post delivery. In one aspect, a method included generating transmission data for a web page served by a first server and rendered on the client device, the first sever belonging to a first domain; determining if the client device supports cross origin resource sharing; in response to a determination that the client device does not support cross origin resource sharing: defining an iFrame for the web page, the iFrame belonging to a second domain of a receiving server, and having a name value derived from the transmission data, receiving iFrame instructions from the receiving server and executing the iFrame instructions in the iFrame, the iFrame instruction causing the client device to: generate an HTTP POST request to the receiving server from the iFrame name value, the first HTTP POST request including the transmission data.

Claims

1. A method comprising:

receiving, by a server that belongs to a first domain, a request for instructions through an iFrame that belongs to the first domain, and is generated, at a client device, within a web page that belongs to a second domain that differs from the first domain;

generating, by the server that belongs to the first domain, the instructions that cause the client device to execute the instructions within the iFrame, wherein execution of the instructions within the iFrame cause the client device to perform operations including;

generating an HTTP POST request that includes event data specifying one or more events for the web page served by a publisher server and rendered on the client device; and

submitting the HTTP POST request including the event data through the iFrame when the event data exceeds a size threshold of submitting data using an HTTP GET request and the client device does not support cross origin resource sharing;

providing, by the server, to the client device, the instructions in response to the request; and

receiving, by the server and from the client device through the iFrame, the HTTP POST request that includes the event data specifying the one or more events for the web page served by the publisher server and rendered on the client device.

2. The method of claim 1, wherein the web page and the publisher server belong to a second domain that is different from the first domain of the server.

3. The method of claim 1, wherein generating the instructions for execution through the iFrame at the client device comprises generating the instructions that cause the client device to derive a name value for the iFrame.

4. The method of claim 1, wherein generating the instructions for execution at the client device comprises generating the instructions that cause the client device to derive a name value.

5. The method of claim 1, wherein generating the instructions for execution at the client device comprises generating the instructions that cause the client device to generate the HTTP POST request through the iFrame on the client device that has at least administrative authority to deliver the event data to an analytics server.

6. The method of claim 5, wherein the event data is delivered through the first domain of the analytics server.

7. The method of claim 1, wherein generating the instructions for execution at the client device comprises generating the instructions that cause the client device to:

change the first domain of the server to the second domain of the publisher; and

delete the iFrame in response to changing the first domain of the server to the second domain of the publisher.

8. A non-transitory computer storage medium encoded with instructions that when executed by a server cause the server to perform operations comprising:

receiving, by a server that belongs to a first domain, a request for instructions through an iFrame that belongs to the first domain, and is generated, at a client device, within a web page that belongs to a second domain that differs from the first domain;

generating, by the server that belongs to the first domain, the instructions that cause the client device to execute the instructions within the iFrame, wherein execution of the instructions within the iFrame cause the client device to perform operations including;

generating an HTTP POST request that includes event data specifying one or more events for the web page served by a publisher server and rendered on the client device; and

submitting the HTTP POST request including the event data through the iFrame when the event data exceeds a size threshold of submitting data using an HTTP GET request and the client device does not support cross origin resource sharing;

providing, by the server, to the client device, the instructions in response to the request; and

receiving, by the server and from the client device through the iFrame, the HTTP POST request that includes the event data specifying the one or more events for the web page served by the publisher server and rendered on the client device.

9. The non-transitory computer storage medium of claim 8, wherein the web page and the publisher server belong to a second domain that is different from the first domain of the server.

10. The non-transitory computer storage medium of claim 8, wherein generating the instructions for execution through the iFrame at the client device comprises generating the instructions that cause the client device to derive a name value for the iFrame.

11. The non-transitory computer storage medium of claim 8, wherein the operations of generating the instructions for execution at the client device comprises generating the instructions that cause the client device to derive a name value.

12. The non-transitory computer storage medium of claim 8, wherein the operations of generating the instructions for execution at the client device comprises generating the instructions that cause the client device to generate the HTTP POST request through the iFrame on the client device that has at least administrative authority to deliver the event data to an analytics server.

13. A system comprising:

a server; and

a memory storage apparatus in data communication with the server, the memory storage apparatus storing instructions executable by the server and that upon such execution cause the server to perform operations comprising;

receiving, by a server that belongs to a first domain, a request for instructions through an iFrame that belongs to the first domain, and is generated, at a client device, within a web page that belongs to a second domain that differs from the first domain;

generating, by the server that belongs to the first domain, the instructions that cause the client device to execute the instructions within the iFrame, wherein execution of the instructions within the iFrame cause the client device to perform operations including;

generating an HTTP POST request that includes event data specifying one or more events for the web page served by a publisher server and rendered on the client device; and

submitting the HTTP POST request including the event data through the iFrame when the event data exceeds a size threshold of submitting data using an HTTP GET request and the client device does not support cross origin resource sharing;

providing, by the server, to the client device, the instructions in response to the request; and

receiving, by the server and from the client device through the iFrame, the HTTP POST request that includes the event data specifying the one or more events for the web page served by the publisher server and rendered on the client device.

14. The system of claim 13, wherein the web page and the publisher server belong to a second domain that is different from the first domain of the server.

15. The system of claim 13, wherein generating the instructions for execution through the iFrame at the client device comprises generating the instructions that cause the client device to derive a name value for the iFrame.

16. The system of claim 13, wherein the operations of generating the instructions for execution at the client device comprises generating the instructions that cause the client device to derive a name value.