Skip Bot

in the "features" section of our configurator, there is a parameter called skipbot the skipbot parameter was introduced to facilitate performance analysis of the website through automated tools such as lighthouse , pagespeed insights , webpagetest , and other similar tools used for monitoring core web vitals , as well as for automated systems—hence the name "bot" when these tools perform an analysis, they do not interact with the user interface and cannot provide explicit consent to the cmp (consent management platform) as a result, under normal conditions, the cmp is displayed but consent is never given, which blocks the execution of scripts and tags that would normally be triggered after an "accept all" action this can significantly affect the measurement results, particularly for metrics like largest contentful paint (lcp) , which may be impacted by the delayed loading of content or scripts essential to page rendering by enabling the skipbot parameter, the system automatically detects when the page is being accessed by one of these tools and simulates full consent , but only for performance measurement purposes this allows scripts that would otherwise be blocked to run, providing a more realistic measurement of the site's performance—as it would appear to a real user who has accepted all consents this approach makes it possible to obtain more reliable insights into the site's actual performance accurately monitor key metrics such as lcp, fid, and cls evaluate the true impact of scripts and resources that load after consent avoid false alarms or performance score penalties caused by the cmp display it’s important to note that the skipbot parameter does not disable the cmp for real users , but only applies in automated contexts (bots)