Hi all,
I was hoping to get a pixel that we use detected by Ghostery. It recently changed slightly, and is now not being picked up as a tracker. In its previous guise, it appeared as 'FLXONE', but now the new version should be 'GDM'
Here is an example url of an existing site on which the pixel sits: http://www.woodhouseclothing.com/
here is the actual pixel used:
We recently changed the url from flx.com to gdmdigital.com and now Ghostery doesn't register it.
Is there any chance that this can be updated so that it registers as 'GDM' as the url change has made it unique to our company (www.gdmdigital.com), where before it was a pixel we licensed from a company called FLXONE (http://www.flxone.com/).
Let me know if you need any more information.
Many thanks,
AJ
-
Hi AJ,
Thanks for reaching out to Ghostery!
Appreciate the info. I'll forward this on to our privacy team for update. We'll update this thread once the change has been pushed to production.-
Pete (Senior Communications Manager) August 21, 2014 17:01You said "Here is the actual pixel used"... I don't see anything.. can you repost?EditDeleteRemove
-
-
-
-
-
-
-
-
Hi all,
I was hoping to get a pixel that we use detected by Ghostery. It recently changed slightly, and is now not being picked up as a tracker. In its previous guise, it appeared as 'FLXONE', but now the new version should be 'GDM'
Here is an example url of an existing site on which the pixel sits: http://www.woodhouseclothing.com/
here is the actual pixel used:
(function(a){var d=document,c=d.createElement("script");c.async=!0,c.defer=!0,c.src=a,d.getElementsByTagName("head")[0].appendChild(c)})((iatDev=(window.location.href.indexOf("iatDev=1")>-1||document.cookie.indexOf("iatDev=1")>-1),"//"+(window.location.protocol=="http:"&&!iatDev?"h":"")+"fp.gdmdigital.com/63864.js?r="+Math.random()*1e16+"&m=992&a=63864"+(iatDev?"&d=1":"")))
It is placed within a script tag, but for some reason when I put that in the pixel doesn't appear in this post!
We recently changed the url from flx.com to gdmdigital.com and now Ghostery doesn't register it.
Is there any chance that this can be updated so that it registers as 'GDM' as the url change has made it unique to our company (www.gdmdigital.com), where before it was a pixel we licensed from a company called FLXONE (http://www.flxone.com/).
Let me know if you need any more information.
Many thanks,
AJ -
-
-
-
Not counting Brown Bag Clothing, I only found three other sites using this integration. It doesn't look like we're missing much.
-
-
There are loads, and we are placing more everyday on new clients' sites.
Try www.vodafone.es for example...
Here are some others:
http://www.vacanceselect.fr/
http://gorillasports.ch/
http://www.tripsta.es/
http://www.rollersnakes.co.uk/
The one variable in the pixel is the 5 digit number.
(function(a){var d=document,c=d.createElement("script");c.async=!0,c.defer=!0,c.src=a,d.getElementsByTagName("head")[0].appendChild(c)})((iatDev=(window.location.href.indexOf("iatDev=1")>-1||document.cookie.indexOf("iatDev=1")>-1),"//"+(window.location.protocol=="http:"&&!iatDev?"h":"")+"fp.gdmdigital.com/63864.js?r="+Math.random()*1e16+"&m=992&a=63864"+(iatDev?"&d=1":"")))
See them replaced by 'X'
(function(a){var d=document,c=d.createElement("script");c.async=!0,c.defer=!0,c.src=a,d.getElementsByTagName("head")[0].appendChild(c)})((iatDev=(window.location.href.indexOf("iatDev=1")>-1||document.cookie.indexOf("iatDev=1")>-1),"//"+(window.location.protocol=="http:"&&!iatDev?"h":"")+"fp.gdmdigital.com/XXXXX.js?r="+Math.random()*1e16+"&m=992&a=XXXXX"+(iatDev?"&d=1":"")))
Let me know if you need anything else.-
www.vodafone.es — absent
www.vacanceselect.fr — absent
gorillasports.ch — absent; unknown 3rd party: shop.toppreise.ch
www.tripsta.es — absent
www.rollersnakes.co.uk — present; unknown 3rd party: connect.nosto.com -
-
-
-
-
The ones that you say are absent have a different ID. This is the variable to which I referred in my previous post.
So vodafone.es has the following:
(function(a){var d=document,c=d.createElement("script");c.async=!0,c.defer=!0,c.src=a,d.getElementsByTagName("head")[0].appendChild(c)})((iatDev=(window.location.href.indexOf("iatDev=1")>-1||document.cookie.indexOf("iatDev=1")>-1),"//"+(window.location.protocol=="http:"&&!iatDev?"h":"")+"fp.gdmdigital.com/364686.js?r="+Math.random()*1e16+"&m=992&a=364686"+(iatDev?"&d=1":"")))-
No, there's nothing there. www.vodafone.es only references Tealium directly, which it uses as a tag container for Digilant, MediaMath, Omniture (Adobe Analytics), Optimizely, Sizmek, SOASTA mPulse, TradeDoubler, and Zanox. I don't see a tag for GDM Digital with that ID, nor any other.
-
-
Well it will be running through the Tealium container then. We have many pixels that run through container tags, and before the change from FLX to GDM they showed up in Ghostery.
If you Inspect element and filter by 'gdm' you will see it. -
-
-
-
Loading Profile...



Twitter,
Facebook, or email.

EMPLOYEE
CHAMP
