<?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>Apogee Results Blog &#187; SEM Tests</title>
	<atom:link href="http://www.apogeeresults.com/Blog/index.php/category/online-marketing/search-engine-marketing/sem-tests/feed" rel="self" type="application/rss+xml" />
	<link>http://www.apogeeresults.com/Blog</link>
	<description>Your professional source for all the latest Search Engine Marketing news and events.</description>
	<lastBuildDate>Thu, 25 Feb 2010 05:02:27 +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>Google SearchWiki and the Future of Search Engine Marketing</title>
		<link>http://www.apogeeresults.com/Blog/index.php/google-searchwiki-and-the-future-of-sem?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=google-searchwiki-and-the-future-of-sem</link>
		<comments>http://www.apogeeresults.com/Blog/index.php/google-searchwiki-and-the-future-of-sem#comments</comments>
		<pubDate>Wed, 18 Feb 2009 21:54:22 +0000</pubDate>
		<dc:creator>opico</dc:creator>
				<category><![CDATA[Natural Search (SEO)]]></category>
		<category><![CDATA[Paid Search (PPC)]]></category>
		<category><![CDATA[SEM Tests]]></category>
		<category><![CDATA[SEM Tools]]></category>
		<category><![CDATA[SMX West 2009]]></category>
		<category><![CDATA[Search Engine Marketing]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Google SearchWiki]]></category>
		<category><![CDATA[personalized search]]></category>
		<category><![CDATA[PPC]]></category>
		<category><![CDATA[SEM]]></category>
		<category><![CDATA[SEO]]></category>
		<category><![CDATA[SMX West]]></category>

		<guid isPermaLink="false">http://www.apogee-search.com/Blog/?p=1917</guid>
		<description><![CDATA[<script type="text/javascript">submit_url = 'http://www.apogeeresults.com/Blog/index.php/google-searchwiki-and-the-future-of-sem';</script><script type="text/javascript" src="http://sphinn.com/evb/button.php"></script>Google SearchWiki was launched in November of 2008 with the purpose of personalizing searches and providing an opportunity to share comments among Google users regarding websites and search results. Since then, many SEM experts have been asking themselves, “where is Google going with this?” As with any new innovation, this new feature comes with pros [...]]]></description>
			<content:encoded><![CDATA[<script type="text/javascript">submit_url = 'http://www.apogeeresults.com/Blog/index.php/google-searchwiki-and-the-future-of-sem';</script><script type="text/javascript" src="http://sphinn.com/evb/button.php"></script><div class="tweetmeme_button" style="float: right; margin-left: 10px; margin-bottom:3px;"><a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.apogeeresults.com%2FBlog%2Findex.php%2Fgoogle-searchwiki-and-the-future-of-sem"><img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.apogeeresults.com%2FBlog%2Findex.php%2Fgoogle-searchwiki-and-the-future-of-sem" height="61" width="51" /></a></div><p><a title="Google SearchWiki" href="http://googleblog.blogspot.com/2008/11/searchwiki-make-search-your-own.html" target="_blank">Google SearchWiki</a> was launched in November of 2008 with the purpose of personalizing searches and providing an opportunity to share comments among Google users regarding websites and search results. Since then, many <a title="SEM" href="http://www.apogee-search.com/Services/index.php" target="_blank">SEM</a> experts have been asking themselves, “where is Google going with this?” As with any new innovation, this new feature comes with pros and cons. </p>
<p><a href="http://www.apogee-search.com/Resources/Glossary/index.php?id=163&#038;term=Danny%20Sullivan" title="Danny Sullivan" target="_blank">Danny Sullivan</a> moderated a session with Corey Anderson, a Google engineer, on Wiki Search at the <a href="http://www.apogee-search.com/Resources/conferences.php" target="_blank" title="Internet Marketing Conference">2009 SMX West conference</a>. The two of them managed to evoke many interesting points of discussion. According to Google&#8217;s representative, the <a href="http://www.apogee-search.com/Resources/Glossary/index.php?id=428&#038;term=Google%20Personalized%20Search" target="_blank" title="Google Personalized Search">personalized rankings</a> (Wiki Search) are not currently being taken into consideration for Google&#8217;s primary search results. So, for all of you who started asking your friends and family to move your website into the number 1 position in their wiki searches, according to Google, this currently has <u>no</u> influence on the rankings. However, the possibility of these personalized rankings having an effect on search results has not been ruled out for the future.</p>
<p>One apparent negative impact Google&#8217;s SearchWiki will have on SEM professionals is the difficulty that will come with gathering ranking data and drawing identifiable comparisons from analytics data based on those rankings, as an individual’s personalized rankings will play a part in this traffic. Ultimately, search rankings will become of much less importance if this does become a reality.</p>
<p>On the other hand, Google will open up the competition with personalized rankings, as <a href="http://www.apogee-search.com/Resources/Glossary/index.php?id=328&#038;term=Domain%20Name" target="_blank">domain</a> age will be an unlikely factor in how an individual searcher ranks sites in their personal listings. This will present the opportunity for new ecommerce and informational sites with high relevancy to a search topic to appear in the top rankings, as searchers will have the ability to judge what is the most relevant, regardless of the age of the domain.</p>
<p>This last point could ultimately be a plus for all web users. In order to gain rankings, website owners will be forced to include content relevant to the user rather than building sites primarily for the search engines. Users will now be choosing the websites they want to visit repeatedly, and this will inform Google which sites are meeting the needs of what a user is searching for. Google will be giving more control to the visitors and therefore, websites must be created with the primary goal of appealing to their target audience. </p>
<p>At this point, you may be asking yourself, “but what about spamming with negative or positive comments to remove your competitors?” Google made it clear that they will be reviewing the comments very carefully to avoid any red flag or <a href="http://www.apogee-search.com/Resources/Glossary/index.php?id=57&#038;term=Black%20Hat" target="_blank">black hat</a> motives. This will hopefully ensure that this type of spamming will not be a problem to your website&#8217;s rankings.</p>
<p>Whether you like it or not, Google is constantly gathering information from everything you are searching for, regardless if you are logged in or not. Currently, Google alerts you when a search result has been customized according to previous searches and your location. However, many people may not realize that even when Google doesn’t inform you that the results have been customized, they may have been, most likely in a less obvious way. In certain instances, it is better to avoid user confusion rather than alert the user to these results.</p>
<p>Currently, Google is testing this Wiki functionality for their <a title="PPC ad space" href="http://searchengineland.com/searchwiki-making-its-way-to-adwords-remove-unwanted-ads-16576" target="_blank">PPC ad space</a> as well.  While this is currently an issue that <a href="http://www.apogee-search.com/Services/SEO/index.php" target="_blank" title="SEO">SEO</a> folks are working to solve, <a href="http://www.apogee-search.com/Services/PPC/index.php" target="_blank" title="PPC">PPC</a> should also be paying close attention, as this will most likely effect how quality scores and bid prices will be determined in the future. </p>
<p>The World Wide Web is becoming more personal on a daily basis, and if websites are not prepared to handle this, they will no longer be able to effectively compete in the same search space that they may have previously dominated in the past.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.apogeeresults.com/Blog/index.php/google-searchwiki-and-the-future-of-sem/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Storm Before the Calm: Evaluating Google&#8217;s Automatic Matching</title>
		<link>http://www.apogeeresults.com/Blog/index.php/the-storm-before-the-calm?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=the-storm-before-the-calm</link>
		<comments>http://www.apogeeresults.com/Blog/index.php/the-storm-before-the-calm#comments</comments>
		<pubDate>Wed, 05 Mar 2008 18:25:52 +0000</pubDate>
		<dc:creator>cobo</dc:creator>
				<category><![CDATA[E-Commerce]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Online Marketing]]></category>
		<category><![CDATA[Paid Search (PPC)]]></category>
		<category><![CDATA[SEM Tests]]></category>
		<category><![CDATA[SEM Tools]]></category>
		<category><![CDATA[Search Engine Marketing]]></category>

		<guid isPermaLink="false">http://www.apogee-search.com/Blog/index.php/the-storm-before-the-calm-evaluating-google%e2%80%99s-automatic-matching/</guid>
		<description><![CDATA[<script type="text/javascript">submit_url = 'http://www.apogeeresults.com/Blog/index.php/the-storm-before-the-calm';</script><script type="text/javascript" src="http://sphinn.com/evb/button.php"></script>The Paid Search world was in a tizzy last week over the announcement of Google&#8217;s beta testing for its new Automatic Matching (AM) feature for AdWords. Below is Google’s explanation of the tools’ functions, and just for fun, see if you can guess what two words triggered the uproar.
“Automatic Matching automatically extends your campaign&#8217;s reach [...]]]></description>
			<content:encoded><![CDATA[<script type="text/javascript">submit_url = 'http://www.apogeeresults.com/Blog/index.php/the-storm-before-the-calm';</script><script type="text/javascript" src="http://sphinn.com/evb/button.php"></script><div class="tweetmeme_button" style="float: right; margin-left: 10px; margin-bottom:3px;"><a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.apogeeresults.com%2FBlog%2Findex.php%2Fthe-storm-before-the-calm"><img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.apogeeresults.com%2FBlog%2Findex.php%2Fthe-storm-before-the-calm" height="61" width="51" /></a></div><p>The Paid Search world was in a tizzy last week over the announcement of Google&#8217;s beta testing for its new Automatic Matching (AM) feature for AdWords. Below is Google’s explanation of the tools’ functions, and just for fun, see if you can guess what two words triggered the uproar.</p>
<p><em>“Automatic Matching automatically extends your campaign&#8217;s reach by using surplus budget to serve your ads on relevant search queries that are not already triggered by your keyword lists. By analyzing the structure and content of your website and AdWords campaigns, we deliver more impressions and clicks while maintaining your current CTRs and CPCs.”</em></p>
<p>So with the news that Google would be using advertiser’s “surplus budget” to fund this feature, the paid search blogosphere exploded with claims that Google will inevitably thrust a money-grab onto its advertisers. Compounding these claims was the ComScore report that came out a day before the AM tool was announced showing Google’s advertisements in the US last month were down 0.3% year-on-year. </p>
<p>So is this a money-grab, or is this just remarkably bad timing for a feature that could benefit Adwords advertisers? In an attempt to reason with the angry mob I’ve listed some quick pros and cons. Hopefully this post will save a liquor store or two.<br />
<strong><br />
PRO:</strong> This is only a beta test that a small, select number of advertisers are using, and can opt out of at any time. In fact I think this is the biggest pro of them all because after feedback is given, Google can either tweak AM’s problems or ultimately scrap the tool leaving it in the same boat as Googlesheets.  </p>
<p><strong>CON: </strong> Relevance is not measured by the advertiser. In an example as to how the feature works Google states: <em>“If you sold Adidas shoes on your website, Automatic Matching would automatically crawl your landing page and target your campaigns to queries such as: &#8220;shoes&#8221; &#8220;adidas&#8221; &#8220;athletic&#8221;, etc., and less obvious ones such as &#8220;slippers&#8221; that our system has determined will benefit you and likely lead to a conversion on your site.”</em> While I’m sure the AM does not override negative keyword listings will the potential leads/sales for unrelated search terms without a bid be worth an individual advertiser’s spend?</p>
<p><strong>PRO:</strong> Relevance is not measured by the advertiser. While paid search vets think they can out smart a machine (and most can), a regular mom and pop user with limited experience is usually bidding on a small amount of keywords because they simply do not know any better. </p>
<p><strong>CON:</strong> If an AM search result click does not turn into a lead or sale, it’s ultimately Google’s fault, and you end up paying for their mistake<br />
<strong><br />
PRO:</strong> The AM queries will appear on you search reports, which in turn will provide a source of untapped keywords to monetize. </p>
<p><strong>CON:</strong> Nearly the same results can be gleaned by using Google’s keyword research tool without having to risk your budget’s surplus.<br />
<strong><br />
PRO:</strong> There has never been a time when AdWords has forced advertisers to use a feature that directly benefits their bottom line. </p>
<p>Yes, AM does siphon funds out of a budget surplus, but if you choose to add this feature it’s ultimately your decision. Furthermore Google states that, “AM will never exceed your budget.” While results of this test will more than likely vary across the board I’m sure a certain amount of advertisers (probably small time) will find this tool helpful, while other, experienced advertisers will choose to opt out and run their own campaign.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.apogeeresults.com/Blog/index.php/the-storm-before-the-calm/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>AdWords Data Consistency &#8211; Longer Term</title>
		<link>http://www.apogeeresults.com/Blog/index.php/adwords-data-consistency-longer-term?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=adwords-data-consistency-longer-term</link>
		<comments>http://www.apogeeresults.com/Blog/index.php/adwords-data-consistency-longer-term#comments</comments>
		<pubDate>Thu, 30 Aug 2007 18:47:08 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Google]]></category>
		<category><![CDATA[Metrics]]></category>
		<category><![CDATA[Paid Search (PPC)]]></category>
		<category><![CDATA[SEM Tests]]></category>
		<category><![CDATA[SEM Tools]]></category>

		<guid isPermaLink="false">http://www.apogee-search.com/Blog/index.php/adwords-data-consistency-longer-term/</guid>
		<description><![CDATA[<script type="text/javascript">submit_url = 'http://www.apogeeresults.com/Blog/index.php/adwords-data-consistency-longer-term';</script><script type="text/javascript" src="http://sphinn.com/evb/button.php"></script>We extended the previous test for Client B so that the data for the same time period was pulled down over a number of days. The hypothesis is that the data might change over time as Google performs analysis on invalid clicks and such. This theory did not hold up in the test:


Day
Time
Clicks
Cost
Impr


1st
2am
199
$759.52
128,242


1st
3am
200
$759.52
762.14


2nd
4am
200
$759.52
762.14


3rd
4am
200
$759.52
762.14


3rd
11am
200
$759.52
762.14


4th
4am
200
$759.52
762.14


4th
11am
200
$759.52
762.14


5th
4am
200
$759.52
762.14


6th
4am
200
$759.52
762.14


7th
4am
200
$759.52
762.14


8th
4am
200
$759.52
762.14


9th
4am
200
$759.52
762.14


10th
4am
200
$759.52
762.14


11th
4am
200
$759.52
762.14


12th
4am
200
$759.52
762.14


13th
4am
200
$759.52
762.14


We also ran [...]]]></description>
			<content:encoded><![CDATA[<script type="text/javascript">submit_url = 'http://www.apogeeresults.com/Blog/index.php/adwords-data-consistency-longer-term';</script><script type="text/javascript" src="http://sphinn.com/evb/button.php"></script><div class="tweetmeme_button" style="float: right; margin-left: 10px; margin-bottom:3px;"><a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.apogeeresults.com%2FBlog%2Findex.php%2Fadwords-data-consistency-longer-term"><img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.apogeeresults.com%2FBlog%2Findex.php%2Fadwords-data-consistency-longer-term" height="61" width="51" /></a></div><p>We extended the <a href="/Blog/index.php/more-on-adwords-data-consistency/">previous test for Client B</a> so that the data for the same time period was pulled down over a number of days. The hypothesis is that the data might change over time as Google performs analysis on invalid clicks and such. This theory did not hold up in the test:</p>
<table border=1>
<tr>
<td><strong>Day</strong></td>
<td><strong>Time</strong></td>
<td><strong>Clicks</strong></td>
<td><strong>Cost</strong></td>
<td><strong>Impr</strong></td>
</tr>
<tr>
<td>1st</td>
<td>2am</td>
<td>199</td>
<td>$759.52</td>
<td>128,242</td>
</tr>
<tr>
<td>1st</td>
<td>3am</td>
<td>200</td>
<td>$759.52</td>
<td>762.14</td>
</tr>
<tr>
<td>2nd</td>
<td>4am</td>
<td>200</td>
<td>$759.52</td>
<td>762.14</td>
</tr>
<tr>
<td>3rd</td>
<td>4am</td>
<td>200</td>
<td>$759.52</td>
<td>762.14</td>
</tr>
<tr>
<td>3rd</td>
<td>11am</td>
<td>200</td>
<td>$759.52</td>
<td>762.14</td>
</tr>
<tr>
<td>4th</td>
<td>4am</td>
<td>200</td>
<td>$759.52</td>
<td>762.14</td>
</tr>
<tr>
<td>4th</td>
<td>11am</td>
<td>200</td>
<td>$759.52</td>
<td>762.14</td>
</tr>
<tr>
<td>5th</td>
<td>4am</td>
<td>200</td>
<td>$759.52</td>
<td>762.14</td>
</tr>
<tr>
<td>6th</td>
<td>4am</td>
<td>200</td>
<td>$759.52</td>
<td>762.14</td>
</tr>
<tr>
<td>7th</td>
<td>4am</td>
<td>200</td>
<td>$759.52</td>
<td>762.14</td>
</tr>
<tr>
<td>8th</td>
<td>4am</td>
<td>200</td>
<td>$759.52</td>
<td>762.14</td>
</tr>
<tr>
<td>9th</td>
<td>4am</td>
<td>200</td>
<td>$759.52</td>
<td>762.14</td>
</tr>
<tr>
<td>10th</td>
<td>4am</td>
<td>200</td>
<td>$759.52</td>
<td>762.14</td>
</tr>
<tr>
<td>11th</td>
<td>4am</td>
<td>200</td>
<td>$759.52</td>
<td>762.14</td>
</tr>
<tr>
<td>12th</td>
<td>4am</td>
<td>200</td>
<td>$759.52</td>
<td>762.14</td>
</tr>
<tr>
<td>13th</td>
<td>4am</td>
<td>200</td>
<td>$759.52</td>
<td>762.14</td>
</tr>
</table>
<p>We also ran a similar test for another client whose website focuses on B2B lead generation (hereafter Client C). Again, the data was remarkably consistent:</p>
<table border=1>
<tr>
<td><strong>Day</strong></td>
<td><strong>Time</strong></td>
<td><strong>Clicks</strong></td>
<td><strong>Cost</strong></td>
<td><strong>Impr</strong></td>
</tr>
<tr>
<td>1st</td>
<td>4am</td>
<td>157</td>
<td>$226.35</td>
<td>412,149</td>
</tr>
<tr>
<td>2nd</td>
<td>4am</td>
<td>157</td>
<td>$226.35</td>
<td>412,149</td>
</tr>
<tr>
<td>3rd</td>
<td>11am</td>
<td>157</td>
<td>$226.35</td>
<td>412,149</td>
</tr>
<tr>
<td>4th</td>
<td>4am</td>
<td>157</td>
<td>$226.35</td>
<td>412,149</td>
</tr>
<tr>
<td>5th</td>
<td>4am</td>
<td>157</td>
<td>$226.35</td>
<td>412,149</td>
</tr>
<tr>
<td>6th</td>
<td>4am</td>
<td>157</td>
<td>$226.35</td>
<td>412,149</td>
</tr>
<tr>
<td>7th</td>
<td>4am</td>
<td>157</td>
<td>$226.35</td>
<td>412,149</td>
</tr>
<tr>
<td>8th</td>
<td>4am</td>
<td>157</td>
<td>$226.35</td>
<td>412,149</td>
</tr>
<tr>
<td>9th</td>
<td>4am</td>
<td>157</td>
<td>$226.35</td>
<td>412,149</td>
</tr>
<tr>
<td>10th</td>
<td>4am</td>
<td>157</td>
<td>$226.35</td>
<td>412,149</td>
</tr>
<tr>
<td>11th</td>
<td>4am</td>
<td>157</td>
<td>$226.35</td>
<td>412,149</td>
</tr>
<tr>
<td>12t</td>
<td>4am</td>
<td>157</td>
<td>$226.35</td>
<td>412,149</td>
</tr>
</table>
<p>The net-net is that all tests to date are showing remarkable consistency in the data coming out of the AdWords API. It is much more consistent than I had expected, in fact.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.apogeeresults.com/Blog/index.php/adwords-data-consistency-longer-term/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>More on AdWords Data Consistency</title>
		<link>http://www.apogeeresults.com/Blog/index.php/more-on-adwords-data-consistency?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=more-on-adwords-data-consistency</link>
		<comments>http://www.apogeeresults.com/Blog/index.php/more-on-adwords-data-consistency#comments</comments>
		<pubDate>Wed, 08 Aug 2007 17:27:52 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Google]]></category>
		<category><![CDATA[Metrics]]></category>
		<category><![CDATA[Paid Search (PPC)]]></category>
		<category><![CDATA[SEM Tests]]></category>
		<category><![CDATA[SEM Tools]]></category>

		<guid isPermaLink="false">http://www.apogee-search.com/Blog/index.php/more-on-adwords-data-consistency/</guid>
		<description><![CDATA[<script type="text/javascript">submit_url = 'http://www.apogeeresults.com/Blog/index.php/more-on-adwords-data-consistency';</script><script type="text/javascript" src="http://sphinn.com/evb/button.php"></script>Continuing our series on Google AdWords API Data Consistency, we repeated yesterday&#8217;s test this morning, this time with a B2C lead generation client (hereafter Client B). Unfortunately, the results from this test were infinitely worse.
Fortunately, the results were still pretty darn good:


Time
Clicks
Cost
Impr


2am
199
$759.52
128,242


3am
200
$762.14
128,715


4am
200
$762.14
128,715


5am
200
$762.14
128,715


6am
200
$762.14
128,715


7am
200
$762.14
128,715


8am
200
$762.14
128,715


9am
200
$762.14
128,715


10am
200
$762.14
128,715


All the stats had settled out completely by 3am, and were quite close to [...]]]></description>
			<content:encoded><![CDATA[<script type="text/javascript">submit_url = 'http://www.apogeeresults.com/Blog/index.php/more-on-adwords-data-consistency';</script><script type="text/javascript" src="http://sphinn.com/evb/button.php"></script><div class="tweetmeme_button" style="float: right; margin-left: 10px; margin-bottom:3px;"><a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.apogeeresults.com%2FBlog%2Findex.php%2Fmore-on-adwords-data-consistency"><img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.apogeeresults.com%2FBlog%2Findex.php%2Fmore-on-adwords-data-consistency" height="61" width="51" /></a></div><p>Continuing our series on <a href="/Blog/index.php/category/online-marketing/search-engine-marketing/sem-tests/">Google AdWords API Data Consistency</a>, we repeated yesterday&#8217;s test this morning, this time with a B2C lead generation client (hereafter Client B). Unfortunately, the results from this test were infinitely worse.</p>
<p>Fortunately, the results were still pretty darn good:</p>
<table border=1>
<tr>
<td><strong>Time</strong></td>
<td><strong>Clicks</strong></td>
<td><strong>Cost</strong></td>
<td><strong>Impr</strong></td>
</tr>
<tr>
<td>2am</td>
<td>199</td>
<td>$759.52</td>
<td>128,242</td>
</tr>
<tr>
<td>3am</td>
<td>200</td>
<td>$762.14</td>
<td>128,715</td>
</tr>
<tr>
<td>4am</td>
<td>200</td>
<td>$762.14</td>
<td>128,715</td>
</tr>
<tr>
<td>5am</td>
<td>200</td>
<td>$762.14</td>
<td>128,715</td>
</tr>
<tr>
<td>6am</td>
<td>200</td>
<td>$762.14</td>
<td>128,715</td>
</tr>
<tr>
<td>7am</td>
<td>200</td>
<td>$762.14</td>
<td>128,715</td>
</tr>
<tr>
<td>8am</td>
<td>200</td>
<td>$762.14</td>
<td>128,715</td>
</tr>
<tr>
<td>9am</td>
<td>200</td>
<td>$762.14</td>
<td>128,715</td>
</tr>
<tr>
<td>10am</td>
<td>200</td>
<td>$762.14</td>
<td>128,715</td>
</tr>
</table>
<p>All the stats had settled out completely by 3am, and were quite close to actuals by 2am. Impressive.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.apogeeresults.com/Blog/index.php/more-on-adwords-data-consistency/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Consistency of AdWords API Data</title>
		<link>http://www.apogeeresults.com/Blog/index.php/consistency-of-adwords-api-data?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=consistency-of-adwords-api-data</link>
		<comments>http://www.apogeeresults.com/Blog/index.php/consistency-of-adwords-api-data#comments</comments>
		<pubDate>Tue, 07 Aug 2007 16:16:59 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Google]]></category>
		<category><![CDATA[Metrics]]></category>
		<category><![CDATA[Paid Search (PPC)]]></category>
		<category><![CDATA[SEM Tests]]></category>
		<category><![CDATA[SEM Tools]]></category>

		<guid isPermaLink="false">http://www.apogee-search.com/Blog/?p=502</guid>
		<description><![CDATA[<script type="text/javascript">submit_url = 'http://www.apogeeresults.com/Blog/index.php/consistency-of-adwords-api-data';</script><script type="text/javascript" src="http://sphinn.com/evb/button.php"></script>For some time, we have seen a rumor floating around that data downloaded via the Google AdWords API can fluctuate for the first day or so after it is created. One theory is that it takes time for all the data to be registered from the various data centers.
To test the validity of this theory, [...]]]></description>
			<content:encoded><![CDATA[<script type="text/javascript">submit_url = 'http://www.apogeeresults.com/Blog/index.php/consistency-of-adwords-api-data';</script><script type="text/javascript" src="http://sphinn.com/evb/button.php"></script><div class="tweetmeme_button" style="float: right; margin-left: 10px; margin-bottom:3px;"><a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.apogeeresults.com%2FBlog%2Findex.php%2Fconsistency-of-adwords-api-data"><img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.apogeeresults.com%2FBlog%2Findex.php%2Fconsistency-of-adwords-api-data" height="61" width="51" /></a></div><p>For some time, we have seen a rumor floating around that data downloaded via the Google AdWords API can fluctuate for the first day or so after it is created. One theory is that it takes time for all the data to be registered from the various data centers.</p>
<p>To test the validity of this theory, we pulled the  pervious day&#8217;s clicks, costs and impressions down hourly for one of our smaller B2C clients (hereafter Client A). The first download of data occurred at 2am central time. The actual data pulled is as follows:</p>
<table border=1>
<tr>
<td><strong>Time</strong></td>
<td><strong>Clicks</strong></td>
<td><strong>Cost</strong></td>
<td><strong>Impr</strong></td>
</tr>
<tr>
<td>2am</td>
<td>435</td>
<td>$59.99</td>
<td>22,002</td>
</tr>
<tr>
<td>3am</td>
<td>435</td>
<td>$59.99</td>
<td>22,002</td>
</tr>
<tr>
<td>4am</td>
<td>435</td>
<td>$59.99</td>
<td>22,002</td>
</tr>
<tr>
<td>5am</td>
<td>435</td>
<td>$59.99</td>
<td>22,002</td>
</tr>
<tr>
<td>6am</td>
<td>435</td>
<td>$59.99</td>
<td>22,002</td>
</tr>
<tr>
<td>7am</td>
<td>435</td>
<td>$59.99</td>
<td>22,002</td>
</tr>
<tr>
<td>8am</td>
<td>435</td>
<td>$59.99</td>
<td>22,002</td>
</tr>
<tr>
<td>9am</td>
<td>435</td>
<td>$59.99</td>
<td>22,002</td>
</tr>
<tr>
<td>10am</td>
<td>435</td>
<td>$59.99</td>
<td>22,002</td>
</tr>
</table>
<p>Looks remarkably consistent to me!</p>
<p>To be fair, more testing is needed. We intend to look at a number of clients and to pull data for a number of time periods. We also plan to pull data for the same time period over a number of days to see how it changes (perhaps as click fraud analysis is completed).</p>
<p>Early indications are, however, that Google is doing a fine job on data integrity.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.apogeeresults.com/Blog/index.php/consistency-of-adwords-api-data/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
