<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" version="2.0"><channel><atom:id>tag:blogger.com,1999:blog-6329594498573451684</atom:id><lastBuildDate>Tue, 11 Oct 2011 05:39:52 +0000</lastBuildDate><category>Apache Log Format</category><category>U5-66</category><category>FAQ</category><category>U5-48</category><category>U5-57</category><category>Helper Scripts</category><category>U5-10</category><category>report conversion</category><category>Issues Accessing Log Files</category><category>DNS database update</category><category>U5-49</category><category>Default Log File Formats</category><category>Multi-threading</category><category>U5-65</category><category>Urchin 6 Changelist (v. 6.500)</category><category>Renaming Existing Profiles</category><category>Urchin Configuration</category><category>Solaris 10</category><category>U5-58</category><category>U5-9</category><category>urchin experts</category><category>Using 'convert-u5data' Script</category><category>U5-55</category><category>daylight savings error</category><category>Urchin 6</category><category>Urchin Software Update</category><category>U5-68</category><category>(#126)</category><category>U5-38</category><category>IIS Log Files</category><category>Reporting Previous Visitors</category><category>Accurate Data Reports</category><category>U5-20</category><category>Plesk</category><category>Urchin 6 Changelist (v. 6.501)</category><category>rolling back to urchin 5</category><category>welcome</category><category>Processing Logs</category><category>URI lowercase</category><category>U5-67</category><category>Downloading Urchin</category><category>U5-39</category><category>Traffic Breakdown</category><category>U5-56</category><category>U5-18</category><category>U5-53</category><category>privacy policy</category><category>Log Files</category><category>Demo Restrictions</category><category>Parallel Log Processing</category><category>Report Data</category><category>(#125)</category><category>Traffic Filters</category><category>Text Content</category><category>how licensing works</category><category>Report Issues</category><category>U5-22</category><category>U5-45</category><category>Urchin 5</category><category>U5-30</category><category>utm update</category><category>Support</category><category>U5-19</category><category>Processing Log Files</category><category>Segmentation</category><category>Urchin Back Up</category><category>U5-54</category><category>Locked Profile</category><category>shtml extensions</category><category>Geo-update Command</category><category>(#120)</category><category>Urchin Report Problems</category><category>utmlinker function</category><category>Sharing Log Sources</category><category>MS SQL Server 2005</category><category>Urchin Reports</category><category>file migration</category><category>U5-46</category><category>U5-21</category><category>Using Urchin and GA at the same time</category><category>Storage Space</category><category>Page Hits</category><category>User-Agents</category><category>Time Zone and Apache Logs</category><category>Reports</category><category>Binary Log Files</category><category>proprietary database</category><category>U5-24</category><category>differences in U5 and U6 data</category><category>Interrupt Signal Error</category><category>U5-47</category><category>Banner Referrals</category><category>U5-52</category><category>utm cookies</category><category>UTM Domain Name</category><category>MS SQL Server 2005 Support</category><category>U5-23</category><category>urchin experts blog</category><category>Running on a 64-bit OS</category><category>Missing Report Files</category><category>Databases</category><category>Profile Problems</category><category>U5-1</category><category>(#153)</category><category>Activity Tracking</category><category>(#140)</category><category>Issues with Visit Count</category><category>U5-51</category><category>Data Center Mode</category><category>(#136)</category><category>U5-42</category><category>U5-34</category><category>Mobile Device</category><category>Auto Reports</category><category>MySQL database</category><category>U5-33</category><category>U5-15</category><category>U5-50</category><category>U5-3</category><category>setup and configuration</category><category>Data Fields</category><category>Switching Servers</category><category>U5-25</category><category>individual record defined</category><category>ct_runstatus</category><category>U5-16</category><category>U5-32</category><category>U5-27</category><category>Tracking Methods</category><category>URI stem</category><category>U5-61</category><category>Raw Data</category><category>Log File Format for Helix</category><category>U5-4</category><category>Accessing the SQL database</category><category>Task Scheduler Error</category><category>U5-44</category><category>U5-17</category><category>U5-31</category><category>Urchin</category><category>U5-60</category><category>Exporting Profiles</category><category>U5-26</category><category>Mobile User-Agents</category><category>DD and %d wildcards</category><category>Load Balancing Module</category><category>U5-5</category><category>Configuration Database</category><category>U5-43</category><category>Top Content</category><category>Procesing Log Files</category><category>UTM Tracking Methods</category><category>Traffic</category><category>U5-63</category><category>Data Storage</category><category>U5-11</category><category>U5-37</category><category>(#142)</category><category>U5-29</category><category>Squid Servers</category><category>U5-6</category><category>Report Window Configuration</category><category>Mobile Browsers</category><category>Internal Web Server</category><category>Exporting Data</category><category>Urchin 6 Changelist (v. 6.402)</category><category>Urchin Processing Power</category><category>Registering for Urchin</category><category>Urchin Database</category><category>U5-28</category><category>U5-62</category><category>U5-12</category><category>U5-7</category><category>Traffic Reporting</category><category>Overture PPC</category><category>Applying Filters</category><category>(#161)</category><category>Urchin Module</category><category>Licensing</category><category>U5-41</category><category>Configuration Data</category><category>User Agent Detection</category><category>Max Urchin Memory Use</category><category>Configuring Urchin</category><category>Filtering String Queries</category><category>serial activation and IE</category><category>Re-process data</category><category>U5-36</category><category>U5-64</category><category>Language in Admin Section</category><category>Clickpaths</category><category>Machine Section</category><category>Installation and win2000</category><category>U5-13</category><category>urchin and windows vista</category><category>DB file Error</category><category>U5-40</category><category>Data</category><category>UserAgent</category><category>Old Log Processing</category><category>U5-8</category><category>SQL database</category><category>U5-35</category><category>(#174)</category><category>U5-59</category><category>Calculating Session Length</category><category>Default Adwords Format</category><category>U5-14</category><category>Urchin 5 hardware needs</category><title>UrchinExperts Analytics Software Support Blog</title><description /><link>http://urchinexperts.blogspot.com/</link><managingEditor>noreply@blogger.com (Actual Metrics)</managingEditor><generator>Blogger</generator><openSearch:totalResults>111</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/UrchinexpertsAnalyticsSoftwareSupportBlog" /><feedburner:info xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" uri="urchinexpertsanalyticssoftwaresupportblog" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6329594498573451684.post-1546334217020033037</guid><pubDate>Fri, 22 May 2009 18:48:00 +0000</pubDate><atom:updated>2009-05-22T14:58:54.759-04:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Urchin Software Update</category><category domain="http://www.blogger.com/atom/ns#">utm update</category><title>Update:  UTM Update for Remote Logging</title><description>Google is retiring the service.urchin.com server on 1 June, 2009. If your legacy Urchin 5.x installation references this server, you'll need to update the "__utm.js" that's being used on your web pages.&lt;br /&gt;&lt;br /&gt;What to do: Check to see if your Urchin Traffic Monitor (UTM) file is referencing this old service. If it is, you must make a change to the javascript or replace it if you wish to continue logging traffic both locally and to the Google Analytics system. &lt;br /&gt;&lt;br /&gt;You can either update or replace your existing UTM.  Both options are detailed in the following help document at the &lt;a href="http://www.google.com/support/urchin45/bin/answer.py?answer=148341&amp;amp;topic=7391"&gt;Urchin Help Center.&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6329594498573451684-1546334217020033037?l=urchinexperts.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://urchinexperts.blogspot.com/2009/05/update-utm-update-for-remote-logging.html</link><author>noreply@blogger.com (Epik Phil)</author><thr:total>40</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6329594498573451684.post-4158983162287622281</guid><pubDate>Fri, 15 May 2009 21:43:00 +0000</pubDate><atom:updated>2009-05-15T17:50:06.129-04:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">FAQ</category><category domain="http://www.blogger.com/atom/ns#">setup and configuration</category><title>Urchin Q and A:  Recommended Environment for Andvanced Setup</title><description>&lt;span style="font-weight: bold;"&gt;Question:&lt;/span&gt;  What would be the ideal condition to run Urchin without low speed: some servers with Urchin and database in all of them; some servers with Urchin and one master database; 2 or 3 servers with Urchin and some databases configured as master and slave? &lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;Answer:&lt;/span&gt;  Reporting data is stored in proprietary databases.  Reporting data can be configured to be stored on your NAS.  The MySQL or PostgreSQL database may also reside on a separate box.  You will need a license for each Urchin installation that is crunching logs.  Start with the minimum system requirements to see how Urchin's log processing performs.  With a baseline measurement, you'll be able to easily scale from there. &lt;br /&gt;&lt;br /&gt;Server specifications and configuration are really dependent upon your unique situation.  You must set up a test environment to see what kind of resources you are going to need.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6329594498573451684-4158983162287622281?l=urchinexperts.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://urchinexperts.blogspot.com/2009/05/urchin-q-and-recommended-environment.html</link><author>noreply@blogger.com (Epik Phil)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6329594498573451684.post-6926297685242229394</guid><pubDate>Fri, 15 May 2009 21:38:00 +0000</pubDate><atom:updated>2009-05-15T17:43:41.705-04:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">FAQ</category><category domain="http://www.blogger.com/atom/ns#">Storage Space</category><title>Urchin Q and A:  Special Data Storage Circumstance</title><description>&lt;span style="font-weight: bold;"&gt;Question:&lt;/span&gt;  How much disk space, memory and processing is required if we have to store 1-year's of data information for 50.000 domains with about 50 million pageviews per day?&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;Answer:&lt;/span&gt;  Server specifications are really based on size of log data being crunched, and resulting amount of reporting data.  Report data is going to be ~10% of raw log data.  Try starting with the minimum system specifications, and scale from there:&lt;br /&gt;&lt;br /&gt;* 2.5Ghz Pentium dual-core&lt;br /&gt;* 2GB RAM per Core (i.e. dual-core = 4GB; quad-core = 16GB)&lt;br /&gt;* Ultra2/Wide SCSI hard disk (such as a Seagate Cheetah)&lt;br /&gt;* Backup utility external to Urchin&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6329594498573451684-6926297685242229394?l=urchinexperts.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://urchinexperts.blogspot.com/2009/05/urchin-q-and-special-data-storage.html</link><author>noreply@blogger.com (Epik Phil)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6329594498573451684.post-4703817945453116195</guid><pubDate>Mon, 11 May 2009 16:19:00 +0000</pubDate><atom:updated>2009-05-11T12:25:37.978-04:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">FAQ</category><category domain="http://www.blogger.com/atom/ns#">Urchin 6</category><category domain="http://www.blogger.com/atom/ns#">how licensing works</category><title>Urchin Q and A:  How Urchin 6 Licensing Works</title><description>&lt;span style="font-weight: bold;"&gt;Question:&lt;/span&gt;  How does Urchin 6 licensing work?&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;Answer:&lt;/span&gt;  The Urchin activation process is as follows:&lt;br /&gt;&lt;br /&gt;When installing a serial code, your Urchin machine sends the serial code and key code to the Urchin licensing server.&lt;br /&gt;&lt;br /&gt;Urchin verifies these two values and returns a license key enabling the customer to complete the installation through the following process:&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;  1.&lt;/span&gt; ugetlicense utility automates the sending of the serial code and key code to the Urchin license center&lt;br /&gt;&lt;br /&gt;  &lt;span style="font-weight: bold;"&gt;2.&lt;/span&gt; A unique license key is returned and written to the Urchin configuration. You can use uconf-export to export your Urchin configuration which contains this value&lt;br /&gt;&lt;br /&gt; &lt;span style="font-weight: bold;"&gt; 3. &lt;/span&gt;The key code is computed using:&lt;br /&gt;&lt;br /&gt;         * Inode numbers of configuration database files (Unix systems)&lt;br /&gt;         * System identifiers (Windows systems)&lt;br /&gt;         * Note that the IP address is NOT used in the license key!&lt;br /&gt;         * Also note that copying Urchin config databases or moving Urchin to another disk or partition will change the computed key code&lt;br /&gt;&lt;br /&gt; &lt;span style="font-weight: bold;"&gt; 4.&lt;/span&gt; Once activated no further network-based license authentication is done by any Urchin component.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6329594498573451684-4703817945453116195?l=urchinexperts.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://urchinexperts.blogspot.com/2009/05/urchin-q-and-how-urchin-6-licensing.html</link><author>noreply@blogger.com (Epik Phil)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6329594498573451684.post-2285233333769230547</guid><pubDate>Fri, 10 Apr 2009 20:02:00 +0000</pubDate><atom:updated>2009-04-10T16:11:06.412-04:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Urchin Software Update</category><category domain="http://www.blogger.com/atom/ns#">Urchin 6 Changelist (v. 6.501)</category><title>Urchin 6.501 Changelist (Mar 26, 2009)</title><description>&lt;p class="line867"&gt;&lt;span class="u"&gt;&lt;strong&gt;&lt;a href="https://secure.urchin.com/helpwiki/en/Urchin_6.5_and_6.501_Changelists"&gt;&lt;span style="font-weight: normal;"&gt;From the Urchin Help Center:&lt;/span&gt;&lt;/a&gt;&lt;br /&gt;&lt;/strong&gt;&lt;/span&gt;&lt;/p&gt;&lt;p class="line874"&gt;Urchin 6.501 is a minor release fixing the following four issues in the Urchin 6.500 release. (Scroll down to see the Urchin 6.500 changelist.) &lt;span class="anchor" id="line-15"&gt;&lt;/span&gt;&lt;span class="anchor" id="line-16"&gt;&lt;/span&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;Downloading CPC data in v6.500 frequently took a long time. &lt;span class="anchor" id="line-17"&gt;&lt;/span&gt;&lt;ul&gt;&lt;li style="list-style-type: none;"&gt;&lt;p class="line862"&gt;o v6.501 fixes a performance issue that affected accounts with a very large CPC history. v6.501 can download up to 256 MB of GZIPPED historical CPC data and process it much more quickly. Due to Google &lt;a class="nonexistent" href="https://secure.urchin.com/helpwiki/en/AdWords"&gt;AdWords&lt;/a&gt; limitations, however, downloads over this threshold are not supported. &lt;span class="anchor" id="line-18"&gt;&lt;/span&gt;&lt;span class="anchor" id="line-19"&gt;&lt;/span&gt;&lt;span class="anchor" id="line-20"&gt;&lt;/span&gt;&lt;/p&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/li&gt;&lt;li class="gap"&gt;Proxy Settings &lt;span class="anchor" id="line-21"&gt;&lt;/span&gt;&lt;ul&gt;&lt;li style="list-style-type: none;"&gt;o Fixed v6.500 proxy issue when downloading CPC data. All traffic is now being redirected through proxy (with or without authentication). &lt;span class="anchor" id="line-22"&gt;&lt;/span&gt;&lt;p class="line862"&gt;o For new proxy setup instructions, see &lt;strong&gt;Downloading CPC Data via proxy (6.501+)&lt;/strong&gt; in &lt;a href="https://secure.urchin.com/helpwiki/en/CPC_Data_Import_Utilities"&gt;CPC Data Import Utilities&lt;/a&gt;. &lt;span class="anchor" id="line-23"&gt;&lt;/span&gt;&lt;span class="anchor" id="line-24"&gt;&lt;/span&gt;&lt;span class="anchor" id="line-25"&gt;&lt;/span&gt;&lt;/p&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/li&gt;&lt;li class="gap"&gt;64-bit Visitor ID overflow issue &lt;span class="anchor" id="line-26"&gt;&lt;/span&gt;&lt;ul&gt;&lt;li style="list-style-type: none;"&gt;o We continue to recommend that you use "urchin.js", not "ga.js". However, for ga.js users, v6.501 addresses the issue of the utma cookie containing a 64-bit value that is used during visitor_id generation. The Urchin parser has been modified to handle both 32 and 64 bit values in the utma cookie. &lt;span class="anchor" id="line-27"&gt;&lt;/span&gt;&lt;span class="anchor" id="line-28"&gt;&lt;/span&gt;&lt;span class="anchor" id="line-29"&gt;&lt;/span&gt;&lt;/li&gt;&lt;/ul&gt;&lt;/li&gt;&lt;li class="gap"&gt;uconf-manager &lt;ul&gt;&lt;li style="list-style-type: none;"&gt;o The v6.501 uconf-manager can perform 'add', 'delete' and 'update' operations on the uprofiles table. &lt;/li&gt;&lt;/ul&gt;&lt;/li&gt;&lt;/ul&gt;&lt;a style="font-weight: bold;" href="http://www.google.com/urchin/download.html"&gt;Download 6.501&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6329594498573451684-2285233333769230547?l=urchinexperts.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://urchinexperts.blogspot.com/2009/04/urchin-6501-changelist-mar-26-2009.html</link><author>noreply@blogger.com (Epik Phil)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6329594498573451684.post-4849706794653128204</guid><pubDate>Fri, 10 Apr 2009 19:48:00 +0000</pubDate><atom:updated>2009-04-10T15:57:39.139-04:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">FAQ</category><category domain="http://www.blogger.com/atom/ns#">differences in U5 and U6 data</category><title>Urchin Q and A:  Differences in U5 and U6 Data Results</title><description>&lt;span style="font-weight: bold;"&gt;Question:&lt;/span&gt;  We see differences in Urchin 5 versus Urchin 6 results.  There is also some information that we used to get in urchin 5 that we no longer see in urchin 6. Are you able to speak with us about a few examples?&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;Answer:&lt;/span&gt;  In comparing any two web analytics packages (including U5 vs U6), a difference in data should be expected.  It's not always easy to compare U5 to U6 because of the change in report organization and naming.  In addition, there are a lot of reasons why the numbers may not be exact.  Here's some of the things you should check:&lt;br /&gt;&lt;br /&gt;1. Is the Pageview Mimes Match field in the Reporting tab of the profile's configuration the same for both profiles? &lt;br /&gt;2. Is the Session Timeout the same for both profiles? &lt;br /&gt;3. Do you have Session Requires Pageview on in Urchin 5 (It's always "on" in Urchin 6)? &lt;br /&gt;4. Is Log Tracking on for both profiles? &lt;br /&gt;5. Are you using the same Visitor Tracking Method for both installations? &lt;br /&gt;6. Are you processing the log source from both profiles, or are you processing in Urchin 5 and then migrating the data to Urchin 6? &lt;br /&gt;7. Are metrics different for the most recent day, week, and month and for historic days, weeks, and months? &lt;br /&gt;8. Are any other metrics the same?&lt;br /&gt;&lt;br /&gt;Urchin 6 has changed a good deal since Urchin was originally acquired (U5.7).  Thus, proprietary back-end algorithms may also be different.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6329594498573451684-4849706794653128204?l=urchinexperts.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://urchinexperts.blogspot.com/2009/04/urchin-q-and-differences-in-u5-and-u6.html</link><author>noreply@blogger.com (Epik Phil)</author><thr:total>1</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6329594498573451684.post-6841614457247251813</guid><pubDate>Wed, 11 Mar 2009 22:40:00 +0000</pubDate><atom:updated>2009-03-11T18:47:44.805-04:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">FAQ</category><category domain="http://www.blogger.com/atom/ns#">daylight savings error</category><title>Urchin Q and A:  Fixing Daylight Savings Error</title><description>&lt;span style="font-weight: bold;"&gt;Question:&lt;/span&gt; Ever since daylight savings, we get the following error when Urchin tries to process logs:&lt;br /&gt;&lt;br /&gt;ERROR: (9003-942-883) Failed to query the database&lt;br /&gt;DETAIL: Incorrect datetime value: '2009-03-08 02:59:50' for column 'utpt_data_start_time' at row 1&lt;br /&gt;&lt;br /&gt;How do we fix this? &lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;Answer:&lt;/span&gt; Reconfigure your MySQL installation and uncheck the checkbox for Enable Strict Mode. &lt;br /&gt;&lt;br /&gt;Then, stop and restart the Urchin service. &lt;br /&gt;&lt;br /&gt;If that doesn't work, from the MySQL Command Line&lt;br /&gt;Prompt enter the following command:&lt;br /&gt;&lt;br /&gt;mysql&gt;SET @@global.sql_mode='MYSQL40'&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6329594498573451684-6841614457247251813?l=urchinexperts.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://urchinexperts.blogspot.com/2009/03/urchin-q-and-fixing-daylight-savings.html</link><author>noreply@blogger.com (Epik Phil)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6329594498573451684.post-6383591366556929265</guid><pubDate>Tue, 23 Dec 2008 19:54:00 +0000</pubDate><atom:updated>2008-12-23T15:17:37.849-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Urchin Software Update</category><category domain="http://www.blogger.com/atom/ns#">Urchin 6 Changelist (v. 6.500)</category><title>Urchin 6 Software Changelist (v. 6.500)</title><description>Google recently released v.6.500 update for Urchin 6 software.  Here is a summary of the changelist:&lt;br /&gt;&lt;br /&gt;&lt;ul&gt;&lt;li&gt;New Cost Per Click (CPC) Data Import Manager allows to create 'CPC Sources' &lt;/li&gt;&lt;/ul&gt;&lt;ul&gt;&lt;li&gt;Reporting:  Urchin now recognizes "Chrome" as a browser and "Android" as a platform &lt;/li&gt;&lt;/ul&gt;&lt;ul&gt;&lt;li&gt;Profiles:  Global Settings for DB Tables are now properly appled.  Reporting data is deleted correctly from a file system on Windows when "Delete All Data" is clicked or profile is deleted.  &lt;/li&gt;&lt;/ul&gt;&lt;ul&gt;&lt;li&gt;Scheduler and History:  Profile scheduled weekly no longer runs several times.  Geo-DB moved to separate screen &lt;br /&gt;&lt;/li&gt;&lt;/ul&gt;&lt;ul&gt;&lt;li&gt; Users and Groups:  Override Dashboard option on Group Management screen fixed&lt;/li&gt;&lt;/ul&gt;&lt;ul&gt;&lt;li&gt; Installer:  404 error when a different port was specified during Windows upgrade fixed&lt;br /&gt;&lt;/li&gt;&lt;/ul&gt; &lt;ul&gt;&lt;li&gt; Utilities:  Functionality of uconf-manager utility has been extended.  Works on several other tables in addition to "uusers" table&lt;br /&gt;&lt;/li&gt;&lt;/ul&gt; &lt;ul&gt;&lt;li&gt; Running Urchin Profile Scheduler in console mode on Windows fixed&lt;br /&gt;&lt;/li&gt;&lt;/ul&gt;&lt;ul&gt;&lt;li&gt; Other:  Updated geo database up until 12/2008 geo data, various localization issues repaired, Urchin embedded help topics and updated articles on Urchin Help Center. &lt;br /&gt;&lt;/li&gt;&lt;/ul&gt;For further information, refer to the &lt;a href="https://secure.urchin.com/helpwiki/en/Help_Center"&gt;Urchin Help Center&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;Go to the &lt;a href="http://www.google.com/urchin/download.html"&gt;Urchin Download&lt;/a&gt; page to get v.6.500.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6329594498573451684-6383591366556929265?l=urchinexperts.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://urchinexperts.blogspot.com/2008/12/urchin-6-software-changelist-v-6500.html</link><author>noreply@blogger.com (Epik Phil)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6329594498573451684.post-3072420211865559560</guid><pubDate>Tue, 16 Dec 2008 19:05:00 +0000</pubDate><atom:updated>2008-12-16T14:08:18.372-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">FAQ</category><category domain="http://www.blogger.com/atom/ns#">rolling back to urchin 5</category><title>Urchin Q and A: Rolling Back to Urchin 5 from 6</title><description>&lt;span style="font-weight: bold;"&gt;Question:&lt;/span&gt;  Is there a way to manually rollback from Urchin 6 to Urchin 5?&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;Answer: &lt;/span&gt; One way to rollback from Urchin 6 to Urchin 5 is to restore from backup.  Another way you can restore Urchin 5 is, if you still have the log files, you can reinstall Urchin 5 and reprocess log files.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6329594498573451684-3072420211865559560?l=urchinexperts.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://urchinexperts.blogspot.com/2008/12/urchin-q-and-rolling-back-to-urchin-5.html</link><author>noreply@blogger.com (Epik Phil)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6329594498573451684.post-3891591180928959712</guid><pubDate>Tue, 16 Dec 2008 19:01:00 +0000</pubDate><atom:updated>2008-12-16T14:04:23.629-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">FAQ</category><category domain="http://www.blogger.com/atom/ns#">report conversion</category><title>Urchin Q and A:  Report Conversion from Urchin 5 to 6</title><description>&lt;span style="font-weight: bold;"&gt;Question: &lt;/span&gt; I have reports going further back than my logs. How can I convert these reports from Urchin 5 to Urchin 6?&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;Answer:  &lt;/span&gt;Urchin provides a script, convert-u5data, to convert report data from U5 to U6.  As with the configuration database, the structure of reporting database (that stores profile information) has also been changed in Urchin 6. This utility, convert-u5data, provides an option for importing the reporting database directly from Urchin 5 installation into the Urchin 6 installation.  convert-u5data is located in the util directory of the Urchin 6 distribution.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6329594498573451684-3891591180928959712?l=urchinexperts.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://urchinexperts.blogspot.com/2008/12/urchin-q-and-report-conversion-from.html</link><author>noreply@blogger.com (Epik Phil)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6329594498573451684.post-1054043553480116050</guid><pubDate>Tue, 16 Dec 2008 18:57:00 +0000</pubDate><atom:updated>2008-12-16T14:00:39.289-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">file migration</category><category domain="http://www.blogger.com/atom/ns#">FAQ</category><title>Urchin Q and A:  File Migration Slow Going</title><description>&lt;span style="font-weight: bold;"&gt;Question: &lt;/span&gt; I am migrating from Urchin 5 to Urchin 6. Why is uconf-import going so slow?&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;Answer:&lt;/span&gt;  The migration script chokes on archived files.  You have to unpack and delete the archive; then, run the migration script.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6329594498573451684-1054043553480116050?l=urchinexperts.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://urchinexperts.blogspot.com/2008/12/urchin-q-and-file-migration-slow-going.html</link><author>noreply@blogger.com (Epik Phil)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6329594498573451684.post-372744565791263724</guid><pubDate>Tue, 16 Dec 2008 18:53:00 +0000</pubDate><atom:updated>2008-12-16T13:56:25.937-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">utm cookies</category><category domain="http://www.blogger.com/atom/ns#">FAQ</category><category domain="http://www.blogger.com/atom/ns#">utmlinker function</category><title>Urchin Q and A: Utmlinker Function and UTM Cookies Across Domains</title><description>&lt;span style="font-weight: bold;"&gt;Question: &lt;/span&gt; Can you describe in detail how the utmlinker function and utm cookies work across domains?&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;Answer: &lt;/span&gt; Urchin cookies are 1st party. Thus, if you intend to track visitors across a primary domain and/or sub-domains of that primary domain, you have to set cookies to the primary domain.  We recommend you set _udn equal to whatever the primary domain is the page resides on.  The reason for __utmLinker() is to copy values from one set of cookies to another set, usually between different primary domains all together.  The uLink option enables Urchin to execute utmLinker() and also to look for utmLinker values in the URI. &lt;br /&gt;If your site spans multiple primary domains, you will also want to set _uLink=1.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6329594498573451684-372744565791263724?l=urchinexperts.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://urchinexperts.blogspot.com/2008/12/urchin-q-and-utmlinker-function-and-utm.html</link><author>noreply@blogger.com (Epik Phil)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6329594498573451684.post-1857581709605682942</guid><pubDate>Tue, 16 Dec 2008 18:42:00 +0000</pubDate><atom:updated>2008-12-16T13:46:05.767-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">FAQ</category><category domain="http://www.blogger.com/atom/ns#">shtml extensions</category><title>Urchin Q and A:  Urchin and *.shtml Extensions</title><description>&lt;span style="font-weight: bold;"&gt;Question:&lt;/span&gt;  Does Urchin support *.shtml extensions?&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;Answer:&lt;/span&gt;  There are no limitations in Urchin with respect to .shtml file extensions. Try adding the extension to the Pageview Mime Match field under Profile Settings &gt; Reporting.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6329594498573451684-1857581709605682942?l=urchinexperts.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://urchinexperts.blogspot.com/2008/12/urchin-q-and-urchin-and-shtml.html</link><author>noreply@blogger.com (Epik Phil)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6329594498573451684.post-3233346181882069190</guid><pubDate>Mon, 24 Nov 2008 17:11:00 +0000</pubDate><atom:updated>2008-11-24T13:09:01.454-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">MS SQL Server 2005 Support</category><category domain="http://www.blogger.com/atom/ns#">FAQ</category><category domain="http://www.blogger.com/atom/ns#">MS SQL Server 2005</category><category domain="http://www.blogger.com/atom/ns#">MySQL database</category><category domain="http://www.blogger.com/atom/ns#">Support</category><title>Urchin Q and A: Urchin and Microsoft SQL Server 2005 Support</title><description>&lt;span style="font-weight:bold;"&gt;Question:&lt;/span&gt;&lt;br /&gt;Does Urchin support Microsoft SQL Server 2005 instead of MySQL?  &lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Answer:&lt;/span&gt; &lt;br /&gt;Currently, Urchin does not support MS SQL Server 2005.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6329594498573451684-3233346181882069190?l=urchinexperts.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://urchinexperts.blogspot.com/2008/11/urchin-q-and-urchin-and-microsoft-sql.html</link><author>noreply@blogger.com (-EpikLabs-)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6329594498573451684.post-2448227132691728596</guid><pubDate>Mon, 24 Nov 2008 17:03:00 +0000</pubDate><atom:updated>2008-11-24T13:08:38.540-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Data Storage</category><category domain="http://www.blogger.com/atom/ns#">FAQ</category><category domain="http://www.blogger.com/atom/ns#">Storage Space</category><category domain="http://www.blogger.com/atom/ns#">Urchin Database</category><category domain="http://www.blogger.com/atom/ns#">Reports</category><category domain="http://www.blogger.com/atom/ns#">Raw Data</category><title>Urchin Q and A: What's Taking Up Storage Space</title><description>&lt;span style="font-weight:bold;"&gt;Question:&lt;/span&gt; Is the main consumer of storage space the raw data and Urchin report data folders?  &lt;br /&gt;&lt;span style="font-weight:bold;"&gt;&lt;br /&gt;Answer:&lt;/span&gt; Yes, the main consumer of storage space is the raw data and reports.  You can estimate the size of the proprietary Urchin databases to be ~10% of the size of the raw logs that were processed to populate the Urchin databases.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6329594498573451684-2448227132691728596?l=urchinexperts.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://urchinexperts.blogspot.com/2008/11/urchin-q-and-whats-taking-up-storage.html</link><author>noreply@blogger.com (-EpikLabs-)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6329594498573451684.post-4369987844814053849</guid><pubDate>Mon, 24 Nov 2008 16:57:00 +0000</pubDate><atom:updated>2008-11-24T13:08:10.978-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">FAQ</category><category domain="http://www.blogger.com/atom/ns#">MySQL database</category><category domain="http://www.blogger.com/atom/ns#">Urchin Configuration</category><title>Urchin Q and A: MySQL Database Size</title><description>&lt;span style="font-weight:bold;"&gt;Question:&lt;/span&gt; Can we expect the MySQL database size to grow?  &lt;br /&gt;&lt;span style="font-weight:bold;"&gt;&lt;br /&gt;Answer:&lt;/span&gt; You can expect the SQL database to grow, only as much as you add users/groups/accounts and profiles to your Urchin configuration.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6329594498573451684-4369987844814053849?l=urchinexperts.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://urchinexperts.blogspot.com/2008/11/urchin-q-and-mysql-database-size.html</link><author>noreply@blogger.com (-EpikLabs-)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6329594498573451684.post-7991022613822485656</guid><pubDate>Mon, 24 Nov 2008 16:51:00 +0000</pubDate><atom:updated>2008-11-24T13:07:54.647-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Data Storage</category><category domain="http://www.blogger.com/atom/ns#">FAQ</category><category domain="http://www.blogger.com/atom/ns#">Urchin Database</category><category domain="http://www.blogger.com/atom/ns#">MySQL database</category><category domain="http://www.blogger.com/atom/ns#">Configuration Data</category><title>Urchin Q and A: What's Stored in the MySQL Database</title><description>&lt;span style="font-weight:bold;"&gt;Question:&lt;/span&gt; What is stored in the MySQL database?  &lt;br /&gt;&lt;span style="font-weight:bold;"&gt;&lt;br /&gt;Answer:&lt;/span&gt; Urchin configuration data is stored in the SQL database.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6329594498573451684-7991022613822485656?l=urchinexperts.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://urchinexperts.blogspot.com/2008/11/urchin-q-and-whats-stored-in-mysql.html</link><author>noreply@blogger.com (-EpikLabs-)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6329594498573451684.post-6591131814052343589</guid><pubDate>Mon, 24 Nov 2008 16:45:00 +0000</pubDate><atom:updated>2008-11-24T13:07:23.524-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">FAQ</category><category domain="http://www.blogger.com/atom/ns#">Report Data</category><category domain="http://www.blogger.com/atom/ns#">Databases</category><category domain="http://www.blogger.com/atom/ns#">proprietary database</category><category domain="http://www.blogger.com/atom/ns#">Data</category><category domain="http://www.blogger.com/atom/ns#">Urchin Reports</category><title>Urchin Q and A: Data Storage Format</title><description>&lt;span style="font-weight:bold;"&gt;Question:&lt;/span&gt; What format are the Urchin reporting data stored in?  &lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Answer: &lt;/span&gt;&lt;br /&gt;Urchin report data is stored in proprietary databases.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6329594498573451684-6591131814052343589?l=urchinexperts.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://urchinexperts.blogspot.com/2008/11/urchin-q-and-data-storage-format.html</link><author>noreply@blogger.com (-EpikLabs-)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6329594498573451684.post-2470647627587669068</guid><pubDate>Mon, 24 Nov 2008 16:42:00 +0000</pubDate><atom:updated>2008-11-24T13:07:03.965-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">FAQ</category><category domain="http://www.blogger.com/atom/ns#">Traffic Breakdown</category><category domain="http://www.blogger.com/atom/ns#">Traffic</category><category domain="http://www.blogger.com/atom/ns#">Traffic Reporting</category><title>Urchin Q and A: Traffic Breakdown</title><description>&lt;span style="font-weight:bold;"&gt;Question:&lt;/span&gt; Does Urchin reporting provide a breakdown of average traffic by hour of the day?  &lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Answer:&lt;/span&gt; No, Urchin does not provide a breakdown of average traffic by hour of the day.  We lost this reporting after version 3.X.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6329594498573451684-2470647627587669068?l=urchinexperts.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://urchinexperts.blogspot.com/2008/11/urchin-q-and-traffic-breakdown.html</link><author>noreply@blogger.com (-EpikLabs-)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6329594498573451684.post-1324998509870432183</guid><pubDate>Mon, 24 Nov 2008 16:33:00 +0000</pubDate><atom:updated>2008-11-24T13:06:39.708-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Report Window Configuration</category><category domain="http://www.blogger.com/atom/ns#">FAQ</category><category domain="http://www.blogger.com/atom/ns#">Report Issues</category><category domain="http://www.blogger.com/atom/ns#">Urchin Reports</category><title>Urchin Q and A:Report Window Configuration Limit</title><description>&lt;span style="font-weight:bold;"&gt;Question:&lt;/span&gt; In the report window, there is a drop down where the number of results to display can be changed.  The upper limit seems to be 500.  Is this upper limit configurable to a larger number?&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;&lt;br /&gt;Answer:&lt;/span&gt; Unfortunately, there is no built-in configuration option for the values available in the drop-down. These values are hardcoded into an HTML template (~/urchin/lib/reporting/templates/main_rform.tpl).  You can increase this value at your own risk!  Bear in mind, this change might slowdown Urchin output and/or cause Urchin server timeouts.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6329594498573451684-1324998509870432183?l=urchinexperts.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://urchinexperts.blogspot.com/2008/11/urchin-q-and-areport-window.html</link><author>noreply@blogger.com (-EpikLabs-)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6329594498573451684.post-4416879870369333540</guid><pubDate>Mon, 24 Nov 2008 15:49:00 +0000</pubDate><atom:updated>2008-11-24T11:04:51.744-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Traffic Filters</category><category domain="http://www.blogger.com/atom/ns#">Accurate Data Reports</category><category domain="http://www.blogger.com/atom/ns#">Traffic</category><category domain="http://www.blogger.com/atom/ns#">Urchin Reports</category><category domain="http://www.blogger.com/atom/ns#">Applying Filters</category><title>Urchin 6 and Filters</title><description>&lt;span style="font-weight:bold;"&gt;Two Filters We Often Recommend:&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;Filters are applied to the information coming into your Urchin reports in order to manipulate the data and provide accurate reports. Filters can be set up to exclude visits from particular IP addresses, to report only on a sub-domain or directory, or to take dynamic page URLs and convert them into readable text strings.  &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;First, we highly recommend creating a filter to exclude internal traffic from your Urchin reports as this data set isn’t an accurate representation of how your visitors are using your site. &lt;br /&gt;&lt;br /&gt;To exclude internal traffic from your Urchin reports, follow these steps: &lt;br /&gt;&lt;br /&gt;1 - Navigate to Configuration -&gt; Urchin Profiles -&gt; Filter Manager in the Urchin administration interface.  &lt;br /&gt;2 - Click the "Add" button to create a new filter.  &lt;br /&gt;3 - Choose "Filter Out Internal Traffic" from the "Select Example Filters" dropdown menu.  &lt;br /&gt;4 - Replace the sample IP address in the "Filter Pattern" box with the IP address you wish to filter out.  &lt;br /&gt;5 - Click "Finish".&lt;br /&gt;6 - On the next window, click "More Options".  &lt;br /&gt;7 - Select all the Profiles you want to apply the filter to in the "Available Profiles" box, and then click the right arrow to transfer them to the "Applied To" box.  &lt;br /&gt;8 - Click "Update" to apply the filter to the selected Profiles.  &lt;br /&gt;&lt;br /&gt;Second, in order to ensure Urchin is not capturing unique page views as multiple pages due to different character cases being used, we highly  recommend implementing this filter that forces the URI to lowercase.  &lt;br /&gt;&lt;br /&gt;As an example, Urchin will think “Default.aspx” and “default.aspx” are two separate pages, thus dividing pageview data.  &lt;br /&gt;&lt;br /&gt;Urchin has an advanced log setting that can force the URI to lowercase thus consolidating hits to the same page. &lt;br /&gt;&lt;br /&gt;To force the URI to lowercase, follow these steps: &lt;br /&gt;&lt;br /&gt;1 - Navigate to Log Manager in your Urchin GUI.  &lt;br /&gt;2 - Select a log source by clicking on the Edit icon.  &lt;br /&gt;3 - Click the "Advanced Settings" tab. There will be an option for "URI Stem to Lower Case". Select the "On" radio button. This will force all URIs in the reports to lower case, thus making the data uniform and easier to analyze.  &lt;br /&gt;&lt;br /&gt;Implementing these filters will help make the data in your Urchin reports uniform and easier to analyze, and more accurately represent visitor interaction with your website&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6329594498573451684-4416879870369333540?l=urchinexperts.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://urchinexperts.blogspot.com/2008/11/urchin-6-and-filters.html</link><author>noreply@blogger.com (-EpikLabs-)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6329594498573451684.post-4767714549943885461</guid><pubDate>Mon, 24 Nov 2008 15:35:00 +0000</pubDate><atom:updated>2008-11-24T13:05:36.048-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">User Agent Detection</category><category domain="http://www.blogger.com/atom/ns#">FAQ</category><category domain="http://www.blogger.com/atom/ns#">UserAgent</category><category domain="http://www.blogger.com/atom/ns#">Mobile User-Agents</category><category domain="http://www.blogger.com/atom/ns#">Mobile Device</category><category domain="http://www.blogger.com/atom/ns#">Mobile Browsers</category><category domain="http://www.blogger.com/atom/ns#">Activity Tracking</category><title>Urchin Q and A: Moblie Device Activity Tracking and UserAgent Detection</title><description>&lt;span style="font-weight:bold;"&gt;Question:&lt;/span&gt; What is your recommended solution for mobile device activity tracking to include user agent detection? &lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Answer:&lt;/span&gt; You can use the IP+UserAgent tracking method for mobile browsers.  However, you would have to inspect your log files to see if they log device specific information.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6329594498573451684-4767714549943885461?l=urchinexperts.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://urchinexperts.blogspot.com/2008/11/urchin-q-and-moblie-device-activity.html</link><author>noreply@blogger.com (-EpikLabs-)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6329594498573451684.post-570812347668118216</guid><pubDate>Mon, 24 Nov 2008 15:16:00 +0000</pubDate><atom:updated>2008-11-24T13:03:50.973-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">FAQ</category><category domain="http://www.blogger.com/atom/ns#">Report Data</category><category domain="http://www.blogger.com/atom/ns#">Urchin Database</category><category domain="http://www.blogger.com/atom/ns#">SQL database</category><category domain="http://www.blogger.com/atom/ns#">proprietary database</category><category domain="http://www.blogger.com/atom/ns#">Configuration Data</category><title>Urchin Q and A: Urchin6 and data storage</title><description>&lt;span style="font-weight:bold;"&gt;Question:&lt;/span&gt; What types of data is stored in the Urchin6 database?  Is it only the configuration data or both configuration data and report data? &lt;br /&gt;&lt;span style="font-weight:bold;"&gt;&lt;br /&gt;Answer:&lt;/span&gt; The SQL database is used solely for the purposes of storing the configuration data.  Report data is still stored in Urchin Software's proprietary databases.  .&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6329594498573451684-570812347668118216?l=urchinexperts.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://urchinexperts.blogspot.com/2008/11/urchin-q-and-urchin6-and-data-storage.html</link><author>noreply@blogger.com (-EpikLabs-)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6329594498573451684.post-2852783085316816016</guid><pubDate>Fri, 24 Oct 2008 21:40:00 +0000</pubDate><atom:updated>2008-10-24T17:47:00.286-04:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Urchin 5</category><category domain="http://www.blogger.com/atom/ns#">FAQ</category><category domain="http://www.blogger.com/atom/ns#">individual record defined</category><category domain="http://www.blogger.com/atom/ns#">Urchin 6</category><title>Urchin Q and A:  "Individual Record" Defined</title><description>&lt;span style="font-weight: bold;"&gt;Question:&lt;/span&gt;  Can you define what an "individual record" is? Is it a single hit from the access log?&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;Answer:&lt;/span&gt;  A 'record' is a table row which contains a whole host of information based on the visit.  It is not a single hit from the access log.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6329594498573451684-2852783085316816016?l=urchinexperts.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://urchinexperts.blogspot.com/2008/10/urchin-q-and-individual-record-defined.html</link><author>noreply@blogger.com (Epik Phil)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6329594498573451684.post-3891801069026921997</guid><pubDate>Wed, 22 Oct 2008 21:59:00 +0000</pubDate><atom:updated>2008-10-22T18:05:42.937-04:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">FAQ</category><category domain="http://www.blogger.com/atom/ns#">Installation and win2000</category><category domain="http://www.blogger.com/atom/ns#">Urchin 6</category><title>Urchin Q and A:  Urchin 6 Installation and Windows 2000</title><description>&lt;span style="font-weight: bold;"&gt;Question: &lt;/span&gt; I have tried to install Urchin 6 on Win2000 server using PostgreSQL and MySQL, and it does not install correctly. The Urchin services crash and the bundled Apache web server service won't start.   Do you have any suggestions or tips on how to get this successfully installed? &lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;Answer: &lt;/span&gt; There are no known issues with installing Urchin on the platform you described.  This leads us to believe there is something at the system level that is interfering with the installation of Urchin.  For example, if you are using a password generator, the passwords created may contain special characters that are interfering with Urchin's configuration file (urchin.conf).  Urchin stores its database login information unencrypted in the urchin.conf file. &lt;br /&gt;&lt;br /&gt;For example, if the password created contains a '#' sign, this is also a comment character in Urchin's configuration file.  Thus, your database login will fail, and the Urchin services will keep failing. &lt;br /&gt;&lt;br /&gt;Unfortunately, Urchin does not log error messages to aid in troubleshooting installation and runtime errors.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6329594498573451684-3891801069026921997?l=urchinexperts.blogspot.com' alt='' /&gt;&lt;/div&gt;</description><link>http://urchinexperts.blogspot.com/2008/10/urchin-q-and-urchin-6-installation-and.html</link><author>noreply@blogger.com (Epik Phil)</author><thr:total>0</thr:total></item></channel></rss>

