Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...DNN and Google AnalyticsDNN and Google Analytics
Previous
 
Next
New Post
4/16/2009 12:28 PM
 

Hi just a quick question about this.

I followed someones instructions to copy the code that google give you to put into the site to link it with the google analytics into a hiddle text/html module on each page of my site. However just logging into google now, it says that we havnt had any site traffic at all. Does anyone know if this method should work?

If not could anyone tell me a better way to link the dnn site with google analytics?

Thanks.

James

 
New Post
4/16/2009 12:54 PM
 

That's the approach I have used without problems. It usually takes a few hours to a day before site traffic data begins to show up in Google Analytics. Here are a couple of point to check in making this work:

1. Place the Google Analytics code in the Header, not the content of the Text/Html module.
2. Make sure that you have set the View permission for the module to "All Users"

I have also seen a few Google Analytics modules or skin objects available for DNN but have never tried any of them. Check Snowcovered.com or the DNN Marketplace for more information.


Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
4/16/2009 2:27 PM
 

I included the code into my skin files (directly at the end of the code in the .ascx files, without a skin object), and this works as well. But to use a single HTML module for all pages makes it easier to maintain the code if you have more than one skin. On the other hand, Google recommends (AFAIR) to put the code at the end of the page's HTML, and you cannot do that with a module if your skin contains footer elements.

 
New Post
4/16/2009 4:58 PM
 

Mart'n is correct:  Google does currently recommend end-of-page placement for GA code.  (Originally it was the other way around.)
 
Skin placement is the best method overall (truer end-of-page placement plus slightly less page load effort for DNN compared to a dedicated GA module).  However, I've also used module header/footer as well as the content area of Text/HTML modules (must use "source" view when adding code) without issue. I doubt the average DNN website would see any variation in site performance or GA report data between the three approaches.
 
-mamlin


esmamlin atxgeek.me
 
New Post
4/16/2009 11:30 PM
 

I think the skin method for GA is the worst method to use.

Here's why:

1) you can't use a skin on more than one site : the skin is tied into the site.  Many people use bought skins, and have to merge changes to get updates to those skins.

2) putting the code in the skin file means you track every single page on your DNN install, including admin and host pages.

3) you can't easily modify the code to take advantage of more advanced GA settings like timeouts, etc, without uploading a new skin.

4) you can't easily disable the tracking calls for testing/staging domains

A module based approach is much better.  There are many around, including free ones.  I develop and maintain a free analytics module, which you can get from http://www.ifinity.com.au/Products/Google_Analytics_Script_Module/

This module has the following benefits:

- only place on the pages you want tracked

- can exclude tracking for set security groups (ie admins).  This stops your admin behaviour skewing statistics

- can modify the default timeout for the 'bounce' time

- tracks clicks to external links from your site (so you can see where your visitors are going after clicking a link)

- can exclude certain domain names (ie localhost) from tracking

- easily and quickly added to any site without skin modification

- inserts the tracking code at the end of the html page, per google guidelines

- can track registered users as an analytics segment

Given that analytics modules are freely available and have more features than skin based or 'head' based tracking, I think that every DNN site using Analytics should use one. 

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...DNN and Google AnalyticsDNN and Google Analytics


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out