Cookie Consent

This article explains how to manage cookie consent for purchase tracking with Neocom

Description

Cookie consent is relevant when the Purchase Tracking script is integrated, and session ID storage is enabled (Admin Portal | Settings | Purchase Tracking | Permissions). In this case, and with the acceptance of cookies, Neocom stores the session ID in the user's browser to link it with a later purchase. By default, Neocom assumes consent is given.

If you want to change the default behavior, you can explicitly inform Neocom whether cookies have been accepted. This consent can be obtained through a Consent Management Platform (CMP) or another tool and communicated to Neocom via a JavaScript function.

Neocom checks this function before loading the advisor to determine if cookie consent has been given. If this function returns “false” (i.e., declined), Neocom periodically calls this function to see if the consent status has changed to “true” (i.e., accepted) and then stores the session ID accordingly. The logic or trigger for when “true” or “false” is communicated to Neocom must be defined and implemented by you.

This function should be integrated on every page where Neocom is embedded, ideally in the header

💡 Please note: If this function is integrated, the purchase tracking performance will only reflect purchases from customers who have given consent.

Example

<script>
  function neocomConsent() {
    // Returns a boolean (true/ false) based on the consent
    return true;
  }
</script>