We are still waiting on information on what the status of your Urchin/Google Analytics situation is at this time. When we know something accurately I will get it posted here. In the meantime, I hope to answer a few side questions in this thread.
QUOTE(basketsforher @ Nov 14 2005, 06:27 AM)
I never added the code to my site that google says to add - how is this info getting to them? [right] [snapback]96444[/snapback] [/right]
If you have had Urchin On Demand and MC set it up for you, you should note that there is a string of code in the <head /> section referenced on every page of your site with MC -
CODE
<script src="__utm.js" type="text/javascript"></script>
- and it is this file that logs all information and collects it for the Urchin system. The new Google Analytics appears to me to use a slightly different code string that will need to be added PER client, but will work the same way.
QUOTE(rubberstampingfun @ Nov 14 2005, 07:45 AM)
When I submit my ticket to monstercommerce to have "urchin removed" I am hoping they will be kind enough to simply stop charging me instead of actually removing the __utm.js file and messing up the statistics??[right] [snapback]96447[/snapback] [/right]
QUOTE(rubberstampingfun @ Nov 14 2005, 07:47 AM)
If

removes the __utm.js reference from the <HEAD> section when I submit my ticket today to have the stats "removed" will I lose the archive data?[right] [snapback]96449[/snapback] [/right]
QUOTE(rubberstampingfun @ Nov 14 2005, 08:27 AM)
MC, can you comment on what happens when I submit my ticket to "remove" Urchin On Demand so as not to be charged...will you also automatically remove the reference to the __utm.js script from all of the pages and therefore remove all of my archived data? [right] [snapback]96453[/snapback] [/right]
If you request that your Urchin On Demand account be removed, there are a couple steps that we take. The first is to send the ticket to billing to have that addressed first. From there, the ticket will be worked on by tech reps who will remove the setting that references the "__utm.js" file. This alone will simply stop new statistics from being collected, but will not delete old information. However, the other (and final) step to this is to turn off access to the Urchin reports page where this information is collected and disable your username. Any statistics in the 'archive' will be unavailable at that time.
You should be able to access standard Urchin 5 and the data available to Urchin 5 can be backdated if it is not currently being logged.
My advice is to hold off for at least the next few days as we get things straightened out for this new service. It may be (I hope) that we can smoothly transition from Urchin On Demand to Google Analytics with out any work on anyone's part. Optimally, there may be a small amount of changes that need to be done per site or per account and we may be able to script this out to get it done very quickly. Of course, this is being optimistic, but I don't want anyone to cancel their Urchin On Demand account and lose that data and then realize that they could have had it connected with their original account... Anyhow, thanks for your patience.