Under review

Tagcommander

9 років тому • оновлено 9 років тому • 5

Hello all,

I was scanning www.orcanta.fr and I observed only 8 tags regarding my scan results but I found 16 using Gosthery (on the home page).
When I analysed the gap between both tools, I detected that Tag Inspector doesn't scan the Tagcommander (a French TMS tool) javascript (tc_header.js and tc_catalog.js). In those JS, I think I found all the calls to various missing tags such as ABTasty, GA,... but a part of those JS are crypted (var CryptoJS=CryptoJS) and my skills in JS are really poor.

Can you have a look at this and fix the reason why Tagcommander is not detected with Tag Inspector ?

Thanks in advance

Голос

Відповіді 5
Старі зверху
- Нові зверху
- Старі зверху

Under review

9 років тому

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.

9 років тому

Hello Andy,

Thank you for your return, it's pretty clear.

The fact that Tag Explorer and Tag Inspector is not showing the same results is quite bad for us because we are using Tag Inspector to run some audit for our customers. The Tag Explorer is not enough for us because we need a global overview of the website and not page per page. How can you fix this issue ?

Using only Tag Inspector before your answer, I was quite impressed by the functionnalities of Tag Explorer via the Map View and all the caracteristics display per technology obn the "List View", do you plan to add those functionnalities to Tag Inspector ?

Thanks in advance for your help.

Thibault

9 років тому

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.

9 років тому

Hello Andy,

I'm sorry but orcanta.fr is only a prospect and not our own website. We will not be able to integrate the Realtime tag to listen every tags. Just to be sure to understand everything, you're saying that you will not look for a fix to this gap between TI solution and Tag Explorer ? It's quite a huge problem for our agency if we can't rely on the scan we launch for our prospect, we can make a wrong analyse on their situation and so a wrong proposal...

Thanks in advance for your help

9 років тому

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.

Служба підтримки клієнтів працює на UserEcho