What cookies and similar technologies does cludo use?

Cludo uses cookies to gather information about user behavior. This data helps improve user experience and is used for the statistics you see in MyCludo. Cludo uses local storage, which, in short, is a successor to cookies so they are effectively treated the same under EU cookie laws and GDPR.

Types of cookies


Remember that it is possible to connect Cludo to your general cookie consent, leveraging the instructions found here.

Cludo currently uses four types of cookies. You may read about the purpose of each cookie below.

CookieUsageSet AutomaticallyPurpose
cludoSessionIdUnique ID for the session. Connects user sessions across multiple page views. Used to determine unique versus total searches and clickes. This in turn is used to calculate ineffective searches and click-through rate.Statistics
cludoSessionIdStartIndicates the beginning of the current session, specified by cludoSessionIdStatistics
recentSearchesUsed for storing recent searches by the end-user. Introduced for the instant suggestions functionality.
Only set if the instant Suggestions feature is enabled
cludoTraitUsed for storing user traits. Introduced for the audiences functionality.
Only if the audience feature is enabled

What happens if cookies are disabled?

When checking “Do not use cookies” in the Content › Data Settings section of MyCludo, cookies will no longer be collected.

Such an action will have the following effects:

  • Any unique search analytics will be affected. All searches will appear as 1 unique search.
  • Ineffective searches will no longer work as intended because of the above.
  • Intents will no longer be able to produce results.
  • Instant suggestions will be able to show popular searches, but not recent searches.

Similar technologies

All search implementations except API will be referring to at least one JS file and one CSS file, hosted on customer.cludo.com, depending on the implementation type. These file references are seen as third-party elements since they are located externally.

https://customer.cludo.com/scripts/bundles/search-script.jsCore search script. Responsible for the entire search functionality, including setting the cookies documented above. The cookies may be disabled, but the script must be in place for the search to work.User interface customization cookies
https://customer.cludo.com/css/templates/v2.1/essentials/cludo-search.min.cssDefault stylesheet used for the inline template.User interface customization cookies
https://customer.cludo.com/css/overlay/cludo-search-default.min.cssDefault stylesheet used for the overlay template.User interface customization cookies
https://customer.cludo.com/assets/…/cludo-search.min.cssCustom stylesheet developed for custom implementations, handling the design of all Cludo search elements.
(URL reference/file name will vary)
User interface customization cookies
https://customer.cludo.com/assets/…/cludo-helper.jsCustom Javascript developed for custom implementations, handling the functionality of the search.
(URL reference/file name will vary)
User interface customization cookies

How should the similar technologies be assessed?

  • These file references fall under similar technologies according to the EU directive. Additionally, they all fall under the category of user interface customization cookies, which do not require consent from the user.
  • If preferred, all of the above files can be hosted locally by extracting the code and uploading it as (part of) a locally hosted file. However, for all of the above, this is not recommended, since updates will no longer be applied automatically as they happen.