The present invention relates to computer-implemented processes for identifying the terms and/or phrases most suitable for serving contextually relevant content. The invention also relates to processes for serving contextually relevant content for display within web pages or other types of documents.
A variety of systems exist for selecting content, such as advertisements, to present on web pages based on the content of such web pages. These systems often fail to select content that is relevant to, or suitable for display on, the particular page at issue. For example, an ad for a particular product or company may be selected to display on a web page containing an article that is critical of that product or company. As another example, an ad for a particular product may be displayed on a page containing an article about a completely unrelated topic merely because the product is briefly mentioned in the article. Existing systems also frequently display the selected ad in a manner that is distracting to users. These and other issues contribute to a low industry-wide click through rate of less than 1%.
A process is described for assessing the suitability of particular keyword phrases for use in serving contextually relevant content for display on pages of network-accessible sites. In one embodiment, the process involves scoring the key phrases based in part on collected user behavioral data, such as view counts of associated social media content items. A process is also disclosed in which selected keyword phrases on a page are transformed into links that can be selected by a user to view bundled content that is related to such keyword phrases.
A system that embodies various inventive features will now be described with reference to the drawings. Nothing in this description is intended to imply that any particular feature, characteristic, or component of the system or its use is essential to the invention.
I. Overview
As illustrated, the Intextual system 30 (hereinafter “the system”) includes a bundle server 40 that serves bundled content for display within, or in conjunction with, web pages 42 of the publisher sites 34. The bundled content is preferably displayed in association with specific key phrases that appear in pages of the publisher sites 34. (As used herein, a “key phrase” can be either a single term or a sequence of two or more terms.) As described below, the system 30 uses a novel process to select the key phrases that are likely to be the most effective for particular ads, advertisers and publishers. This process involves analyzing social media content obtained from one or more social media sites 38 to assess the popularity levels of particular key phrases.
As depicted in
The videos and photos are preferably obtained from social media sites 38 such as YouTube™, Flickr™ and Myspace™, and may be obtained via interfaces to these sites or by using a crawling/scraping process. If the user clicks on a thumbnail of a video, the panel 44 expands on the screen (expanded views not shown), loads the corresponding web page from the associated social media site, and begins to play the video as displayed on that page. If the user clicks on a thumbnail image of a photo, the panel 44 expands and loads the corresponding photo page of the associated social media web site. If the user clicks on an ad, the panel expands and loads the corresponding landing page of the advertiser's web site. (As discussed below, the system tracks, and charges the corresponding advertisers for, such ad selection events.) In each of these scenarios, the user can click on additional links within the panel 44 to navigate to other content (e.g., to other videos or photos of a social media site, or to other content of the advertiser site). If the user clicks on one of the links at the bottom of the panel.
Thus, the panel 44 acts as a portal or mini browser that enables the user to access social and sponsored content without navigating away from the publisher's web page 42. Because the key phrases are selected so as to correspond to current popular topics, the sponsored and social content displayed within the panel 44 tends to be highly useful and relevant to users.
As depicted in
As shown in
As illustrated in
The indexing engine 52 is preferably invoked in two primary scenarios. The first is when an advertiser creates an ad for display on a particular publisher web site 34 or a group of publisher sites. In this scenario, the indexing engine 52 is used to select and rank key phrases to suggest to the advertiser. The second scenario is when an end user/browser 36 loads a panel-enabled page 42 of a publisher site 34. In this scenario, if the page 42 has not recently been analyzed by the indexing engine 52, the indexing engine retrieves and analyzes the web page 42 to identify key phrases to transform into links. Both of these scenarios are described below.
The various components of the system 30 may be implemented as executable code (software) executed by one or more general purpose computers. The components may reside at a common location, or may be distributed geographically. The software code and associated data may be stored in any type or types of computer data repository (e.g., relational databases, flat files, hard disk storage, RAM, etc.). The browsers 36 may be any conventional web browser capable of executing JavaScript. The various communications depicted in
II. Operation of Indexing Engine
In block 1, the indexing engine 52 receives a URL for which to identify relevant key phrases. If the indexing process is triggered by advertiser generation of an ad, this URL is typically the advertiser-specified landing page URL of the ad. If the process is triggered by a user loading a panel-enabled web page 42 of a publisher site 34, the URL is the URL of this panel-enabled web page. For ease of description, the URL received in block 1 will be referred to as the “target URL,” and the corresponding web page will be referred to as the “target page.”
In blocks 2-4, the indexing engine 52 retrieves and parses the target page (block 2) to extract a set of key phrases (block 3) and a set of outbound link URLs (block 4). The key phrases are extracted in one embodiment by stripping out HTML tags, and by using one or more language files to remove stop words. As depicted by block 5, the indexing engine 52 also accesses an external service/database, such as a web service provided by Alexa Internet, to identify inbound link URLs (i.e., URLs of web pages that point to the target page and are not part of the target page's Internet domain). The inbound and outbound URLs form a “peer group” for the target URL. As mentioned below, in scenarios in which the advertiser is creating an ad campaign, the peer group may also include some or all of the web pages of the advertiser's target site 32 (i.e., the site that includes the landing page for the ad campaign).
As depicted by block 6, the indexing engine 52 retrieves and scans the content of the identified inbound and outbound URLs (and possibly additional pages of the peer group) to determine phrase frequency of the extracted phrases within the peer group. Key phrases having relatively high frequencies of occurrence across the peer group tend to best characterize the target page, and thus tend to be more useful than less-frequently-occurring key phrases for serving context-relevant content.
Various other methods may be used to form the peer group. For example, web usage trails of users may be analyzed in aggregate to identify other web pages that are behaviorally related to (e.g., commonly accessed during the same browsing session as) the target web page; these behaviorally related pages may then be used as, or used to supplement, the peer group.
As depicted by block 7 of
The popularity levels of the key phrases may additionally or alternatively be assessed using other sources of information. For example, the key phrase popularity levels can be assessed by analyzing search query logs of an Internet search engine, a social media site, and/or a news site. As another example, a service such as Google™ Trends may be used to assess key phrase popularity trends, so that key phrases rapidly gaining in popularity can be given more weight.
In addition, some social media sites 38 include publicly accessible APIs that provide access to usage statistics regarding the frequencies with which particular key phrases are used to tag, or are used to search for, particular photos, videos or other content items on a social media site. YouTube.com is one example of a social media site that provides such an API. These APIs may be used as an additional or alternative source of information for assessing the key phrase popularity levels in block 7.
For example, each key phrase may be scored or assessed based (or based in-part) on its acceleration (i.e., the rate at which it is gaining in popularity) in social media sites, or based on another popularity metric, as determined via a mathematical scoring model that examines user activity over time. One example of such a model is depicted in
In block 8, each extracted key phrase is scored by combining its peer frequency with its social media frequency/popularity. An appropriate weighting method may optionally be used to give more weight to one type of content (peer versus social) than the other. Various other criteria may also be incorporated into the scores. For example, key phrases that appear relatively infrequently across the entire web (or some other reference document collection) may be scored more highly on the basis that they better distinguish the peer group from the web or reference document collection as a whole. As another example, relatively popular web pages in the peer group, and/or relatively popular social content items, may be weighted more heavily in measuring key phrase frequency.
The output of the indexing engine 52 is a set of name/value pairs representing the extracted key phrases and their respective scores. These name/value pairs are stored in a database 60 of the system in association with the target URL. The most highly scored key phrases tend to be relatively popular key phrases that characterize the target site or page, and which are the most useful for selecting contextually relevant content.
If the target URL is a landing page of an advertisement, the extracted key phrases with the highest scores are suggested to the advertiser as part of a “campaign cloud” (see
As mentioned above, in ad generation scenarios in which the advertiser designates a particular publisher site 34, the process shown in
As will be recognized, the PLP process described above can be used in a wide range of applications, including applications that do not involve the display of bundled content, and including applications in which the key phrases on the publisher page are not converted into special links. The present invention encompasses such applications. As one example, the PLP process can be used in Google™ AdSense™ type applications in which ads are displayed in a designated area of the publisher web page.
III. Advertiser Use (
The process by which an advertiser interacts with the system to create an ad campaign will now be described with reference to
In event B, the indexing engine is invoked to generate a set of key phrases and associated scores for the designated landing page. This may be accomplished using the process shown in
In event D, a web page depicting a resulting “campaign cloud” is generated and displayed to the advertiser. An example of such a display is shown in
While viewing the campaign cloud, the advertiser can “mouse over” a key phrase to view its estimated average CPC and average CPM. These values are preferably calculated based on the publisher's minimum CPC and CPM values, and based further on the key phrase scores. CPM and CPC rates are calculated by simplifying the phrase scores to a scale of 1-10 and multiplying the base cost set by the publisher by the score. For example, a publisher specifying a base CPM of $0.50 will equate to a $5.00 CPM for the most popular phrases in its peer group. Market trend data, publisher traffic statistics and category information may be factored into the CPM value as well. Phrases entered by the advertiser will be added to the cloud with their corresponding scores on the publisher site. If no score exists or the phrase does not exist on the publisher site, the phrase is assigned the publisher's minimum cost.
Upon proceeding from the campaign cloud page (event E in
The above-described process by which the advertiser interacts with the system to create an ad campaign is summarized in
IV. Browser Loading of Panel-Enabled Page (
If the page is not indexed, the system invokes the indexing engine 52, which generates a dataset of key phrases and associated scores. This dataset is stored in a database 60 (event 102b) in association with the URL of the panel-enabled page, and is maintained therein for a selected period of time (e.g., 1 day or 1 week). Once the indexing is completed in this scenario, the process ends (i.e., no panel is generated).
Returning to the scenario in which the page is already indexed, if a user clicks on one of the special links/key phrases 66 (one shown in
The JavaScript displays the panel on an independent graphic layer of the web page 42, and loads the panel 44 with the bundle content associated with the key phrase selected by the user. If the user thereafter selects a different key phrase/special link on the page, the panel is reloaded with the bundle content associated with that key phrase. The JavaScript may also be configured to draw ads and related content within other ad units.
The foregoing description of specific embodiments does not limit the invention in any way. Other embodiments and applications that are apparent to those of ordinary skill in the art, including embodiments that do not provide all of the features and advantages set forth herein, are also within the scope of this invention. The scope of the present invention is intended to be defined only by reference to the following claims. Applicants also reserve the right to pursue additional claims that are supported by the present disclosure, including claims of broader scope.
This application is a continuation of U.S. application Ser. No. 14/546,744, filed Nov. 18, 2014, now U.S. Pat. No. 9,418,374, which is a continuation of U.S. application Ser. No. 13/478,002, filed May 22, 2012, now U.S. Pat. No. 8,909,639, which is a continuation of U.S. application Ser. No. 13/174,296, filed Jun. 30, 2011, now U.S. Pat. No. 8,209,333, which is a continuation of U.S. application Ser. No. 12/016,887, filed Jan. 18, 2008, now U.S. Pat. No. 8,073,850, which claims the benefit of U.S. Provisional Appl. No. 60/885,853, filed Jan. 19, 2007. The disclosures of the aforesaid applications are hereby incorporated by reference in their entirety.
Number | Name | Date | Kind |
---|---|---|---|
5708825 | Sotomayor | Jan 1998 | A |
6421675 | Ryan et al. | Jul 2002 | B1 |
6563514 | Samar | May 2003 | B1 |
6691108 | Li | Feb 2004 | B2 |
6920448 | Kincaid | Jul 2005 | B2 |
7428522 | Raghunathan | Sep 2008 | B1 |
7752534 | Blanchard, III | Jul 2010 | B2 |
7975019 | Green et al. | Jul 2011 | B1 |
7975020 | Green | Jul 2011 | B1 |
8073850 | Hubbard et al. | Dec 2011 | B1 |
8135617 | Agostino et al. | Mar 2012 | B1 |
8209333 | Hubbard et al. | Jun 2012 | B2 |
8909639 | Hubbard et al. | Dec 2014 | B2 |
9418374 | Hubbard et al. | Aug 2016 | B2 |
20020016786 | Pitkow et al. | Feb 2002 | A1 |
20020059574 | Tudor | May 2002 | A1 |
20020120505 | Henkin et al. | Aug 2002 | A1 |
20030120662 | Vishik | Jun 2003 | A1 |
20040141016 | Fukatsu et al. | Jul 2004 | A1 |
20040181525 | Itzhak et al. | Sep 2004 | A1 |
20050004909 | Stevenson et al. | Jan 2005 | A1 |
20050137939 | Calabria et al. | Jun 2005 | A1 |
20050165753 | Chen et al. | Jul 2005 | A1 |
20050222901 | Agarwal | Oct 2005 | A1 |
20060020523 | Song | Jan 2006 | A1 |
20060053095 | Koch et al. | Mar 2006 | A1 |
20070073756 | Manhas | Mar 2007 | A1 |
20070143176 | Nong et al. | Jun 2007 | A1 |
20070244866 | Mishkanian et al. | Oct 2007 | A1 |
20080154847 | Chellapilla et al. | Jun 2008 | A1 |
20080172615 | Igelman | Jul 2008 | A1 |
20110258204 | Hubbard et al. | Oct 2011 | A1 |
20120290407 | Hubbard et al. | Nov 2012 | A1 |
20150066664 | Hubbard et al. | Mar 2015 | A1 |
Entry |
---|
New York Times article titled, “How to Use Google Trends,” by David Leonhardt, dated Jul. 5, 2006, printed from nytimes.com web site at http://nytimes.com/2006/07/05/business/051leonhardt-aboutgoogtrends.html, 2 pp. |
Listing of Related Cases, Schwabe Williamson & Wyatt, dated Jun. 12, 2018 (1 page). |
Number | Date | Country | |
---|---|---|---|
20160335665 A1 | Nov 2016 | US |
Number | Date | Country | |
---|---|---|---|
60885853 | Jan 2007 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14546744 | Nov 2014 | US |
Child | 15219010 | US | |
Parent | 13478002 | May 2012 | US |
Child | 14546744 | US | |
Parent | 13174296 | Jun 2011 | US |
Child | 13478002 | US | |
Parent | 12016887 | Jan 2008 | US |
Child | 13174296 | US |