The first-party cookie blocking feature stops cookies from being stored, not the scripts. This means that even if a script tries to set a cookie before consent is given, the cookie will be blocked.
However, the script can still run, and in some cases, the service it belongs to will still work, especially if it doesn’t rely on the blocked cookie to function. For example, a live chat widget might load visually, even if tracking or personalization features are blocked.
So if you see a script firing before consent, that doesn’t mean cookie blocking isn’t working. It simply means the cookie it tries to set is blocked, and the script continues running with limited or no functionality.
