FAQ

What level of support is included?

Support can be as light or in-depth as you like, we have packages for all levels. We also have a marketing team that continuously provides helpful content around product usage or answers to FAQs added to our resources section inside each Tag Inspector account.

What setup is included with each package?

Every Tag Inspector client will have a Tag Inspector Technician to help with initial reporting set up, particularly with scheduling regular scans. This helps ensure the fastest and most accurate set up possible for every client.

Is there training involved?

Though we do not have open training sessions or regular webinars at this time, our Tag Inspector Technicians would be happy to provide demos and walkthroughs of the product upon request.

Can Tag Inspector show changes in tag deployment throughout time?

Yes, Tag Inspector has a feature allowing users to toggle between different scans based on the date and time scanned. This allows for analysis of changes occurring with tags over time. We will soon have an alerting system that can also detect changes between scheduled scans and send a notification to users when any change occurs, such as a tag dropping off a site.

How do we update our tag library? How often do we update it?

We currently have over 700 classified tags documented in our tag library database. The more site scans we have, the more this library will continue to grow and update. With every site scan we run, we find all tags that are classified and build the reports you see in the interface. However, for all unclassified or unknown tags, we collect those in a separate repository to review. If there are any common tags found that are not classified, our team of highly qualified marketers research the tag and script to get the information needed to classify it in our tag library. Since Tag Inspector can find image tags, javascript files, and other forms of tags, we update the tag library several times a month.

Does Tag Inspector follow a certain path when scanning a site?

Tag Inspector can do two types of crawls: 1) Random crawl based on the links it finds on the pages and 2) it can follow a XML sitemap (ex: http://content.infotrustllc.com/sitemap.xml).

What is tag latency?

Tag latency is the time between the start of the tag request and the beginning of the response (also known as the "time to first byte").

How many domains does the Consultant Edition do?

The limits for the Consultant Edition are 10 scans per day at 2,500 pages for each scan. We don't limit the domains - you can scan 10 different domains each day if you wanted.

Will you pick up the tag's for Effective Measures?
Yes, Effective Measure is included in our tag library. You can see the other tags we support here: http://tagopedia.taginspector.com/wiki/Main_Page.
If there is a tag you need to track that we currently don't have in our library, we can easily add it.

Will your audit do x2 domains - eg .co.za & then the .mobi version of a site - and can it do server side testing of the GA code for the .mobi?

Yes, we can scan both domains. For the '.mobi' site, we even simulate an Android/iPhone browser user agent.
We can pick up Google Analytics tags if requests happen from the client browser to Google Analytics servers (google-analytics.com). If the server side code adds the '_utm.gif' to the source code of the 'mobi' page we can pick up that the GA tag fired. If the server side code communicates directly to GA with CURL (bypassing the client), we cannot pick that up. We would be happy to do a sample scan on the '.mobi' site to test if we pick up the Google Analytics tags.

Can you add an additional tag to your library?
Absolutely! Please send us a url that contains the Tag.

What tags does Tag Inspector support?

See http://tagopedia.taginspector.com/for the tags we support.

Does the scan include pages such as confirmation pages or logged in user pages?

Not out of the box, nor in the interface. We do have functionality to do this with customized reports, however it will require some manual set up initially. Our crawler cannot access these pages automatically, but it can follow a predetermined path we set. So we (real users going to site) would need to manually go through the process of logging in or making a purchase once, while recording a macro that Tag Inspector will be able to replicate hundreds of times to go through password protected pages and capture all tags before and after these barrier pages. Tag Inspector can do two types of crawls: 1) Random crawl based on the links it finds on the pages and 2) it can follow a XML sitemap. A custom XML sitemap can be created to include the confirmation pages so they will be scanned.
We are unable to crawled logged in pages at this time. It's on our roadmap to be released soon.