Skip to main content

Use Fresh Relevance with cookie management tools

Manage how Fresh Relevance respects your visitors' cookie preferences when using a cookie management tool.

Updated this week

Fresh Relevance doesn't have a native integration with cookie management platforms. However, you can configure your cookie management tool to control when the Fresh Relevance script loads based on your visitors' consent preferences.


Before you start

Things you need to know:

  • You must have a cookie management platform or tool already implemented on your website.

  • You need admin access to your cookie management platform's settings.


How Fresh Relevance uses cookies

Fresh Relevance uses first-party cookies to track visitor behaviour and enable personalization. The tracking script loads using JavaScript on your website, captures visitor activity, and then uses this data to display personalized content.


Configure your cookie management tool to control the Fresh Relevance script

To respect your visitors' cookie preferences, you must configure your cookie management platform to conditionally load the Fresh Relevance script tag.

The script should only load when visitors accept the appropriate cookie categories. Typically, these are marketing or personalization cookies.

When the script doesn't load, Fresh Relevance functionality is completely disabled for that visitor.

Configure conditional script loading

To prevent the Fresh Relevance script from loading until visitors provide consent:

This is an all-or-nothing approach

When the Fresh Relevance script doesn't load, all Fresh Relevance functionality is disabled. This includes both activity tracking and web personalization. You can't load Slots while preventing activity capture using this approach.

  • Find the script management or tag blocking settings in your cookie management platform.

  • Add the Fresh Relevance script tag to your platform's script inventory.

    For example:

    <script async type="text/javascript" src="//ls.dycdn.net/[your account ID].js"></script>

    or

    <script async type="text/javascript" src="//d81mfvml8p5ml.cloudfront.net/dc2jylfs.js"></script>

  • Assign the script to your marketing or personalization cookie category.

  • Configure your platform to block scripts in that category until consent is given.

  • Test the implementation to ensure the script loads correctly when consent is granted and remains blocked when consent is denied.

The exact method for configuring conditional script loading is different between cookie management platforms. Make sure to read your cookie management system's documentation for specific instructions.


Alternative: Use server-side personalization

If you want to show personalized content on your website without loading the Fresh Relevance script, you can use server-side personalization.

Server-side personalization requires development work

Server-side personalization requires development work on your web server and may involve additional implementation costs. Consider whether this approach suits your requirements before proceeding.

With server-side personalization, your web server requests content from Fresh Relevance and renders it before the page reaches the visitor's browser. This approach gives you more granular control over which Fresh Relevance features are active.


More information

Learn more about the cookies Fresh Relevance uses in Understand Fresh Relevance cookies and their duration.

Did this answer your question?