Revenue for Internet companies is often driven by advertising, which is typically paid out based on a network interaction (e.g., a click) on an advertisement. However, one network interaction is not equivalent to another network interaction—for example, a botnet may be developed to cause network interactions on an advertisement as compared to a user that causes a network interaction on an advertisement while surfing the net.
Various embodiments of the invention are disclosed in the following detailed description and the accompanying drawings.
The invention can be implemented in numerous ways, including as a process, an apparatus, a system, a composition of matter, a computer readable medium such as a computer readable storage medium or a computer network wherein program instructions are sent over optical or communication links. In this specification, these implementations, or any other form that the invention may take, may be referred to as techniques. A component such as a processor or a memory described as being configured to perform a task includes both a general component that is temporarily configured to perform the task at a given time or a specific component that is manufactured to perform the task. In general, the order of the steps of disclosed processes may be altered within the scope of the invention.
A detailed description of one or more embodiments of the invention is provided below along with accompanying figures that illustrate the principles of the invention. The invention is described in connection with such embodiments, but the invention is not limited to any embodiment. The scope of the invention is limited only by the claims and the invention encompasses numerous alternatives, modifications and equivalents. Numerous specific details are set forth in the following description in order to provide a thorough understanding of the invention. These details are provided for the purpose of example and the invention may be practiced according to the claims without some or all of these specific details. For the purpose of clarity, technical material that is known in the technical fields related to the invention has not been described in detail so that the invention is not unnecessarily obscured.
Determination and application of a rating for a network interaction are disclosed. A rating is provided to an advertiser and/or a publisher so that an understanding can be determined of a payment between the advertiser and the publisher.
In some embodiments, a rating is used to determine a payment and/or a payment level between an advertiser and publisher. In some embodiments, a rating is used to determine the placement of an advertisement on a publishing site. In some embodiments, a rating is used to assess an advertisement.
In some embodiments, edge appliances can also be used to monitor traffic at other points in the network other than in front of or just beside a server—for example, on a trunk line, an internet service provider network, an advertising network, or any other appropriate traffic site.
In some embodiments, server 106 reports information regarding the network interaction. For example, a software monitor records information regarding a network interaction including a time, an IP originating address, a domain, a country, an operating system, user agent, referrer, stem portion of referrer (“referrer-stem”, query portion of referrer (“referrer-query”), referrer query length, search key word, search key word frequency, etc. The software monitor forwards the information regarding the network interaction to model server 112 or analytics server 116 as appropriate to enable the use of the information to rate the network interaction. In some embodiments, where server 106 reports information regarding the network interaction, edge appliance 108 is not present.
Edge appliance 108 is able to communicate with model server 112. Edge appliance 108 periodically transmits reports and receives models from model server 112. Model server 112 can store information on storage device 114. Model server 112 forwards reports from edge appliance 108 to analytics server 116 and forwards models from analytics server 116 to edge appliance 108. In some embodiments, there are a plurality of model servers and a plurality of edge appliances, where an analytics server is able to support the communications with a plurality of model servers, and a model server is able to support the communications with a plurality of edge appliances. In some embodiments, scalability is achieved using a plurality of model servers.
Models are used by edge appliance 108 to calculate a preliminary score in real-time or quasi-real-time for detected network interactions. A preliminary score can be based on information associated with detected network interaction(s) as well as on stored parameters or models received from a model server or an analytics server such as model server 112 and analytics server 116, respectively.
Analytics server 116 stores report information to storage device 120 which acts as a data warehouse for the report information. Reports web server 122 can build reports based on the data stored in storage device 120. Network operations server 118 monitors the health and status of the system for analyzing network interactions including model server 112, analytics server 116, reports web server 122, and edge appliance 108. Network operations server 118 is able to communicate with each of the system hardware units including model server 112, analytics server 116, reports web server 122, and edge appliance 108 (in some cases directly or via the Internet with edge appliance 108 and in some cases via the Internet, through firewall 104, and via LAN 105).
In various embodiments, edge appliance 108 monitors network traffic on a local network that is separated from other networks (e.g., the Internet) by a firewall, receives network traffic from a local network and transmits the network traffic to a web server, receives network traffic from a local network that also transmits the network traffic to a web server, or receives network traffic from any other point or between any other two points appropriate for monitoring network traffic.
In various embodiments, model server 112, analytics server 116, network operations server 118, and reports web server 122 are implemented in separate servers or computer hardware units, in a single server or computer hardware unit, or any combination of separate and combined servers or computer hardware units.
In various embodiments, different combinations of model server 112, analytics server 116, and reports web server 122 are used to determine a rating for a network interaction.
In some embodiments, a payment for publishing an advertisement to an advertiser by a publisher is based on a rating of a network interaction. For example, a higher quality network interaction is associated with a higher payment, and a lower quality network interaction is associated with a lower payment.
In some embodiments, the placement of an advertisement on a publisher's web page is determined by a rating of a network interaction. For example, a higher quality network interaction is shown advertisements that are associated with a higher payment to an advertiser, and a lower quality network interaction is shown advertisements that are associated with a lower payment to an advertiser. Or for another example, a network interaction that is more likely to convert (or click on an advertisement) is shown an advertisement that earns a publisher more if converted, and a network interaction that is less likely to convert is shown an advertisement that earns a publisher the same whether converted or not. In various embodiments, placement of an advertisement comprises publishing or not publishing an advertisement by a publisher, publishing in a particular location of an advertisement by a publisher, or any other appropriate placement of an advertisement by a publisher.
In some embodiments, the rating of network interactions associated with a particular advertisement enables the assessment of the content of the advertisement. For example, ratings can be used to determine which advertisements to continue with based on the quality of ratings that the advertisement attracts.
In some embodiments, the rating of the network interactions associated with a particular advertisement enables the assessment of the placement of the advertisement. For example, ratings can be used to determine which publishers to continue with based on the quality of rating that the advertisement attracts.
In various embodiments, any other relevant information (e.g., from layer 3 to layer 7) regarding a network interaction is received. In some embodiments, relevant information detected from a hardware or software detector regarding the network interaction is received and used to rate the network interaction. In some embodiments, information regarding a plurality of network interactions is used in rating a single network interaction for averaging, comparison, or any other appropriate manner of rating of a network interaction.
In some embodiments, data received regarding a network interaction indicates that the network interaction is one of many recent visits from the same IP address, the rating process rates the network interaction such that the rating would decrease, whereas data received regarding a network interaction that indicates that the network interaction is one of many recent visits from the same IP address during which conversions and/or purchases have been made, the rating for the network interaction would increase. In this example, the rating system has ratings that increase for a better/desirable network interaction and decrease for worse/undesirable network interactions.
In various embodiments, a rating calculation is based on empirical and/or statistical models of network interactions and outcomes (i.e., conversions and/or purchases). In various embodiments, a rating calculation is based on a series of business rules which in turn rely on statistical models, do not rely of statistical models, rely on empirical models, or any other appropriate basis for ratings.
Although the foregoing embodiments have been described in some detail for purposes of clarity of understanding, the invention is not limited to the details provided. There are many alternative ways of implementing the invention. The disclosed embodiments are illustrative and not restrictive.
This application is a continuation in part of co-pending U.S. patent application Ser. No. 11/986,311, entitled A NETWORK INTERACTION MONITORING APPLIANCE filed Nov. 19, 2007 which is incorporated herein by reference for all purposes, which claims priority to U.S. Provisional Application No. 61/007,915, entitled A NETWORK INTERACTION MONITORING APPLIANCE filed Dec. 15, 2006 which is incorporated herein by reference for all purposes; and is a continuation in part of co-pending U.S. patent application Ser. No. 11/890,312 entitled USING A REASON CODE TO INDICATE A REASON FOR A RATING OF A NETWORK INTERACTION filed Aug. 3, 2007, which is incorporated herein by reference for all purposes.
Number | Name | Date | Kind |
---|---|---|---|
6437812 | Giles et al. | Aug 2002 | B1 |
7493655 | Brown | Feb 2009 | B2 |
7657626 | Zwicky | Feb 2010 | B1 |
7712141 | Agrawal et al. | May 2010 | B1 |
8160924 | Daniels et al. | Apr 2012 | B2 |
8321269 | Linden et al. | Nov 2012 | B2 |
8554804 | Muret et al. | Oct 2013 | B2 |
8572733 | Rockwood | Oct 2013 | B1 |
20030105863 | Hegli et al. | Jun 2003 | A1 |
20030145233 | Poletto et al. | Jul 2003 | A1 |
20030195960 | Merriam | Oct 2003 | A1 |
20030225811 | Ali et al. | Dec 2003 | A1 |
20040117654 | Feldmen et al. | Jun 2004 | A1 |
20040230476 | Messer | Nov 2004 | A1 |
20040254857 | Onizuka | Dec 2004 | A1 |
20060004633 | Ashbaugh | Jan 2006 | A1 |
20060026067 | Nicholas et al. | Feb 2006 | A1 |
20060069784 | Hsu et al. | Mar 2006 | A2 |
20060136294 | Linden et al. | Jun 2006 | A1 |
20060253578 | Dixon et al. | Nov 2006 | A1 |
20060259542 | Wu et al. | Nov 2006 | A1 |
20060265493 | Brindley et al. | Nov 2006 | A1 |
20070033106 | Mason | Feb 2007 | A1 |
20070061211 | Ramer et al. | Mar 2007 | A1 |
20070083519 | Daniels et al. | Apr 2007 | A1 |
20070192190 | Granville | Aug 2007 | A1 |
20070244857 | Yu | Oct 2007 | A1 |
20070255821 | Ge et al. | Nov 2007 | A1 |
Number | Date | Country |
---|---|---|
WO 2005053226 | Jun 2005 | WO |
Entry |
---|
Binkley et al. “Ourmon and Network Monitoring Performance” FREENIX Track: 2005 USENIX Annual Technical Conference, 2005, pp. 95-108. |
Non-Final Office Action dated Nov. 20, 2014, U.S. Appl. No. 11/640,125, filed Dec. 15, 2006, pp. 1-22. |
Final Office Action dated Jul. 23, 2015, U.S. Appl. No. 11/640,125, pp. 1-22. |
Non-Final Office Action dated Sep. 11, 2015, U.S. Appl. No. 11/890,312, pp. 1-30. |
Final Office Action dated Mar. 24, 2016, U.S. Appl. No. 11/890,312, pp. 1-24. |
Non-Final Office Action dated Sep. 22, 2016, U.S. Appl. No. 11/640,125, pp. 1-28. |
Final Office Action dated Mar. 27, 2017, U.S. Appl. No. 11/640,125, pp. 1-28. |
Non-Final Office Action dated Apr. 7, 2017, U.S. Appl. No. 11/890,312, pp. 1-25. |
Number | Date | Country | |
---|---|---|---|
61007915 | Dec 2006 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 11986311 | Nov 2007 | US |
Child | 12077947 | US | |
Parent | 11890312 | Aug 2007 | US |
Child | 11986311 | US |