Patent Application
20130024283
1. Field of the Invention
The present invention concerns serving advertisements (“ads”), such as serving ads in an online environment. In particular, the present invention concerns improving an ad configuration or finding the optimal ad configuration (e.g., the one expected to yield an increase in revenue or the maximum revenue) per document or document type.
2. Background Information
Advertising using traditional media, such as television, radio, newspapers and magazines, is well known. Unfortunately, even when armed with demographic studies and entirely reasonable assumptions about the typical audience of various media outlets, advertisers recognize that much of their ad budget is simply wasted. Moreover, it is very difficult to identify and eliminate such waste.
Recently, advertising over more interactive media has become popular. For example, as the number of people using the Internet has exploded, advertisers have come to appreciate media and services offered over the Internet as a potentially powerful way to advertise.
Interactive advertising provides opportunities for advertisers to target their ads to a receptive audience. That is, targeted ads are more likely to be useful to end users since the ads may be relevant to a need inferred from some user activity (e.g., relevant to a user's search query to a search engine, relevant to content in a document requested by the user, etc.) Query keyword relevant advertising, such as the AdWords advertising system by Google of Mountain View, Calif. (referred to as “Google”), has been used by search engines. Similarly, content-relevant advertising systems have been proposed. For example, U.S. patent application Ser. Nos. 10/314,427 (incorporated herein by reference and referred to as “the '427 application”) titled “METHODS AND APPARATUS FOR SERVING RELEVANT ADVERTISEMENTS”, filed on Dec. 6, 2002 and listing Jeffrey A. Dean, Georges R. Harik and Paul Buchheit as inventors; and 10/375,900 (incorporated by reference and referred to as “the '900 application”) titled “SERVING ADVERTISEMENTS BASED ON CONTENT,” filed on Feb. 26, 2003 and listing Darrell Anderson, Paul Buchheit, Alex Carobus, Claire Cui, Jeffrey A. Dean, Georges R. Harik, Deepak Jindal and Narayanan Shivakumar as inventors, describe methods and apparatus for serving ads relevant to the content of a document, such as a Web page for example. The AdSense advertising system by Google is an example of a content targeted ad delivery system used to serve ads on Web pages.
Current systems for serving targeted text ads may auction or arbitrate a given number of “spots” on a document (e.g., a Web page instance) to competing ads. Such spots typically specify a particular type of ad that may be served. For example, a search result Web page might have two (2) wide-format, text ad spots at the top of the Web page and eight (8) normal-format text ad spots in the right column of the Web page. There may be more than two (2) ads competing to be served in the two (2) wide-format text ad spots and more than eight (8) ads competing to be served in the eight (8) normal-format text ad spots. Ad serving facilities may arbitrate each ad spot to competing ads using an auction model. For example, competing ads can be placed in available ad spots using a bid price (associated with each ad) only. As another example, competing ads can be placed in available ad spots using some combination of an offer price, ad performance (e.g., in terms of selection rate, user ratings, conversion rate, etc.), and/or ad relevancy.
Regardless of the arbitration technique used, generally, all available ad spots are filled (to the extent that there are enough ads available to fill them). However, there may be some instances in which a policy of filling all available ad spots, if possible or to the greatest extent possible, might not be desirable from the standpoint of the end user, the Web page owner or publisher, and/or the ad serving facility. (See, e.g., U.S. patent application Ser. No. 11/169,323 (incorporated herein by reference and referred to as “the '323 application”) titled, “USING THE UTILITY OF CONFIGURATIONS IN AD SERVING DECISIONS,” filed on June 28, 2005, and listing Amit PATEL and Hal VARIAN, as the inventors; and U.S. patent application Ser. No. 11/396,300 (incorporated herein by reference and referred to as “the '300 application”), titled “DYNAMICALLY RESIZING OR OTHERWISE ALTERING AD CREATIVES AND/OR DETERMINING NUMBER OF ADS TO IMPROVE SCORE OF SET OF ONE OR MORE ADS AS AN AD UNIT,” filed on Mar. 31, 2006, and listing Jeff EDDINGS, Gokul Rajaram, and Scott Benson, as the inventors.)
Although the '323 and '300 applications describe techniques to optimize or at least improve ad configurations, the present inventors believe that an ad configuration that works well for one document or type of document, might not work well for another document or type of document. Thus, it would be useful to further improve ad serving decisions.
An ad configuration that works well (or best) for a given document or a given type of document is determined and/or used. For example, advertisements having different advertisement configurations may be served with different instances of a given document of a document type. Performance of the different advertisement configurations for at least one of the given document and document type may be tracked. A preferred advertisement configuration for at least one of the given document and document type may then be determined using the tracked performance of the different advertisement configurations. Finally, the determined preferred advertisement configuration may be associated with the at least one of a given document and document type.
Once such an association has been determined (or accepted), document information of a document to be provided with advertisements may be accepted, and a document type of the document may be determined using the document information. The preferred advertisement configuration associated with the determined document type may then be determined, and advertisements may be served with the document in accordance with the determined preferred ad configuration.
The present invention may involve novel methods, apparatus, message formats, and/or data structures for determining, and/or using, an ad configuration improved or optimized (e.g., yielding an increased or maximum revenue) per document, or per document type. The following description is presented to enable one skilled in the art to make and use the invention, and is provided in the context of particular applications and their requirements. Thus, the following description of embodiments consistent with the present invention provides illustration and description, but is not intended to be exhaustive or to limit the present invention to the precise form disclosed. Various modifications to the disclosed embodiments will be apparent to those skilled in the art, and the general principles set forth below may be applied to other embodiments and applications. For example, although a series of acts may be described with reference to a flow diagram, the order of acts may differ in other implementations when the performance of one act is not dependent on the completion of another act. Further, non-dependent acts may be performed in parallel. No element, act or instruction used in the description should be construed as critical or essential to the present invention unless explicitly described as such. Also, as used herein, the article “a” is intended to include one or more items. Where only one item is intended, the term “one” or similar language is used. Thus, the present invention is not intended to be limited to the embodiments shown and the inventors regard their invention as any patentable subject matter described.
In the following, definitions of terms that may be used in the specification are set forth in §4.1. Then, environments in which, or with which, embodiments consistent with the present invention may operate are described in §4.2. Then, exemplary embodiments consistent with the present invention are described in §4.3. Finally, some conclusions regarding the present invention are set forth in §4.4.
Online ads may have various intrinsic features. Such features may be specified by an application and/or an advertiser. These features are referred to as “ad features” below. For example, in the case of a text ad, ad features may include a title line, ad text, and an embedded link. In the case of an image ad, ad features may include images, executable code, and an embedded link. Depending on the type of online ad, ad features may include one or more of the following: text, a link, an audio file, a video file, an image file, executable code, embedded information, etc.
When an online ad is served, one or more parameters may be used to describe how, when, and/or where the ad was served. These parameters are referred to as “serving parameters” below. Serving parameters may include, for example, one or more of the following: features of (including information on) a document on which, or with which, the ad was served, a search query or search results associated with the serving of the ad, a characteristic of a user (e.g., their geographic location, the language used by the user, the type of browser used, previous page views, previous behavior, user account, any Web cookies used by the system, user device characteristics, etc.) to whom the ad was served, a host or affiliate site (e.g., America Online, Google, Yahoo) that initiated the request, an absolute position of the ad on the page on which it was served, a position (spatial or temporal) of the ad relative to other ads served, an absolute size of the ad, a size of the ad relative to other ads, a color of the ad, a number of other ads served, types of other ads served, time of day served, time of week served, time of year served, etc. Naturally, there are other serving parameters that may be used in the context of the present invention.
Although serving parameters may be extrinsic to ad features, they may be associated with an ad as serving conditions or constraints. When used as serving conditions or constraints, such serving parameters are referred to simply as “serving constraints” (or “targeting criteria”). For example, in some systems, an advertiser may be able to target the serving of its ad by specifying that it is only to be served on weekdays, no lower than a certain position, only to users in a certain location, etc. As another example, in some systems, an advertiser may specify that its ad is to be served only if a page or search query includes certain keywords or phrases. As yet another example, in some systems, an advertiser may specify that its ad is to be served only if a document, on which or with which the ad is to be served, includes certain topics or concepts, or falls under a particular cluster or clusters, or some other classification or classifications (e.g., product and/or service verticals). In some systems, an advertiser may specify that its ad is to be served only to (or is not to be served to) user devices having certain characteristics. Finally, in some systems, an ad might be targeted so that it is served in response to a request sourced from a particular location, or in response to a request concerning a particular location.
“Ad information” may include any combination of ad features, ad serving constraints, information derivable from ad features or ad serving constraints (referred to as “ad derived information”), and/or information related to the ad (referred to as “ad related information”), as well as an extension of such information (e.g., information derived from ad related information).
The ratio of the number of selections (e.g., click-throughs) of an ad to the number of impressions of the ad (i.e., the number of times an ad is rendered) is defined as the “selection rate” (or “click-through rate”) of the ad.
A “conversion” is said to occur when a user consummates a transaction related to a previously served ad. What constitutes a conversion may vary from case to case and can be determined in a variety of ways. For example, it may be the case that a conversion occurs when a user clicks on an ad, is referred to the advertiser's Web page, and consummates a purchase there before leaving that Web page. Alternatively, a conversion may be defined as a user being shown an ad, and making a purchase on the advertiser's Web page within a predetermined time (e.g., seven days). In yet another alternative, a conversion may be defined by an advertiser to be any measurable/observable user action such as, for example, downloading a white paper, navigating to at least a given depth of a Website, viewing at least a certain number of Web pages, spending at least a predetermined amount of time on a Website or Web page, registering on a Website, etc. Often, if user actions don't indicate a consummated purchase, they may indicate a sales lead, although user actions constituting a conversion are not limited to this. Indeed, many other definitions of what constitutes a conversion are possible.
The ratio of the number of conversions to the number of impressions of the ad (i.e., the number of times an ad is rendered), and the ratio of the number of conversions to the number of selections (or the number of some other event), are both referred to as the “conversion rate.” The type of conversion rate will be apparent from the context in which it is used. If a conversion is defined to be able to occur within a predetermined time since the serving of an ad, one possible definition of the conversion rate might only consider ads that have been served more than the predetermined time in the past.
A “property” is something on which ads can be presented. A property may include online content (e.g., a Website, an MP3 audio program, online games, etc.), offline content (e.g., a newspaper, a magazine, a theatrical production, a concert, a sports event, etc.), and/or offline objects (e.g., a billboard, a stadium score board, and outfield wall, the side of truck trailer, etc.). Properties with content (e.g., magazines, newspapers, Websites, email messages, etc.) may be referred to as “media properties.” Although properties may themselves be offline, pertinent information about a property (e.g., attribute(s), topic(s), concept(s), category(ies), keyword(s), relevancy information, type(s) of ads supported, etc.) may be available online. For example, an outdoor jazz music festival may have entered the topics “music” and “jazz”, the location of the concerts, the time of the concerts, artists scheduled to appear at the festival, and types of available ad spots (e.g., spots in a printed program, spots on a stage, spots on seat backs, audio announcements of sponsors, etc.).
A “document” is to be broadly interpreted to include any machine-readable and machine-storable work product. A document may be a file, a combination of files, one or more files with embedded links to other files, etc. The files may be of any type, such as text, audio, image, video, etc. Parts of a document to be rendered to an end user can be thought of as “content” of the document. A document may include “structured data” containing both content (words, pictures, etc.) and some indication of the meaning of that content (for example, e-mail fields and associated data, HTML tags and associated data, etc.) Ad spots in the document may be defined by embedded information or instructions. In the context of the Internet, a common document is a Web page. Web pages often include content and may include embedded information (such as meta information, hyperlinks, etc.) and/or embedded instructions (such as JavaScript, etc.). In many cases, a document has an addressable storage location and can therefore be uniquely identified by this addressable location. A universal resource locator (URL) is an address used to access information on the Internet.
A “Web document” includes any document published on the Web. Examples of Web documents include, for example, a Website or a Web page.
“Document information” may include any information included in the document, information derivable from information included in the document (referred to as “document derived information”), and/or information related to the document (referred to as “document related information”), as well as an extensions of such information (e.g., information derived from related information). An example of document derived information is a classification based on textual content of a document. Examples of document related information include document information from other documents with links to the instant document, as well as document information from other documents to which the instant document links.
Content from a document may be rendered on a “content rendering application or device”. Examples of content rendering applications include an Internet browser (e.g., Explorer, Netscape, Opera, Firefox, etc.), a media player (e.g., an MP3 player, a Realnetworks streaming audio file player, etc.), a viewer (e.g., an Abobe Acrobat pdf reader), etc.
A “content owner” is a person or entity that has some property right in the content of a media property (e.g., document). A content owner may be an author of the content. In addition, or alternatively, a content owner may have rights to reproduce the content, rights to prepare derivative works of the content, rights to display or perform the content publicly, and/or other proscribed rights in the content. Although a content server might be a content owner in the content of the documents it serves, this is not necessary. A “Web publisher” is an example of a content owner.
“User information” may include user behavior information and/or user profile information.
“E-mail information” may include any information included in an e-mail (also referred to as “internal e-mail information”), information derivable from information included in the e-mail and/or information related to the e-mail, as well as extensions of such information (e.g., information derived from related information). An example of information derived from e-mail information is information extracted or otherwise derived from search results returned in response to a search query composed of terms extracted from an e-mail subject line. Examples of information related to e-mail information include e-mail information about one or more other e-mails sent by the same sender of a given e-mail, or user information about an e-mail recipient. Information derived from or related to e-mail information may be referred to as “external e-mail information.”
An “ad area” may be used to describe an area (e.g., spatial and/or temporal) of a document reserved or made available to accommodate the rendering of ads. For example, Web pages often allocate a number of spots where ads can be rendered, referred to as “ad spots”. As another example, an audio program may allocate “ad time slots,” which may be thought of more generally as “ad spots.”
A combination of an ad's parameters (e.g., size, color, font, brightness, style, etc.), its spatial and/or temporal position, its frequency, etc. may be referred to as the ad's “treatment.” Thus, “treatment” can be used to described characteristics of the rendering (e.g., display) of an ad. The way in which ads with different treatments can be determined from common “seed” information is illustrated in an example described in §4.4 and
In the following, a “configuration” is defined to be a description of a set of ad participants (which may be served with a document). It is possible to generate different ad participants from common “seed” information. For example, creative text may be used as seed information to generate ads of different sizes, colors, fonts, brightnesses, etc. (which may be referred to as ad “parameters” or ad “formats”). Further, a given ad participant may be placed in different spatial and/or temporal positions (e.g., ad spots) in different configurations. Furthermore, a given ad participant may be placed with different frequencies in different configurations. Thus, a “configuration” may be used to describe a set of ads, and their associated treatments, to be placed on, or otherwise rendered in association with, a document. Note that the same set of ads may be described by different configurations if the ads have different treatments.
The ad server 120 may be similar to the one described in
As discussed in the '900 application, ads may be targeted to documents served by content servers. Thus, one example of an ad consumer 130 is a general content server 230 that receives requests for documents (e.g., articles, discussion threads, music, video, graphics, search results, Web page listings, etc.), and retrieves the requested document in response to, or otherwise services, the request. The content server may submit a request for ads to the ad server 120/210. Such an ad request may include a number of ads desired (or the number of available ad spots). The ad request may also include document request information. This information may include the document itself (e.g., a Web page), a category or topic corresponding to the content of the document or the document request (e.g., arts, business, computers, arts-movies, arts-music, etc.), part or all of the document request, content age, content type (e.g., text, graphics, video, audio, mixed media, etc.), geo-location information, document information, etc.
The content server 230 may combine the requested document with one or more of the advertisements provided by the ad server 120/210. This combined information including the document content and advertisement(s) is then forwarded towards the end user device 250 that requested the document, for presentation to the user. Finally, the content server 230 may transmit information about the ads and how, when, and/or where the ads are to be rendered (e.g., position, selection or not, impression time, impression date, size, conversion or not, etc.) back to the ad server 120/210. Alternatively, or in addition, such information may be provided back to the ad server 120/210 by some other means.
Another example of an ad consumer 130 is the search engine 220. A search engine 220 may receive queries for search results. In response, the search engine may retrieve relevant search results (e.g., from an index of Web pages). An exemplary search engine is described in the article S. Brin and L. Page, “The Anatomy of a Large-Scale Hypertextual Search Engine,” Seventh International World Wide Web Conference, Brisbane, Australia and in U.S. Pat. No. 6,285,999 (both incorporated herein by reference). Such search results may include, for example, lists of Web page titles, snippets of text extracted from those Web pages, and hypertext links to those Web pages, and may be grouped into a predetermined number of (e.g., ten) search results.
The search engine 220 may submit a request for ads to the ad server 120/210. The request may include a number of ads desired (or the number of available ad spots). This number may depend on the search results, the amount of screen or page space occupied by the search results, the size and shape of the ads, etc. In one embodiment, the number of desired ads will be from one to ten, and preferably from three to five. The request for ads may also include the query (as entered or parsed), information based on the query (such as geolocation information, whether the query came from an affiliate and an identifier of such an affiliate, and/or as described below, information related to, and/or derived from, the search query), and/or information associated with, or based on, the search results. Such information may include, for example, identifiers related to the search results (e.g., document identifiers or “docIDs”), scores related to the search results (e.g., information retrieval (“IR”) scores such as dot products of feature vectors corresponding to a query and a document, Page Rank scores, and/or combinations of IR scores and Page Rank scores), snippets of text extracted from identified documents (e.g., Web pages), full text of identified documents, topics of identified documents, feature vectors of identified documents, etc.
The search engine 220 may combine the search results with one or more of the advertisements provided by the ad server 120/210. This combined information including the search results and advertisement(s) is then forwarded towards the user that submitted the search, for presentation to the user. Preferably, the search results are maintained as distinct from the ads, so as not to confuse the user between paid advertisements and presumably neutral search results.
Finally, the search engine 220 may transmit information about the ad and when, where, and/or how the ad was to be rendered (e.g., position, click-through or not, impression time, impression date, size, conversion or not, etc.) back to the ad server 120/210. Such information may include information for determining on what basis the ad was determined to be relevant (e.g., strict or relaxed match, or exact, phrase, or broad match, etc.). Alternatively, or in addition, such information may be provided back to the ad server 120/210 by some other means.
Finally, the e-mail server 240 may be thought of, generally, as a content server in which a document served is simply an e-mail. Further, e-mail applications (such as Microsoft Outlook for example) may be used to send and/or receive e-mail. Therefore, an e-mail server 240 or application may be thought of as an ad consumer 130. Thus, e-mails may be thought of as documents, and targeted ads may be served in association with such documents. For example, one or more ads may be served in, under, over, or otherwise in association with an e-mail.
Although the foregoing examples described servers as (i) requesting ads, and (ii) combining them with content, one or both of these operations may be performed by a client device (such as an end user computer for example).
Embodiments consistent with the present invention may be used to determine and/or use an improved (e.g., optimum) ad configuration for serving with a given document or document type. (Note, however, that the types and numbers of ads that may be served with a document may be determined in a number of different ways, and need not be determined solely by the document, or solely by the document type.)
The pages may be Web pages, collections of Web pages (e.g., a Website), or some other document(s).
In some embodiments consistent with the present invention, one or more of the operations introduced above might be “components” of a system or apparatus. For example, one or more of the operations introduced above might be modules of computer-executable instructions, and an exemplary system or apparatus consistent with the present invention might include storage device(s) to store the modules of computer-executable instructions, and/or input means to receive the modules of computer-executable instructions. Alternatively, at least some of the components might be implemented as hardware or firmware.
The per page experimental serving operations 320 may be used to help learn how different ad configurations and/or types of ad configurations perform on different documents and/or types of documents. Thus, when ads 315 are to be served on pages 310, the operations 320 can be used to vary ad configurations for a given page or type of page, using the experimental state information 310. Page information 310 may include the genre of the content on the page (e.g., news site, blog, forum, etc.), the placement of the various ad blocks (e.g., above the fold, below the fold, left margin, right margin, top margin, etc.), the dominant font type of the page, the background color or background image of the page, the dominant font color of the page, the dominant font size of the page, number of images or total pixel count of images on the page, the location of other elements in the page (e.g., main navigation, the main content, etc.), the technology used on the page (e.g., javascript, Macromedia flash, video, etc).
The tracking/logging operations 330 may generate page or page type serve and user-ad interaction log information 335. For example,
Referring back to
The per page or page type preferred ad configuration determination operations 350 may generate per page or page type preferred ad configuration information 355. For example,
The operations and information above the dashed line 399 may be thought of as a “predictive engine” that and analyzes performance information for various {page, ad configuration), and/or {page type, ad configuration) pairs to determine which ad configuration is expected to work best for a given page or page type. To summarize, multiple different formatting options (i.e., different ad configurations) may be used for a given ad block for various impressions of a given page or page type. The performances of the different ad configurations are determined. Thus, the system might try out various combinations of formatting options (i.e., different ad configurations) to determine what the best (e.g., best performing) ad configuration should be for a given page or a given page type. This data may also be fed back into the “predictive engine” system in order to supply more data for future decision making on new pages. Ad configurations might be defined by values or value ranges for one or more of number of ads, type of ads (image, text, links, multimedia, etc.), size of ad block, background color of ads, background image of the ads, text size of ads, text color of ads, font type of ads, border width of ads or ad block, border color of ads or ad block, video, animation or audio segments for the advertisement, length (e.g., amount of text or time of display) or size of ad creative, whether or not the ad(s) include maps, whether or not the ad(s) includes an accompanying image(s), whether or not the ad(s) includes dynamic functionality (e.g., roll-over text, video, audio or images), whether or not the ad(s) includes interaction with other aspects of the ad block (e.g., clicking links in one part of the ad block resulting in new ads in a different part of the ad block), whether or not the ad(s) includes text decoration, text underlining, bold text, italics, spacing, etc., etc.
Thus, in
Referring back to block 410, experimental state information 305 might be used to ensure that different ad configurations are tried for a given page or page type during an experiment. For example, if only one ad configuration was used for a page type during an experiment, the system would not be able to discover whether such an ad configuration is better or worse, for the page type, than untried ad configurations.
Referring back to 420, the tracked performance might be selection rates, conversion rates, etc. (Recall, e.g.,
Referring back to block 430 the preferred ad configuration for a page or page type might be the one with the best performance (e.g., in terms of selection rate, click-through rate, revenue amount (e.g., a collective, per page impression, ad revenue amount), etc.), or the best performance score.
Finally, referring back to block 440, the preferred configuration might be stored in association with a page and/or a page type. (Recall, e.g., exemplary data structure 700 of
The method 400 may be used to perform the operations 320, 330, 340 and 350 of
Referring back to block 820, a document type might be derived from features of an input document using known and/or proprietary classification techniques. Document types might include news, blogs, forum, user rating, entertainment, search results, video search results, image search results, audio search results, e-mail search results, universal search results, gaming, social network, commerce and online encyclopedia (e.g., a WIKI), etc.
Still referring to block 820, the preferred ad configuration might be looked up in a table (Recall, e.g., data structure 700 of
Referring back to block 920, a document type might be derived from features of an input document using known and/or proprietary classification techniques. Document types might include, for example, news, blogs, forum, user rating, entertainment, search results, video search results, image search results, audio search results, e-mail search results, universal search results, gaming, social network, commerce and online encyclopedia (e.g., a WIKI), etc. A document type might be defined by an attribute value, and/or by a collection of attribute values.
Referring back to block 930, a document type might be derived from features of an input document using known and/or proprietary classification techniques. Document types might include news, blogs, forum, user rating, entertainment, search results, video search results, image search results, audio search results, e-mail search results, universal search results, gaming, social network, commerce and online encyclopedia (e.g., a WIKI), etc. A document type might be defined by an attribute value, and/or by a collection of attribute values.
The one or more processors 1010 may execute machine-executable instructions (e.g., C, C++, Java, JavaScript, AJAX, or other programming or scripting languages running on the Solaris operating system available from Sun Microsystems Inc. of Palo Alto, Calif. or the Linux operating system widely available from a number of vendors such as Red Hat, Inc. of Durham, N.C.) to effect one or more aspects of the present invention. At least a portion of the machine executable instructions may be stored (temporarily or more permanently) on the one or more storage devices 1020 and/or may be received from an external source via one or more input interface units 1030.
In one embodiment, the machine 1000 may be one or more conventional personal computers. In this case, the processing units 1010 may be one or more microprocessors. The bus 1040 may include a system bus. The storage devices 1020 may include system memory, such as read only memory (ROM) and/or random access memory (RAM). The storage devices 1020 may also include a hard disk drive for reading from and writing to a hard disk, a magnetic disk drive for reading from or writing to a (e.g., removable) magnetic disk, and an optical disk drive for reading from or writing to a removable (magneto-) optical disk such as a compact disk or other (magneto-) optical media.
A user may enter commands and information into the personal computer through input devices 1032, such as a keyboard and pointing device (e.g., a mouse) for example. Other input devices such as a microphone, a joystick, a game pad, a satellite dish, a scanner, or the like, may also (or alternatively) be included. These and other input devices are often connected to the processing unit(s) 1010 through an appropriate interface 1030 coupled to the system bus 1040. The output devices 1034 may include a monitor or other type of display device, which may also be connected to the system bus 1040 via an appropriate interface. In addition to (or instead of) the monitor, the personal computer may include other (peripheral) output devices (not shown), such as speakers and printers for example.
The various operations described above may be performed by one or more machines 1000, and the various information described above may be stored on one or more machines 1000. The ad server 210, search engine 220, content server 230, e-mail server 240, and/or user device 250 may include one or more machines 1000.
Some embodiments consistent with the present invention might help the publisher of a Webpage to give the system more room to experiment with size of an ad block. Traditionally the publisher would specify the exact width and height of an ad block that they would like placed on their Webpage. Some embodiments consistent with the present invention might allow a publisher (e.g., a Webpage publisher) to specify maximum widths and heights by pixel count, by percentage of page, and/or by percentage of an html object such as a table row or column. Such embodiments might then test configurations of an ad block that use only the space that it needs to achieve the highest performance (e.g., estimated revenue per impression(s)). If the best configuration has unused space, such unused space might be “returned” to the publisher to be used on their page at its discretion.
As an alternative to the method 900 of
As can be appreciated from the foregoing, embodiments consistent with the present invention can be used to further improve ad serving decisions. In particular, at least some embodiments consistent with the present invention can determine and/or use an ad configuration that works well (or best) for a given document or a given type of document.
The present application is a continuation-in-part of U.S. patent application Ser. No. 10/895,026 filed Jul. 20, 2004.
| Number | Date | Country | |
|---|---|---|---|
| Parent | 10895026 | Jul 2004 | US |
| Child | 11823924 | US |
