Thanks to the 𝕏 team for discovering this and @DoubleVerify for responding quickly to correct the error