DATA DELIVERY

• US 20120110062A1
• Filed: 11/03/2010
• Published: 05/03/2012
• Est. Priority Date: 11/03/2010
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Wogulis, James L., Savage, Jesse, Kuhn, Brian N.
• Granted Patent: US 8,452,837 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 computer storage medium encoded with tracking instructions that when executed by a client device cause the client device to perform operations comprising:

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

determining if 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 belonging 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 exceeds the size threshold, determining if the client supports cross origin resource sharing;

in response to determining that the client 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 origin resource sharing compliant message; and

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

2. The computer storage medium of claim 1, wherein generating the first HTTP POST request to the analytics server comprises generating a cross-domain AJAX HTTP POST request that is a cross origin resource sharing compliant message.

3. The computer storage medium of claim 1, wherein generating the second HTTP POST to the analytics server comprises:

generating the environment with a name value derived from the event data;

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

receiving the environment instructions and executing the environment instructions in the environment, the second instructions causing the client device to generate the second HTTP post to the analytics server.

4. The computer storage medium of claim 3, wherein the environment is an iFrame.

5. The computer storage medium of claim 3, wherein:

the environment instructions further cause the client device to perform operations comprising changing the domain of the environment from the second domain of the analytics server to the first domain of the publisher; and

the tracking instructions further cause the client device to perform operations comprising deleting the environment in response to the changing of the domain of the environment.

6. The computer storage medium of claim 5, wherein changing the domain of the environment from the domain of the analytics server to the domain of the publisher comprises assigning the name value of the environment to a uniform resource locator of the first domain.

7. A computer storage medium encoded with tracking instructions that when executed by a client device cause the client device to perform operations comprising:

generate event data detailing one or more events for a web page served by a publisher server and rendered on the client device, the web page and the publisher sever belonging to a first domain, and the one or more events measured relative to the client device;

determine 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 an analytics server, and the iFrame having a name value derived from the event data;

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

receiving the environment instructions from the analytics server and executing the environment instructions in the iFrame, the environment instruction causing the client device to;

generate a first HTTP POST request to the analytics server from the iFrame name value, the first HTTP POST request including the event data; and

changing the domain of the iFrame from the second domain to the first domain.

8. The computer storage medium of claim 7, wherein changing the domain of the iFrame from the second domain to the first domain comprises changing the name value of the environment to a uniform resource locator of the first domain.

9. The computer storage medium of claim 8, wherein the tracking instructions further cause the client device to perform operations comprising:

determining if the iFrame name value includes the uniform resource locator of the first domain; and

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

10. The computer storage medium of claim 7, wherein the tracking instructions further cause the client device to perform operations comprising:

in response to determining that the client device does support cross origin resource sharing, generating a second HTTP POST request to the analytics server, the second HTTP POST request including the event data and being a cross origin resource sharing compliant message.

11. A computer implemented method performed by a client device, comprising:

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

determining if 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 belonging 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 exceeds the size threshold, determining if the client supports cross origin resource sharing;

in response to determining that the client 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 origin resource sharing compliant message; and

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

12. The computer implemented method of claim 11, wherein generating the first HTTP POST request to the analytics server comprises generating a cross-domain AJAX HTTP POST request that is a cross origin resource sharing compliant message.

13. The method of claim 11, wherein the environment is an iFrame and generating the second HTTP POST to the analytics server comprises:

generating the environment with a name value derived from the event data;

changing the domain of the environment from the second domain of the analytics server to the first domain of the publisher; and

deleting the environment in response to the changing of the domain of the environment;

wherein changing the domain of the environment from the domain of the analytics server to the domain of the publisher comprises assigning the name value of the environment to a uniform resource locator of the first domain.

14. A computer implemented method performed by a client device, comprising:

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

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 an analytics server, and the iFrame having a name value derived from the event data;

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

receiving the environment instructions from the analytics server and executing the environment instructions in the iFrame, the environment instruction causing the client device to;

generate a first HTTP POST request to the analytics server from the iFrame name value, the first HTTP POST request including the event data; and

change the domain of the iFrame from the second domain to the first domain.

15. The method of claim 14, wherein changing the domain of the iFrame from the second domain to the first domain comprises changing the name value of the environment to a uniform resource locator of the first domain.

16. The method of claim 14, further comprising:

determining that the iFrame name value includes the uniform resource locator of the first domain and in response deleting the iFrame.

17. The method of claim 14, further comprising:

in response to determining that the client device does support cross origin resource sharing, generating a second HTTP POST request to the analytics server, the second HTTP POST request including the event data and being a cross origin resource sharing compliant message.

18. A system, comprising:

a processing subsystem; and

a memory subsystem storing instructions that when executed by the processing subsystem cause the processing subsystem to perform operations comprising;

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

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 an analytics server, and the iFrame having a name value derived from the event data;

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

receiving the environment instructions from the analytics server and executing the environment instructions in the iFrame, the environment instruction causing the client device to;

generate a first HTTP POST request to the analytics server from the iFrame name value, the first HTTP POST request including the event data; and

change the domain of the iFrame from the second domain to the first domain.

19. A computer storage medium encoded with data delivery instructions that when executed by a client device cause the client device to perform operations comprising:

generating transmission data for a web page served by a first server and rendered on the client device, the web page and the first sever belonging to a first domain;

determine 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 the iFrame having a name value derived from the transmission data;

issuing a request from the iFrame for iFrame instructions from the receiving server;

receiving the iFrame instructions from the receiving server and executing the iFrame instructions in the iFrame, the iFrame instruction causing the client device to;

generate a first HTTP POST request to the receiving server from the iFrame name value, the first HTTP POST request including the transmission data; and

changing the domain of the iFrame from the second domain to the first domain.