Deleting customer data

Before you can use the Deliver utility to generate queries, you must set up the gdpr.properties file and create an input .csv file that contains information for the customers that are to be deleted from the Deliver database.

Before you begin

Deliver GDPR utility supports JDK version 1.8 or higher. GDPR <UTILITY_HOME> is <CAMAPIGN_HOME>/tools/GDPR

Complete the following steps before you run the Deliver utility to generate queries.
  • You must delete the customer data from the Campaign user database before you run the utility.
  • It is recommended that you take a backup of the database before you run the queries that are generated by the utility.

About this task

Any errors that occur during the running of the utility are logged in the gdpr.log file that is located in the <UTILITY_HOME>/logs folder.

Use the log4j2.xml file that is located in the <UTILITY_HOME> folder to make changes to the logging for the utility.

Procedure

To delete customer information from the Deliver system tables, complete the following steps.
  1. For Unix, ensure that the file permissions are set to 777. For Windows, ensure that you have permissions to run the utility as an administrator.
  2. Create the input .csv that contains the customer records that are to be deleted. Enter each record on a new line.
    Use the sample .csv files that are provided for your reference. They are located in the <UTILITY_HOME>/sample folder.
    • If the audience contains a single database field, use the sample Customer.csv file. For example, if you have a Customer audience with field CustomerID field in the database, create a .csv file similar to Customer.csv that contains the Customer IDs of all the customers who have asked for their information to be deleted.
    • For a composite audience that contains multiple database fields, use the sample CompositeAudience.csv file. For example, if you have a composite audience with fields Field1PK, Field2PK, and Field3PK in the database, create a .csv file similar to CompositeAudience.csv that contains the field values of all the customers who have who have asked for their information to be deleted.
  3. Configure the various properties as required in the gdpr.properties located in the <UTILITY_HOME> folder. The gdpr.properties file contains the detailed description for all the properties.

    For example: set IsUnicaDeliverIntegrated=true, set DBType, GDPR_HOME, Db.Schema.Name, etc.

  4. Set GDPR_HOME and Java_HOME in gdpr_purge.bat or gdpr_purge.sh and in log4j2.xml located at <UTILITY_HOME>located at <UTILITY_HOME>
  5. Go to the <UTILITY_HOME> folder.
    • For Unix, run gdpr_purge.sh.
    • For Windows, run gdpr_purge.bat as an administrator.

    The SQL queries are generated and saved in the location that is mentioned in the gdpr.properties file. Multiple SQL files may be generated depending on the output file size that is specified in the gdpr.properties file.

  6. Run the queries on the database. The Deliver system tables are part of the Unica Campaign schema.
    • The Campaign application must be shut down when the delete statements are run on the Campaign system database.
    • You must run the queries for composite audience IDs before you run the queries for single audience IDs that might be part of the composite audience.
    • You must run all the SQL files that are generated by the utility.
    • If there are multiple partitions, the SQL queries must be run on every database schema for every partition.
  7. Verify that the required data is deleted and commit the results.