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

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;

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. 

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!

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

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.

Thanks for contacting us.

Hey There,