<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: New site features (Jan 2011)</title>
	<atom:link href="http://www.biddingtraveler.com/blog/?feed=rss2&#038;p=3" rel="self" type="application/rss+xml" />
	<link>http://www.biddingtraveler.com/blog/?p=3</link>
	<description>A resource for bidding for hotels on Priceline</description>
	<pubDate>Sun, 19 May 2013 05:54:24 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: [Priceline Bidding] New site for Priceline hotel bidding help - Page 6 - FlyerTalk Forums</title>
		<link>http://www.biddingtraveler.com/blog/?p=3#comment-12</link>
		<dc:creator>[Priceline Bidding] New site for Priceline hotel bidding help - Page 6 - FlyerTalk Forums</dc:creator>
		<pubDate>Mon, 31 Jan 2011 08:55:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.biddingtraveler.com/blog/?p=3#comment-12</guid>
		<description>[...] Originally Posted by msimons   Have never gotten a booking with it yet.    Hmm, maybe the latter is the result of the former?   In all seriousness, we just finished tweaking the bid range recommendation slightly to weight more heavily towards winning bids. (It does not make sense to tell someone to start his 4* NYC bidding at $30.. that just wastes everyone's time). We've also been somewhat busy as a result of steady site users and some recent great press. Analyzing the site logs and bugs takes up quite a fair bit of time and prevents me from being able to peruse and respond on this thread 24 hours a day.  If I could address the point about choosing bid increments: this is totally available in the manual bidding path. Just override all the edit boxes to contain your own increments. We just don't do this in the automatic bidding path because we don't want the tool to become exploitative (I'd mentioned this earlier in the thread).   There was also a comment or two about the site data and experimentation. The site collects data as people use it, so yes, it does get better the more users come and play. We do curate the data as well, both algorithmically and manually. The algorithms which recommend bid ranges and choose what data to display are also sensitive to different factors (like when you're going, weekend/weekday status), so that might explain why certain numbers are the way they are.  Lastly, I wanted to mention that we've been busy and just released a few minor improvements. I'd rather not crosspost here and pollute the thread with more screenshots so I'll just redirect interested readers to the blog. [...]</description>
		<content:encoded><![CDATA[<p>[...] Originally Posted by msimons   Have never gotten a booking with it yet.    Hmm, maybe the latter is the result of the former?   In all seriousness, we just finished tweaking the bid range recommendation slightly to weight more heavily towards winning bids. (It does not make sense to tell someone to start his 4* NYC bidding at $30.. that just wastes everyone&#8217;s time). We&#8217;ve also been somewhat busy as a result of steady site users and some recent great press. Analyzing the site logs and bugs takes up quite a fair bit of time and prevents me from being able to peruse and respond on this thread 24 hours a day.  If I could address the point about choosing bid increments: this is totally available in the manual bidding path. Just override all the edit boxes to contain your own increments. We just don&#8217;t do this in the automatic bidding path because we don&#8217;t want the tool to become exploitative (I&#8217;d mentioned this earlier in the thread).   There was also a comment or two about the site data and experimentation. The site collects data as people use it, so yes, it does get better the more users come and play. We do curate the data as well, both algorithmically and manually. The algorithms which recommend bid ranges and choose what data to display are also sensitive to different factors (like when you&#8217;re going, weekend/weekday status), so that might explain why certain numbers are the way they are.  Lastly, I wanted to mention that we&#8217;ve been busy and just released a few minor improvements. I&#8217;d rather not crosspost here and pollute the thread with more screenshots so I&#8217;ll just redirect interested readers to the blog. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
