Since you are publishing examples, the best way to use them in your site is to have clear descriptions of what the code does, elaborate the idea that you are showing, the reason why you choose something instead of another option, some caveats, what you accomplish with that code, how can you call it, or integrate it, or whatever is related to the piece of code that you are publishing.
There are tons of code examples on Internet, but very little good explanations. Help to change that. If you do, that will help you, and your readers much more.
Lets consider some scenarios.
People get to your site, read the article/post and go to your jsfiddle/code. From the traffic perspective, you already have what you want, you already had a visitor. If your explanation and your code are good enough, that person will come back some other time. If your explanation is bad, most probably won't even go to see your code. I wouldn't. Adding extra code to your original code, will make it more complex, and require that you explain that some parts are not required, which implies more work from your part and the reader. There is almost never a good reason to do extra work.
People get to your jsfiddle/code, without going to your site. What is that code for? how did they get there? why there is an analytics code on the script? do I need that part for the code to work? if not, why did the programmer put it there?. Plus the above consideration, you had to add more explanations to the code to make clear which part is needed and which is not.
To the second scenario, I have to add, how many times have you made a search and there have been jsfiddle results on it? or pastebin, or sqlfiddle, or any other site similar?. In my experience, less than 1%, only when the search is extremely specific and there are like 4 results on the whole Internet (crawled). And they are never useful. So, is it worth polluting your code for, how many visits?.
Now, for any scenario, assume that you add a brief comment, adding your site, your email or the url of the article where the code is explained, that is much more useful because the visitor can keep it and have a reminder of your site/name/article and visit it from time to time. Even more, if your code is complex enough and can be improved, you may add in the comment something like there will be new versions referenced on the original article, which will, in turn, grant more visits.
There are more options, but this is getting too long already. The important part is that if you just try to get traffic/visitors/views without providing something useful for the user, that is an empty experience and doesn't benefit anybody.