DATA DELIVERY

• US 20130204932A1
• Filed: 03/15/2013
• Published: 08/08/2013
• Est. Priority Date: 11/03/2010
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Savage, Jesse, Kuhn, Brian N., Wogulis, James L.
• Granted Patent: US 9,154,388 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• 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 performed by data processing apparatus, the method comprising:

generating event data specifying one or more events for a web page served by a publisher server and rendered on the client device, the web page and publisher belonging to a first domain;

determining whether the event data exceeds a size threshold;

in response to determining that the event data does not exceed the size threshold, generating an HTTP GET request to an analytics server that belongs to a second domain that is different from the first domain, the HTTP GET request including the event data;

in response to determining that the event data exceeds the size threshold, determining whether the client device supports cross origin resource sharing; and

in response to determining that the client device supports cross origin resource sharing, generating a first HTTP POST request to the analytics server, the first HTTP POST request including the event data and being a cross-domain HTTP POST request that is a cross origin resource sharing compliant message.

2. The method of claim 1, further comprising generating a second HTTP POST request to the analytics server in response to determining that the client device does not support cross origin resource sharing, the second HTTP POST request including the event data and being sent from an environment on the client device that belongs to the second domain.

3. The method of claim 2, wherein generating the second HTTP POST request to the analytics server comprises generating the second message from a web page of the environment.

4. The method of claim 1, wherein generating the second HTTP POST request to the analytics server comprises:

defining an iFrame for the web page, the iFrame belonging to the second domain and the iFrame having a name value derived from the analytics server;

issuing a request from the iFrame for environment instructions from the analytics server; and

receiving the environment instructions from the analytics server and executing the environment instructions in the iFrame, the environment instructions causing the client device to generate the second HTTP POST request to the analytics server.

5. The method of claim 4, further comprising:

determining that the iFrame name value includes a uniform resource locator for the first domain; and

in response to determining that the iFrame name value includes a uniform resource locator for the first domain, deleting the iFrame.

6. The method of claim 1, wherein generating the second HTTP POST request to the analytics server comprises:

generating the environment with a name value;

requesting, from the environment, environment instructions from the analytics server;

receiving the environment instructions from the analytics server; and

executing the environment instructions in the environment, the environment instructions causing the client device to generate the second HTTP POST request to the analytics server.

7. The method of claim 6, wherein the environment instructions further cause the client device to perform operations comprising changing the domain of the environment from the second domain to the first domain.

8. The method of claim 7, further comprising deleting the environment in response to the changing of the domain of the environment.

9. The method of claim 7, wherein changing the domain of the environment from the second domain to the first domain comprises assigning the name value of the environment to a uniform resource locator of the first domain.

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

generating event data specifying one or more events for a web page served by a publisher server and rendered on the client device, the web page and publisher belonging to a first domain;

determining whether the event data exceeds a size threshold;

in response to determining that the event data does not exceed the size threshold, generating an HTTP GET request to an analytics server that belongs to a second domain that is different from the first domain, the HTTP GET request including the event data;

in response to determining that the event data exceeds the size threshold, determining whether the client device supports cross origin resource sharing; and

in response to determining that the client device supports cross origin resource sharing, generating a first HTTP POST request to the analytics server, the first HTTP POST request including the event data and being a cross-domain HTTP POST request that is a cross origin resource sharing compliant message.

11. The non-transitory computer storage medium of claim 10, wherein the instructions further cause the client device to perform operations comprising generating a second HTTP POST request to the analytics server in response to determining that the client device does not support cross origin resource sharing, the second HTTP POST request including the event data and being sent from an environment on the client device that belongs to the second domain.

12. The non-transitory computer storage medium of claim 10, wherein generating the second HTTP POST request to the analytics server comprises:

defining an iFrame for the web page, the iFrame belonging to the second domain and the iFrame having a name value derived from the analytics server;

issuing a request from the iFrame for environment instructions from the analytics server; and

receiving the environment instructions from the analytics server and executing the environment instructions in the iFrame, the environment instructions causing the client device to generate the second HTTP POST request to the analytics server.

13. The non-transitory computer storage medium of claim 12, wherein the instructions further cause the client device to perform operations comprising:

determining that the iFrame name value includes a uniform resource locator for the first domain; and

in response to determining that the iFrame name value includes a uniform resource locator for the first domain, deleting the iFrame.

14. A system comprising:

a processing apparatus;

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

generating event data specifying one or more events for a web page served by a publisher server and rendered on a client device, the web page and publisher belonging to a first domain;

determining whether the event data exceeds a size threshold;

in response to determining that the event data does not exceed the size threshold, generating an HTTP GET request to an analytics server that belongs to a second domain that is different from the first domain, the HTTP GET request including the event data;

in response to determining that the event data exceeds the size threshold, determining whether the client device supports cross origin resource sharing; and

in response to determining that the client device supports cross origin resource sharing, generating a first HTTP POST request to the analytics server, the first HTTP POST request including the event data and being a cross-domain HTTP POST request that is a cross origin resource sharing compliant message.

15. The system of claim 14, wherein the instructions further cause the client device to perform operations comprising generating a second HTTP POST request to the analytics server in response to determining that the client device does not support cross origin resource sharing, the second HTTP POST request including the event data and being sent from an environment on the client device that belongs to the second domain.

16. The system of claim 15, wherein generating the second HTTP POST request to the analytics server comprises generating the second message from a web page of the environment.

17. The system of claim 14, wherein generating the second HTTP POST request to the analytics server comprises:

defining an iFrame for the web page, the iFrame belonging to the second domain and the iFrame having a name value derived from the analytics server;

issuing a request from the iFrame for environment instructions from the analytics server; and

receiving the environment instructions from the analytics server and executing the environment instructions in the iFrame, the environment instructions causing the client device to generate the second HTTP POST request to the analytics server.

18. The system of claim 17, wherein the instructions further cause the client device to perform operations comprising:

determining that the iFrame name value includes a uniform resource locator for the first domain; and

in response to determining that the iFrame name value includes a uniform resource locator for the first domain, deleting the iFrame.

19. The system of claim 14, wherein generating the second HTTP POST request to the analytics server comprises:

generating the environment with a name value;

requesting, from the environment, environment instructions from the analytics server;

receiving the environment instructions from the analytics server; and

executing the environment instructions in the environment, the environment instructions causing the client device to generate the second HTTP POST request to the analytics server.

20. The system of claim 19, wherein the environment instructions further cause the client device to perform operations comprising changing the domain of the environment from the second domain to the first domain.

21. The system of claim 20, wherein the instructions further cause the client device to perform operations comprising deleting the environment in response to the changing of the domain of the environment.

22. The system of claim 20, wherein changing the domain of the environment from the second domain to the first domain comprises assigning the name value of the environment to a uniform resource locator of the first domain.