We Keep Coding

How to add multiple Google Analytics trackers on website? (HTML, JS)

I'm working on a portfolio, and I had an idea to add a section saying:
"My work has been seen by this __ many people."
In order to do this I have settled on using ShowMyStats, but in order to get that stats, I need to add another Google Analytics tracker to all the websites I manage. Is this possible? I've seen something answering this question here on stackoverflow, but it didn't work. Any ideas? All help appreciated.
Original post

It's best to use GTM to manage your ga trackers/properties. It becomes a trivial task that way. Here is a good article that goes quite deeply into the matter: https://www.simoahava.com/gtm-tips/send-google-analytics-tag-multiple-properties/
Another concern here is that it seems unlikely that an extension like that requires a new property. Why not just feeding it your existing property?
Your older question's accepted answer actually answers the question pretty well. Provide your debugging and fixing efforts for us to be able to move forward.
Finally, Google is deprecating GA UA, so you probably want to stop doing it for UA and start implementing it for GA4, which makes your code snippets obsolete, but also makes a good case for using GTM, since switching from UA to GA4 via GTM is a lot easier than via code. GTM tends to do its best to abstract the code from the users while still allowing liberal code injections.

How can web and error events be logged to Splunk using node.js?

I've found plenty of documentation on how to perform Splunk searches from within Node.js (thanks in chief to the Splunk javascript SDK documentation).
However, that's not what I'm trying to accomplish. I am hoping to use Splunk as my logging/monitoring/analytics solution for a site which is driven by node.js. I need to be able to log different types of events (login errors, page requests/responses, etc) for Splunk to index and make usable.
How can this be accomplished? Is it part of the SDK (or the API itself) that I'm just overlooking?
Thanks for any insight.

At our recent Splunk Conference we held a Hackathon and one of the winners actually developed a Splunk transport for Winston. You can grab it from github.

Take a look at Winston. This is a framework similar to Log4Net or Log4J which provides variable log levels and transport options.
They do not appear to have a "transport" / plug-in for Splunk, but they have several others including the relatively similar Loggly. They also have instructions on rolling your own, so it looks like a good place to start.

how to make own custom widgets like facebook social plugins?

How do I make my own widget just like facebook? https://developers.facebook.com/docs/guides/web/#plugins
Basically it's a bit of javascript, css and html code, but how to do it?
Any example, tutorials?

I highly recommend Third Party Javascript (Manning) from the guys at Disqus for a great overview of everything. While it won't give you a magic bullet solution for your SDK/widget-making, it will help you bullet-proof things as you go. It's a great reference, if short/concise and the code is definitely not for JavaScript beginners.
As to how Facebook does it, while it's not fully descriptive of their iframe/widget approach, it shows how they do bullet-proof embedding in non-standard webpages: http://calendar.perfplanet.com/2011/the-art-and-craft-of-the-async-snippet/
For extra bonus points, combine that with http://www.phpied.com/non-onload-blocking-async-js/ and it should get rid of the loading spinner in all but iOS 6 if memory serves me well.
For even more advanced iframe fun, see https://github.com/benvinegar/seamless-talk and any other slides/posts at http://benv.ca/. (I think I'd like to meet Ben one day, given how much of his stuff I've been borrowing from lately, and he's a fellow Canadian to boot.)
Note that seamless iframes, as a native browser concept, are webkit-only and buggy at that: https://bugs.webkit.org/show_bug.cgi?id=99289 (On Firefox, dev. is stopped due to an 11-year old bug? https://bugzilla.mozilla.org/show_bug.cgi?id=631218) So for the foreseeable future, iframe customization will require JavaScript. :)

Look here for a tutorial on how to build your own widget using JSONP:
http://alexmarandon.com/articles/web_widget_jquery/
and here on how to make it secure:
http://wordpress.tv/2011/08/31/mike-adams-developing-secure-widgets-secure-iframe-communication-in-a-pre-postmessage-world/

You can do this with the Facebook Javascript SDK (see https://developers.facebook.com/docs/reference/javascript/). You need to understand the Graph API (see https://developers.facebook.com/docs/reference/api/) which you can query from the Javascript SDK. Throughout Facebook's documentation there's tonnes of example code. Have fun!

Non-invasive javascript performance agent?

I am seeking to (legitimately) plant bugging in my web pages to collect and report information about website performance.
Preference for internally hosted. While I expect that there are commercial offerings out there (e.g. Google Analytics) I'm keen to find something we can run entirely in-house (its not a public website and may contain sensitive data).
Also, I'm looking for something where it can report back to an independent URL - i.e. not relying on adding in a reverse-proxy / recording results within existing webserver logs. Indeed, I'd prefer something which does not require access to the webserver logs logs at all (other than those for the URL the bug reports back to).
I need to be able to monitor bulk traffic - so things tools like pagespeed and tamperdata are not appropriate.
I've tried googling but just seem to be getting lots of noise about the performance of javascript and web pages rather than how to actually measure these.
TIA

You could use the open source analytics software Piwik and write a plugin for it that sends the performance data to it.

Thanks chiborg. I'd kind of forgotten about this it was so long ago I asked. Yes, I was aware of PiWik - but not been very impressed with either its implementation nor the quality of documentation.
I'm currently working on a solution using Boomerang.

Hosted Yui, Google maps, JQuery - an easy way of monitoring website usage?

The Yahoo Javascript library (YUI), JQuery and less so Google maps all allow you to reference their files using the following format:
<script type="text/javascript" src="http://yui.yahooapis.com/2.6.0/build/yahoo-dom-event/yahoo-dom-event.js"></script>
This does a request for the script from their servers, which will also pass to their web server the HTTP referrer. Do Yahoo etc. use this to produce statistics on which websites get what traffic? Or is this a conspiracy theory?
Of course their servers most of the time will be a lot faster than any small company would buy, so using the hosted version of the script makes more sense.

Chris,
I work on the YUI team at Yahoo.
We host only YUI on yui.yahooapis.com; Google hosts YUI and many other libraries on its CDN. I can tell you from the Yahoo side that we don't monitor site usage of YUI from our CDN. We do track general growth of yui.yahooapis.com usage, but we don't track which sites are generating traffic. You're right to suggest that we could track usage -- and we state as clearly as we can in our hosting docs that you should only use this kind of service if the traffic logs generated on our side don't represent a privacy concern for you.
In general, though, I don't regard CDN traffic for library usage to be a reliable measurement of anything. Most YUI usage, even at Yahoo, doesn't use yui.yahooapis.com or Google's equivalent, and I'm sure the same is true for other libraries. And even when a site is using YUI from our servers, we wouldn't have comprehensive traffic data of the kind you'd get from Google Analytics or Yahoo Analytics -- because not all pages would use YUI or the CDN uniformly.
Given the advantages of the hosted service -- including SSL from Google and YUI combo-handling from Yahoo -- I see the CDN as being a big win for most implementers, with little downside.
-Eric

Of course they produce statistics - at minimum they need to know how many resources they spend on hosting these scripts. And it's also nice to know who uses your code.
I don't think it's a bad thing.
And using a hosted version makes even more sense because your visitors might have the script already cached after visiting another site.

Sure, they can easily have statistics about which sites use YUI and how often, and also which parts of YUI API are more populare (among small sites). However, they cannot know what exactly web site visitors do with their libs.
Given, that they (Google & Yahoo) index a lot of web pages, they can get an even more precise statistics if they analyze their indexes. So you cannot hide that you are using YUI if your site is public.
The same applies to Google maps and jQuery.