[MGNLSTK-406] Google analytic for STK Created: 29/Jun/09  Updated: 23/Jan/13  Resolved: 04/Aug/09

Status: Closed
Project: Magnolia Standard Templating Kit (closed)
Component/s: concept
Affects Version/s: 1.1
Fix Version/s: 1.2

Type: New Feature Priority: Major
Reporter: Christian Ringele Assignee: Christian Ringele
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
supersession
is superseded by MGNLGA-1 Initial implementation of Google Anal... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

Google Analytics is used on many sites and is a almost de facto standard as a use case on sites.

STK should provide a easy possibility to activate/configure the Google Ananlytics.
As Google describes, the JS of GA should be placed at the very bottom before the body-end tag. See link below, point two:
http://www.google.com/support/googleanalytics/bin/answer.py?answer=55488&cbid=1th4gth8puw5m&src=cb&lev=answer

This shouldn't be a big problem to implement with JQuery, because the JS's get executed after the html structure is available.
Here i found a JS for JQuery which should work in STK, just added as a normal JS-node:
http://playground.ebiene.de/2148/google-analytics-mit-jquery/
The only static part of this JS is the '_gat._getTracker('UA-XXXXXXX-X');' which defines you GA uid.

So this should be implemented into STK:

  • A way to define the 'UA-XXXXXXX-X' value over the site configuration and hand it to the JS.
  • A option on page level, for excluding a page if it shouldn't be GA analyzed.

Some more info I found about the GA-Tracker and JQuery:
http://plugins.jquery.com/project/gaTracker



 Comments   
Comment by Philipp Bärfuss [ 30/Jun/09 ]

ideally we would use the latter (the gaTracker plugin) it brings the feature of updating all links so that tracking is easier to follow (navigation tracking)

Comment by Magnolia International [ 02/Jul/09 ]

What's the use case for having pages of one same site not analyzed ?

Comment by Christian Ringele [ 30/Jul/09 ]

The use case is, to keep some pages out of over all statistics.

When reading about GA i often found this theoretical use case for it:
You have three main parts of you website, products - service - shop with their subpages.

Now you launch on Christmas an contest for winning something below shop.
But you don't want the visits on this content being added to the over all statistics of you site, and of you shop part.
Otherwise its quite cumbersome to calculate:
all shops visits without the contest visits.

But the exclusion of a page won't be a part of the first implementation.

Another use case i often read about is on having subsections of a site analyzed into a different account/observation.
So that you could split up between products and shop section with it's single GS stats and overalls.

Comment by Boris Kraft [ 30/Jul/09 ]

I don't get it, can't imagine a use case to turn of analytics per page. Glad its not in the first release, and unless some external input provides a clear use case, analytics should be on or off per site, not per page. There is no harm to see what is happening when and where, even if you chose to ignore the results

Comment by Christian Ringele [ 30/Jul/09 ]

I won't implement it
And am really wondering too, if there will be a real use case from reality.

I guess the use case i read is from when you can't ignore the results -> generated reports matter on its numbers.
I somebody pays your site for commercials you put on, but wants that a some site doesn't count into the over all hits (less paying).
That's the only situation i could image.
Reports form GA and somebody pays for numbers, but not for hits on a specific pages.

Comment by Magnolia International [ 31/Jul/09 ]

I don't know if you guys know about this, but it could be interesting to see how to work/integrate with piwik:
http://piwik.org/

Comment by Boris Kraft [ 31/Jul/09 ]

Well, yes and no. In the sales process, people understand that we are a CMS and not analytics, and typically want to integrate with whatever is their favorite tool. Knowing that we do provide Google Analytics makes them understand that this is possible. I feel that integration with other tools should best be left to the community, as there is no real benefit for us (unless of course we integrate with something absolutely state-of-the-art which provides us with a significant competitive advantage).

One of the ideas I recently discussed with C. is to selectively get some of the G.A. data back into Magnolia and display some key figures directly in Magnolia; or at least provide direct links for each page to its G.A. report.

Comment by Magnolia International [ 31/Jul/09 ]

Entirely agree, just thought i'd mention the alternative (about the only one who can compete with GA, at least in terms of sexy reports; as far as I know anyway).

Comment by Boris Kraft [ 31/Jul/09 ]

yep, its definitely worth collection thee bits!

Comment by Christian Ringele [ 04/Aug/09 ]

Task is implemented as own module, see linked task in module project.

Generated at Mon Feb 12 07:26:43 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.