Unexpected consequences of GDPR

[kexej28769@nongnue]

I have found value in the content Ometria has produced on this front, such as 6 Things Ecommerce Marketersجی ڈی پی آر کے بارے میں جاننا چاہیے۔and their in-depth GDPR Guide (registration required).
If you work in this area, this GDPR impact on social posts from Buffer will get you there faster.
And for the paid marketers among us, this GDPR impact on AdWords article from WordStream is just what you need.
My goal is not to write a general guide, but rather to alert you to two specific things you should do with analytics (specifically Google Analytics) as a result of the changes Google is making due to GDPR.


When you deal directly with an individual in the EU, belgium number data they provide you with personally identifiable information (PII) about them, you are generally in a role called a “data controller.” The GDPR also identifies another role, which it calls a “data processor,” which is any other company that your company uses as a supplier and that handles that PII. When you use a product like Google Analytics on your website, Google takes on the role of a data processor. While most of the GDPR’s restrictions apply to you as the controller, processors must also comply, and this is where we see some of the potentially unintended (but likely predictable) consequences of the legislation.

Google is surprisingly trying to mitigate their risk (I say this not surprisingly because those GDPR fines could be as much as $4.4 billion based on last year’s revenue if they get it wrong). They are doing this first by putting as much responsibility as possible on you (the data controller), and second, by going much further than the GDPR requires and being more aggressive than the regulation requires by terminating accounts that violate their terms (regardless of whether the violation also violates the GDPR).