Adsense: ‘We’ve detected an error on your IAB TC string’

KB ID 0001709

Problem

A couple of weeks ago I logged into Adsense and saw this;

‘We’ve detected an error on your IAB TC string on one or more of your sites or apps. These errors may affect your ability to serve ads to European users. A detailed report is available for you on the EU user consent page’.

Solution

Well all of that made no sense to me, so I downloaded the report, which is a spreadsheet and it looked like this;

Erm OK, so what’s error 2.1a? well it’s this;

Everything I read didn’t make much sense, and a search of Google revealed a ton of things that made little or no sense to me.

Why Am I Seeing European IAM TC String Errors?

In short: People in Europe are protected by the GDPR. This says, (very basically) that website visitors should be ‘asked’ what their Ad preference, and tracking cookie preferences are, BEFORE the website can show them any ads, or attempt to embed tracking cookies, (like the ones Google uses), on their machines.

This is why you will notice most sites you go to now ask you about cookies and ads the fist time you visit,  you generally then tick a box that says ‘accept preferences‘, or ‘that’s fine‘, and you are bothered no more.

So that’s basically the root cause of the problem. Well I run my website on WordPress so “There will be a plugin for that right?” I tried a few and settled on UniConsent CMP. I installed it, and enabled cover for GDPR, (and CCPA compliance).

Note: Sign up for a free licence, then you can manage everything directly at UniConsent.

Extra Tip: Go To Consent Manager Version 2 > Manage > Fill everything in  > Enable GDPR (For European Countries) > Enable IAB TCF > Select Pop-up Box > Save and Exit (Top right).

Do You Cache Your Website? If so, don’t forget to ‘flush the caches’ at this point.

So That Fixed It Yes?

Sadly no, but because I now manage my CMP online they have a support/chat feature, and I was asked to do the following;

    1. A third party Ad agency I use has their own CMP I asked them to disable that, which they did, (don’t forget flush the caches again!)
    2. I had some embedded code with my Adsense ads that was calling this script;

[box]

script async src="//pagead2.googlesyndication.com/pagead/js/adsbygoogle.js

[/box]

I had to remove each instance of that, and put the following code in my websites < HEAD > section; Download Code

Update (28 Oct 2020)

Well my errors came back, The good folks at UniConsent investigated and found out that I was caching, information (Javascript,) that was being called, and so breaking the TCF rules again. I logged a call to the people who provide my WordPress Caching Plugin (WP-Rocket.) Who remoted onto the server, and added the following onto their ‘File optimisation’ Settings;

The Adsense TCF Error Wont Go Away!

That’s because the errors stay on Google Adsense for 7 DAYS, even if you have fixed the errors, you need to wait 7 days for the errors to stop showing!

Which Ad Network Should You Replace Adsense With?

For everyone asking “What ad network did you move to”, then you can message me (link above) and I will let you know. There are some caveats, most of your traffic needs to be EN-US / EN-GB traffic, and you need to have a decent amount of traffic to be considered. If you fall into that category, message me and I will pass on you details to them. (Disclaimer: I get a financial kick back for doing so). 

Related Articles, References, Credits, or External Links

NA

VMware: Upgrade Errors

KB ID 0001576

Problem

This weekend I had to upgrade some servers from VMware 5.5 to version 6U3, (that’s the latest supported version, on the hardware I was using: HP BL460c). As the VC was at version 6.5 I couldn’t use the built in update manager, so I had to use the ‘offline bundle’ method. 

TWO THINGS then jumped up and bit me;

Problem 1

[DependencyError]
File path of ‘etc/init.d/hp-mst.init’ is claimed by multiple overlay VIBs: set([‘Mellanox_bootbank_net-mst_4.3.0.29-10EM.550.0.0.1331820’, MEL_bootbank_nmst_1.3.0.29-10EM.600.0.0.2768847′[)

Problem 2

[DependencyError]
VIB VMware_bootbank_esx-base_6.0.0-3.100.931334 requires vsan >= 6.0.0-3.101, but the requirement cannot be satisfied within the ImageProfile.
VIB VMware_bootbank_esx-base_6.0.0-3.100.931334 requires vsan << 6.0.0-3.101, but the requirement cannot be satisfied within the ImageProfile.
Please refer to the log file for more details.

Solution

Both these problems BOTH need to be dealt with separately;

Solution to Problem 1

Easy one, execute the following command (Note: Despite what it says, you don’t need to reboot the host!)

[box]

esxcli software vib remove -n net-mst

[/box]

Solution to Problem 2

I’d been bitten by this one in the past, so luckily I knew what the fix was, you see this a lot with custom, (vendor) VMware ESX images HP, and Dell for example. To proceed you need to specify which ImageProfile to use, and you get that from your update bundle, like so

[box]

esxcli software sources profile list -d /vmfs/volumes/{volume-name}/VMware-ESXi-6.0.0-Update3-9313334-HPE-preGen9-600.9.8.5.4-Sep2018-depot.zip

[/box]

It will display the ImageProfile name, copy that to the clipboard;

Note: In the example (above) the ImageProfile name is HPE-ESXi-6.0.0-Update3-preGen9-600.9.8.5.4

Then you re run the upgrade command, BUT you specify the ImageProfile with a -p switch, like so;

[box]

esxcli software profile update -d /vmfs/volumes/{volume-name}/VMware-ESXi-6.0.0-Update3-9313334-HPE-preGen9-600.9.8.5.4-Sep2018-depot.zip -p HPE-ESXi-6.0.0-Update3-preGen9-600.9.8.5.4

[/box]

Have a coffee! When it’s completed, scroll to the top of the text and look for Update was successful, then reboot the host.

[box]

reboot

[/box]

Related Articles, References, Credits, or External Links

NA