Subscribing to web site syndication feeds is a popular mechanism for users to receive information about web pages in an efficient manner. In general, syndication data for a web page is data that represents the content of the web page and may even be identical in content to the content of the web page, but is not itself the content of the web page. The syndication data is available to syndication-aware programs that subscribe to a “feed” of the syndication data. The syndication data is typically designed to be machine-readable for efficient processing (e.g., into human-readable form). For example, the syndication data is typically XML-based or otherwise structured to ensure or enhance the machine-readability.
A typical use of syndication data is by subscription via a syndication feed aggregation service, which combines the contents of multiple syndication feeds for display on a single screen or series of screens. Examples of syndication data include data formatted according to standards such as past, current and to-be promulgated versions of RSS and Atom. While RSS and Atom are popular syndication data formatting standards, there are (and, in high probability, will be) other standards for syndication data formatting.
The syndication feed content for a data item typically includes a human-readable description of the data item, where the human-readable description is “clickable” to the web page URL so that the user can easily view the corresponding underlying web page content. In addition, many aggregation programs are configured to display advertising in conjunction with the display of syndication feed content. Thus, for example, the syndication feed aggregation service provider may earn money each time a user clicks on an advertisement.
In accordance with one aspect, the invention may include a method to provide syndication data feed items to a user program. The syndication data feed items correspond to hosted content. For each of a plurality of syndication data feed items, a resource locator to hosted content to which that syndication data feed item corresponds is processed. The processing includes adjusting the resource locator to associate the resource locator with an intervention service with regard to the syndication data feed item. The processed syndication data feed items are provided to the user program.
In accordance with another aspect, the invention may include a method to process requests to view hosted content corresponding to syndication data feed items. An intervention service receives a request from a user program to view hosted content to which a syndication data feed item corresponds. The request includes a resource locator to the host that has been adjusted in the syndication data feed item to associate the resource locator with an intervention service with regard to the syndication data feed item. The intervention service performs intervention processing with respect to the syndication data feed item of the request and causes interaction with the host of the requested content such that the host content is caused to be displayed at a user location.
The inventors have realized that is desirable to observe and/or act upon a user activating a syndication feed data item. For example, a feed aggregator program may be able to monetize these activations or otherwise improve user experience relative to use of the feed aggregator (which can indirectly result in improved revenue, e.g., by attracting more users to the feed aggregator, which can result in higher advertising revenue) or even relative to other services provided by or otherwise associated or affiliated with the feed aggregator.
In accordance with an example, the aggregation service adjusts the locator (typically, a universal resource locator, or URL) of a syndication data feed item subscribed to by, and presented to, a user. When the syndication data feed item is activated by the user, an intervention service is notified of the activation as a result of the locator being adjusted. In this way, the intervention service can take an intervention action in association with the activation. The intervention service is configured such that a desired action can be taken in conjunction with causing the hosted content corresponding to the syndication data feed item to be provided to the user.
The host web site 102 has associated with it an RSS module 108 (which, more generically, includes functionality to cause a syndication data feed to be provided). The RSS module 108 operates to cause an RSS feed 110 to be provided to an RSS aggregation service 114. In particular, the RSS feed 110 comprises a structured representation of the web site content 104, including locators 112 (in
The RSS aggregation service 114 (or, in some examples, functionality associated with the RSS aggregation service, which may be a separate service) is configured to rewrite the locators 112 to include location information of an intervention service 116 which may be, for example, closely associated with the RSS aggregation service 114. The rewritten locators 118 are provided via an RSS module 120 output of the aggregation service 114 to the feed reader program 106 and, for example, indications of the RSS feeds are caused to be displayed by the feed reader program 106. For example, the aggregation service 114 may be part of a service known as MyYahoo®, which can provide a user-configurable web page including information corresponding to RSS feeds subscribed to by the MyYahoo® user.
In accordance with some examples, in addition to or instead of adjusting the locators of the RSS syndication feed items, the aggregation service adjusts the syndication data feed items to include one or more beacons, such that user behavior relative to viewing the syndication data feed item may be monitored using, for example, a feed reader program.
While the discussion herein is in terms of “programs,” it is noted that, in some examples, the described functionality may be accomplished by hardware, software, or some combination of both. The programs may be carried out by at least one computing device executing computer program instructions that are stored in at least one computer readable medium.
The user, using the feed reader program 106 to view the display including the indication of the RSS feeds, may activate one or more of the RSS feed item indications to cause a request 122 corresponding to the RSS feed item to be provided from the feed reader program 106. More particularly, the request is provided to a location indicated by a locator received by feed reader program 106 in association with the activated RSS feed item indication. As discussed earlier, the locator has been adjusted to point to the intervention service 116. In general, the adjusting is such that the original information in the locator is preserved.
For example, the URL http://somewhere.com/story23.htm may be adjusted to http://intervention.com?=http://somewhere.com/story23.htm. The use of the “?=” is a one way to provide a parameter to the location indicated by the URL. That is, in the example, the URL is http://intervention.com (the location of the intervention service 116) and the parameter provided to the intervention service 116 is http://somewhere.com/story23.htm.
There are many other ways to provide the parameter. Furthermore, the parameter may even have been encoded by the RSS aggregation service 114 such that, for example, the encoded parameter is not readable by a user of the RSS feed program. In this case, the parameter would be decoded at the intervention service 116.
Continuing on with the
In addition, the intervention service 116 may be configured to provide and/or cause intervention operations associated with the request for the content associated with the RSS feed. Operations may include, for example, tracking requests to view hosted content based on syndication data feed items (and, e.g., correlating the activations with characteristics of the users causing the requests to be made). Such tracking may provide useful information for targeted marketing, for example.
In general, the intervention operations may depend on or be a function of the identity of the requesting user and/or characteristics associated with the requesting user. The identity of the requesting user may be available to the intervention operations via a cookie or some other means. Knowing the identity of the requesting user, it may be possible to identify characteristics associated with the requesting user.
Another example of intervention operations may include causing additional information, other than the requested content associated with a syndication data feed item, to be displayed to the user.
In some examples, advertising or other material (e.g., relevant to the requested content) may be caused to be displayed to the user. For example, such material may be caused to be displayed based on characteristics of the user and/or characteristics of the activated syndication data item. With respect to characteristics of the activated syndication data item, in some examples, as the syndication data item passes through the RSS aggregation service 114 from the RSS feed 110 to the RSS 120 module output, RSS data items are analyzed and the results of the analysis are saved in association with an indication of the syndication data item (e.g., in association with an indication of the original URL or other locator associated with the syndication data item).
When a request is made for web site content corresponding to a syndicated data item, the aggregation service 114 can access the saved analysis and correlate the analysis results to the request. In this manner, advertisements or other material can be displayed in conjunction with the requested content based on the results of the previously carried out analysis. See, for example, U.S. patent Ser. No. 11/550,307, entitled SUPPLEMENTAL DISPLAY MATCHING USING SYNDICATION INFORMATION, filed Oct. 17, 2006 and incorporated herein by reference for all purposes, for a discussion of processing syndication data to determine supplemental content, such as advertising, to be displayed in association with the content of a web site corresponding to the syndication data.
In some examples, the analysis used to correlate the RSS data item, for which content is requested, with material to be displayed in conjunction with the requested content is carried out at the time the content is requested. For example, the request (such as 122 in
As another example, the information provided as part of the URL may be an encoded version of the full content URL of the feed item that may then be decoded by the intervention service 114. For example, data may be maintained such as a table, usable by the intervention service to correlate the encoded version of the locator, to the hosted content, to the actual locator to the hosted content. As another example, all of the information to determine the actual locator to the hosted content may be present in the encoded version of the locator, obtainable by directly applying an appropriate decoding algorithm.
In fact, examples of processing of the intervention service being dynamically determined with respect to a particular activated RSS data item is not limited to correlating the RSS data item, for which content is requested, with material to be displayed. More generally, the intervention processing with respect to a particular RSS data item (or, more generally, to RSS data items having particular characteristics) may be dynamically determined by the intervention service 116. For example, the database of the intervention service 114 may include an indication of historical activity with respect to the particular activated RSS feed item, and the intervention processing may be determined based on the historical activity (e.g., an advertisement or other additional content to be displayed in conjunction with the feed-associated content may be determined based on the historical activity).
The
In addition, an interface may be provided via which a moderator may create or otherwise cause metadata to be associated with a syndication feed item. For example, the moderator user interface may provide facility for the moderator to provide comments to be associated with a syndication feed item, or the moderator user interface may provide facility for the moderator to cause metadata not directly created by the moderator via the moderator user interface to be associated with a syndication data feed item. For example, the moderator user interface may provide facility for the moderator user to cause metadata from the del.icio.us “social bookmarking” site to be associated with a syndication data item.
Co-pending patent application Ser. No. 11/611,668, entitled MODERATED SYNDICATION DATA FEED, and filed concurrently herewith, provides details of adjusting feed items and operation of an intervention service. Co-pending patent application Ser. No. 11/611,668 is incorporated herein by reference in its entirety for all purposes.
Furthermore, upon activation of a feed item that results in a request for the content associated with the feed item, in addition, an indication of metadata associated with the syndication data feed item (such as metadata provided by the moderator or caused by the moderator to be associated with the syndication data feed item) may be caused by intervention processing to be displayed in conjunction with the feed-associated content.
We have described a method and system to perform intervention operations to observe and/or act upon a user activating a syndication feed data item. The intervention operations may be such as to monetize these activations or otherwise improve user experience.
Number | Name | Date | Kind |
---|---|---|---|
20030191816 | Landress et al. | Oct 2003 | A1 |
20050033657 | Herrington et al. | Feb 2005 | A1 |
20050114198 | Koningstein et al. | May 2005 | A1 |
20050144305 | Fegan et al. | Jun 2005 | A1 |
20050165615 | Minar | Jul 2005 | A1 |
20050216516 | Calistri-Yeh et al. | Sep 2005 | A1 |
20050267973 | Carlson et al. | Dec 2005 | A1 |
20050289147 | Kahn et al. | Dec 2005 | A1 |
20060026067 | Nicholas et al. | Feb 2006 | A1 |
20060085259 | Nicholas et al. | Apr 2006 | A1 |
20060095507 | Watson | May 2006 | A1 |
20060167749 | Pitkow et al. | Jul 2006 | A1 |
20060173985 | Moore | Aug 2006 | A1 |
20060206584 | Hyder et al. | Sep 2006 | A1 |
20060242663 | Gogerty | Oct 2006 | A1 |
20060282312 | Carlson et al. | Dec 2006 | A1 |
20070038643 | Epstein | Feb 2007 | A1 |
20070055748 | Kim et al. | Mar 2007 | A1 |
20070061311 | Kurose | Mar 2007 | A1 |
20070078714 | Ott et al. | Apr 2007 | A1 |
20070083468 | Wetherell | Apr 2007 | A1 |
20070083894 | Gonsalves et al. | Apr 2007 | A1 |
20070094082 | Yruski et al. | Apr 2007 | A1 |
20070094083 | Yruski et al. | Apr 2007 | A1 |
20070094391 | Nussey | Apr 2007 | A1 |
20070150343 | Kannapell et al. | Jun 2007 | A1 |
20070174255 | Sravanapudi et al. | Jul 2007 | A1 |
20070174340 | Gross | Jul 2007 | A1 |
20070299935 | Plastina et al. | Dec 2007 | A1 |
20080065737 | Burke et al. | Mar 2008 | A1 |
20080091521 | Ho et al. | Apr 2008 | A1 |
20080244091 | Moore et al. | Oct 2008 | A1 |
20080288640 | Trevor et al. | Nov 2008 | A1 |
20090172547 | Sparr | Jul 2009 | A1 |
Number | Date | Country |
---|---|---|
WO0169428 | Sep 2001 | WO |
WO2005065237 | Jul 2005 | WO |
WO2005098675 | Oct 2005 | WO |
WO2005114525 | Dec 2005 | WO |
WO2006076424 | Jul 2006 | WO |
WO2006083958 | Aug 2006 | WO |
Entry |
---|
U.S. Appl. No. 11/550,307, filed Oct. 17, 2006. |
Smith, Steve; “Tapping the Feed: in search of an RSS Money Trail” Econtent; Mar. 2005; vol. 28; Issue 3; p. 30-34. |
Krol, Carol; “RSS ad programs feed needs” B to B; Jul. 11, 2005; vol. 90 Isue 9; p. 1-33. |
http://web.archive.org/web/20060208061851/www.amazon.com/gp/browse.html? encoding=UTF8&node=3434671&no=3435361&me=A36L942TSJ2AJA. |
Non-Final Office Action dated Aug. 5, 2009, from U.S. Appl. No. 11/550,307. |
Final Office Action dated Mar. 16, 2010, from U.S. Appl. No. 11/550,307. |
Non-Final Office Action dated Jul. 8, 2010, from U.S. Appl. No. 11/550,307. |
Nagano, H.; “New Web Marketing with RSS” Web Designing, vol. 5, No. 12, Japan Dec. 1, 2005, pp. 102-105. |
Chinese First Office Action dated Mar. 29, 2011 from CN200780038865.5. |
EP Search Report dated Jan. 24, 2011 from EP07844299.3. |
Japanese Office Action dated May 30, 2011 from JP2009-533463. |
Japanese Office Action dated Oct. 24, 2011 from JP2009-533463. |
Korean Office Action dated Feb. 16, 2011 from KR10-2009-7010073. |
Korean Office Action dated Nov. 20, 2011 from KR10-2009-7010073. |
Final Office Action dated Dec. 13, 2010, from U.S. Appl. No. 11/550,307. |
Non-Final Action dated May 26, 2011, From U.S. Appl. No. 11/550,307. |
Number | Date | Country | |
---|---|---|---|
20080147780 A1 | Jun 2008 | US |