1. Home
  2. Extra
  3. Managing Privacy Policy

Managing Privacy Policy

This post is also available in: Czech

Samba.ai is fully compliant with the EU General Data Protection Regulation (GDPR). Below you can find options to manage your customer/visitor privacy policy in all aspects using Samba features instead of completely disabling Samba integration on your website.

Data feeds

Customers feed can contain optional parameter DATA_PERMISSON (see Data feeds integration) which can have one of the following values:

  • full
    • All data of the customer can be used for personalisation and segmented targeting without limitation
    • It is a default value.
  • do_not_personalize 
    • Only not personalised targeting available – no purchase history and tracked behavior patterns are used for targeting.
    • Such customer will not be targeted by behavior triggers (Abandoned Cart, Shopping Intention, Repeated Orders) and he will not match selected segmentation filters using his activity (Recently purchased, Recently visited, Churn prediction, etc.) as if he didn’t have an order and a product visit before.
    • Only these filters work unchanged:  A/B test audience split, Custom customer parameter, Customer id, Data permission, Date when last mail was received, Days since last mail received, Days since registration, District, Email, First name, Full name, Gender (based on the name and the email address), Newsletter frequency, Phone number, Registration date, SMS frequency, Zip code.
  • anonymized_only
    • All data of the customer are ignored, the system only uses anonymized data (behavior patterns) in order to train our algorithms.
    • Such customer can’t be targeted by Samba in any way – this customer isn’t available in the Samba database.
    • Use this option when the customer asks you to delete all the data and you are not able to delete him from all feeds used in Samba.

 

Customer Tracking

As an extension to Samba tracking script and methods, when a visitor decides not to allow tracking website behavior for web personalisation, you can implement setTrackingPermissions method below.

diffAnalytics.setTrackingPermissions(perms)

  • perms{doNotTrack: boolean}
  • doNotTrack
    • required parameter (boolean)
    • Whenever the visitor deny to allow tracking website behavior, call this method with “doNotTrack: true“. In other cases, use “doNotTrack: false” or just do not call this method at all.
    • In case of “doNotTrack: true” , the web personalisation doesn’t take the browsing history of the customer into account, but purchase history can be reflected. See Web personalisation section on how to ignore purchase history in recommenders too.
  • Default value doNotTrack: false” is assumed if it has never been called for the visitor.
  • Call this method after every change of consent or after every page load.
  • Samba always remembers the last known value for the visitor. This is the only added value compared to using “doNotPersonalize:true” when calling product recommenders (see below), which is blocking usage of web activity and, additionally, purchase history for the specific method call only. This can be a useful feature if you don’t store the non-consent information on your side.

Web personalisation

All Samba personalisers can additionally contain the following optional parameters beyond the standard implementation of web personalisation via Javascript API:

  • customerId
    • optional parameter (string)
    • Samba uses the purchase history for the customerId (which does not have personalization disabled in the feed using the DATA_PERMISSION attribute). The actual merging to the customer profile does not take place (the customerLoggedIn method is used for this).
    • In the case of absence, there is no personalization based on the customer’s account and thus only web browsing history can be reflected.
  • doNotPersonalize
    • optional parameter (boolean, default: false)
    • If true, personalization is based on the currently viewed product only, i.e., no visit or purchase history of the customer is taken into account.

Examples

Customer refused to use any tracking or purchase history for web personalisation.

var yPers = diffAnalytics.personaliser("campaignName");
var result = 0
yPers.personalisedHomepage({count: 6, doNotPersonalize:true}, function(err, data) {result=data})

Customer allowed to use all tracking and purchase history for web personalisation.

var yPers = diffAnalytics.personaliser("campaignName");
var result = 0
var sambaCustomerId = Math.random().toString(); // just for testing purposes yPers.personalisedHomepage({count: 6, doNotPersonalize:false, customerId:sambaCustomerId}, function(err, data) {result=data})

 

Use cases

Not logged-in user allowed to be tracked

  • Data feeds
    • not available
  • Customer tracking
    • all methods except customerLoggedIn
    • setTrackingPermissions(doNotTrack: false)
  • Web personalisation
    • customerId  not used
    • doNotPersonalize:false or not used

Logged-in user allowed to be tracked

  • Data feeds
    • DATA_PERMISSION = full
  • Customer tracking
    • all methods
    • setTrackingPermissions(doNotTrack: false)
  • Web personalisation
    • customerId  used
    • doNotPersonalize:false or not used

Not logged-in user refused to be tracked

  • Data feeds
    • not available
  • Customer tracking
    • setTrackingPermissions(doNotTrack: true)
  • Web personalisation
    • customerId  not used
    • doNotPersonalize:true
 

Logged-in user refused to be tracked

  • Data integration
    • DATA_PERMISSION = do_not_personalize
  • Customer tracking
    • setTrackingPermissions(doNotTrack: false)
  • Web personalisation
    • customerId  not used
    • doNotPersonalize:true
 
 

 

This post is also available in: Czech

Updated on October 8, 2021

Was this article helpful?

Related Articles