Introduction to Integrating Third-Party Cookie Consent

To integrate a third-party Cookie Consent on the website, the following steps should be followed.



Step 1: Create an Account with Osano


Visit the third-party website: https://www.osano.com/plans/cookie-consent.


Select the Free Account option.




Once the account is created, click on Cookie Consent.



Hit the Create Button with the + Icon.


Click on the Customization tab.




Step 2: Customize the Cookie Consent Dialog Box


Customize the Consent Dialog Box.

Click on  the <> Get Code button.



Click on Copy.



Step 3: Add Code to Brilliant Directories


Go to the Brilliant Directories Admin Dashboard.


Navigate to Toolbox, then click on Widget Manager. Next, search for the widget Bootstrap Theme - Cookie Consent Code and enter the snippet in the HTML editor. Finally, click on Save Changes.




Step 4: Classify Scripts and Cookies 

Go back to Osano and click on Scripts. 


The scripts and cookies must be classified. For guidance on how to classify them, refer to the article on Osano and watch the accompanying video to fully understand how to use the tool. Cookie Consent: Full Product Overview


The majority of the scripts are classified by Osano, but for those that are not recognized, Essential and the domain name of the site can be added.



Step 5: Verify Cookie Vendors

Use a tool like https://www.cookie.is/ to see what are the official vendors of the cookies. Once the cookies are classified click on Save Changes.



Step 6: Finalize and Publish Changes

Click on Publish to push all the updates made.




Select Clear and Publish and hit Publish.



Step 7: Set Cookie Consent Listener


Hover the mouse on Discovery/Listener and select Strict.


Select Yes on the confirmation pop up. Then click on Save Changes.



Step 8: Troubleshooting

If the banner is not visible on the website, it may be due to the browser saving a cached version of the site that doesn't include the banner.


Clearing the browser cache and cookies or opening the website in a private or incognito window may resolve this issue. It is recommended to always test in a private or incognito browser after publishing changes.



Additional Osano Documentation and Videos