4.1 Several questions

Marc,
1) Yup, the Google Analytics stuff looks broken. We misread some of the docs, and implemented something a little off. It will be fixed in 4.1.1 (due out next week). If you want to fix it now, you can edit the /components/com_jfbconnect/includes/jfbconnect.js file, and search for "trackerName" Remove it and the plus sign the 3 times you see it in the tracking code.

We tried to prepend jfbcSocial to the beginning thinking that it would indicate what actually caused the tracking. That was to prevent double-tracking in case another extension was already installed to do the tracking... and that's a common problem we've run into.

2) We changed a bit with the URL redirection stuff in JFBConnect. There were many reasons, and a few other issues that popped up that we'll also be clearing up in 4.1.1 release. However, you shouldn't still be having issues with 404's from JFBConnect, however, if you had any in the past, it may still appear in your logs for a while. Let us know specifically if there are any 404 or other page errors you know of that are caused by JFBConnect, and we'll gladly investigate.

Thanks,
Alex

The 4.1.1 release will add FB comment tracking. Just an omission from 4.1. Future versions will likely have tracking for the other social buttons, but that would need more testing as right now we add the tracking based off the Facebook Javascript library loading. Not sure what we need to trigger off of for the other networks (though we may be able to do the same thing we're doing now).

Hope that all helps you out, but definitely let us know if you run into any further issues!

Thanks,
Alex

I'm sure it will be in there soon. You're free to modify the jfbconnect.js file to add your own tracking (just to keep it all in one place). It won't be in the v4.1.1 version though simply because that code in the jfbconnect.js file is only executed after the Facebook Javascript library is loaded. Every site is different, and so using that event (the loading of Facebook) to hook onto the other social buttons may cause some issues. So, it's something we'd need to do a bit of testing with first before we'd be comfortable adding it to our release.

Hope that makes sense. If you do add the tracking to the jfbconnect.js file, feel free to let us know if you run into any issues. We'd love to hear your feedback.

Thanks again for the suggestion. This wasn't a planned feature, but we agree, it's a good one!
Alex