I was in a situation where multiple analytics keys were needed and saw this was possible through the "after" field. Since this is not very user-friendly to end-users I decided to adjust the module a bit.

With the attached patch the end-user can simply enter multiple numbers in the account field (seperated by semicolons) to track multiple accounts.

Maybe a nice feature for future versions?

CommentFileSizeAuthor
ga.patch4.67 KBmarkwittens

Comments

hass’s picture

hass commented
Status: Active » Closed (won't fix)

Normally you should not track one site in multiple accounts. There is no reason to do so and you loose page load time (bad UX), too.

This feature is very special. Why should we implement something so special that is only used by a handfull of sites and that is only a ONE time configuration? Additional this advanced settings are not for end-users :-). It's for hardcore or crazy admins... there are so many people who already have issues entering only their UA code into one field and press save... :-( - telling them they are able to add more than one UA would be more hard for them and I'm not very willingly to support this. I tend to say won't fix for this edge case.

daveparrish’s picture

daveparrish commented

I'm not a crazy admin (in my opinion) but I have a client who wanted to move a website profile from an account to another account. He wanted to be able to have two accounts tracking the website so he could keep the account running with the history as well as the separate account which he could give other users administrative access. For a situation like this, I think adding the functionality to add multiple accounts would be nice.

joshua.stout’s picture

joshua.stout commented

I agree this is helpful. I have a client with the same situation.

newmediaist’s picture

newmediaist commented

You should be able to do this already in the module using the Google Analytic Config -> Advanced Settings -> Code Snippet (After) section, adding something like:
_gaq.push(['_setAccount', 'UA-XXXXX-X']);
_gaq.push(['_trackPageview']);

I would think the performance impact would be very minimal, as you have already loaded the GA code and are just sending a one-way request to the GA servers.

see http://drupal.org/node/697168 for more discussion on this -