Web-beacon plug-ins and their certification
View Patent ↗Tools and techniques are provided to allow partners of analytics providers and others who use web-beacons to submit web-beacon plug-ins for scrutiny, and for the plug-in to either be refused or else to be certified for use in a core JavaScript file or similar component. Analytics providers and others may also write web-beacon plug-ins. Certified plug-ins are executed in response to page loads, visitor clicks, and other visitor and programmatic actions at a website that has been tagged by the analytics provider's web-beacon, without requiring re-tagging of the website with a separate web-beacon for the partner. This allows the partner to obtain analytics data by piggybacking on the analytics provider, without re-tagging, and without compromising the availability and accuracy of the analytics data already being gathered. To be certified, web-beacon plug-ins must satisfy specific criteria as to their size, behavior, namespace, and the like.
1. A method implemented in an analytics server for gathering and reporting analytics data about user interactions with a website, the method comprising:
providing a web-beacon code for inclusion in a web page of a website, wherein the web-beacon code is configured to invoke core analytics code for gathering analytics data associated with the website; and
in response to the web-beacon code being executed in a visitor computer of a visitor to the web page:
receiving a first request from the visitor computer to invoke the core analytics code, wherein the core analytics code is executed in the visitor computer to gather the analytics data and to execute a plug-in to the core analytics code, wherein the plug-in is an executable function provided by an analytics provider partner and certified to comply with one or more certification criteria for interfacing with the core analytics code, wherein the plug-in is configured to send at least some of the analytics data from the visitor computer to a server for the analytics provider partner, and wherein the core analytics code comprises an interface for (i) passing control and data to the plug-in and (ii) protecting availability and accuracy of the analytics data by limiting an effect of the plug-in on the core analytics code; and
receiving a second request from the visitor computer comprising the analytics data.
2. The method of claim 1 , wherein an analytics provider tracks execution of the plug-in.
3. The method of claim 2 , wherein tracking execution of the plug-in comprises tracking a number of executions of the plug-in or tracking a number of web pages from which execution of the plug-in was invoked.
4. The method of claim 1 , wherein the core analytics code and the plug-in are configured to write to a shared cookie on the visitor computer.
5. The method of claim 1 , wherein the core analytics code executes a plurality of plug-ins, each belonging to an execution class, wherein plug-ins in one execution class have higher execution priority than plug-ins in another execution class.
6. The method of claim 1 , wherein the plug-in is invoked in response to at least one of the following events: page event, visitor action event, and programmatic event.
7. The method of claim 1 , wherein the analytics data comprises a unique visitor ID generated by the web page for identifying the visitor computer.
8. The method of claim 1 , wherein the core analytics code executes a plurality of plug-ins associated with a plurality of different analytics provider partners.
9. The method of claim 1 , wherein code for the plug-in introduces a new variable not present in the core analytics code.
10. A non-transitory computer-readable medium embodying a program for gathering and reporting analytics data about user interactions with a web site, the program executable in an analytics server, comprising:
code that provides a web-beacon code for inclusion in a web page of a website, wherein the web-beacon code is configured to invoke core analytics code for gathering analytics data associated with the website; and
code that in response to the web-beacon code being executed in a visitor computer of a visitor to the web page:
receives a first request from the visitor computer to invoke the core analytics code, wherein the core analytics code is executed in the visitor computer to gather the analytics data and to execute a plug-in to the core analytics code, wherein the plug-in is an executable function provided by an analytics provider partner and certified to comply with one or more certification criteria for interfacing with the core analytics code, wherein the plug-in is configured to send at least some of the analytics data from the visitor computer to a server for the analytics provider partner, and wherein the core analytics code comprises an interface for (i) passing control and data to the plug-in and (ii) protecting availability and accuracy of the analytics data by limiting an effect of the plug-in on the core analytics code; and
receives a second request from the visitor computer comprising the analytics data.
11. The non-transitory computer-readable medium of claim 10 , wherein the core analytics executes a plurality of plug-ins associated with a plurality of different analytics provider partners.
12. The non-transitory computer-readable medium of claim 10 , wherein the analytics data comprises a unique visitor ID generated by the web page for identifying the visitor computer.
13. The non-transitory computer-readable medium of claim 10 , wherein an analytics provider tracks execution of the plug-in.
14. The non-transitory computer-readable medium of claim 13 , wherein tracking execution of the plug-in comprises tracking a number of executions of the plug-in or tracking a number of web pages from which execution of the plug-in was invoked.
15. A system for gathering and reporting analytics data about user interactions with a website, the system comprising:
one or more processors;
a memory coupled to the one or more processors; and
an analytics service executed by the one or more processors, the analytics service comprising logic that:
provides a web-beacon code for inclusion in a web page of a website, wherein the web-beacon code is configured to invoke core analytics code for gathering analytics data associated with the website; and
in response to the web-beacon code being executed in a visitor computer of a visitor to the web page:
receives a first request from the visitor computer to invoke the core analytics code, wherein the core analytics code is executed in the visitor computer to gather the analytics data and to execute a plug-in to the core analytics code, wherein the plug-in is an executable function provided by an analytics provider partner and certified to comply with one or more certification criteria for interfacing with the core analytics code, wherein the plug-in is configured to send at least some of the analytics data from the visitor computer to a server for the analytics provider partner, and wherein the core analytics code comprises an interface for (i) passing control and data to the plug-in and (ii) protecting availability and accuracy of the analytics data by limiting an effect of the plug-in on the core analytics code; and
receives a second request from the visitor computer comprising the analytics data.
16. The system of claim 15 , wherein the plug-in is invoked in response to at least one of the following events: page event, visitor action event, and programmatic event.
17. The system of claim 15 , wherein the analytics data comprises a unique visitor ID generated by the web page for identifying the visitor computer.
18. The system of claim 15 , wherein an analytics provider tracks execution of the plug-in.
19. The system of claim 15 , wherein the core analytics code executes a plurality of plug-ins, each belonging to an execution class, wherein plug-ins in one execution class have higher execution priority than plug-ins in another execution class.
20. The system of claim 15 , wherein the core analytics code and the plug-in are configured to write to a shared cookie on the visitor computer.