WCA Tables

  • UA_EmailClick
  • UA_EmailOpen
  • UA_EmailSend
  • UA_EmailBounce
  • UA_EmailOptOut
  • UA_InteractedSMS
  • UA_Mob_Push_Send
  • UA_SentSMS
  • UA_SimpNot_AppOpened
  • UA_SimpNot_URLClicked
  • UA_Gen_Event_Record

Customer information can also reside in the additional audience history tables used in the Unica Campaign system. The Unica Campaign user may hence configure the GDPR property file for additional Audience level to delete records from the additional history tables.

Note:
  1. Deleting Customer information from Strategic segments: Customer information also can reside in Strategic segments (.bin files) located at <CAMPAIGN_HOME>/partition/partition1/segments. To delete customer information from these bin files, the user is required to follow the steps below:
    1. Refresh / Remove Campaign user database to delete customer records (that is required to be erased from the Unica Campaign system).
    2. Execute all the flowcharts from which the strategic segments are created.
  2. Deleting customer information from the output files / tables generated by Snapshot and Maillist/Calllist process box: The user is required to delete customer information from the user database and re-run all the flowcharts in which the Snapshot and the Maillist/Callist process boxes are used.

    For existing/old output files: The customer must review and delete user records (that are required to be erased in the Unica Campaign system) from the output files.

  3. Deleting customer information from temporary tables (UACS and UAC_EX) generated by Create_seg, Extract and Segment process box: The user is required to delete customer information from the user database and re-run all the flowcharts in which Create_seg, Extract and Segment process box is used.
    Note: Segment process box: This is applicable only to the Segment process box in which the 'Create Extract tables' configuration check-box is selected.
  4. Unica Campaign application down time is mandatory when these delete statements are executed on the Unica Campaign system database.
  5. Unica Campaign users must ensure that they delete the user records that are to be erased from the Unica Campaign system, from Unica Campaign user database. The Unica Campaign GDPR utility does not delete user records.
  6. The Unica Campaign GDPR utility provides the delete statements only. The Unica Campaign user should share these delete statements with the DBA, get them reviewed, and then execute on Unica Campaign system tables for all the partitions configured.
  7. The Unica Campaign GDPR utility generated delete statements do not contain commit statements. User can set the auto commit settings as required, or do a manual commit.
  8. It is recommended to have indexes created on all the Additional history tables. This speeds up the delete operation.
  9. The Unica Campaign GDPR utility does not take care of deleting customer records (that are required to be forgotten in Unica Campaign system) apart from the tables mentioned above. The Unica Campaign user should take care of deleting these records on their own. This might include deleting records from Unica Campaign temporary tables, output flat files, custom output tables generated from Unica Campaign, and so on.
  10. No Data from reference tables such as UA_OfferHistAttrib , UA_TREATMENT and UA_OfferHistory is deleted if it has reference data in the UA_CONTACTHISTORY table. For example, if one offer / multiple offers are given to multiple customers (say CustomerID = 1,2,3,4,5) and the user wishes to delete only CustomerID =1 then no data from reference tables will be deleted because CustomerID = 2,3,4,5 will still refer to data in those reference tables.
  11. All files and executable related to GDPR are available at the<CAMPAIGN_HOME>/tools/GDPR path
  12. This gdpr_purge utility does not generate any delete statements for tables related to Unica Deliver.
  13. GDPR for Unica Optimize: The Files/ Data that we use in Unica Optimize are taken from Unica Campaign. Hence, when we run the GDPR utility in Unica Campaign, that very data is also used by Unica Optimize. So, we do not need a separate GDPR process for Unica Optimize.
    Note: However, once the GDPR utility is run in Unica Campaign, we need to re-run Unica Optimize sessions so that the respective records are updated.