This technote explains how to install and deploy the Privacy (GDPR) package on Adobe Campaign Classic legacy versions. It applies to versions 6.1 and 7 from build 8600 to 8930.


The General Data Protection Regulation (GDPR) is the European Union’s (EU) new privacy law that harmonizes and modernizes data protection requirements, effective as of May 25, 2018. GDPR applies to Adobe Campaign customers who hold data for Data Subjects residing in the EU. As compliance will be a shared responsibility with your enterprise, we look forward to partnering with you to address any new obligations for data governance and privacy by design features.

The GDPR package, which contains additional functionality to help you become GDPR compliant, is available, out-of-the-box, in Campaign Classic 18.4 (for both 32 bits and 64 bits versions). Customers using Campaign Classic 18.4 can import the package using the standard package import wizard in the client console.

To learn how to use Campaign Classic's Privacy features, refer to the detailed documentation.

For customers using older versions, the package can be deployed as explained below.


This technote applies only from build 8600 to builds prior to Adobe Campaign 18.4.

For builds prior to 8600, customers can install the package but it will not be supported by Adobe. An upgrade to recent builds is required if any issue is found when using the feature.

Package content

The package contains new entities for GDPR (schemas, forms, javascript and JSSP) as described below.

These entities are found in <Adobe Campaign installation folder>/datakit/nms/<language> folders


The package is available in 4 languages.





<Campaign installation folder>/datakit/nms/eng English
  • strings
  • srcSchema
  • schema
  • package
  • form
  • js
  • jssp

When installing the package on Windows, please verify the JS and JSSP folders existence in the /eng sub-folder. If they are not available in this folder, they should be available in the /fra sub-folder.

<Campaign installation folder>/datakit/nms/fra French
  • strings
  • srcSchema
  • schema
  • package
  • form
<Campaign installation folder>/datakit/nms/deu German
  • strings
  • srcSchema
  • schema
  • package
  • form
<Campaign installation folder>/datakit/nms/jpn Japanese
  • strings
  • srcSchema
  • schema
  • package
  • form

Downloading the package

Hosted instances

For hosted instances (Marketing, Mid and/or Message Center execution), please contact Adobe for deployment request.

On-premise instances

The GDPR package is available in the Extranet Download Portal.


If you cannot find the GDPR package from the Download Center, please contact Adobe Campaign support ( to get access to it.

Installing and deploying the package


Please verify that the package is installed on all the containers in case Campaign server is running on multi containers architecture.

Here are the general steps for install the GPDR package:

  1. Install the package on the Campaign server: copy the package files listed in the Package content section to the right places on the Campaign installation folder.

  2. Deploy the package on the Campaign instance: run the package entity to import GDPR entities (schemas, forms, etc.) into a given instance. This step is similar to importing standard package via the import wizard in the client console.


The GDPR package for Linux contains:

  • a shell script:
  • a zipped package: gdpr.tgz

To install the package:

  1. Place the and gdpr.tgz files in the same folder (for example /tmp).

  2. Launch passing instance name as parameter: root@CampaingServer:/tmp# ./ <instance_name>

  3. Once the script is finished, customers can use the feature and do not need to deploy/import the package in the client console which is already handled by the script.


  • In case of multiple containers, the script MUST be executed sequentially.
  • The script is run on ansible mode and not interactively.
  • Root user MUST be used to execute the script.
  • <Instance_name> parameter is required, otherwise the script will throw an error.
  • The package is installed with the corresponding language found in the instance configuration file.



The installation on Windows is manual. There is no script/executable file supporting.

The GDPR package for Windows contains a zipped package:

To install the package:

  1. Extract the zipped package in the temporary folder. The files are archived using relative path from datakit node (i.e. datakit/nms/...).

  2. Copy one by one all the files found in the language sub-folders to corresponding destination sub-folders of Campaign installation folder.

  3. Verify JS and JSSP folders are available in the Campaign /eng folder. Otherwise, they should be found in the /fra folder. If so, move gdpr.js and gdpr.jssp files to JS and JSSP folders in /fra.

  4. After copying all the files to the correct destinations, log in to the client console and use the standard package import wizard to import the GDPR package.



The GDPR package introduces a new named right :  PRIVACY DATA ADMIN (privacyRight) to manage collecting and deleting data.

All Data Controller operators who have access to the client console need to have this right to manage privacy requests.

If the Campaign instance is being deployed with Mid and/or Message Center execution instances, the operators used in the external accounts to access remote instances are also required to have this right.

  • The package must be installed on Mid and Execution instances to delete data on remote instances (mirror page, event, broadlog, etc.)
  • By default, privacyRight is added to 'mid' and 'mc' out-of-the-box operators. For other operators created by customers on Mid and Execution instances, the right needs to be added manually.
  • Hybrid customers should check with Customer Care in case they do not have access to remote instances.


If you migrate to 18.4 or above, you should not experience any issue since the new build already integrates the GDPR package.

When migrating to a build prior to 18.4:

  • clients still using V6: please verify that GDPR package files are not removed during upgrade process. If so, just re-apply the instructions given in Installing and deploying the package to install/deploy the package again.
  • clients switching from V6 to V7: the package needs to be re-deployed because Campaign installation folder will be changed.