Receive new blog posts immediately direct to your email inbox!
The ROI Revolution Blog
« Tracking Subdomains | Main | New Graphing Options »
All About Historical Data
April 2, 2008
Everybody makes mistakes at some point, but there are ways to help prevent those mistakes from making their way into your Google Analytics reports.
With Google Analytics, you do not have the option to reprocess data like you do with log file analytics systems, so it's important that you are cautious with the changes you're making to your profiles.
If you set up a new filter incorrectly and no one notices for two weeks that you are collecting the wrong data, there is no way to go back and reprocess that data. It's gone and it's not coming back. Because of this, it is highly recommended that you make your filter, goal, and/or funnel changes to a test profile before making them to your main profile. By collecting the results in a test profile, you can gauge whether or not you are receiving the outcome you anticipated.
Likewise, if you create a new filter or goal, it will only affect the data from that point moving forward. For example, if you only want to include visitor traffic to a specific subdirectory, your historical data will still include visitor traffic to the rest of your site. This can also make things tricky with goals and funnels.
Also, if you create a new profile for an existing domain, you will not have access to historical data within that new profile. Profiles only collect data that is processed after they were created, so you may want to create several profiles at once if you think you may want to use the historical data in a later profile.
Recently, Google Analytics had introduced a new feature called Benchmarking, where you can see your stats compared to others' in your industry. If you decide to opt-in to data sharing, Google Analytics will include historical data up to a month before your opt-in date.
And for those of you who haven't switched over from urchin.js yet, historical data will be kept when you move your site over to ga.js, so don't worry.
So don't forget to test before you implement anything new to your main profile, and consider keeping a change log of the changes to your profiles. Remember that any changes you make won't change your historical data.
Interested in learning more about Google Analytics?
Attend our LIVE Google Analytics Seminars for Success training in Atlanta, GA Wednesday, April 14th, 2010 and Thursday, April 15th, 2010 or get the latest tips and tricks sent to you via our free, twice-monthly Google Analytics newsletter.
Posted by Caitlin Cook, Analytics and Optimization Specialist at 9:40 AM
Permalink | Comments ( 2 ) | TrackBacks ( 0 )
Filed under: Analytics
Tagged as: Analytics Basics
Comments
said:@ Rachel
Well considering the large number of Google Analytics users, its really not feasible that they reprocess historical data - as this would be an enormous task. Even if you have your own log file analyzer processing data can take time, and thats only including your data! You could always make a new profile so you know that profile is the filtered data moving forward, or just keep track of when the filters were applied.
Thanks for reading!
This is my least favorite thing about GA. I wonder how we can go about effectively getting them to change this. I don't see why, if they have the data, they can't reprocess it. I'd be happy to wait over time for it to come through if it meant getting filtered data historically! We're going through a major overhaul of our website and this will definitely be a problem.
April 2, 2008 3:27 PM