Knowledgebase
Privacy Control
Posted by Innometrics Profile Cloud on 5 Apr 2016 15:53

Introduction

Privacy control is a functionality within the Innometrics Web Data Collection app, that allows you to manage how different apps and web events related to your website are activated depending on user acceptance/rejection.

Typical uses of this functionality would be to handle cookie compliance laws, or to allow users to explicitly opt-in / opt-out of different types of data tracking and personalization mechanisms.

How it works

Privacy control works with something called Activation Policies. An Activation Policy describes how a specified set of apps or tags should be activated.

Activiation Policies are defined per section, so if you have multiple sections you might need to configure multiple Activation Policies. This also means you can have different activation logic on different sections.

It is also possible to specify different activation logic for different apps. For example, some apps might be active by default, but allow users to “opt out” from, while other apps might be opt out and requires an acceptance from the user to be “opt in”.

 

How to setup a new activation Policy

·         Start by creating a new Activation Policy and give your policy a name

An Activation Policy consists of four parts:

1. A list of which apps the Policy governs.

 Select the application you intend to add a conditional rule to. An application in this case refers to an app or a tag.

 

 

2. Whether it is an “opt-in” policy or a “opt-out” policy.

This controls the default behavior of the selected application, meaning that the user has not provided any explicit acceptance or refusal.

·         If the policy is set to be “opt-in” it means that the application will not be activated until an explicit opt-in Event is triggered.

·         If the policy is set to be “opt-out” it means that the application will be active on first visit and all subsequent visits, until an explicit opt-out Event is triggered.

 

 3.      An “opt-in Event” reference, specifying the Event that signals to Profile Cloud that the user has Accepted

 

Any of your configured Events can be used here, or you might need to set up a new Event for this specific purpose.

If the policy is by default “opt-in”, this is mandatory.

 

4.      An “opt-in Event” reference, specifying the Event that signals to Profile Cloud that the user has Rejected

 

Any of your configured Events can be used here.

If the policy is by default “opt-out”, this is mandatory.

 

Example

Scenario

Imagine that we have a website which runs Profile Cloud, Google Analytics and On-Site Personalisation (mainly using Geolocation).

On this site we want to:

·         Get visitor permission before we store any data tracking cookies or save any data into a cloud service

·      Also allow visitors to the site to “opt out” of any personalization mechanisms

To accomplish this, we would define two Activation Policies:

  1. An “opt-in” policy for Profile Cloud Data Collection and Google Analytics. Let’s call this policy “Tracking Policy.”
  2. An “opt-out” policy for On-Site Personalization. Let’s call this the “Personalization Policy.”

 

First task: set up the Tracking Policy:

  1. Go to Innometrics Web Data Collect App and find the “Privacy Control” tab. If the tab is not present, contact your Profile cloud account manager or clientcare@innometrics.com
  2. Click on “Create new activation policy”

 

3.      Name it “Tracking Policy” and click “Create”

 

 

4.      Click “Add new Application”

 

 

5.      Search for and add Google Analytics and Profile Cloud Data Collection

 

 

6.      Select that the policy should be “opt-in”

 

 

7.      Select your opt-in Event. For instance, you might have a cookie bar with a button the user can click to Accept tracking cookies

 

 

8.      Save the policy

 

 

Now you have a Tracking Policy which will prevent Profile Cloud from storing any tracking cookies (both its own, and Google Analytics’) and prevent any data from being collected by both Profile Cloud and Google Analytics, until the user triggers the “Accept Cookies” event.

Setting up the Personalisation Policy follows the same procedure, but using an opt-out policy instead.

 

1.      Go to Innometrics Web Data Collect App and find the “Privacy Control” tab:

2.      Click on “Create new activation policy”

 

3.      Name it “Personalisation Policy” and click “Create”

 

 

4.      Click “Add new Application”

 

 

5.      Search for and add On-site Personalization

 

 

 

6.      Select that the policy should be “opt-in”

 

 

7.      Leave the “opt-in Event” empty – since this is an opt-out policy, it is optional and for the current example we don’t need it.

8.      Select your opt-in Event. For instance, you might have a cookie bar with a button the user can click to Refuse cookies

 

9.      Save the policy

 

 

Now you have a Personalization Policy which will prevent Profile Cloud from triggering the On-Site Personalisation for any reason.

 

                                              

(1 vote(s))
Helpful
Not helpful

Comments (0)