<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>blackhatzen &#187; blackhatzen</title>
	<atom:link href="http://blackhatzen.com/author/admin/feed/" rel="self" type="application/rss+xml" />
	<link>http://blackhatzen.com</link>
	<description>Anything you can do, we can do meta.</description>
	<lastBuildDate>Mon, 14 Dec 2009 16:01:21 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>BlackHatWorld Down: December 14th, 2009</title>
		<link>http://blackhatzen.com/blackhatworld-down-december-14th-2009/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=blackhatworld-down-december-14th-2009</link>
		<comments>http://blackhatzen.com/blackhatworld-down-december-14th-2009/#comments</comments>
		<pubDate>Mon, 14 Dec 2009 16:00:11 +0000</pubDate>
		<dc:creator>blackhatzen</dc:creator>
				<category><![CDATA[General]]></category>

		<guid isPermaLink="false">http://blackhatzen.com/?p=711</guid>
		<description><![CDATA[BlackHatWorld is currently experiencing a large-scale DDoS attack. We&#8217;re working on it and will be back up soon.
Thanks for your patience.
]]></description>
			<content:encoded><![CDATA[<p>BlackHatWorld is currently experiencing a large-scale DDoS attack. We&#8217;re working on it and will be back up soon.</p>
<p>Thanks for your patience.</p>
<img src="http://blackhatzen.com/?ak_action=api_record_view&id=711&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://blackhatzen.com/blackhatworld-down-december-14th-2009/feed/</wfw:commentRss>
		<slash:comments>18</slash:comments>
		</item>
		<item>
		<title>December 2009 News</title>
		<link>http://blackhatzen.com/december-2009-news/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=december-2009-news</link>
		<comments>http://blackhatzen.com/december-2009-news/#comments</comments>
		<pubDate>Tue, 08 Dec 2009 15:29:05 +0000</pubDate>
		<dc:creator>blackhatzen</dc:creator>
				<category><![CDATA[General]]></category>

		<guid isPermaLink="false">http://blackhatzen.com/?p=707</guid>
		<description><![CDATA[It officially feels like December here at the blackhatzen offices. Snow is on the ground, coats are no longer optional, and we&#8217;re spending more and more time inside enjoying the warmth. Aside from providing customer support, we have three things on our agenda this month:

Forum Generator 2.0
WP Guardian 1.4
Referer Guardian 1.3

Forum Generator 2.0
Over the last [...]]]></description>
			<content:encoded><![CDATA[<p>It officially feels like December here at the blackhatzen offices. Snow is on the ground, coats are no longer optional, and we&#8217;re spending more and more time inside enjoying the warmth. Aside from providing customer support, we have three things on our agenda this month:</p>
<ol>
<li>Forum Generator 2.0</li>
<li>WP Guardian 1.4</li>
<li>Referer Guardian 1.3</li>
</ol>
<h3>Forum Generator 2.0</h3>
<p>Over the last 24 hours, the basic framework that will become Forum Generator 2.0 has been written. We&#8217;re going to continue with the same UI stylistically, but a lot of changes are happening under the hood. A massive overhaul of the gathering system is my biggest priority at the moment, along with adding support for various forum platforms other than phpBB3. While phpBB has a lot to offer, it is limited by a lack of basic plugin support. After spending some time working with the bbPress and vBulletin forum platforms more closely, this limitation is blatantly obvious. As development continues, my plan is to continue updating the blog with what I&#8217;m finding so that others who are developing plugins for forum platforms can gain from what will most likely be a major learning experience for me.</p>
<h3>WP Guardian 1.4</h3>
<p>I&#8217;m going to begin integrating some of the features requested <a href="http://blackhatzen.com/feature-requests-for-wp-guardian-1-4-mini-contest/">in this post</a>, as well as changes and bug-fixes we&#8217;ve discovered since the last release. One thing that I plan on working on is the UI. Specifically, I&#8217;d like to integrate some of the design features used in Referer Guardian to make it easier for users to assign links to advertisements and advertisements to posts, pages, and categories. Once the feature set of 1.4 becomes set in stone, I&#8217;ll update the blog.</p>
<h3>Referer Guardian 1.1</h3>
<p>The <a href="http://www.refererguardian.com/">Referer Guardian</a> launch was a success. We&#8217;ve received a handful of feature requests for the next version from customers. One big new feature will be the inclusion of basic statistics into the Referer Guardian control panel. This tracking isn&#8217;t intended to compete with any of the various analytics packages available, but will allow Referer Guardian users the ability to see how their campaigns are performing in real-time.</p>
<h3>Other News</h3>
<p>During non-development hours in the next week or so, I&#8217;m going to put together a thorough tutorial (or potentially series of tutorials) on utilizing WP Guardian and Referer Guardian together. This probably should have been done before launch, but the main focus at that point in time was testing. We are also requesting that customers of any of our products provide us feedback ASAP for any new features they&#8217;d like to see in the next releases of all three of our current products.</p>
<p>That is all for now. I hope you all are having a good December and looking forward to a great start to the new year.</p>
<img src="http://blackhatzen.com/?ak_action=api_record_view&id=707&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://blackhatzen.com/december-2009-news/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Referer Guardian 1.0.2 Released</title>
		<link>http://blackhatzen.com/referer-guardian-1-0-2-released/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=referer-guardian-1-0-2-released</link>
		<comments>http://blackhatzen.com/referer-guardian-1-0-2-released/#comments</comments>
		<pubDate>Sat, 05 Dec 2009 01:26:59 +0000</pubDate>
		<dc:creator>blackhatzen</dc:creator>
				<category><![CDATA[General]]></category>

		<guid isPermaLink="false">http://blackhatzen.com/?p=700</guid>
		<description><![CDATA[We&#8217;ve just sent out the updates for Referer Guardian 1.0.2. This update includes the following improvements:

More adaptive to different permalink structures.
You can now redirect through pages AND posts

Customers, please let me know if you do not receive an update email.
]]></description>
			<content:encoded><![CDATA[<p>We&#8217;ve just sent out the updates for Referer Guardian 1.0.2. This update includes the following improvements:</p>
<ul>
<li>More adaptive to different permalink structures.</li>
<li>You can now redirect through pages AND posts</li>
</ul>
<p>Customers, please let me know if you do not receive an update email.</p>
<img src="http://blackhatzen.com/?ak_action=api_record_view&id=700&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://blackhatzen.com/referer-guardian-1-0-2-released/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Referer Guardian Launched!</title>
		<link>http://blackhatzen.com/referer-guardian-launched/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=referer-guardian-launched</link>
		<comments>http://blackhatzen.com/referer-guardian-launched/#comments</comments>
		<pubDate>Thu, 03 Dec 2009 19:14:26 +0000</pubDate>
		<dc:creator>blackhatzen</dc:creator>
				<category><![CDATA[General]]></category>

		<guid isPermaLink="false">http://blackhatzen.com/?p=695</guid>
		<description><![CDATA[After yesterday&#8217;s debacle, we&#8217;re happy to announce that Referer Guardian has launched! All who signed up for launch announcements should be receiving emails soon. If for some reason you don&#8217;t receive one or have any questions about the product, please contact us by clicking the questions button on the left-hand side of your screen!

Check Out [...]]]></description>
			<content:encoded><![CDATA[<p>After yesterday&#8217;s debacle, we&#8217;re happy to announce that Referer Guardian has launched! All who signed up for launch announcements should be receiving emails soon. If for some reason you don&#8217;t receive one or have any questions about the product, please contact us by clicking the questions button on the left-hand side of your screen!</p>
<div align="center">
<h2><a href="http://www.refererguardian.com/">Check Out Referer Guardian!</a></h2>
</div>
<p><ins datetime="2009-12-03T22:04:14+00:00">About half of the announcement list emails weren&#8217;t ever sent. Everyone expecting them should be receiving them within the next 10-15 minutes. Sorry for the inconvenience!</ins></p>
<img src="http://blackhatzen.com/?ak_action=api_record_view&id=695&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://blackhatzen.com/referer-guardian-launched/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>And then that happened &#8230;</title>
		<link>http://blackhatzen.com/and-then-that-happened/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=and-then-that-happened</link>
		<comments>http://blackhatzen.com/and-then-that-happened/#comments</comments>
		<pubDate>Thu, 03 Dec 2009 09:46:39 +0000</pubDate>
		<dc:creator>blackhatzen</dc:creator>
				<category><![CDATA[General]]></category>

		<guid isPermaLink="false">http://blackhatzen.com/?p=687</guid>
		<description><![CDATA[We here at blackhatzen have to apologize. Our home state of Pennsylvania got rocked by some serious storms this evening. Rocked so hard, in fact, that we lost power here at blackhatzen manor until just before 4:30AM. Obviously, we didn&#8217;t launch on time, and that sucks, but chaos will be chaos and over the years [...]]]></description>
			<content:encoded><![CDATA[<p>We here at blackhatzen have to apologize. Our home state of Pennsylvania got rocked by some serious storms this evening. Rocked so hard, in fact, that we lost power here at blackhatzen manor until just before 4:30AM. Obviously, we didn&#8217;t launch on time, and that sucks, but chaos will be chaos and over the years we&#8217;ve learned to embrace this sort of thing as a sign that we are indeed still living in a universe that is, for the most part, completely out of our control. Either that or we just have really bad luck and need to buy a back-up generator &#8230; or move back into civilization where we can get 3G reception without having to scale mountains&#8230; whatever.</p>
<p>The long and tall of it is that we&#8217;re going to launch Referer Guardian at 2PM EST today. Fifteen hours later than we anticipated, but we need to get some sleep and no one likes reading email early in the morning anyway.</p>
<p>Thanks for understanding,<br />
bhz</p>
<img src="http://blackhatzen.com/?ak_action=api_record_view&id=687&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://blackhatzen.com/and-then-that-happened/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Referer Guardian Launches Tonight!</title>
		<link>http://blackhatzen.com/referer-guardian-launches-tonight/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=referer-guardian-launches-tonight</link>
		<comments>http://blackhatzen.com/referer-guardian-launches-tonight/#comments</comments>
		<pubDate>Thu, 03 Dec 2009 00:10:26 +0000</pubDate>
		<dc:creator>blackhatzen</dc:creator>
				<category><![CDATA[General]]></category>

		<guid isPermaLink="false">http://blackhatzen.com/?p=675</guid>
		<description><![CDATA[
Referer Guardian launches TONIGHT at 11PM EST!

Just a quick update for everyone waiting for Referer Guardian to launch.
We made a great discovery yesterday during the final round of testing. We&#8217;ve tested and scrutinized the human generated clicks themselves extensively without ever having a leak, but had never seriously abused a Referer Guardian guarded iframe. So, [...]]]></description>
			<content:encoded><![CDATA[<h2>
<div align="center"><a href="http://refererguardian.com/">Referer Guardian</a> launches TONIGHT at 11PM EST!</div>
</h2>
<p>Just a quick update for everyone waiting for <a href="http://refererguardian.com/">Referer Guardian</a> to launch.</p>
<p>We made a great discovery yesterday during the final round of testing. We&#8217;ve tested and scrutinized the human generated clicks themselves extensively without ever having a leak, but had never seriously abused a Referer Guardian guarded iframe. So, a good friend was kind enough to lend us a 1&#215;1 iframe on a site that gets hundreds of thousands of hits a day. We routed this iframe through Referer Guardian and to a tracking page where we recorded the referer as well as the header information (which carries browser information, among other things.) What better way to do a final test than to put it through some <strong>insane</strong> abuse?</p>
<p>The results were very, very good and we learned something that, as far as we know, no one else has ever discovered. After well over 100,000 iframe loads, we had a leak rate of ~0.03%. That means that for every 100,000 visitors that hit the iframe, we recorded 30 leaks. Now, leaks are a scary thing when you&#8217;re developing (or using) something to hide your referer, but this isn&#8217;t a surprise. Iframes are notoriously hard to deal with because each browser handles them a little bit differently.</p>
<p>When we began to analyze the logs, we saw a very clear pattern for the tiny amount of referers that did leak through; they were all (as in 100%) based on the Apple WebKit browser framework, which is used by both Safari and Chrome. What was even more strange was the fact that there were literally thousands of other users, using the same browsers and operating systems, whose referers were cloaked perfectly. Our first thought was security software, but the fact that a majority of these leaks were from iPhones and Mac users indicates otherwise.</p>
<p>We also noticed that almost all of these leaks happened in pairs in very close succession to one another. After putting some serious thought into the issue, what we&#8217;re almost positive is occurring is the result of pre-fetching and caching. Under certain, rare circumstances (such as an extremely fast refresh or back button hit) some browsers will load the end result of a series of redirections rather than follow the redirection path itself. We have been unable to recreate this event using the same browsers (including the iPhone) after many, many, many tries, but we&#8217;re almost certain this is the case.</p>
<p>Since we are unable to control browsers&#8217; behavior at the system-level, we&#8217;ve added the option to block all WebKit-based browsers. The referer is checked all along the cloak path, so it isn&#8217;t possible for a browser that either sends <em>no referer</em> or an <em>unexpected</em> referer to actually pass through Referer Guardian directly. We added the option <em>specifically</em> for people who choose to iframe.</p>
<p>For the sake of comparison, we also tested the currently most popular referer cloaking plugin, CPA-Redirector, and found that a little more than 5% of referers passed through during the same iframe test with very little pattern to the browsers or operating systems of those leaks. This means that under a strenuous iframe test, CPA-Redirector was <strong>167 times</strong> more likely to leak the referer than <strong><a href="http://refererguardian.com">Referer Guardian</a></strong>.</p>
<p>How is that for extensive research?</p>
<img src="http://blackhatzen.com/?ak_action=api_record_view&id=675&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://blackhatzen.com/referer-guardian-launches-tonight/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Getting Google Keyword Suggestions with PHP</title>
		<link>http://blackhatzen.com/getting-google-keyword-suggestions-with-php/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=getting-google-keyword-suggestions-with-php</link>
		<comments>http://blackhatzen.com/getting-google-keyword-suggestions-with-php/#comments</comments>
		<pubDate>Sun, 29 Nov 2009 17:52:56 +0000</pubDate>
		<dc:creator>blackhatzen</dc:creator>
				<category><![CDATA[General]]></category>

		<guid isPermaLink="false">http://blackhatzen.com/?p=665</guid>
		<description><![CDATA[Yesterday, someone on the forum asked about getting Google Keyword Suggestion results easily. I wrote this PHP file in a few minutes. It grabs keyword suggestions based on the keyword you provide and lists them, including the number of results available for each keyword.

View Code PHP&#60;?php 
	if&#40;isset&#40;$_GET&#91;'kw'&#93;&#41;&#41;&#123;
		$keyword = urlencode&#40;$_GET&#91;'kw'&#93;&#41;;
		echo 'Keyword Suggestions for: &#60;strong&#62;'.$keyword.'&#60;/strong&#62;';
	&#125; else &#123;
		echo [...]]]></description>
			<content:encoded><![CDATA[<p>Yesterday, someone on the forum asked about getting Google Keyword Suggestion results easily. I wrote this PHP file in a few minutes. It grabs keyword suggestions based on the keyword you provide and lists them, including the number of results available for each keyword.</p>

<div class="wp_codebox_msgheader"><span class="right"></span><span class="left"><a href="javascript:;" onclick="javascript:showCodeTxt('p665code2'); return false;">View Code</a> PHP</span><div class="codebox_clear"></div></div><div class="wp_codebox"><table><tr id="p6652"><td class="code" id="p665code2"><pre class="php" style="font-family:monospace;"><span style="color: #000000; font-weight: bold;">&lt;?php</span> 
	<span style="color: #b1b100;">if</span><span style="color: #009900;">&#40;</span><a href="http://www.php.net/isset"><span style="color: #990000;">isset</span></a><span style="color: #009900;">&#40;</span><span style="color: #000088;">$_GET</span><span style="color: #009900;">&#91;</span><span style="color: #0000ff;">'kw'</span><span style="color: #009900;">&#93;</span><span style="color: #009900;">&#41;</span><span style="color: #009900;">&#41;</span><span style="color: #009900;">&#123;</span>
		<span style="color: #000088;">$keyword</span> <span style="color: #339933;">=</span> <a href="http://www.php.net/urlencode"><span style="color: #990000;">urlencode</span></a><span style="color: #009900;">&#40;</span><span style="color: #000088;">$_GET</span><span style="color: #009900;">&#91;</span><span style="color: #0000ff;">'kw'</span><span style="color: #009900;">&#93;</span><span style="color: #009900;">&#41;</span><span style="color: #339933;">;</span>
		<span style="color: #b1b100;">echo</span> <span style="color: #0000ff;">'Keyword Suggestions for: &lt;strong&gt;'</span><span style="color: #339933;">.</span><span style="color: #000088;">$keyword</span><span style="color: #339933;">.</span><span style="color: #0000ff;">'&lt;/strong&gt;'</span><span style="color: #339933;">;</span>
	<span style="color: #009900;">&#125;</span> <span style="color: #b1b100;">else</span> <span style="color: #009900;">&#123;</span>
		<span style="color: #b1b100;">echo</span> <span style="color: #0000ff;">'No Keyword Selected!'</span><span style="color: #339933;">;</span>
		<a href="http://www.php.net/exit"><span style="color: #990000;">exit</span></a><span style="color: #009900;">&#40;</span><span style="color: #009900;">&#41;</span><span style="color: #339933;">;</span>
	<span style="color: #009900;">&#125;</span>
	<span style="color: #000088;">$url</span> <span style="color: #339933;">=</span> <span style="color: #0000ff;">'http://google.com/complete/search?output=toolbar&amp;q='</span><span style="color: #339933;">.</span><span style="color: #000088;">$keyword</span><span style="color: #339933;">;</span>
	<span style="color: #000088;">$xml</span> <span style="color: #339933;">=</span> <a href="http://www.php.net/simplexml_load_file"><span style="color: #990000;">simplexml_load_file</span></a><span style="color: #009900;">&#40;</span><span style="color: #000088;">$url</span><span style="color: #009900;">&#41;</span><span style="color: #339933;">;</span>
	<span style="color: #000088;">$data</span> <span style="color: #339933;">=</span> <span style="color: #000088;">$xml</span><span style="color: #339933;">-&gt;</span><span style="color: #004000;">xpath</span><span style="color: #009900;">&#40;</span><span style="color: #0000ff;">&quot;/toplevel/CompleteSuggestion/suggestion&quot;</span><span style="color: #009900;">&#41;</span><span style="color: #339933;">;</span>
	<span style="color: #000088;">$queries</span> <span style="color: #339933;">=</span> <span style="color: #000088;">$xml</span><span style="color: #339933;">-&gt;</span><span style="color: #004000;">xpath</span><span style="color: #009900;">&#40;</span><span style="color: #0000ff;">&quot;/toplevel/CompleteSuggestion/num_queries&quot;</span><span style="color: #009900;">&#41;</span><span style="color: #339933;">;</span>
	<span style="color: #000088;">$i</span> <span style="color: #339933;">=</span> <span style="color: #cc66cc;">0</span><span style="color: #339933;">;</span>
	<span style="color: #000088;">$count</span> <span style="color: #339933;">=</span> <a href="http://www.php.net/count"><span style="color: #990000;">count</span></a><span style="color: #009900;">&#40;</span><span style="color: #000088;">$data</span><span style="color: #009900;">&#41;</span><span style="color: #339933;">-</span><span style="color: #cc66cc;">1</span><span style="color: #339933;">;</span>
	<span style="color: #b1b100;">while</span><span style="color: #009900;">&#40;</span><span style="color: #000088;">$i</span> <span style="color: #339933;">&lt;=</span> <span style="color: #000088;">$count</span><span style="color: #009900;">&#41;</span><span style="color: #009900;">&#123;</span>
		<span style="color: #b1b100;">echo</span> <span style="color: #000088;">$data</span><span style="color: #009900;">&#91;</span><span style="color: #000088;">$i</span><span style="color: #009900;">&#93;</span><span style="color: #009900;">&#91;</span><span style="color: #0000ff;">'data'</span><span style="color: #009900;">&#93;</span><span style="color: #339933;">.</span> <span style="color: #0000ff;">' - '</span><span style="color: #339933;">.</span> <span style="color: #000088;">$queries</span><span style="color: #009900;">&#91;</span><span style="color: #000088;">$i</span><span style="color: #009900;">&#93;</span><span style="color: #009900;">&#91;</span><span style="color: #0000ff;">'int'</span><span style="color: #009900;">&#93;</span><span style="color: #339933;">;</span>
		<span style="color: #b1b100;">echo</span> <span style="color: #0000ff;">&quot;&lt;br /&gt;&quot;</span><span style="color: #339933;">;</span>
		<span style="color: #000088;">$i</span><span style="color: #339933;">++;</span>
	<span style="color: #009900;">&#125;</span>
<span style="color: #000000; font-weight: bold;">?&gt;</span></pre></td></tr></table></div>

<p>Just save this to a .php file, upload, and visit http://path.to/the/file?kw={keyword} where {keyword} is the keyword or phrase you&#8217;re looking to get results for. With a little bit of PHP know-how, it should be very easy to extend this code to meet your needs.</p>
<p>Hope it helps!</p>
<img src="http://blackhatzen.com/?ak_action=api_record_view&id=665&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://blackhatzen.com/getting-google-keyword-suggestions-with-php/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>WP Guardian 1.3 Released!</title>
		<link>http://blackhatzen.com/wp-guardian-1-3-released/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=wp-guardian-1-3-released</link>
		<comments>http://blackhatzen.com/wp-guardian-1-3-released/#comments</comments>
		<pubDate>Sun, 29 Nov 2009 04:22:26 +0000</pubDate>
		<dc:creator>blackhatzen</dc:creator>
				<category><![CDATA[General]]></category>

		<guid isPermaLink="false">http://blackhatzen.com/?p=672</guid>
		<description><![CDATA[We&#8217;ve just released the WP Guardian 1.3 update! All customers should be receiving their updated download links in the near future. If you don&#8217;t receive one, let us know by clicking the &#8220;Questions&#8221; tab on the left-hand side of your screen or posting in the support forum and we&#8217;ll get you sorted out.
As we mentioned [...]]]></description>
			<content:encoded><![CDATA[<p>We&#8217;ve just released the <strong><a href="http://wpguardian.com/">WP Guardian 1.3</a></strong> update! All customers should be receiving their updated download links in the near future. If you don&#8217;t receive one, let us know by clicking the &#8220;Questions&#8221; tab on the left-hand side of your screen or posting in the support forum and we&#8217;ll get you sorted out.</p>
<p><a href="http://blackhatzen.com/wp-guardian-1-3-coming-todaytonight/">As we mentioned earlier</a>, <strong>WP Guardian 1.3</strong> includes the following features and improvements:</p>
<ul>
<li>Category-based blocking</li>
<li>Page-based Blocking</li>
<li>Optional Close button</li>
<li>Increase Range of Time Before Ad Pops</li>
</ul>
<p>We&#8217;ve also included an experimental method to automatically add the <code>wmode="transparent"</code> parameter to all embedded videos. You&#8217;ll find instructions on how to unlock that feature in the updated instruction manual.</p>
<img src="http://blackhatzen.com/?ak_action=api_record_view&id=672&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://blackhatzen.com/wp-guardian-1-3-released/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WP Guardian 1. 3 Coming Today/Tonight!</title>
		<link>http://blackhatzen.com/wp-guardian-1-3-coming-todaytonight/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=wp-guardian-1-3-coming-todaytonight</link>
		<comments>http://blackhatzen.com/wp-guardian-1-3-coming-todaytonight/#comments</comments>
		<pubDate>Sat, 28 Nov 2009 21:12:06 +0000</pubDate>
		<dc:creator>blackhatzen</dc:creator>
				<category><![CDATA[General]]></category>

		<guid isPermaLink="false">http://blackhatzen.com/?p=661</guid>
		<description><![CDATA[After a much needed break for the Thanksgiving holiday, we&#8217;re back in full swing. We&#8217;re currently working on finishing up the WP Guardian 1.3 update, due out later today or late tonight. It includes both some improvements and new features. We figured out how to programmatically solve the issue where videos were leaking in front [...]]]></description>
			<content:encoded><![CDATA[<p>After a much needed break for the Thanksgiving holiday, we&#8217;re back in full swing. We&#8217;re currently working on finishing up the WP Guardian 1.3 update, due out later today or late tonight. It includes both some improvements and new features. <del datetime="2009-11-29T00:11:25+00:00">We figured out how to programmatically solve the issue where videos were leaking in front of the ads if their embed tags didn&#8217;t have the <code>wmode=transparent</code> parameter set.</del> <ins datetime="2009-11-29T00:11:25+00:00">Unfortunately, the solution that we came up with seems to break on some versions of IE. We&#8217;re still going to include the code with WP Guardian 1.3, but customers will have to enable it by uncommenting a line of code. Instructions for uncommenting will be included.</ins></p>
<p>We&#8217;ve implemented the following improvements and features: </p>
<ul>
<li>Category-based blocking</li>
<li>Page-based Blocking</li>
<li>Optional Close button</li>
<li>Increase Range of Time Before Ad Pops</li>
</ul>
<p>If you have any questions about the 1.3 release, please comment here. We&#8217;ll be sending out an email blast and the updates as soon as we&#8217;re done finishing up documentation and the final round of testing. </p>
<p>I hope all of our US customers had a great Thanksgiving and that everyone is getting pumped up for the holiday season sales rush. From where we&#8217;re sitting, this season is looking to be a very profitable one.</p>
<img src="http://blackhatzen.com/?ak_action=api_record_view&id=661&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://blackhatzen.com/wp-guardian-1-3-coming-todaytonight/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PlentyOfFish Self-Serve Beta Ad Network Review</title>
		<link>http://blackhatzen.com/plentyoffish-self-serve-ad-network-review/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=plentyoffish-self-serve-ad-network-review</link>
		<comments>http://blackhatzen.com/plentyoffish-self-serve-ad-network-review/#comments</comments>
		<pubDate>Wed, 25 Nov 2009 00:07:49 +0000</pubDate>
		<dc:creator>blackhatzen</dc:creator>
				<category><![CDATA[General]]></category>

		<guid isPermaLink="false">http://blackhatzen.com/?p=650</guid>
		<description><![CDATA[A little less than a week ago, the popular dating site PlentyOfFish launched a beta self-serve advertising network. We decided to give the network a quick test to see how well their traffic performed in comparison to other social networks. While the result was disappointing, it is important to keep in mind that the network [...]]]></description>
			<content:encoded><![CDATA[<img width="625" height="162" src="http://blackhatzen.com/wp-content/themes/bigfeature/library/timthumb/timthumb.php?src=/wp-content/uploads/2009/11/fish-japanese1.jpg&amp;w=625&amp;zc=1" alt="PlentyOfFish Self-Serve Beta Ad Network Review" /><p>A little less than a week ago, the popular dating site PlentyOfFish <a href="http://plentyoffish.wordpress.com/2009/11/17/plentyoffish-self-service-advertising-platform/">launched a beta self-serve advertising network</a>. We decided to give the network a quick test to see how well their traffic performed in comparison to other social networks. While the result was disappointing, it is important to keep in mind that the network is still in beta, so they know there is room for improvement. Hopefully this post is seen as (mostly) constructive criticism and not an outright indictment.</p>
<p>Before I begin, I should also point out that, despite our namesake and all associated negative connotations, all ads were compliant with affiliate network standards and serious effort was put forth to comply with PoF&#8217;s ad network&#8217;s somewhat vague standards.</p>
<h3>The Setup</h3>
<p><strong>Budget: </strong>~$500.00<br />
<strong>Tracking: </strong> <a href="http://prosper.tracking202.com/apps/">Prosper202</a> (<a href="http://prosper.tracking202.com/blog/tracking202-has-been-acquired">Congrats, Wes and Steven!</a>)<br />
<strong>Offers: </strong>Dating, self-improvement (teeth whitening and weight loss), grants/loans.<br />
<strong>Campaigns: </strong>10, 3-5 ads per campaign. All with a history of converting well on other ad networks in similar segments.</p>
<h3>The Network</h3>
<p>The sign-up process is simple. My account was approved and funded within 15 minutes. To avoid confusion, it is a total pain in the ass to actually find the network from the main PlentyOfFish domain. The address of the ad network is <a href="http://ads.pof.com/">http://ads.pof.com/</a>. The minimum network deposit is $25.00, which is entirely reasonable. </p>
<p>Once the account was setup and funded, I created my first campaign, promoting a dating network. PoF&#8217;s advertising model is bid-based CPM (cost-per-mille/1,000 impressions.) The minimum bid is $0.15 per thousand impressions. They don&#8217;t provide much information with respect to competition within your bid range or how much others bidding on similar segments are bidding. I&#8217;ll explain why this sort of blind bidding process can be a big pain in the ass later in the post.</p>
<p>A quick look at their advertising guidelines reads like a list of ever profitable campaign I&#8217;ve ever run. Their restrictions get particularly vague with regards to the promotion of other dating sites. No free dating sites are allowed. No dating sites that are considered &#8220;risque&#8221; are allowed. To me, passing some sort of high-handed moral judgment on how &#8220;adult&#8221; a lander for a site that is 18+ seems silly, but I understand wanting to control your network.</p>
<p>The segmentation, which is what originally attracted us to the network, has some serious potential. You can select the user segment that you&#8217;d like to advertise to based on the following criteria:</p>
<ul>
<li>Zip/Postal Code</li>
<li>State/Province</li>
<li>Country</li>
<li>Age</li>
<li>Gender</li>
<li>Education Level</li>
<li>Profession</li>
<li>Has children</li>
<li>Car</li>
<li>Body Type</li>
<li>Drinking Habits</li>
<li>Ethnicity</li>
<li>Height</li>
<li>Income</li>
<li><strong><em>Login Count</em></strong></li>
<li>Marital Status</li>
<li>Religion</li>
<li>Search Type/Looking For</li>
<li>Smoking Habits</li>
<li><strong><em>Session Depth</em></strong></li>
</ul>
<p>I&#8217;ve emphasized two separate segmentation options here; Login Count and Session Depth. In an ideal situation, these two segments could be used to target &#8220;engaged&#8221; users. Engagement is a sort of unquantifiable metric that helps advertisers gain insight on how likely a person is to click on an ad. The level of engagement is absolutely key in CPM advertising.</p>
<p>The <em>Login Count</em> segment is easy to understand. It allows you to choose to target users who have logged in at least a certain number of times. This can help eliminate users who may only be logging in for the first time and are more interested in checking out the dating and social networking aspects of the site, ignoring the ads entirely.</p>
<p><em>Session Depth</em> may be a little more confusing to some. As I understand it, session depth reflects the number of pages or clicks a user has made on the site during their current session. Similar to Login count, this can help separate the people who are just logging on to check a message from those who are actively surfing the site.</p>
<p>One missing targeting segment that is available for their premium ad service is targeting based on interest and profile content. I made contact with PoF ad managers a few weeks ago to try and promote a client&#8217;s e-commerce business. They mentioned the self-serve option as an alternative. Without interest targeting, it is absolutely not.</p>
<p>I created a few campaigns, targeting to similar demographics that I have on Facebook and other social networks. PoF offers a few more metrics than some networks, so I had high hopes that this would keep my ad spend down. The key to successful CPM campaigns is knowing your target audience.</p>
<p>Because they don&#8217;t provide any real information as to the number of users an ad will reach within a segment, nor what a reasonable bid is for a particular segment, I ranged my bids from $0.15 (the minimum) to $0.50 to try to get a decent sample size while doing testing. </p>
<h3>The Ad Review Process</h3>
<p>It was during the ad review process that the first major shortcomings of the system became apparent. Ad approval times ranged from an hour (for updates to pre-existing campaigns) to five hours (for new campaigns.) They state in their FAQ section that approval can take up to 24 hours, because they need to make sure that your landers are compliant with their rules. IMHO, this delay is unacceptable.</p>
<p>My first few ads were rejected (after a few hours) for vague reasons. According to their FAQ, &#8220;If denied, an explanation will be provided to help you better design your ads in the future.&#8221; The reality of the situation was, &#8220;If denied, an explanation that doesn&#8217;t provide any real information will be posted to the History section of your account panel, but you won&#8217;t be notified, so keep refreshing, sucka!&#8221;</p>
<p>After a few failed attempts, I was able to stumble into a handful of landing page/ad text combos that met network standards. Forget about using even remotely <em>piquant</em> language. Even phrases that have made it passed US TV censors seem to be off-limits. This aspect wouldn&#8217;t be as frustrating if the exact reason an ad was denied was provided OR the review time wasn&#8217;t as long. Once again, it is important to note that the network is still in beta and these sorts of network management issues shouldn&#8217;t be too hard to iron out.</p>
<h3>The Results</h3>
<p><strong>Average Impressions: </strong>150,000<br />
<strong>Average CTR: </strong>A gruesome 0.009%. I&#8217;d be embarrassed about this if similar ads targeted at similar segments hadn&#8217;t performed much, much better on other networks.<br />
<strong>Average Conversion Rate: </strong> A very telling 0.005%. These same offers are converting at nearly 500x this rate on other ad networks.<br />
<strong>Profit: </strong> A few hundred dollars in the red. I should note that I&#8217;ve had individual campaigns over the course of my career that failed miserably. Everyone does. That said, I&#8217;ve never had a string of campaigns fail like this, especially ones that are performing well on other networks.</p>
<p>At first, some of the campaigns seemed to be performing quite well. A few were seeing a reasonable amount of clicks and converting at 3-5% for the first hour or two of the campaign going live. However, almost across the board, CTR and conversion numbers declined rapidly after an ad had been live for 3-4 hours. The segments I was targeting for some campaigns were (purposefully) broad enough that ad overlap shouldn&#8217;t have been an issue on a network as large as PoF.</p>
<p>In a few cases, campaigns stopped being displayed altogether with no explanation. Increasing the bids made no difference whatsoever and, as I&#8217;ll describe in the next section, without a way to contact an ad manager, I never figured out how to get them to start again. Adding new campaigns and waiting for their (re-)approval seemed the only way to restart certain campaigns. There were no common trends across these &#8220;stopped&#8221; campaigns that I could see that might provide some sort of explanation.</p>
<p>User engagement was poor across the board. I combined both my own landers and direct linking and found that most users were only sticking around for a couple of seconds, including a handful of repeat visitors. </p>
<h3>The Problems</h3>
<ol>
<li><strong>Budgets and Account Replenishment</strong> On more than one occasion, campaigns went over-budget by 5-10%. Not too bad, but not too good either. My account also needed to be manually refunded after it sat at $0 for hours, even though I had setup automatic replenishment at $5.00.</li>
<li><strong>Where are my ads?</strong> Some ads simply stopped being displayed. No reason given. According to the management panel, they were approved and active. Increasing bids didn&#8217;t seem to make a difference. Why?</li>
<li><strong>Bid Surfing</strong> There is no way to tell a reasonable bid range. Blind bidding can work, but not when the ad delivery itself is questionable.</li>
<li><strong>Help please?!</strong> I pride myself on not asking for too much help from ad account managers, so when I need it, I really need it. I couldn&#8217;t find any contact information listed on the actual PoF network site. I emailed various people who I&#8217;ve had contact with regarding their premium ad network and received absolutely no response. I understand that they are in beta still, but (unless you&#8217;re Google) you need to give your advertisers SOME WAY to get their questions answered. A vague FAQ isn&#8217;t going to cut it.</li>
</ol>
<h3>The Highlights</h3>
<ol>
<li><strong>Promising segment targeting options</strong> They&#8217;ve made a solid attempt to introduce new/uncommon segments to advertisers which, in the long run, will probably prove powerful.</li>
<li><strong>Low competition</strong>&#8230; for now at least. Many campaigns seemed to get a decent amount of impressions for low bids. Without knowing how accurate the ad delivery system is, it is hard to tell how competitive segments are.</li>
<li><strong>Stats</strong> Their reporting seemed near real-time and offers a nice cross-section for doing impression and click distribution analysis on a campaign-to-campaign basis. I can see the potential for customizing this information to a higher degree being another big positive if they work out the other issues outlined here first.</li>
</ol>
<h3>Final Conclusion</h3>
<p>There is a ton of potential here, but it is quite obvious that this is very much a beta and they really need to iron a few things out. Even with the &#8220;beta&#8221; label, the network doesn&#8217;t make up for the many shortcomings I&#8217;ve experienced during the small amount of time I&#8217;ve tried to advertise through the network. Much of this could be alleviated by offering some sort of advertiser support. I&#8217;d love to see a <a href="http://campfirenow.com/">Campfire</a>/chat system setup similar to the one used by <a href="http://slicehost.com/">Slicehost</a>. </p>
<p>I&#8217;m also not convinced that the PoF user base is this disinterested in ads. Facebook is free for users and advertising on Facebook can be extremely lucrative if you know <a href="http://finchsells.com/2009/08/29/the-shit-ive-learnt-not-to-do-on-facebook/">how to target the right audience</a>. It will be interesting to see how PoF ads perform over the next few months. I&#8217;m certainly not writing them off just yet. </p>
<h3>Your Thoughts?</h3>
<p>I&#8217;m very interested to hear the thoughts and experiences of others that have used the network. If you have any thoughts at all on the subject, please feel free to comment away.</p>
<img src="http://blackhatzen.com/?ak_action=api_record_view&id=650&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://blackhatzen.com/plentyoffish-self-serve-ad-network-review/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
