• You can do this in a skin. The problem is that you bind your skin to your portal. All the skins I use on that portal must be modified and can't be used outside of it.
• You can do it n the Copiright field of the portal. There are two problems with this one. First, the database field is only 100 chars, and the javascript is more than that. You could modify the db field to 200 chars, but DNN internally truncates the copyright field anyway. The second problem is that the copyright field gets int the every page header too, not only in the [COPYRIGHT] tag of the skin.
• You could use a special HTML/Text module that you repeat in each page. This is not really handy.

The best way would be a simple skin object i have one i did for 3.x that you can have

email at dylan.barber@earthlink.net or MSN IM at the same address

• gryff_1000: I was aware of that module before I posted my question. A sepcific module on each page is technically a solution. But the thing I want is to be able to manage this extra javascript at the portal level. I don't want to have to check every page regularly if it has the module, because someone might inadvertantly remove it on a specific page.
• famdylan: the skin solution ties your skin to your portal and vice-versa. I want to be able to buy a skin and use it. Not having to modify it for each portal I have.
  
• greenflash: This would be my solution of choice if it weren't that ... default.aspx is there for ALL the protals. That way I wouldn't be able to differentiate the different portals in Google Analytics.