fast_cache and lost of anonymous stats - what about google analytics/piwik?
igorik - April 4, 2009 - 16:49
| Project: | Cache Router |
| Version: | 6.x-1.x-dev |
| Component: | Documentation |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
Hi
I read you wrote about fast_cache option:
"fast_cache is new in beta8 for turning page_fast_cache on. WARNING: you will not get Anonymous statistics if you use this option. Please set it to FALSE if you want to get Anonymous statistics."
I am not sure how it coworks with internet statistics e.g. google analytics or piwik? If I enable fast cache, will be number of anonymous visitors drastic different/lower?
Thanks for your explanation
Igorik
http://www.somvprahe.sk

#1
GA works fine for me like all js based
With fast cache enabled most anonymous visits are retrieved from cache without DB so no drupal modules are invoked
#2
This only affects the "Statistics" module in drupal core. GA/Omniture, etc will all work fine.
#3
Automatically closed -- issue fixed for 2 weeks with no activity.
#4
Thanks for this. Had the exact same question.
So for anonymous users, it is best to look at google analytics with fastcache on?
And can I use stats module for logged in users?
Thanks,
Chris
#5
@activelyOUT GA code works fine
What is stats module?
#6
statistics module
#7
As for statistics module, I would consider that unreliable, as it will measure both logged in users, and cache-missing anonymous users (i.e. visiting a page that didn't get cached before, or expired), so the result will be dependent on the structure of anonymous visits (i.e. users hitting popular content won't get measured, because that will be mostly served from cache, but search engines crawling all old/forgotten content that no one else reads, will get measured, because all these pages will be hit first time in a long period and so not available in cache).
I'm unsure though, whether it makes sense to run statistics module with cache router. If your site is so busy, that performance of caching is a concern, then statistics module is a good candidate to be dropped, as it writes/updates its tables in database on every single page view [where it gets a chance].
#8
@activelyOUT dont use statistics for sites with cache - try different GA/spylog...
#9
Automatically closed -- issue fixed for 2 weeks with no activity.