You can get your base tag code by going into iQ, click on your user-name on the top right (next to help centre) then go to Code Center.
To check to see if they're firing, go to developer tools in your browser, go to sources, expand tags.tiqcdn.com and you will see a sub-folder relating to your account, profile and environment - in the format of utag/account/profile/environment
If you expand that, you will see a list of tags for that page (utag.1.js utag.2.js etc. ) The numbers relate directly to the tag id within iq.
The main base tag, assuming you have a standard async installation, will show on this list as as utag.js
The Tealium files follow the structure of utag.js (the controller file) and utag.X.js where X is a numeric ID of the tag (it will be the same as the UID listed for a tag on the Tags tab).
We don't fire any tags other than the ones that you define so if you're inspecting the network panel for the Google Universal Analytics tag you could look for that.
Additionally, if you install the Tealium WebCompanion bookmarklet in your browser (available from the menu underneath your username in the top right of Tealium iQ) we can tell you the state of any tag that you have configured.
Thanks for the quick reply Steve!
However, I am looking to see the variables as pagename, pagetitle, etc and corresponding values coming in. e.g. - pagename - Title of the page, pageurl - URL of the page etc.
Please let me know in case you need further details.
I still do not see them with the Tealium WebCompanion bookmarklet. I just want to make sure that the tags which are being fired, I can see them in any html debugger such as fiddler. The same way I check in querystring for other tools.
Currently Tealium does not have a tool that shows you which server requests were made and what data is was sent to each vendor. To do this you will need to use any HTML debugger like Charles, HTTPFox, the browser Dev Tools, etc.
Using one of these tools you can do a search for "utag," and it will show you which libraries were loaded on the page, similar to what Steve is explaining. Then you can search for each vendor and their specific server requests and see the correlating data that was sent to that vendor.