<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Google Analytics Configuration Mistake #2: Query String Variables</title>
	<atom:link href="http://cutroni.com/blog/2006/09/21/google-analytics-configuration-mistake-2-query-string-variables/feed/" rel="self" type="application/rss+xml" />
	<link>http://cutroni.com/blog/2006/09/21/google-analytics-configuration-mistake-2-query-string-variables/</link>
	<description></description>
	<lastBuildDate>Fri, 25 Jun 2010 14:53:55 -0400</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: URLs in Google Analytics, Page Tagging Update, and Wow, its hot &#124; Intersections</title>
		<link>http://cutroni.com/blog/2006/09/21/google-analytics-configuration-mistake-2-query-string-variables/comment-page-1/#comment-311</link>
		<dc:creator>URLs in Google Analytics, Page Tagging Update, and Wow, its hot &#124; Intersections</dc:creator>
		<pubDate>Tue, 28 Jul 2009 04:42:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.epikone.com/blog/2006/09/21/google-analytics-configuration-mistake-2-query-string-variables/#comment-311</guid>
		<description>[...] for simple solutions, but if you have more complex needs, see this post by Justin Cutroni. Or if you need web analytics inspiration in general, read Avinash Kaushik&#8217;s latest [...]</description>
		<content:encoded><![CDATA[<p>[...] for simple solutions, but if you have more complex needs, see this post by Justin Cutroni. Or if you need web analytics inspiration in general, read Avinash Kaushik&#8217;s latest [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony</title>
		<link>http://cutroni.com/blog/2006/09/21/google-analytics-configuration-mistake-2-query-string-variables/comment-page-1/#comment-310</link>
		<dc:creator>Tony</dc:creator>
		<pubDate>Wed, 10 Jun 2009 09:46:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.epikone.com/blog/2006/09/21/google-analytics-configuration-mistake-2-query-string-variables/#comment-310</guid>
		<description>Interesting post, keep the good stuff coming, good content appreciated!</description>
		<content:encoded><![CDATA[<p>Interesting post, keep the good stuff coming, good content appreciated!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Johnny W</title>
		<link>http://cutroni.com/blog/2006/09/21/google-analytics-configuration-mistake-2-query-string-variables/comment-page-1/#comment-307</link>
		<dc:creator>Johnny W</dc:creator>
		<pubDate>Thu, 30 Apr 2009 14:46:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.epikone.com/blog/2006/09/21/google-analytics-configuration-mistake-2-query-string-variables/#comment-307</guid>
		<description>Hi Justin, thanks for your reply. I constructed an advanced filter in a different way using RegEx, and I think it will work fine.

(.*products)/(\d.*)$

Thanks!

(The Google Conversion University is excellent, too -- I didn&#039;t understand RegEx before their video!)

- Johnny</description>
		<content:encoded><![CDATA[<p>Hi Justin, thanks for your reply. I constructed an advanced filter in a different way using RegEx, and I think it will work fine.</p>
<p>(.*products)/(\d.*)$</p>
<p>Thanks!</p>
<p>(The Google Conversion University is excellent, too &#8212; I didn&#8217;t understand RegEx before their video!)</p>
<p>- Johnny</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Cutroni</title>
		<link>http://cutroni.com/blog/2006/09/21/google-analytics-configuration-mistake-2-query-string-variables/comment-page-1/#comment-306</link>
		<dc:creator>Justin Cutroni</dc:creator>
		<pubDate>Thu, 30 Apr 2009 13:21:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.epikone.com/blog/2006/09/21/google-analytics-configuration-mistake-2-query-string-variables/#comment-306</guid>
		<description>Johnny,

In that case you can either leave the data or you would need to use an advanced filter to remove the 23 from the URL.  The advanced filter would need to capture different parts of the URI and override the Request URI field.  Here are the basic settings:

Field A: Request URI
Pattern A: (^/products/)
Constructor: Request URI
Output Patter: $A1

Make sure to test the above filter!  Without know the exact format of your URLs it may not be right.  But that should get you moving in the right direction.

Thanks for the question,

Justin</description>
		<content:encoded><![CDATA[<p>Johnny,</p>
<p>In that case you can either leave the data or you would need to use an advanced filter to remove the 23 from the URL.  The advanced filter would need to capture different parts of the URI and override the Request URI field.  Here are the basic settings:</p>
<p>Field A: Request URI<br />
Pattern A: (^/products/)<br />
Constructor: Request URI<br />
Output Patter: $A1</p>
<p>Make sure to test the above filter!  Without know the exact format of your URLs it may not be right.  But that should get you moving in the right direction.</p>
<p>Thanks for the question,</p>
<p>Justin</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Johnny W</title>
		<link>http://cutroni.com/blog/2006/09/21/google-analytics-configuration-mistake-2-query-string-variables/comment-page-1/#comment-305</link>
		<dc:creator>Johnny W</dc:creator>
		<pubDate>Thu, 30 Apr 2009 10:51:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.epikone.com/blog/2006/09/21/google-analytics-configuration-mistake-2-query-string-variables/#comment-305</guid>
		<description>I&#039;m currently struggling and I hope someone can help me. What if your site uses &quot;SEO Friendly&quot; (aka &quot;Static&quot;) URIs?

For example, instead of:
http://www.domain.com/products.aspx?page=23

We use:
http://www.domain.com/products/23

I don&#039;t want to see the page number (23) so how would I strip that out?

Thanks for any help!</description>
		<content:encoded><![CDATA[<p>I&#8217;m currently struggling and I hope someone can help me. What if your site uses &#8220;SEO Friendly&#8221; (aka &#8220;Static&#8221;) URIs?</p>
<p>For example, instead of:<br />
<a href="http://www.domain.com/products.aspx?page=23" rel="nofollow">http://www.domain.com/products.aspx?page=23</a></p>
<p>We use:<br />
<a href="http://www.domain.com/products/23" rel="nofollow">http://www.domain.com/products/23</a></p>
<p>I don&#8217;t want to see the page number (23) so how would I strip that out?</p>
<p>Thanks for any help!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Cutroni</title>
		<link>http://cutroni.com/blog/2006/09/21/google-analytics-configuration-mistake-2-query-string-variables/comment-page-1/#comment-304</link>
		<dc:creator>Justin Cutroni</dc:creator>
		<pubDate>Thu, 12 Mar 2009 13:21:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.epikone.com/blog/2006/09/21/google-analytics-configuration-mistake-2-query-string-variables/#comment-304</guid>
		<description>Hey Jon,

This setting, is in fact, a batch field.  If you enter &#039;code&#039; into the field then it will strip all instances of the query string parameter regardless of the value.

Hope that helps and thanks for the question!

Justin</description>
		<content:encoded><![CDATA[<p>Hey Jon,</p>
<p>This setting, is in fact, a batch field.  If you enter &#8216;code&#8217; into the field then it will strip all instances of the query string parameter regardless of the value.</p>
<p>Hope that helps and thanks for the question!</p>
<p>Justin</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Beals</title>
		<link>http://cutroni.com/blog/2006/09/21/google-analytics-configuration-mistake-2-query-string-variables/comment-page-1/#comment-303</link>
		<dc:creator>Jon Beals</dc:creator>
		<pubDate>Fri, 06 Mar 2009 21:06:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.epikone.com/blog/2006/09/21/google-analytics-configuration-mistake-2-query-string-variables/#comment-303</guid>
		<description>This is a great post. Is there a way to batch ignore query string data? We have many campaigns tracked and they all start with the same string of characters &quot;?code=&quot;. If I enter that into the ignore field will it ignore all those that start with that string?

Thanks again for the post.</description>
		<content:encoded><![CDATA[<p>This is a great post. Is there a way to batch ignore query string data? We have many campaigns tracked and they all start with the same string of characters &#8220;?code=&#8221;. If I enter that into the ignore field will it ignore all those that start with that string?</p>
<p>Thanks again for the post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Cutroni</title>
		<link>http://cutroni.com/blog/2006/09/21/google-analytics-configuration-mistake-2-query-string-variables/comment-page-1/#comment-302</link>
		<dc:creator>Justin Cutroni</dc:creator>
		<pubDate>Wed, 29 Oct 2008 12:01:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.epikone.com/blog/2006/09/21/google-analytics-configuration-mistake-2-query-string-variables/#comment-302</guid>
		<description>Hey Mike,

Good troubleshooting.  Exactly the steps that I would follow.  I would use an advanced filter that strips off all query string parameters.  Remember, you can capture parts of the URL and then rewrite those parts out to a field.  Try this reg ex:

(.*?)\?

Then put $A1 in the constructor.

You could tweak the JS and pass it an explicit value that does not include the query string parameters.  I know all the data is available in the DOM, so you can use all JS, you don&#039;t need to worry about using but would have to look it up.

Try the advanced filter.

Justin</description>
		<content:encoded><![CDATA[<p>Hey Mike,</p>
<p>Good troubleshooting.  Exactly the steps that I would follow.  I would use an advanced filter that strips off all query string parameters.  Remember, you can capture parts of the URL and then rewrite those parts out to a field.  Try this reg ex:</p>
<p>(.*?)\?</p>
<p>Then put $A1 in the constructor.</p>
<p>You could tweak the JS and pass it an explicit value that does not include the query string parameters.  I know all the data is available in the DOM, so you can use all JS, you don&#8217;t need to worry about using but would have to look it up.</p>
<p>Try the advanced filter.</p>
<p>Justin</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://cutroni.com/blog/2006/09/21/google-analytics-configuration-mistake-2-query-string-variables/comment-page-1/#comment-301</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Tue, 14 Oct 2008 22:57:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.epikone.com/blog/2006/09/21/google-analytics-configuration-mistake-2-query-string-variables/#comment-301</guid>
		<description>I have been looking for an effective way to create a profile which ignores all query parameters.  With the help of an Excel macro that I discovered (possibly on another post on this site?) I found that there were about 200 different query parameters across the different pages of the site.  Rather than maintain a 200+ item list (which may change), I decided to use search and replace filters to change the recorded URIs.  I initially tried to filter &quot;\?.*&quot; to &quot;&quot;, but GA will not accept an empty replace field (nor will it accept whitespace).  To get around that I went to filters which looked like &quot;aspx\?.*&quot; filtered to &quot;aspx&quot;.  That seems to work ok, but it requires multiple filters for different extensions.  It doesn&#039;t seem like a particularly elegant way to go about it, but I haven&#039;t found any other ideas.  It would be a simple fix in the javascript, but that would prevent any additional profiles from recording parameters which may be of interest.  Any thoughts?</description>
		<content:encoded><![CDATA[<p>I have been looking for an effective way to create a profile which ignores all query parameters.  With the help of an Excel macro that I discovered (possibly on another post on this site?) I found that there were about 200 different query parameters across the different pages of the site.  Rather than maintain a 200+ item list (which may change), I decided to use search and replace filters to change the recorded URIs.  I initially tried to filter &#8220;\?.*&#8221; to &#8220;&#8221;, but GA will not accept an empty replace field (nor will it accept whitespace).  To get around that I went to filters which looked like &#8220;aspx\?.*&#8221; filtered to &#8220;aspx&#8221;.  That seems to work ok, but it requires multiple filters for different extensions.  It doesn&#8217;t seem like a particularly elegant way to go about it, but I haven&#8217;t found any other ideas.  It would be a simple fix in the javascript, but that would prevent any additional profiles from recording parameters which may be of interest.  Any thoughts?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Har du l&#230;st vilk&#229;rene i Google Analytics? -- Online marketing og webstatistik</title>
		<link>http://cutroni.com/blog/2006/09/21/google-analytics-configuration-mistake-2-query-string-variables/comment-page-1/#comment-300</link>
		<dc:creator>Har du l&#230;st vilk&#229;rene i Google Analytics? -- Online marketing og webstatistik</dc:creator>
		<pubDate>Sat, 19 Jul 2008 07:24:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.epikone.com/blog/2006/09/21/google-analytics-configuration-mistake-2-query-string-variables/#comment-300</guid>
		<description>[...] Som det st&#229;r, m&#229; du ikke benytte Google Analytics eller tredje part software til at indsamle personlige oplysninger om dine brugere. Det kan blandt andet ske ved at dit site generer URL&#8217;er med emailadresse eller navn i. URL&#8217;erne vil blive samlet ind i dine rapporter som resten af dine URL&#8217;er og det kan alts&#229; godt skride imod den privatlivspolitik, du skal f&#248;lge. Er det tilf&#230;ldet kan du f&#248;lge denne vejledning til hvordan du ekskluderer disse URL i Google Analytics. [...]</description>
		<content:encoded><![CDATA[<p>[...] Som det st&#229;r, m&#229; du ikke benytte Google Analytics eller tredje part software til at indsamle personlige oplysninger om dine brugere. Det kan blandt andet ske ved at dit site generer URL&#8217;er med emailadresse eller navn i. URL&#8217;erne vil blive samlet ind i dine rapporter som resten af dine URL&#8217;er og det kan alts&#229; godt skride imod den privatlivspolitik, du skal f&#248;lge. Er det tilf&#230;ldet kan du f&#248;lge denne vejledning til hvordan du ekskluderer disse URL i Google Analytics. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
