The present invention generally relates to profile-based behavioral targeting advertisement placement methods. More specifically, the present invention relates to electronic advertisement placement based on expected profit from the placement.
DoubleClick's “Boomerang” is a service for advertisers that places a cookie on computers of visitors to an advertiser's site for the purpose of finding those visitors on other sites where DoubleClick is the ad server (“ad” is short for advertisement). When the same visitors are found on those other sites, additional advertiser's ads are served to them by the DoubleClick ad sever or by the advertiser's ad server following a redirect from the DoubleClick ad server.
The only server that can read a cookie on a user's computer is a server operating under the same domain as the server that placed the cookie on a user's computer to begin with. In other words, a cookie placed by a server operating under one domain cannot be read by another server working under a separate domain. That is why the advertiser cannot expect to place a cookie of its own (e.g., ford.com cookie) on a visitor to its site and then later expect the DoubleClick ad server (doubleclick.com) to be able to recognize the visitor when that visitor is visiting sites where DoubleClick serves ads by reading the ford.com cookies. Only a server operating under the DoubleClick domain can read a cookie placed by a server operating under the DoubleClick domain. So, DoubleClick needs to place a doubleclick.com cookie on visitors to the ford.com site for DoubleClick to later find those visitors within other sites, i.e., where the DoubleClick ad server is used to serve ads.
For a site to have its ad served by an ASP-hosted ad server, such as the one operated by DoubleClick, the site needs to redirect visitors from the site to the DoubleClick ad server, to fetch the ad from the server. Following the redirect from the site, the visitor accesses the DoubleClick ad server. Because the DoubleClick server is operating under the DoubleClick domain, it can read the DoubleClick cookie or cookies and then recognize that it encountered the same visitor in the past. In this example, the DoubleClick ad server recognizes the visitor as someone who visited the ford.com site.
AlmondNet, Tacoda, RevenueScience, and other companies (herein “BT companies”; “BT” stands for behavioral targeting) specialize in targeting ads based on observed behavior of sites' visitors. BT companies place a cookie (or cookies) on the computers of visitors to specific sections of a publisher's website or on the computers of visitors of the publisher who conducted a specific action such as search, click content, click an ad, request information, acquire a product, etc.
The placement of cookies allows those publishers or the BT company itself to sell ads to advertisers. Those ads will be presented to the visitors when they are found later on the same site or on other sites. Such sites can be either a site where the BT company's software is used or a site where the BT company has bought media. The BT company may buy the media on behalf of itself or on behalf of the publisher, who is interested in delivering ads to its audience outside the publisher's site.
Although a BT company (AlmondNet, Tacoda, RevenueScience, etc.) acts as an agent that places cookies on the computers of publisher's visitors for the purpose of delivering targeted ads to the publisher's visitors on other sites, the publisher can work without an agent and place cookies or tags on the computers of the publisher's own visitors for the purpose of delivering ads to those visitors on other sites where the publisher buys ad space. Such a publisher, acting without an agent, is also included in the definition of a BT company.
A publisher may also be referred to as a “profile supplier” when it transfers profile information, such as behavioral information, demographic information, etc., to a BT company. Therefore, a publisher that is a BT company may also be its own profile supplier. Furthermore, although the name “BT company” implies the targeting of ads is based on collected behavioral profiles, a BT company may also collect other kinds of profile information, such as demographic information or user-provided information, and target ads to those visitors wherever found based on the collected profile information.
Another kind of a BT company is a company that has software installed on a person's computer, such as toolbar software, desktop search software, weather software, or any kind of software that is used by the computer's user. Such software also monitors the computer user's visits to different publishers' sites and media properties and collects profile information about the computer user for the purpose of delivering ads to the user within ad space of sites and media properties that the user visits based on the collected profiles.
A BT company using software installed on a user's computer does not need the cooperation of a visited media property to collect information about the visitor's visit because that software monitors whatever the user is doing on his or her computer. A BT company that has software installed on a user's computer is therefore its own profile supplier. Such software can place a cookie or another kind of tag on the user's computer. Because the software is installed on the user's computer, it can write cookies readable by any domain. That means that the BT company can place a tag or cookie of a second media property, if the BT company would like the second media property to recognize the visitor when the visitor visits that second media property site, by simply having the software place a cookie operating under the domain of the second property on the visitor's computer. The software may also report the collected profiles to a central server of the BT company.
The central server may also tag the visitor or arrange for the visitor to be tagged by operators of other media properties. A BT company can place a cookie on a site's section when a visitor's computer visits that section, if a code of the company was integrated into the page of that section by the site that owns the page. The code (e.g., HTML or Java) redirects to the BT company's server all visitors to the page. Also, in the case that the BT company is the publisher itself, the publisher will simply “cookie” (by itself) all visitors that either read a specific content, search, click, ask for information, make a phone call, etc.
The BT company's server, which either gave the site a unique code for a page, received from the page its URL, or received access to the page's content that could be analyzed by the BT company's server, etc., identifies the content read by the page's visitor or the keyword searched for by the user, or an ad clicked on the page, etc. The content read by the page visitor could be identified by the BT company's server whether the content was reported by the site or whether the content was identified following the analysis of the page. The server then places a cookie on the user's computer indicating what content was read by the visitor on the page, what keyword was searched for by the user, or what ad was clicked on the page, etc. The placed cookie indicates that information (1) in the cookie per se, (2) in a central database operated by the server where the cookie ID is used as a record finder, or (3) both in the cookie and in the database.
Although the above description relates to cookies, a cookie is only one example of a possible tag. A tag generally is a unique identifier used to mark a person electronically visiting a media property, such as a web site, TV channel, radio show, or the like, using a computer, a mobile device, a TV set, a TV set top box, or any other device.
The tag is used for the purpose of delivering additional ads to a visitor to one media property when that visitor is found later on other media properties, based on the visitor's profile collected on the first media property. The profile could be the observed behavior of the visitor on the media property, demographic information collected on the media property, profile information provided by the visitor to the media property, etc.
Because the purpose of the tag is to enable the delivery of additional ads on other media properties visited by the visitor, and because the delivery of an ad requires only control of the ad space and not necessarily control of the entire media property visited by the visitor, a media property (in the present context) can also be defined as any equipment that controls an ad space viewed by a visitor, including a web site, an ad network's site (where the ad network represents the ad space of different sites), a TV program, some of the ad space within TV programs or TV channels (represented by a cable company), a TV network, or any ad space for which an entity is allowed to sell an advertisement and deliver it within the ad space; whether the ad space is owned by that entity, or whether the entity pays the owner of the ad space when using its ad space to deliver an ad sold by the entity. Ad space can be on a web site, in a TV program, in a text message, in a radio show, in any broadcasted material, in any streaming video or audio, etc. An ad space can be a fixed position on a page, or the ad space can be made available by a web site to an ad network (for example) only when the web site did not sell all of the site's ad inventory and therefore wishes to make some of the inventory available to the ad network.
In the case of a media property controlling an ad space viewed by a visitor, a specific ad space on a page might be controlled only temporarily. For example, in the case of the web site that did not sell all the ad impressions available to be delivered within an ad space on a page and therefore makes the unsold ad space available to the ad network to fill, the ad network will have temporary control of the ad space, i.e., when that ad space is given to it by the web site. Once the site redirects the ad space on the page to the ad network (so the ad network could fill the ad space with an ad sold by the ad network), the ad network controls the ad space and has access to the visitor viewing the ad space that was redirected to the ad network by the site, and therefore the ad network's equipment is considered a media property, as it controls an ad space viewed by a visitor.
The tag can be placed on the device used by the user to access the first media property where the user's profile was collected (in case of observed behavior, that behavior can be reading a specific content, searching, clicking an ad or content, making a phone call, asking for product information, acquiring a product, or taking any other kind of action). A tag placed on the device (1) could be read only by a server operating under the same domain as the server that placed the tag on the device to begin with as in the case of a cookie for example, (2) could be placed on the device when the user visited the first media property, and then the tag can be read by any second media property visited by the visitor, or (3) could be encrypted and, while accessed by any second media property visited by the visitor, the tag could be deciphered only by second media property computers that received the deciphering code from the first media property. In case of a tag placed by software installed on a user's computer, the tag could be whatever the software wants it to be, including a cookie of any domain.
A tag does not have to be placed on the user's device. A tag can also be used in a central database of a BT company or a central database of any second media property visited by the visitor, where the tag could be a unique identifier either of the device or of the user. In the case where the tag identifies the device, the tag might denote an IP address, a phone number, a device's manufacturer serial number, etc. A cookie placed on the device can also uniquely identify the device and the cookie therefore can be used as a tag in a central database. In the case where the tag identifies the user, the tag might denote the username and password used to access a media property, a user's name and address, a user's e-mail, a user's social security number, or any other personal identifiable information.
As already mentioned, the observed behavior of a visitor to a first media property is referred to as profile information about a specific visitor. A visitor's profile might be enhanced by the visitors' observed behavior on other media properties or by other profile information collected on other media properties.
A visitor's profile can be represented by a unique tag, or the profile can be stored with the tag, whether the tag is placed on the device, on a central database, or both. For example, the profile can be stored within a cookie (tag) on a visitor's device, or the profile can be stored in a central database where the tag connected to the profile is used as a unique identifier of the visitor's device or of the visitor personally. The profile can also be saved on both the device and a central database.
One of the major challenges in targeting a first site visitor on another site with an ad based on his observed behavior on sites visited by him previously (such as the first site) is actually finding the visitor on other sites.
Depending on the tag placed (or arranged to be placed) by the BT companies, the visitor could be recognized either by the entity that placed the tag to begin with (which requires access by that entity to the tag when the visitor visits a second media property) or by the second media property reading the tag (in which case the tag can be placed by the second media property if the BT company so arranges).
BT companies, acting as an agent, can find visitors tagged by them, when the tagged visitors are present on sites that use the BT companies' software (either to serve ads or in conjunction with those sites' ad servers). BT companies (whether it is acting as an agent, is the publisher itself, or is operating with any other BT company) can find visitors tagged by them, when the visitors are present on sites and ad networks where the BT companies buy media.
To make the process of finding people who visited a first media property on other media properties more efficient, BT companies enable sites and ad networks (from whom the BT companies buy media) to also place their cookies on the computers of people (visitors) on whose computers the BT company has placed its own cookie. That technique is similar to the way DoubleClick's Boomerang system places cookies on visitors to an advertiser site for the purpose of finding those visitors later on other sites where Doubleclick serves ads.
An ad network ad server (or any other server of the ad network) or a site's ad server (or any other server of the site) can place their own cookies on the computers of visitors that are redirected to them by the BT companies, for the purpose of later recognizing those visitors within their own ad space (i.e., the ad space of the ad networks or the sites).
This process—where sites and ad networks place cookies on visitors' computers redirected to them by BT companies (or other entities interested in additional ads presented to their audience elsewhere)—is sometimes referred to as “cookie matching.”
For example, weather.com might place a weather.com cookie on a user's computer marking him or her as a visitor to BT company #1, following a redirect from BT company #1 server. Later, if and when the weather.com ad server recognizes that the same visitor (previously redirected to him by BT company #1) happened to visit weather.com (weather.com will recognize the visitor by reading its own weather.com cookie, which marked the visitor as a BT company #1 visitor), the weather.com ad server can, if it wishes, redirect the visitor's computer to the BT company #1 server, to have an ad served to the visitor, either by BT company #1's ad server or another ad server to which BT company #1 ad server further redirects the visitor. The weather.com ad server's decision, whether or not to redirect the visitor's computer to BT company #1's server can be based on the price that BT company #1 promised to pay weather.com for the presentation of an ad within weather.com's ad space, to a visitor previously redirected to weather.com by BT company #1's server.
Although the above-described processes enable a second media property to recognize a first media property visitor, it is still a very inefficient process for the following reasons:
(1) Media properties' ad space prices vary.
(2) Profiles of media properties' visitors are worth different amounts to advertisers depending on the profiles. For example, a person who searched for a “mortgage” on a search engine might be presented with a mortgage-related ad, for which the advertiser is willing to pay $3 if that person clicks on that ad. A person who searched for “socks” on a search engine might be presented with a socks-related ad, for which the advertiser is willing to pay $0.50 if that person clicks on that ad. A person who visited the mutual fund section of a site might be presented with a mutual-fund related ad (wherever the person is found, i.e., either on the same site or on other sites), in which case the advertiser is willing to pay $25 for every thousand ads (CPM) presented to people who visited that mutual fund section.
(3) The same person might have several profile attributes in his or her profile (as a result, for example, of that person conducting several different searches and visiting different sites). Different advertisers might be willing to pay different amounts for delivering ads to the person based on the specific profile attribute or attributes that the respective advertisers are looking to target.
In summary, the cost of ad space at a second media property might not be covered by revenues generated for a BT company buying the space, i.e., from an ad delivered within the second media property ad space based on a profile collected in a first media property or properties. Alternatively, the revenues might cover the media cost but not deliver satisfactory margins to the BT company, when taking into account other costs, such as ad sales people cost, ad serving cost etc.
According to various aspects of the invention, therefore, an automatic system is described to facilitate selection of media properties on which to display an advertisement, responsive to a profile collected on a first media property, where a BT company calculates expected profit for an ad correlated with the profile and arranges for the visitor to be tagged with a tag readable by the selected media property.
The profit can be calculated by deducting, from the revenues that are expected to be generated from an ad delivered based on the collected profile, at least the price of ad space at a media property where the BT company might like to deliver ads to the profiled visitor. When the calculated profit is positive (i.e., not a loss), the BT company arranges for the visitor to be tagged with a tag readable by the selected media property through which the BT company expects to profit.
The above summary does not include an exhaustive list of all aspects of the present invention. Indeed, the inventor contemplates that the invention may include all systems and methods that can be practices from all suitable combinations of the various aspects summarized above, as well as those disclosed in the detailed description below and particularly pointed out in the claims filed with the application. Such combinations have particular advantages not specifically recited in the above summary.
Referring to the embodiment of
Profit can be defined as:
(1) revenues expected to be generated, from an ad delivered based on the collected profile, minus the ad space cost at a specific media property (i.e., Pr=Rev (profile)−P (mp), where “Pr” is profit, “Rev” is revenue generated from advertising to a visitor with a particular profile, and “P” is the price charged by media property “mp” for advertising in an ad space);
(2) revenues expected to be generated, from an ad delivered based on the collected profile, minus the sum of (a) the price for buying ad space on the specific media property, (b) ad serving cost, (c) ad sales associated cost, and (d) desired profit margin (i.e., Pr=Rev(profile)−P(mp)−C−Mar, where “C” represents costs and “Mar” represents desired profit margin), or
(3) in other ways.
If the calculated profit indicates that the BT company will lose (negative profit) from delivering an ad, based on the received profile on any of the possible media properties where it is buying ad space, the BT company won't arrange for the visitor to be tagged by a tag readable by any of those media properties, and the BT company might even decide not to collect the profile (so the visitor's profile will not be stored). Using the equation defining profit in item (2) just above, the question of whether the profit is positive or negative, as stated in this paragraph, equates to testing (4) whether Rev(profile)−P(mp)−C−Mar>0, which is the same as (5) whether Rev(profile)−P(mp)−C>Mar, or (6) whether Rev(profile)>P(mp)+C+Mar, or (7) whether P(mp)<Rev(profile)−C−Mar. Grouping the terms on the right-hand side of the equation in item (7) reduces that equation to the same as testing whether the price charged by a media property is less than a price cap, with the price cap being defined as the difference determined by subtracting from the revenue generated from advertising to a visitor with a particular profile a selected amount, here defined by the costs and desired profit margin.
Likewise, using the equation defining profit in item (1) just above, the question of whether the profit is positive or negative equates to testing (8) whether Rev(profile)−P(mp)>0, which equates to testing (9) whether P(mp)<Rev(profile), which again is the same as testing whether the price charged by a media property is less than a price cap, with the price cap being defined in this instance simply as the available revenue generated from advertising to a visitor with a particular profile.
The method includes the following basic steps, shown in
1. A profile supplier 20 redirects (100) a visitor 10 to a BT company 30 along with the visitor's profile. In case the profile supplier 20 is also the BT company 30, this step either does not take place or takes place internally, for example via an internal redirect from one server to another server operating under the same domain that belongs to the publisher/BT Company. In case the BT company 30 has software on a user's computer 11 that enables it to monitor the user's visits to media properties (e.g., 20, 40, 50) without the cooperation of the media properties, this step either does not take place or takes place internally, e.g., by the software on the user's computer communicating the collected profile to the BT company's central server.
2. The BT company 30 recognizes (200) the content read by the user 10, the category to which the content read by the user 10 belongs, the keyword searched for by the user 10, an ad clicked by the user 10, or any other action conducted on the page/site 20 by the user 10 (such as click on an item of content or an ad, purchase of a product, request for more information, etc) during the site visit (110). The recognizing might be as simple as pulling a keyword for which the visitor 10 searched from a URL used by the profile supplier 20 to redirect the visitor 10 to the BT company 30, for example.
3. The BT company 30 optionally can categorize (300) specific content read by the user 10, or an action conducted by a user 10. An example action might be a search for a keyword. To illustrate, suppose a person searched for an airline ticket to Florida on a travel site. When the BT company 30 receives that information, in addition to recording the search for the flight to Florida in the visitor's profile (whether the profile is stored in the cookie or tag, the BT company's central database 31, or both of those places), the BT company 30 may further categorize the person under the “Travel” category and in the “Search for Flights” subcategory of “Travel.”
4. The BT company 30 calculates (400) expected revenues from delivering ads based on the collected profile (Rev(profile) in the equations above). The revenues are calculated based on the kind of collected profile: (a) Expected revenues from content read by the visitor 10 can be calculated by checking, for example, how much advertisers are willing to pay for delivering ads to visitors who read specific content. (b) Expected revenues from delivering ads based on a keyword searched by the visitor 10 can be calculated by checking, for example, how much advertisers are willing to pay for each click on an ad related to the keyword for which the visitor searched and multiplying that price per click by an assumed click-through rate on ads related to the searched-for keyword, up to 14 days after the visitor's search. In general, expected revenues can be calculated for the delivery of ads based on a category of content read by the visitor 10, for specific content read by the visitor 10, or for action taken by the visitor 10 (e.g., made a phone call, clicked an ad, clicked specific content, asked for information, acquired product, etc.).
5. The BT company 30 selects (500) media properties (e.g., 40) for the delivery of an advertisement based on a profile collected on a first media property 20. The BT company 30 makes the selection based on a calculated expected profit and then arranges for the visitor 10 to be tagged (610 or 620) with a tag readable by the selected media property 40. The profit is calculated in any of the alternative manners stated above.
The BT company's arranging placement of the tag can be achieved in different ways:
A. The BT company 30 can redirect (630) a visitor to the selected media property 40, 50 with a request to have the selected media property 40, 50 tag (620) the visitor with the media property's own tag, which obviously is readable by the selected media property 40, 50 (such a tag could be a cookie on the visitor's storage device 12).
B. The BT company 30 can itself place (610) a tag that will be readable by the selected media property 40.
C. The BT company 30 can place an encoded tag that, although accessible by any media property (e.g., 40, 50), can be read only by a selected media property 40 to which the BT company gave a deciphering code.
D. In cases when the BT company 30 has software installed on a user's computer 10, the BT company 30 can arrange for the software to place (not shown) a tag readable by the selected media property 40 (such a tag could be a cookie operating under the selected media property domain).
E. The BT company 30 can arrange for the selected media property 40 to place a tag in the selected media property's central database 41, in which case the tag can uniquely identify (1) the device 11 that the visitor 10 will use to access the selected media (IP address, set-top box ID, mobile phone number, manufacturer serial number, cookie readable by the selected media property, etc.), or (2) the user as a person (personal identifiable information).
When a selected media property 40 recognizes a tagged visitor 10 (tagged previously, at time t1) later (at time t2) visiting (710) its ad space, the media property 40 will arrange for the BT company 30 to serve an ad (720) to the visitor 10 (which will appear with the media content (730) requested by the visitor), by redirecting (700) a visitor to the BT company 30, for example.
The media properties can be of the same kind of media (e.g., two web sites 40, 60 on the Internet 80) or of different media (e.g., first media property can be a web site 40 on the Internet 80, and the second media property can be a TV channel on TV or a text message system on a mobile phone, etc.). In the case (not shown) where the second media property operates within a different media than the first media, the tagging of the visitor with a tag readable by the second media property (which is arranged by the BT company 30) might include finding the device used by the visitor 10 to access the second media by using personal identifiable information about the visitor 10. As there may be no connection between the device used by the visitor to access the first media property (computer 11, for example) and the device used by the visitor to access the second media property (TV, for example) besides the commonality of the user (visitor) 10, personal identifiable information about the visitor 10 could be used to allow the second media property to learn which device the visitor 10 uses to access the second media property and tag the visitor 10. The second media property could tag the device used by the visitor 10 to access the second media property by placing a tag on the device itself or in a central database of the second media property, for example).
Although the BT company 30 stores the visitor's collected profile, in the above-described implementation it does not transfer the collected profile to the second media property 40, 50 but simply asks the second media property 40, 50 to tag the visitor as a BT company visitor or arrange for a tag to be placed (620) that is readable by the second media property 40 and that marks the visitor as a BT company visitor. As the BT company 30 buys ad space from the proprietor of the second media property 40 and delivers therein an ad based on the collected profile, the BT company 30 has no economic incentive to transfer the profile information itself (such as the fact that the visitor searched for “car insurance”) to the second media property 40. The second media company's proprietor is being paid for the ad space and therefore just needs to know that the visitor 10 has been profiled by the BT company 30, which will pay the second media property's proprietor for an opportunity to deliver an ad to this visitor 10 within the ad space of the second media property 40.
Suppose, for example, a person searches for “mortgage” on Google (Google is a BT company 30 in this example). Using the method above, Google calculates that advertisers are willing to pay $3 per click on a mortgage-related ad, that the expected click-through on a mortgage-related ad is 0.3%, and therefore Google will earn $9 for every thousand mortgage-related ads delivered to people that searched for “mortgage” on Google when those people are found later, anywhere on the web (i.e., this is “Rev(profile)”). Google further knows that it costs Google $3 CPM to deliver a thousand ads on weather.com (i.e., “P(mp)”) to computers that were tagged by weather.com as Google visitors. Google therefore can calculate a profit of $6 CPM (without taking into account other costs, i.e., “C”) for delivering a thousand mortgage-related ads to Google visitors who searched for “mortgage” on Google when found later within the ad space of weather.com. Google will therefore arrange for weather.com to tag the person who searched for “mortgage” on Google as a Google visitor (by redirecting the visitor to weather.com with the request to tag the person as a Google visitor, for example).
In the case where a second media property controls ad space with prices that fall within a range, the BT company 30—in addition to arranging for the second media property (e.g., 50) to tag (620) its visitor—may also provide the second media property 50 with the price the BT company 30 is willing to pay the second media property 50 for delivering an ad within the second media property's ad space. In
Given that some kind of profiles such as behavioral profiles are time-sensitive (in other words, their value diminishes with time), the BT company 30—in addition to arranging the placement of a tag readable by the second media property 40, 50—may also provide the second media property 40, 50 (via the tag, for example) with a time period within which the BT company 30 will agree to deliver ads to the profiled visitor 10 within the ad space of the second media property 40, 50. Suppose, for example, a BT company 30 collected a profile of a visitor 10 who searched for “flowers.” The BT company 30 might arrange for the visitor 10 to be tagged with a tag, readable by a second media property 40, marking the visitor 10 as the BT company's visitor and setting a time limit of two days, which means that the second media property 40 can call upon the BT company 30 to serve an ad to the tagged visitor 10 only when the visitor 10 is found within the second media property's ad space up to two days after the visitor 10 was tagged (the tag may have a time stamp identifying the date and time the tag was placed to help the second media property 40 calculate the date before which the second media property 40 can call upon the BT company 30 to serve an ad).
The calculation that takes place in steps 4 and 5 of the above-described method may take place not at the time of profile collection as described above but beforehand. Conducting the calculation before the profile is collected can shorten the time it takes the server 30 to select the media properties. The calculation might be done beforehand for other reasons.
Specifically, step 4 (which states that the BT company 30 calculates the expected revenues from delivering ads based on the collected profile, where the revenues are calculated based on the kind of collected profile, i.e., “Rev(profile)”) may take place in advance. If for example, a collected profile describes the content read by a visitor, then, if other profiles were previously collected of the same kind of profile, there is no need to check how much advertisers are willing to pay for delivering ads, as it was already checked for profiles of the same kind.
The word “calculating” expected revenues can encompass a scenario in which there are no arithmetic calculations, but rather simply an act of locating the correct information. In this example, the information concerning how much advertisers are willing to pay for delivering their ads to visitors 10 that read a specific content is located, and no arithmetic calculation is needed.
For another example, if the expected revenues for delivering an ad for someone who searched for “mortgage” has recently been calculated, then there is no need to calculate it again, and the information can simply be located.
Although the examples describe calculation of revenues from delivering an ad at a media property 40, 50, depending on the method of payment for the media property, different calculations of expected revenues can take place.
If the media property only gets paid for when a visitor visiting it takes action, then the revenues per profile-based ad delivery should also be based on an action. Such a visitor action can be a click on an ad, a request for information from the advertiser (following a click on the ad), a registration with the advertiser, an act of buying a product or service from the advertiser, etc.
For example, if the media property 40 is paid at the rate of $0.40 per click on an ad presented to the media property's visitor, the BT company 30 will check how much the advertiser will pay the BT company 30 per visitor click when viewing an ad based on the collected profile. If the price per click paid by the advertiser at least exceeds the price per click paid for the media property, then the BT company 30 can arrange for the tagging of the visitor 10 with a tag readable by the selected media property (the one that will cost $0.40 per click).
In some scenarios, the BT company 30 might be paid for every ad delivered to a visitor, but the media property might trigger payment for every visitor click on an ad. Conversely, the BT company 30 might be paid for a visitor click on an ad, but the media property might trigger payment for every delivered ad regardless of whether a click took place or not. In those scenarios, so as not to expose itself to the risk of loss, the BT company 30 preferably translates the payment it receives (whether per ad delivery or ad click or per action) to the payment method applied to the media property. For example, if the BT company 30 is paid $0.25 per click on an ad by a visitor who searched for a “DVD” but a media property triggers payment for every ad delivery at $0.50 CPM (regardless of whether a click took place), the BT company 30 can translate the payment per click it receives to payment for ad delivery. In this example, the BT company 30 can calculate that, with an expected click-through of 0.4% on DVD-related ads by people who searched for “DVD” up to seven days before they are presented with an ad, the BT company 30 will generate $1 CPM (0.4% CTR*1,000 ads*$0.25 per click=$1), i.e., Rev(profile)≈$1 CPM. Because $1 CPM is more than the $0.50 cost of the media property (i.e., Rev(profile)>P(mp)), the BT company 30 will make a gross profit of $0.50 CPM and therefore (assuming costs are low or ignored) arrange for tag placement.
Likewise with respect to step 5 (which states that the BT company 30 selects media properties for delivery of an advertisement based on a profile collected on a first media property where the selection is made by the BT company 30 based on a calculated expected profit), the calculation on which the media property selection is based could be a calculation done beforehand. If the collected profile is of the same kind as another profile that was collected recently (for example, both profiles describe “searching for flights”) then the information concerning how much revenues would be generated from such a profile is already available, and there is no need to recalculate. Also, the profit has also been calculated, because the cost of ad space at the different media properties probably does not change in a short period of time. A look-up table can be used that lists, based on the kind of profile, the media properties that should be selected. In such a scenario, the steps of the method will be:
1. The BT company 30 calculates expected revenues from delivering ads based on different collected profiles.
2. The BT company 30 calculates expected profits (or losses) for the delivery of ads based on different collected profiles within the ad space of different available media properties 40, 50.
3. The BT company 30 builds a table wherein each kind of profile is assigned media properties where ads will be delivered based on the profile, and wherein the selection of media properties is made based on the previously calculated profit. The table is updated on a regular basis to make sure it is up to date.
4. The BT company 30 collects a profile.
5. The BT company 30 arranges for placement of a tag readable by a selected media property, where the selected media properties are taken from the table described in step 3 above.
The above is just one possible implementation. Instead of a table, a database or any other data structure can be used. The calculation could be done entirely in advance, entirely when the profile is collected, or a combination wherein some of the calculation is done in advance and some when the profile is collected.
Accordingly, the method can be described in the following more general steps:
1. The BT company 30 collects a profile.
2. The BT company 30 arranges (610, 620) for a tag (readable by a selected media property 40, 50, or both) to be placed, where the media property is selected based on the expected profit from the delivery of an ad (720) based on the collected profile within the ad space of the media property.
Although the above method focuses on profit calculation that takes into account expected revenues from delivery of an ad based on a collected profile, media property ad space cost and other costs, other parameters beyond costs and revenues might be taken into account. For example, an advertiser might insist that its ads appear on media properties that have certain content and not on other media properties, a media property might not agree to show ads from a certain category (for example, a sports media property might not agree to show sports-related ads, to avoid promoting competitors), etc.
The inventor considers various elements of the aspects and methods recited in the claims filed with the application as advantageous, perhaps even critical to certain implementations of the invention. However, the inventor regards no particular element as being “essential,” except as set forth expressly in any particular claim.
Although the invention has been described in terms of preferred embodiments and generally associated methods, the inventor contemplates that alterations and permutations of the preferred embodiments and methods will become apparent to those skilled in the art upon a reading of the specification and a study of the drawings.
This application claims the benefit of provisional application Ser. No. 60/804,937, filed Jun. 16, 2006, and provisional application Ser. No. 60/805,119, filed Jun. 19, 2006, which are herein incorporated by reference.
Number | Name | Date | Kind |
---|---|---|---|
5220655 | Tsutsui | Jun 1993 | A |
5359508 | Rossides | Oct 1994 | A |
5442633 | Perkins et al. | Aug 1995 | A |
5572643 | Judson | Nov 1996 | A |
5710884 | Dedrick | Jan 1998 | A |
5717923 | Dedrick | Feb 1998 | A |
5724424 | Gifford | Mar 1998 | A |
5724521 | Dedrick | Mar 1998 | A |
5751956 | Kirsch | May 1998 | A |
5752238 | Dedrick | May 1998 | A |
5774670 | Montulli | Jun 1998 | A |
5794210 | Goldhaber et al. | Aug 1998 | A |
5819092 | Ferguson et al. | Oct 1998 | A |
5819285 | Damico et al. | Oct 1998 | A |
5835718 | Blewett | Nov 1998 | A |
5848396 | Gerace | Dec 1998 | A |
5855008 | Goldhaber et al. | Dec 1998 | A |
5870546 | Kirsch | Feb 1999 | A |
5870550 | Wesinger, Jr. et al. | Feb 1999 | A |
5901287 | Bull et al. | May 1999 | A |
5918014 | Robinson | Jun 1999 | A |
5933811 | Angles et al. | Aug 1999 | A |
5937390 | Hyodo | Aug 1999 | A |
5937392 | Alberts | Aug 1999 | A |
5948061 | Merriman et al. | Sep 1999 | A |
5959623 | van Hoff et al. | Sep 1999 | A |
5963915 | Kirsch | Oct 1999 | A |
5999912 | Wodarz et al. | Dec 1999 | A |
6014638 | Burge et al. | Jan 2000 | A |
6016504 | Arnold et al. | Jan 2000 | A |
6026368 | Brown et al. | Feb 2000 | A |
6026369 | Capek | Feb 2000 | A |
6026374 | Chess | Feb 2000 | A |
6044376 | Kurtzman, II | Mar 2000 | A |
6047310 | Kamakura et al. | Apr 2000 | A |
6049835 | Gagnon | Apr 2000 | A |
6055513 | Katz et al. | Apr 2000 | A |
6073241 | Rosenberg et al. | Jun 2000 | A |
6128663 | Thomas | Oct 2000 | A |
6133912 | Montero | Oct 2000 | A |
6134532 | Lazarus et al. | Oct 2000 | A |
6141010 | Hoyle | Oct 2000 | A |
6177931 | Alexander et al. | Jan 2001 | B1 |
6188398 | Collins-Rector et al. | Feb 2001 | B1 |
6205432 | Gabbard et al. | Mar 2001 | B1 |
6216112 | Fuller et al. | Apr 2001 | B1 |
6216129 | Eldering | Apr 2001 | B1 |
6269361 | Davis et al. | Jul 2001 | B1 |
6285987 | Roth et al. | Sep 2001 | B1 |
6285991 | Powar | Sep 2001 | B1 |
6289318 | Barber | Sep 2001 | B1 |
6308202 | Cohn et al. | Oct 2001 | B1 |
6324519 | Eldering | Nov 2001 | B1 |
6366298 | Haitsuka et al. | Apr 2002 | B1 |
6377986 | Philyaw et al. | Apr 2002 | B1 |
6385592 | Angles et al. | May 2002 | B1 |
6401075 | Mason et al. | Jun 2002 | B1 |
6408278 | Carney et al. | Jun 2002 | B1 |
6415270 | Rackson et al. | Jul 2002 | B1 |
6415322 | Jaye | Jul 2002 | B1 |
6449657 | Stanbach, Jr. et al. | Sep 2002 | B2 |
6484492 | Meholic et al. | Nov 2002 | B2 |
6487538 | Gupta et al. | Nov 2002 | B1 |
6505169 | Bhagavath et al. | Jan 2003 | B1 |
6615247 | Murphy | Sep 2003 | B1 |
6633850 | Gabbard et al. | Oct 2003 | B1 |
6654725 | Langheinrich et al. | Nov 2003 | B1 |
6810527 | Conrad et al. | Oct 2004 | B1 |
6832207 | Shkedi | Dec 2004 | B1 |
6868392 | Ogasawara | Mar 2005 | B1 |
6868525 | Szabo | Mar 2005 | B1 |
6907566 | McElfresh et al. | Jun 2005 | B1 |
6925440 | Shkedi | Aug 2005 | B1 |
6973436 | Shkedi | Dec 2005 | B1 |
6983379 | Spalink et al. | Jan 2006 | B1 |
6985882 | Del Sesto | Jan 2006 | B1 |
7007074 | Radwin | Feb 2006 | B2 |
7038637 | Eller et al. | May 2006 | B1 |
7039594 | Gersting | May 2006 | B1 |
7039599 | Merriman et al. | May 2006 | B2 |
7043531 | Seibel et al. | May 2006 | B1 |
7058593 | Merritt | Jun 2006 | B1 |
7065550 | Raghunandan | Jun 2006 | B2 |
7072853 | Shkedi | Jul 2006 | B2 |
7085682 | Heller et al. | Aug 2006 | B1 |
7155508 | Sankuratripati et al. | Dec 2006 | B2 |
7181438 | Szabo | Feb 2007 | B1 |
7188076 | Bensemana | Mar 2007 | B2 |
7194424 | Greer et al. | Mar 2007 | B2 |
7299195 | Tawakol et al. | Nov 2007 | B1 |
7386599 | Piersol et al. | Jun 2008 | B1 |
7428493 | Shkedi | Sep 2008 | B2 |
7454364 | Shkedi | Nov 2008 | B2 |
7530020 | Szabo | May 2009 | B2 |
7558795 | Malik et al. | Jul 2009 | B2 |
7580855 | Fernandes | Aug 2009 | B2 |
7756744 | Schiff et al. | Jul 2010 | B2 |
7797274 | Strathearn et al. | Sep 2010 | B2 |
7822636 | Ferber et al. | Oct 2010 | B1 |
7822637 | Shkedi | Oct 2010 | B2 |
7822639 | Shkedi | Oct 2010 | B2 |
7861260 | Shkedi | Dec 2010 | B2 |
7890609 | Shkedi | Feb 2011 | B2 |
7899801 | Bronson et al. | Mar 2011 | B1 |
7930252 | Bender et al. | Apr 2011 | B2 |
7949553 | Wisniewski et al. | May 2011 | B1 |
7979307 | Shkedi | Jul 2011 | B2 |
8015184 | Zito et al. | Sep 2011 | B2 |
8036929 | Reisman | Oct 2011 | B1 |
8050970 | Barry et al. | Nov 2011 | B2 |
8051444 | Shkedi | Nov 2011 | B2 |
8117068 | Shuster et al. | Feb 2012 | B2 |
8135799 | Mekikian | Mar 2012 | B2 |
8175908 | Anderson | May 2012 | B1 |
8239264 | Shkedi | Aug 2012 | B2 |
8244574 | Shkedi | Aug 2012 | B2 |
8244582 | Shkedi | Aug 2012 | B2 |
8244583 | Shkedi | Aug 2012 | B2 |
8244586 | Shkedi | Aug 2012 | B2 |
8280758 | Shkedi | Oct 2012 | B2 |
8281336 | Shkedi | Oct 2012 | B2 |
8364540 | Soroca et al. | Jan 2013 | B2 |
8494904 | Shkedi | Jul 2013 | B2 |
8510174 | Walker et al. | Aug 2013 | B2 |
8527352 | Chatwin et al. | Sep 2013 | B2 |
8554940 | Jennings et al. | Oct 2013 | B2 |
8566164 | Shkedi et al. | Oct 2013 | B2 |
8589210 | Shkedi | Nov 2013 | B2 |
8595069 | Shkedi et al. | Nov 2013 | B2 |
8600815 | Shkedi | Dec 2013 | B2 |
8607267 | Shkedi | Dec 2013 | B2 |
8677398 | Shkedi | Mar 2014 | B2 |
8683502 | Shkedi et al. | Mar 2014 | B2 |
8695032 | Shkedi | Apr 2014 | B2 |
8713600 | Shkedi | Apr 2014 | B2 |
8751310 | van Datta et al. | Jun 2014 | B2 |
8768766 | Ellis et al. | Jul 2014 | B2 |
8775249 | Shkedi | Jul 2014 | B2 |
8880677 | Julia et al. | Nov 2014 | B2 |
8996406 | Jain | Mar 2015 | B2 |
8997138 | Shkedi | Mar 2015 | B2 |
9071886 | Shkedi | Jun 2015 | B2 |
9078035 | Shkedi et al. | Jul 2015 | B2 |
9083853 | Shkedi | Jul 2015 | B2 |
9117217 | Wilson et al. | Aug 2015 | B2 |
9131282 | Shkedi | Sep 2015 | B2 |
9226019 | Shkedi | Dec 2015 | B2 |
9271024 | Shkedi et al. | Feb 2016 | B2 |
9351053 | Shkedi | May 2016 | B2 |
9369779 | Shkedi | Jun 2016 | B2 |
9571865 | Shkedi | Feb 2017 | B2 |
9591380 | Shkedi et al. | Mar 2017 | B2 |
9756372 | Shkedi | Sep 2017 | B2 |
9800917 | Shkedi | Oct 2017 | B2 |
9813778 | Shkedi | Nov 2017 | B2 |
1000963 | Shkedi | Jun 2018 | A1 |
1002610 | Shkedi | Jul 2018 | A1 |
1007020 | Shkedi | Sep 2018 | A1 |
1017844 | Shkedi | Jan 2019 | A1 |
20010014868 | Herz et al. | Aug 2001 | A1 |
20010020242 | Gupta et al. | Sep 2001 | A1 |
20010034646 | Hoyt et al. | Oct 2001 | A1 |
20010039515 | Mayadas | Nov 2001 | A1 |
20010042002 | Koopersmitch | Nov 2001 | A1 |
20010044743 | McKinley et al. | Nov 2001 | A1 |
20020002541 | Williams | Jan 2002 | A1 |
20020026360 | McGregor et al. | Feb 2002 | A1 |
20020046286 | Caldwell et al. | Apr 2002 | A1 |
20020072965 | Merriman et al. | Jun 2002 | A1 |
20020072971 | DeBusk et al. | Jun 2002 | A1 |
20020077891 | Castle et al. | Jun 2002 | A1 |
20020082910 | Kontogouris | Jun 2002 | A1 |
20020082923 | Merriman et al. | Jun 2002 | A1 |
20020091568 | Kraft et al. | Jul 2002 | A1 |
20020099603 | Bandura | Jul 2002 | A1 |
20020112013 | Walsh | Aug 2002 | A1 |
20020112171 | Ginter et al. | Aug 2002 | A1 |
20020123928 | Eldering et al. | Sep 2002 | A1 |
20020133399 | Main | Sep 2002 | A1 |
20020143632 | Walter et al. | Oct 2002 | A1 |
20020161633 | Jacob et al. | Oct 2002 | A1 |
20020161636 | Takahashi et al. | Oct 2002 | A1 |
20020184088 | Rosenberg | Dec 2002 | A1 |
20020194058 | Eldering | Dec 2002 | A1 |
20030023481 | Calvert et al. | Jan 2003 | A1 |
20030028451 | Ananian | Feb 2003 | A1 |
20030036944 | Lesandrini et al. | Feb 2003 | A1 |
20030046156 | Cromer et al. | Mar 2003 | A1 |
20030046689 | Gaos | Mar 2003 | A1 |
20030050827 | Hennessey | Mar 2003 | A1 |
20030065558 | Shaw et al. | Apr 2003 | A1 |
20030065805 | Barnes, Jr. | Apr 2003 | A1 |
20030083931 | Lang | May 2003 | A1 |
20030083938 | Smith et al. | May 2003 | A1 |
20030101126 | Cheung et al. | May 2003 | A1 |
20030110497 | Yassin et al. | Jun 2003 | A1 |
20030135413 | Nishi et al. | Jul 2003 | A1 |
20030135853 | Goldman et al. | Jul 2003 | A1 |
20030149938 | McElfresh et al. | Aug 2003 | A1 |
20030154126 | Gehlot et al. | Aug 2003 | A1 |
20030171990 | Rao et al. | Sep 2003 | A1 |
20030208404 | Michie | Nov 2003 | A1 |
20030220837 | Asayama | Nov 2003 | A1 |
20030229542 | Morrisroe | Dec 2003 | A1 |
20040024632 | Perry | Feb 2004 | A1 |
20040059632 | Kang et al. | Mar 2004 | A1 |
20040068436 | Boubek et al. | Apr 2004 | A1 |
20040117322 | Bjorksten et al. | Jun 2004 | A1 |
20040186776 | Llach | Sep 2004 | A1 |
20040193488 | Khoo et al. | Sep 2004 | A1 |
20040260605 | McIntyre et al. | Dec 2004 | A1 |
20050010472 | Quatse et al. | Jan 2005 | A1 |
20050021397 | Cui et al. | Jan 2005 | A1 |
20050028188 | Latona et al. | Feb 2005 | A1 |
20050038698 | Lukose et al. | Feb 2005 | A1 |
20050038702 | Merriman et al. | Feb 2005 | A1 |
20050080772 | Bem | Apr 2005 | A1 |
20050086112 | Shkedi | Apr 2005 | A1 |
20050120091 | Casais | Jun 2005 | A1 |
20050131762 | Bharat et al. | Jun 2005 | A1 |
20050165644 | Beyda et al. | Jul 2005 | A1 |
20050187818 | Zito et al. | Aug 2005 | A1 |
20050216336 | Roberts et al. | Sep 2005 | A1 |
20050216823 | Petersen et al. | Sep 2005 | A1 |
20050222905 | Wills | Oct 2005 | A1 |
20050278443 | Winner et al. | Dec 2005 | A1 |
20050289590 | Cheok et al. | Dec 2005 | A1 |
20060020508 | Gorti et al. | Jan 2006 | A1 |
20060020510 | Vest | Jan 2006 | A1 |
20060026061 | Collins | Feb 2006 | A1 |
20060026064 | Collins | Feb 2006 | A1 |
20060029296 | King et al. | Feb 2006 | A1 |
20060053047 | Garcia et al. | Mar 2006 | A1 |
20060064351 | Hamor et al. | Mar 2006 | A1 |
20060069614 | Agarwal et al. | Mar 2006 | A1 |
20060095322 | Dierks | May 2006 | A1 |
20060098899 | King et al. | May 2006 | A1 |
20060106710 | Meek et al. | May 2006 | A1 |
20060116924 | Angles et al. | Jun 2006 | A1 |
20060122879 | O'Kelley | Jun 2006 | A1 |
20060129455 | Shah | Jun 2006 | A1 |
20060161553 | Woo | Jul 2006 | A1 |
20060183467 | Stewart | Aug 2006 | A1 |
20060200377 | Wolfe et al. | Sep 2006 | A1 |
20060212349 | Brady | Sep 2006 | A1 |
20060212350 | Ellis et al. | Sep 2006 | A1 |
20060224496 | Sandholm et al. | Oct 2006 | A1 |
20060253432 | Eagle et al. | Nov 2006 | A1 |
20060271690 | Banga et al. | Nov 2006 | A1 |
20060282327 | Neal et al. | Dec 2006 | A1 |
20060287916 | Starr et al. | Dec 2006 | A1 |
20070027850 | Chan et al. | Feb 2007 | A1 |
20070027901 | Chan et al. | Feb 2007 | A1 |
20070038516 | Apple et al. | Feb 2007 | A1 |
20070067297 | Kublickis | Mar 2007 | A1 |
20070079331 | van Datta et al. | Apr 2007 | A1 |
20070088603 | Jouppi et al. | Apr 2007 | A1 |
20070121843 | Atazky et al. | May 2007 | A1 |
20070130015 | Starr et al. | Jun 2007 | A1 |
20070150457 | Goldman et al. | Jun 2007 | A1 |
20070150468 | Goldman et al. | Jun 2007 | A1 |
20070150483 | Goldman et al. | Jun 2007 | A1 |
20070150721 | Goldman et al. | Jun 2007 | A1 |
20070157228 | Bayer et al. | Jul 2007 | A1 |
20070157245 | Collins | Jul 2007 | A1 |
20070162396 | Goldman et al. | Jul 2007 | A1 |
20070179845 | Jain | Aug 2007 | A1 |
20070179846 | Jain et al. | Aug 2007 | A1 |
20070179848 | Jain | Aug 2007 | A1 |
20070179849 | Jain | Aug 2007 | A1 |
20070179853 | Feige et al. | Aug 2007 | A1 |
20070192166 | Van Luchene | Aug 2007 | A1 |
20070192168 | Van Luchene | Aug 2007 | A1 |
20070198385 | McGill et al. | Aug 2007 | A1 |
20070203794 | Hajdukiewicz et al. | Aug 2007 | A1 |
20070214048 | Chan et al. | Sep 2007 | A1 |
20070260624 | Chung et al. | Nov 2007 | A1 |
20080052392 | Webster et al. | Feb 2008 | A1 |
20080109306 | Maigret et al. | May 2008 | A1 |
20080319850 | Shaul et al. | Dec 2008 | A1 |
20090049468 | Shkedi | Feb 2009 | A1 |
20090106100 | Mashinsky | Apr 2009 | A1 |
20090172723 | Shkedi et al. | Jul 2009 | A1 |
20090222329 | Ramer et al. | Sep 2009 | A1 |
20090234711 | Ramer et al. | Sep 2009 | A1 |
20090234861 | Ramer et al. | Sep 2009 | A1 |
20090254971 | Herz et al. | Oct 2009 | A1 |
20090281954 | Waelbroeck et al. | Nov 2009 | A1 |
20090299857 | Brubaker | Dec 2009 | A1 |
20100257053 | Ferber et al. | Oct 2010 | A1 |
20100268605 | Waelbroeck et al. | Oct 2010 | A1 |
20100293057 | Haveliwala et al. | Nov 2010 | A1 |
20100332583 | Szabo | Dec 2010 | A1 |
20110112903 | Goldman et al. | May 2011 | A1 |
20110258049 | Ramer et al. | Oct 2011 | A1 |
20120209705 | Ramer et al. | Aug 2012 | A1 |
20120209706 | Ramer et al. | Aug 2012 | A1 |
20120209707 | Ramer et al. | Aug 2012 | A1 |
20120209708 | Ramer et al. | Aug 2012 | A1 |
20120209709 | Ramer et al. | Aug 2012 | A1 |
20120209710 | Ramer et al. | Aug 2012 | A1 |
20120215635 | Ramer et al. | Aug 2012 | A1 |
20120215639 | Ramer et al. | Aug 2012 | A1 |
20130097019 | Ferber et al. | Apr 2013 | A1 |
20130097026 | Ferber et al. | Apr 2013 | A1 |
20130232001 | van Datta et al. | Sep 2013 | A1 |
20130254035 | Ramer et al. | Sep 2013 | A1 |
20140324576 | van Datta et al. | Oct 2014 | A1 |
Number | Date | Country |
---|---|---|
2246746 | Mar 1998 | CA |
2003-331183 | Nov 2003 | JP |
2012-073990 | Apr 2012 | JP |
10-2001-0096343 | Nov 2001 | KR |
20020037411 | May 2002 | KR |
10-2004-0099222 | Nov 2004 | KR |
WO-9721183 | Jun 1997 | WO |
WO1997021183 | Jun 1997 | WO |
WO 9944159 | Sep 1999 | WO |
WO1999057660 | Nov 1999 | WO |
WO 0154034 | Jul 2001 | WO |
WO 2004084109 | Sep 2004 | WO |
WO-2005022887 | Mar 2005 | WO |
WO 2005046237 | May 2005 | WO |
Entry |
---|
Engage Technologies, Inc., Form S-1A, filed with the SEC, pp. 36-50, Jul. 19, 1999. |
The e-Marketing Report, Morgan Stanley Dean Whitter, May 2000, portions. |
ClickOver, Inc. introduces ClickWise, the first inteligent, high-performance ad management system for electronic advertising, Business Wire, Mar. 24, 1997. |
Advertiser Solutions, https://web.archive.org/web/20050325042542/http://www.premiumnetwork.com/advertisers.shtml, archived Mar. 25, 2005. |
baseview.com website (ClassManagerPro) from www.archive.org, archived Jan. 16, 1997. |
Media Kit—Marketers, RevenueScience, https://web.archive.org/web/20051124105455/http://www.revenuescience.com/datafile/Mediakit_marketers_02.pdf, archived Nov. 24, 2005. |
Publisher Solutions, https://web.archive.org/web/20050325061154/http://www.premiumnetwork.com/publishers.shtml, archived Mar. 25, 2005. |
S-1/A SEC Filing, filed by FlyCast Communications Corporation on Apr. 30, 1999. |
RevenueScience (for Publishers), Behavioral Targeting, Delivering on the Promise of One-to-One Marketing (2005). |
24/7 RealMedia, The Science of Digital Marketing, Company Overview (2007). |
aaddzz.com webpages from www.archive.org, archived Jan. 30, 1998. |
AdForce, Inc., User Guide, A Complete Guide to AdForce, Version 2.6 (1998). |
Fawcett, Adrienne W., Publishers thankful but nervouse about boom, Magazinedotcom, Hot spending boosts . . . , adage.com, Nov. 1, 1999. |
Ad-Star.com website archive from www.archive.org (archived on Apr. 12, 1997 and Feb. 1, 1997). |
Chang et al., “Goodies” in exchange for Consumer Information on the Internet, The Economics and Issues, Proceedings of the Thirty-First Annual Hawaii International Conference on System Sciences, 1998. |
avenuea.com webpage, FAQ, www.avenuea.com/corpinfo/faq.html, archived Oct. 2, 1999. |
Advertising—A Unified Approach to Advertising Management, Baseview Products, Inc. brochure, Oct. 14, 1999. |
Ribeiro-Neto et al., Extracting Semi-Structured Data Through Examples, Proceedings of the Eighth international Conference on Information and Knowledge Management (1999). |
Raskutti and Beitz, Acquiring Customer Preferences for Information Filtering, a Heuristic-Statistical Approach, Fifth Annual Conference on User Modeling (1996). |
AdKnowledge, Campaign Manager—Quick Reference Card (1996). |
Emert, 2 Web Ad Firms Decide to Marry, Palo Alto's Focalink, ClickOver Merging, San Francisco Chronicle, Nov. 17, 1997. |
Elderbrock & Borwankar, Building Successful Internet Businesses, IDG Worldwide (1996). |
Schumann, David W. & Thorson, Ester, Advertising and the World Wide Web, Lawrence Erlbaum Associates (1999). |
Williamson, Debra Aho, Web ads mark 2nd birthday with decisive issues ahead, adage.com, Oct. 21, 1996. |
Williamson, Debra Aho, Targeting distinguishes AdForce from the pack, adage.com, Mar. 1, 1999. |
Doubleclick.com webpages from www.archive.org, archived Feb. 5, 1998. |
Tittel et al., Foundations of World Wide Web Programming with HTML & CGI, IDG Books Worldwide (1995). |
Harrison et al., An Emerging Marketplace for Digital Advertising Based on Amalgamated Digital Signage Networks, IEEE International Conference on E-Commerce, Jun. 24-27, 2003. |
Graham, Ian S., HTML Sourcebook, A Complete Guide to HTML, John Wiley & Sons (1995). |
Aaddzz Brochure, Information Access Technologies, Inc. (1997). |
Gilbert, Special Report, Agencies centralize Web ad serving, adage.com, Mar. 1, 1999. |
Palmer & Eriksen, Digital Newspapers Explore Marketing on the Internet, Communications of the ACM, vol. 42, No. 9, Sep. 1999. |
Angwin, Julia, Focalink Will Monitor World of Online Ads, San Francisco Chronicle, Feb. 7, 1996. |
Gallagher & Parsons, A Framework for Targeting Banner Advertising on the Internet, Proceedings of the Thirtieth Hawaii International Conference on System Sciences, Jan. 1997. |
Kazienko & Adamski, Personalized Web Advertising Methods, Third International Conference, AH 2004, Aug. 23-26, 2004. |
Cleland, Kim, Accipiter latest entrant in race to manage ads, company sets sights on helping content providers target audience, Adage.com, Sep. 9, 1996. |
Cleland, Kim, New Player joins fray of Web ad targeters, adage.com, Feb. 24, 1997. |
Bayne, Kim M., AdKnowledge rolls out Web ad evaluation tool, adage.com, Jul. 8, 1999. |
Langheinrich et al., Unintrusive Customization Techniques for Web Advertising, Computer Networks 31, 1259-1272, May 1999. |
Maekawa et al., A Java-Based Information Browsing System in a Remote Display Environment, IEEE (2004). |
Meeker, Mary, The Internet Advertising Report, Harper Business (1997). |
Yeager & McGrath, Web Server Technology, The Advance Guide for World Wide Web Information Providers, Morgan Kaufmann Publishers (1996). |
net.Genesis & Devra Hall, Build a Website, The Programmer's Guide to Creating, Building, and Maintaining a Web Presence, Prima Publishing (1995). |
NetGravity Launches AdServer 3.5 with Beefed Up Targeting, clickz.com, Sep. 10, 1998. |
Novak & Hoffman, New Metrics for New Media, Toward the Development of Web Measurement Standards, Project 2000, elab.vanderbilt.edu, Sep. 26, 1996. |
RealMedia.com webpages, www.archive.org, archived on May 15, 19977 and Jun. 7, 1997. |
Bruner, Rick E., Interactive, NetGravity to launch new ad service bureau, adage.com, Dec. 1, 1997. |
Bruner, Rick E., Small networks chase per-click ad business, Aaddzz, ValueClik compete, AdvertisingAge, Sep. 8, 1997. |
Zeff & Aronson, Advertising on the Internet, 1st Edition, John Wiley & Sons (1997). |
Zeff & Aronson, Advertising on the Internet, 2nd Edition, John Wiley & Sons (1999). |
Singh & Dalal, Web Home Pages as Advertisements, Communications of the ACM, Aug. 1999. |
The ClickZ Network, Netscape Selects Real Media's Open AdStream, Jan. 13, 1998. |
The ClickZ Network, Real Media Signs More Media Companies, Dec. 30, 1998. |
www.Spinbox.com webpages, www.archive.org, archived beginning Nov. 11, 1998. |
Bakos, The Emerging Role of Electronic Marketplaces on the Internet, Communications of the ACM, vol. 41, No. 8, Aug. 1998. |
Kohda, Youiji & Endo, Susumu, Ubiquitous Advertising on the WWW, Merging Advertisement on the Browser, Fifth International World Wide Web Conference, May 1996. |
Baseview.com webpages from www.archive.org, archived Jan. 16, 1997. |
AdForce, Inc., Quick Reference Guide, Version 3.0 (1999). |
AdManagerPro, Ad Entry Manual, User's Manual V.1.05, 1997. |
AdManagerPro, Ad Entry Manual, User's Manual V.2.0, 1997. |
AdManagerPro, Administration and Receivables Manual, Administrator's Manual Version 1.0.5, Nov. 1997. |
AdManagerPro, Administration and Receivables Manual, Administrator's Manual Version 2.0, Jun. 1998. |
Commercialization of the World Wide Web, The Role of Cookies, vanderbilt.edu web pages, archive.org, Feb. 1, 1997. |
Crabtree et al., Adaptive Personal Agents, Personal Technologies (1998). |
Dalton, Gregory, OPS, Answer to Cookies?, InformationWeek, Oct. 13, 1997. |
Dunn et al., Privacy and Profiling on the Web, Submitted to W3C on Jun. 2, 1997. |
firefly.com web pages, archive.org, archived 1998-2000. |
Gilbert, Jennifer, CMGI's Web dealmaking hits big-time, Advertising Age, Oct. 4, 1999. |
Hersley et al., Implementation of OPS Over HTTP, Submitted to W3C on Jun. 2, 1997. |
Hersley et al., Proposal for an Open Profiling Standard, Submitted to W3C on Jun. 2, 1997. |
Hersley et al., Standard Practices of OPS Systems, Submitted to W3C on Jun. 2, 1997. |
junkbusters.com web pages, archive.org, archived Apr. 1997 through Nov. 2000. |
Karpinski, Richard, ICE application to revolutionize e-commerce, Business Marketing, Mar. 1998. |
matchlogic.com web pages, archive.org, Apr. 13, 2000. |
Roscheisen, R. Martin, A Network-Centric Design for Relationship-Based Rights Management (Dissertation), Dec. 1997. |
Kristol, D. & Montulli, L., HTTP State Management Mechanism, Internet Engineering Task Force, available at https://tools.ietf.org/html/rfc2109, Feb. 1997. |
Berners-Lee, Tim, Information Management: A Proposal, CERN, available at http://www.w3.org/History/1989/proposal.html, May 1990. |
Berners-Lee, Tim, Uniform Resource Locators (URL), A Syntax for the Expression of Access Information of Objects on the Network, Internet Engineering Task Force, available at http://www.w3.org/Addressing/URL/url-spec.txt, Mar. 21, 1994. |
Berners-Lee, Tim, The Original HTTP as defined in 1991, W3C, available at http://www.w3.org/Protocols/HTTP/AsImplemented.html (1991). |
Berners-Lee, Tim et al., Hypertext Transfere Protocol—HTTP/1.0, Network Working Group Request for Comments: 1945, Internet Engineering Task Force, available at https://tools.ietf.org/html/rfc1945, May 1996. |
Leiner, Barry M. et al., Brief History of the Internet, Internet Society, Oct. 15, 2012. |
Berners-Lee, T. & Connolly, D., Hypertext Markup Language—2.0, Network Working Group Request for Comments: 1866, Internet Engineering Task Force, available at https://tools.ietf.org/html/rfc1866, Nov. 1995. |
Tungate, Mark, Adland—A Global History of Advertising, 2d Ed. (2013). |
Johnson, Bradley, Interactive, Planet Oasis Gives Web Sites Promotion Clout, Advertising Age, available at http://adage.com/article/news/interactive-planet-oasise-web-sites-promotion-clout/78467, Jul. 8, 1996. |
Jones, Duncan, The History of Pay Per Click (PPC) Marketing, Online Marketing Bog (www.duncanjonesnz.com) available at https://www.duncanjonesnz.com/history-of-ppc-marketing, Sep. 23, 2014. |
Moukheiber, Z., DoubleClick is watching you, Forbes Magazine, Nov. 4, 1996. |
Fielding, R. et al., Hypertext Transfer Protocol—HTTP/1.1, Network Working Group, RFC 2068, Jan. 1997. |
Glenn, A. and Millman, D., Access Management of Web-based Services, Ariel Glenn, D-Lib Magazine, Sep. 1998. |
Samar, V., Single Sign-on Using Cookies for Web Applications, IEEE 8th Intl. Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises, Jun. 16-18, 1999. |
Kiyomitsu, H., An E-Commerce Technology: Web Personlization on the Patron Web, Kobe University Economic Review 46 (2000). |
Warkentin, M. and Bapna, R., Intelligent Agent-Based Data Mining in Electronic Markets, AMCIS 2000 Proceedings (2000). |
Boncella, R., Internet Privacy—At Home and at Work, Communications of AIS, vol. 7, Article 14, Sep. 2001. |
New Engage ECHO Remarketing Solution Aimed at Decreasing Customer Acquisition Costs, Improving Customer Retention, BusinessWire, Sep. 25, 2000. |
Bilchev, G. and Marston, D., Personalized advertising—exploiting the distributed user profile, BT Technology Journal, vol. 21, No. 1, Jan. 2003. |
Pan, Y. and Zinkhan, G.M., Netvertising characteristics, challenges and opportunities: a research agenda, Int. J. Internet Marketing and Advertising, vol. 1, No. 3, 2004. |
Google Launches Self-Service Advertising Program, http://googlepress.blogspot.com/2000/10/google-launches-self-service.html, Oct. 23, 2000. |
Google Introduces New Pricing For Popular Self-Service Online Advertising Program, http://googlepress.blogspot.com/2002/02/google-introduces-new-pricing-for.html, Feb. 20, 2002. |
AdWords Separate Content Bidding, http://googlepress.blogspot.com/2005/11/adwords-separate-content-bidding_22.html, Nov. 22, 2005. |
WashingtonPost.Newsweek Interactive Selects Revenue Science Audience SearchTM for Behavioral Targeting Services, https://www.audiencescience.com/washingtonpost-newsweek-interactive-selects-revenue-science-audience-search-for-behavioral-targeting-services/, Sep. 20, 2004. |
Revenue Science Hosts Behavioral Targeting Workshop at Interactive Advertising World, https://www.audiencescience.com/revenue-science-hosts-behavioral-targeting-workshop-at-interactive-advertising-world/, Sep. 17, 2004. |
Online Advertising and Privacy Survey Shows Consumers Hold Strong Preference for Targeted Advertising, https://www.audiencescience.com/online-advertising-and-privacy-survey-shows-consumers-hold-strong-preference-for-targeted-advertising/, Sep. 9, 2004. |
Yahoo's Invalidity Contentions (pages related to parent patents in this family); AlmondNet, Inc. et al. v. Yahoo? Inc., Civil Action No. 16-cv-1557-ILG-SMG, U.S. District Court for the Eastern District of New York; Jun. 30, 2017. |
Exhibits C-1 through C-12 (as revised) of Yahoo's Invalidity Contentions cited above; Jun. 30, 2017 and Aug. 22, 2017. |
Number | Date | Country | |
---|---|---|---|
20190180324 A1 | Jun 2019 | US |
Number | Date | Country | |
---|---|---|---|
60805119 | Jun 2006 | US | |
60804937 | Jun 2006 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 15822974 | Nov 2017 | US |
Child | 16194203 | US | |
Parent | 15360762 | Nov 2016 | US |
Child | 15822974 | US | |
Parent | 14960237 | Dec 2015 | US |
Child | 15360762 | US | |
Parent | 14620502 | Feb 2015 | US |
Child | 14960237 | US | |
Parent | 14201494 | Mar 2014 | US |
Child | 14620502 | US | |
Parent | 13491454 | Jun 2012 | US |
Child | 14201494 | US | |
Parent | 12823709 | Jun 2010 | US |
Child | 13491454 | US | |
Parent | 11763286 | Jun 2007 | US |
Child | 12823709 | US |