When installing Termly, you may encounter one of these common issues:
Termly is indicating that the consent management platform (CMP) is not installed when it should be
Your site is behaving differently after installing Termly's CMP
Termly is indicating that the CMP is not installed when it should be
If you think that the CMP is correctly installed on your site but the installation check returns unsuccessful, you can follow these steps to troubleshoot the issue.
Troubleshooting Steps
Confirm that the correct Termly CMP is installed on your site.
Check that the ID used in the banner script on your website matches the website ID of the website that you are checking the installation for. You can find your website ID in the page URL when viewing the Termly Dashboard: https://app.termly.io/dashboard/website/your-website-id
Confirm that the Termly CMP embed code is installed in the
<head>section of your site, above all other third party scriptsConfirm that your site is accessible by Termly's scanner
If your CMP installation check is still indicating that it can't find the banner on your site, please visit our support homepage or contact our customer support team.
Your site is behaving differently after installing Termly's CMP
After installing Termly’s consent banner on your site, you may sometimes find that parts of your website aren’t displaying as expected due to potential conflicts. We recommend following these steps to troubleshoot the issue.
Troubleshooting Steps
Confirm that the Termly script is the issue.
Remove the Termly script from your page and reload the page to see if the issue persists.
Check to see if your consent banner is installed correctly and is the first script on the page.
Review Auto Blocker’s blocked scripts. If you don’t have Auto Blocker enabled, skip to the next step.
Go to your site and decline all cookies.
Open your browser’s developer tools.
Search for “auto-blocked” in the Elements tab to find all the scripts that are being blocked by Termly.
Review the list of blocked scripts and recategorize if necessary using a custom blocking map or manual blocking. If you see a blocked script that is essential for your site to run, you should recategorize that script as “essential” to make Auto Blocker ignore it.
Check to see if any other installed services are directly conflicting with Termly.
While on your website, open your browser’s developer console.
Check for any errors — the name of the conflicting service might appear in an error message.
Remove the conflicting service and see if Termly now works on your website.
If these steps do not fix the issues, please visit our support homepage or contact our customer support team.