Andy / Profil - Kommentare / Tag Inspector

Hello!

A scan will be accessible to you as long as your account is active. Additionally, if you access and share the link to the scan, it should always be active.

Let me know if you have any other questions!

Andy

vor 6 Jahren

How to capture tag id's in the crawl?

We just made an update so the Floodlight tags are broken down by Advertiser ID. All future scans will break down the results like this:

vor 7 Jahren

How to capture tag id's in the crawl?

Yes, we should be able to add this to the scan results.

With the following Floodlight example request below, the advertiser ID would be the 'src' parameter, '1234567', correct?

Ex:: http://1234567.fls.doubleclick.net/activity;src=1234567;type=abc123;cat=fghij456;

vor 7 Jahren

Non public website environment scans

By default, the IP's used by Tag Inspector so scan sites are random. We do have the ability to enable the use of a static IP for scans though. I went ahead and enable this functionality for your account. The IP you will see traffic coming from is: 54.209.73.243.

vor 7 Jahren

sessioncam not detected

We'd love to add SessionCam to our tag library. Can you send me a URL where the SessionCam has been implemented or example http request for this tag? Thanks!

vor 7 Jahren

How do I change my password?

Hello,

The password reset form is located here: https://taginspector.com/wp/reset_password/

Let me know if there is anythine else I can assist with.

Thansk,

Andy

vor 8 Jahren

Tagcommander

Thibault,

That is understandable for the Realtime solution and being unable to implement the tag. For the gap between the TI scans and the behavior showing up within Tag Explorer, we are constantly working to improve the capabilities of the crawler and that reporting.

Right now, the only automated whole-site solution to be able to see all tags (including those fired conditionally based upon user characteristics and cookies) is with the Realtime tag. An inherent limitation of the crawler is that it doesn't browse the internet and pick up/carry cookies like a live person. This is the cause in the gap between the results you're seeing in the Scan Report vs. what you are seeing with the browser plug-in.

Platforms such as analytics, optimization, and personalization are going to fire on pages regardless of user characteristics. The thing that will vary with these platforms is the data that is captured and reported by each tag depending upon the user. These platforms will be picked up all the time with the crawler (Tag Inspector Scans). Some advertising tags, however, will only fire x% of the time based upon either a schedule defined by the publisher/ad platform, a winning bid in the programmatic marketplace, or based upon specific user behavioral characteristics as carried in cookies. These tags make up the gap in the results you are looking at from Tag Inspector vs. Tag Explorer.

The gap is a direct result of the method in which the two tools are collecting information (crawler simulating a user vs. actual user). We are currently playing around with ways to more closely simulate live people with our crawler but no two users are alike and no machine can be a human. This is one primary reason we developed Realtime to be able to address the issue by capturing all tag behavior in the live environment, using live users to trigger the tags.

Which specific tags are you looking for to make recommendations about? I maybe able to provide some specific tips on scan configuration to better look at those specifically.

vor 9 Jahren

Tagcommander

Hey Thibault,

Tag Inspector shows more accurate and in depth results than the browser plugin. If you are seeing more tags on the browser plugin, it is happening because of the variable tag behavior in browsers that cannot be captured in a simulation. However, we do have another capability Tag Inspector Realtime, that captures every request made on the browser all over your site - so every tag that you would see on the browser plugin would be captured. All that you would have to do would be to place our Tag Inspector Tag on all your website pages and it would silently listen to all the requests being made.

I would like to put you in touch with my colleague Lucas Long (lucas@infotrustllc.com), who can take you through the capabilities of Tag Inspector Realtime in depth.

Thanks for contacting us.

vor 9 Jahren

Tagcommander

Hey There,

Thank You for using Tag Inspector. I looked into the issue. Here is what is going on, we are not recognizing the initiator TMS but the tags being fired from it are being captured. Since we are not recognizing the TMS, it looks like they are firing from source. I could find GA and Criteo this way. One tag that I could not find was ABtasty which is not categorized/recognized by us so we are not reporting it. However, we can go ahead and make an addition in our tag library for these two tags - Tag Commander and ABtasty as they are important to you. I will let you know once we have added both of these tags.

Also, regarding your concern that Ghostery is showing many more tags than Tag Inspector, Tag Explorer our Browser plugin for Tag Inspector is showing comparable number of tags to Ghostery - nearly 17. But in the scan only 8 are appearing. This appears to be happening because of variable advertising tags firing based on the cookies getting set in the browser. This is not unusual tag bhavior.

Please feel free to reach back to us if we can help with anything else.

vor 9 Jahren

See link source that lead to page during crawl

Hey Michael,

Thanks for using Tag Inspector. We really appreciate your feedback and suggestions, and will incorporate the same in our future product releases. Feel free to write to us for any other feature requests that you may have, as it is the suggestions of valuable clients like you that help us make our product better.

vor 9 Jahren

Ihre Kommentare

Benutzermenü