[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: |
|
||||||||
| 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. This shouldn't be a big problem to implement with JQuery, because the JS's get executed after the html structure is available. So this should be implemented into STK:
Some more info I found about the GA-Tracker and JQuery: |
| 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: Now you launch on Christmas an contest for winning something below shop. 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. |
| 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 I guess the use case i read is from when you can't ignore the results -> generated reports matter on its numbers. |
| 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: |
| 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. |