google analytics

Google analytics are... showing not all visitors. Can this be related to some of performance module?

Posted by playfulwolf on March 6, 2010 at 2:59pm

Hi,

Have a site with:
-CacheRouter with db caching
-APC on the server, but not used with CacheRouter
-Boost with default-agressive settings, crowler enabled
-JS minify + gzip
-CSS gzip
-block cache module enabled
-"Normal" drupal cache
-Paged are gzipped by drupal
-GA code is in footer

-Google Analytics module was used with "cache locally" and without - but no change.

-All the internal Google Analytics indicators is showing that everything is ok, some stats is available.

-JS minify+gzip is enabled, but I clearly see the .js file, which is accesible.

Cache och statistik

Posted by _dala_ on December 9, 2009 at 12:23pm

Jag vill med det här inlägget berätta om ett problem jag stött på i mitt arbete och tipsa om en tänkbar lösning på detta. Problemet är ett krav på tillförlitlig och (relativt) uppdaterad statistik på ett välbesökt community utan att tappa för mycker prestanda. Statistiken gäller unika sidvisningar per inlägg.

The CASAA module has been released.

Posted by cntlscrut on July 21, 2009 at 10:13pm

I have released the core framework module for the CASAA (Context Ad Serving and Analytics) framework module.

For those of you that aren't aware of what the module is, the system is a plug-able framework that handles ad serving and analytics systems such as, Google Analytics, OAS ad server, Omniture Site Catalyst, Yahoo! APT, plus many other systems.

The framework contains a developer API to allow developers to create new plug-ins for the framework that aren't currently supported.

Drupal Analytics

Posted by jtsnow on March 23, 2009 at 6:26pm

Overview: This project will improve the tracking and analysis of website traffic in Drupal.

Description: There is a need for better traffic analysis in Drupal. A possible implementation of this project may involve writing a script separate from Drupal that accesses server logs directly. Other features may include an API to allow contrib modules to log events or a way to send statistics to third party tools, such as Google Analytics.

Some ideas:

Provide both client and server side tracking APIs.
Access server logs to get statistics for files and requests not served by Drupal (JavaScript, images, other files).
Be aware of Drupal's page caching mechanisms and work around those.
Track actions- Use actions as 'goals'?
Track JavaScript events.
Extensibility: Allow analysis plug-ins to be made.
Performance is a big factor! Traffic tracking shouldn't produce a too big of a load on the system, whether it is database size or performance when actually loading the page.

Please share your thoughts and ideas.

Mentors:

Difficulty: Hard