You can not embed that tracking pixel without first having approval from the user.
(This – third party cookies for tracking – is the entire reason the damn law was written in the first place, and yet we still haven’t gotten rid of them).
A login cookie doesn’t require approval, nor do settings cookies.
Only once you start loading Google Analytics, Piwik, Facebook, etc the law starts to apply.
Add the following to your HOSTS file:
https://github.com/panicsteve/facebook-hosts-file-additions/...
the boiler plate message it allows fails to explain anything. who is receiving the information? for what uses?
the silly message is expertly conceived by published as to fog the reason. most people in the audience think that is a paranoid warning about first party cookies, which are perfectly fine.
Tracking cookies and code can only be set and loaded after the user has accepted them.
If the user says no, well, just redirect to Google, or something – but you can’t load or set that tracking data before the user has clicked "Yes, I agree", and you can’t hide the fact that users are actively tracked in the ToS or somewhere.
If you don’t care about breaking european law, you can just leave the tracking there, never asking the user, but, well, you’re breaking european law then.
Which is why every newspaper then switched to "2-click Like", where the Facebook button is first shown in grey, you click it, it loads the actual button, and you can like.
It was also recently confirmed in a court case from this year (15'000€ fine for using it): http://www.verbraucherzentrale.nrw/mediabig/239773A.pdf
On top of that you can also start respecting the Do Not Track header sent by some browsers https://en.wikipedia.org/wiki/Do_Not_Track
If you want to ensure you don't get fined, I'd rather let the user opt-in than risk a legal confrontation.