There was for example one case of Canadian firm 'AggregateIQ' being pursued by the UK's ICO over privacy violations, and Canadian regulators agreed.
https://www.theguardian.com/world/2019/nov/26/brexit-data-fi...
https://iapp.org/news/a/ico-serves-aggregateiq-with-first-ev...
The first article actually doesn't mention any enforcement at all in Canada, just comments by a provincial and the federal privacy commissioner. Those comments were entirely based on Canadian law, not the GDPR.
As an aside, I'm completely behind GDPR, CCPA, and related privacy laws. I think they're great. I definitely comply with the spirit of the laws in my hobby projects by doing things like not tracking anonymous users, not retaining identifiable logs, etc. This isn't me trying to get away with something nefarious. More like, I don't (and won't) bother with things like cookie banners even if GDPR would want me to.
If a company asks for GDPR consent, either:
• They have cool, optional features of their site / service / system (though they could just ask at run-time, when you try to use those features, in most cases); or
• They're doing something dodgy and want to wave a magic wand and remove the dodginess by getting you to “consent”.
Note that if it is a personal website you are not subject to GDPR. GDPR only applies to companies and organizations.
Also note that most stuff that a layperson would say is reasonable for a website to function isn't a problem in GDPR.
Except revenue of course.
These were the norm in advertising until like 2005.