System and Method for Loading of Web Page Assets

Abstract

The present solution is directed to methods and systems for asynchronously loading tag management code and vendor tags on a web page while remaining portions of the web page load. An application executing on a device may receive a web page comprising a configuration object configured to asynchronously load tag management code. The configuration object may load asynchronously, upon execution by the application, the tag management code into memory of the application while the application continues to load a remainder of the web page. The tag management code may request, while the application continues to load the remainder of the web page, one or more vendor tags from a server over a network. The tag management code may receive, while the application continues to load the remainder of the web page, a vendor tag from the server.

1 - 20 . (canceled) 
     
     
         21 . A method for asynchronously loading tag management code and one or more vendor tags, the method comprising:
 receiving, by a device from a first server, a web page comprising a tag container;   in response to executing the tag container, loading the tag management code into memory while the device continues to load a remainder of the web page;   requesting, by the device while the device continues to load the remainder of the web page, one or more vendor tags from a second server via a network in accordance with the tag management code, wherein the one or more vendor tags are configured to track user behavior;   receiving, by the device while the device continues to load the remainder of the web page, at least one of the one or more vendor tags from the second server;   determining that a particular tag, among the one or more vendor tags, has not been loaded by the device; and   after determining that the particular tag has not been loaded, making a call to a service to cause the device to wait a specified period of time before continuing to load the remainder of the web page.   
     
     
         22 . The method of  claim 21 , wherein the device comprises a browser configured to perform the receiving the web page, the loading the tag management code, the requesting the one or more vendor tags, and the receiving the at least one of the one or more vendor tags. 
     
     
         23 . The method of  claim 21 , wherein the tag container is embedded in a head section of the web page. 
     
     
         24 . The method of  claim 21 , further comprising:
 executing a second tag container within the web page, wherein the second tag container is a child of the tag container and inherits parameters from the tag container.   
     
     
         25 . The method of  claim 21 , further comprising:
 determining, by the device, whether to asynchronously load the tag management code based on a property of a configuration object of the tag management code,   wherein the loading the tag management code is responsive to determining to asynchronously load the tag management code based on the property of the configuration object.   
     
     
         26 . The method of  claim 25 , wherein a system, which provides the tag management code, provides a user interface that allows a user to set the property of the configuration object. 
     
     
         27 . The method of  claim 21 , further comprising providing a user interface through which a user configures the tag container. 
     
     
         28 . The method of  claim 27 , wherein the user interface comprises a drop down menu that allows the user to select one or more parameters for the tag container. 
     
     
         29 . The method of  claim 27 , wherein the user interface comprises a field that allows the user to input text for one or more parameters for the tag container. 
     
     
         30 . The method of  claim 27 , wherein the user interface allows the user to define a client name associated with the tag container. 
     
     
         31 . The method of  claim 27 , wherein the user interface allows the user to define a parameter of the tag container, wherein the parameter is specific to the web page. 
     
     
         32 . The method of  claim 27 , wherein the user interface allows the user to define an identifier for the web page. 
     
     
         33 . The method of  claim 21 , wherein the second server provides a user interface through which a user configures the tag container. 
     
     
         34 . The method of  claim 21 , wherein at least one of the one or more vendor tags comprises one or more scripts to be executed synchronously. 
     
     
         35 . The method of  claim 21 , further comprising synchronously receiving the one or more vendor tags. 
     
     
         36 . The method of  claim 21 , further comprising:
 caching, by the device in accordance with the tag management code, a first vendor tag of the one or more vendor tags; and   after the caching, executing the cached first vendor tag.   
     
     
         37 . The method of  claim 21 , further comprising executing, by the device, at least one of the one or more vendor tags to collect data indicating a user interaction with the web page and transmit the data to a third server different from the first server and the second server. 
     
     
         38 . The method of  claim 21 , further comprising:
 collecting data indicating a user of the device,   wherein the requesting the one or more vendor tags from the second server is based on the data indicating the user of the device.   
     
     
         39 . The method of  claim 21 , further comprising:
 selecting one of a first vendor tag and a second vendor tag to avoid duplication in attribution of an ad click.   
     
     
         40 . The method of  claim 21 ,
 wherein the tag management code defines one or more dependencies for the one or more vendor tags, respectively, and   wherein the requesting the one or more vendor tags in accordance with the tag management code comprises requesting the one or more vendor tags according to an order based on the one or more dependencies to reduce an overall load time of the web page.   
     
     
         41 . A system, comprising:
 a first server comprising memory storing a tag container that, when executed by a device parsing a web page, controls the device to determine whether to asynchronously load tag management code, wherein the first server is configured to transmit the tag container for insertion into the web page; and   a second server comprising:
 one or more processors comprising hardware; 
 first memory storing the tag management code; 
 second memory storing computer-executable instructions that, when executed by at least one of the one or more processors, cause the second server to:
 receive, from the device, a first request to load the tag management code while the device continues to load a remainder of the web page; 
 in response to the first request, transmit the tag management code to the device; 
 receive, from the device in response to the device executing the tag management code, a second request to load one or more vendor tags while the device continues to load the remainder of the web page; 
 in response to the second request, transmit at least one of the one or more vendor tags; and 
 receive, from the device in response to a determination that a particular tag, among the one or more vendor tags, has not been loaded by the device, a call to execute a delay for a specified period of time to cause the device to wait the specified period of time before continuing to load the web page. 
 
   
     
     
         42 . The system of  claim 41 , wherein the computer-executable instructions, when executed, further cause the second server to:
 provide a user interface through which a user configures the tag container.   
     
     
         43 . The system of  claim 42 , wherein the user interface comprises:
 a drop down menu that allows the user to select one or more parameters for the tag container; or   a field that allows the user to input text for one or more parameters for the tag container.   
     
     
         44 . The system of  claim 42 , wherein the user interface allows the user to:
 define a client name associated with the tag container;   define a parameter of the tag container, wherein the parameter is specific to the web page;   
       or
 define an identifier that identifies the web page. 
 
     
     
         45 . The system of  claim 41 , wherein the computer-executable instructions, when executed, further cause the second server to:
 transmit a first vendor tag, among the one or more vendor tags, to the device to cause the device to cache the first vendor tag.   
     
     
         46 . The system of  claim 41 ,
 wherein the tag management code is configured to cause the device to preload and cache the one or more vendor tags while the device continues to load the web page, and   wherein the one or more vendor tags are associated with a website comprising the web page.   
     
     
         47 . A method, comprising:
 requesting, by a device from a web server, a web page of a website, the web page comprising page elements and a tag container;   loading, by the device, the page elements;   asynchronously loading, by the device while the device continues loading the page elements, tag management code in response to executing the tag container;   loading, by the device while the device continues loading the page elements, a first tag;   executing, by the device, the first tag to collect first data indicative of a user interaction with the web page and to transmit the first data via a network to a remote machine;   determining that an asset, which is not yet loaded, has a dependency on a second tag;   making a call to a service that determines that the device is set to allow caching of objects;   preloading a second tag, wherein the preloading comprises:
 requesting, by the device while the device continues loading the page elements, a second tag from a tag server; and 
 caching, in memory by the device, the second tag; and 
   after the caching, recalling the second tag from the memory and executing the second tag to collect second data indicative of a user interaction and to transmit the second data via the network.   
     
     
         48 . The method of  claim 47 , wherein the making the call to a service comprises transmitting a request to a remote server. 
     
     
         49 . The method of  claim 47 , further comprising, prior to making the call, making an initial call to the service to ensure that the service is properly responding and caching a file in the memory. 
     
     
         50 . The method of  claim 47 , further comprising providing a user interface through which a user configures the tag container.