iQ blocked by Firefox Tracking Protection?

[holbue]

Hi Tealium-Team,

I noticed some days ago, that Tealium iQ gets blocked by the Tracking Protection of Firefox. AFAIK the Tracking Protection (TP) is not activated in Firefox by default (yet), but a lot of companies already distribute Firefox with TP activated. This is a major issue for us, as i.e. we use iQ for Cookie Management (GPDR relevant!) and other stuff that is not related to tracking and needs to be on the webpage.

Therefore I investigated a little bit deeper:

1. Tracking Protection of Firefox is based on a list from Disconnect [source]
2. Tealiums whole CDN (tiqcdn.com) is now blacklisted [see github]
3. This was added on Dec. 8th 2018 [see commit]

We could hardcode all of our (non tracking related) tags into the webpage, but  that would somehow contradict the the Tag Management idea.

Question: What can Tealium do about this? What can we do? How do others handle this issue?

I'd appreciate feedback and I'm also interested to hear, if other customers are affect by this change or experiencing similiar difficulties with other browsers.

Thanks & Best regards,

Holger

[mitchellt]

At face value at least, this development is rather alarming.  Closely following this thread and hope that we get some "official" updates soon from Tealium and other vendors.

[GavinAttard]

We are re-platforming and our devs brought this to my attention in the last week. Indeed this is an alarming development.

[UnknownJ]

I've created the following feature suggestion, which I think would work around the problem:

https://community.tealiumiq.com/t5/Product-Ideas/Enable-CNAME-aliasing-to-create-appearance-of-local...

At least until the blocking got smarter, anyway.. From my perspective, we too use Tealium to deliver functionality like Webchat, which wouldn't be blocked by an ad blocker, so it's unfortunate that the delivery vehicle is.

Other alternatives include locally hosting your Tealium instance - bundle all tags, and mirror utag.js onto your own domain, but it's not ideal for a whole bunch of reasons...

[niko_bochan]

It seems like Tealium is no longer on this list: https://github.com/disconnectme/disconnect-tracking-protection/commit/9158ab0bded2a6471112bae2299372...

(see also: https://github.com/disconnectme/disconnect-tracking-protection/issues/31#issuecomment-471711233)

[awarwick]

I believe Tealium was added back to the list on 9/6/2019

[craig_rouse]

@awarwick Although Tealium is on the list, Tealium iQ is not affected. The single Tealium domain listed (.tealiumiq.com) is only used for data collection for the server-side platform components (AudienceStream, EventStream). The client-side platform is not affected by this. The reason for the distinction is that no data is collected by Tealium iQ, and it is often used to serve important content such as consent management platforms (including the Tealium consent manager), which can be essential to the operation of a website. Individual vendor tags served through Tealium iQ, may of course still be blocked by disconnect.me, but the core Tealium iQ scripts are not blocked, as they don't collect any data.