Indicates that Google Ads was allowed to load despite the visitor not having given consent to Google as a vendor.
To fix this, you need to ensure Google Ads doesn't load unless Marketing consent has been given. If you implement Google Ads inline and use manual blocking mode, ensure that the script doesn't load by ensuring it has the following attributes:
When using auto blocking, Google Ads should automatically be blocked prior consent.
In both cases, if users previously accepted marketing cookies, but don't have a consent string that indicates that Google has consent, the script will load, despite Google not having explicitly having consent. This error will occur as a result.
Forcing users to renew consent by using the Renew now button in the Cookiebot Manager will resolve this issue.
You can "ask"if Google as a vendor has been consented to using the following method:
You can also use an event listener using the following method:
Error 2.1a : Tag or SDK isn’t receiving a TC string due to CMP status being
Typically, this is due to Google Ads attempting to retrieve the tcString before consent has been submitted by the visitor. At this time the tcString hasn't been generated yet, making it impossible for Google Ads to determine if consent has been given or not.
This can be due to the Cookiebot script not having been loaded when the Google Ads script loads, or the lack of mark up in manual mode.
You can fix this by ensuring that:
- Cookiebot in implemented correctly and capable of blocking scripts
- Scripts that set marketing cookies are blocked prior consent, either by using the auto blocking function, or by ensuring elements are manually marked up
- Cookies are correctly categorized as "Marketing" cookies in the Manager.
- Visitors don't have a CookieConsent cookie that allows marketing cookies, but doesn't include a tcString. Renew consents in the Manager to ensure this isn't the case.
You can also manually load scripts usingor Cookiebot's events, to ensure that the tcString will only be requested when the tcString has been generated:
This should never happen since the CookieConsent cookie expires after 12 months. Forcing users to renew consent will resolve this issue though.
Error 4.1 : The TC string was generated using a version of the GVL in which Google is not yet listed.
Since Google wasn't listed before August 1st 2020, the tcString may not include Google (vendor id 755).
Forcing users to renew consent will resolve the issue by using the Renew now button in the Cookiebot Manager
Alternatively, you can delete the CookieConsent cookie if it was set before August 1st 2020 (when Google was added to the Global Vendor List):