Acoustic Campaign Ideas


The Acoustic Ideas portal has moved! Please sign up for our new Ideas portal and submit your suggestions at https://ideas.goacoustic.com.

Option to Delete contact from data source at end of program flow

In a situation where no further activity is applied to a contact when a program completes and there is no longer a reason to keep the contact on file, a method should be applied to the "Exit" item facilitating deletion upon exit. 

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Aug 30 2018
  • Under Consideration
How will this idea be used?

GOAL: Having completed all activity related to a contact there is no longer any reason for that contact to remain in the data source.  For example, for the purpose of "onboarding", a prospect is added by API to a data source intended to contain contacts only during the onboarding process. The contact is automatically added to an onboarding program that attempts to send a welcome message immediately and again after 24 hours if the contact has not responded to the initial message. Whether the onboarding attempts are successful or not, the desired outcome is that the prospective contact is removed from the data source.  This eliminate the need to poll the data source or perform scheduled processing to purge processed contacts.

What is your industry? Consumer Products
What is the idea priority? Medium
DeveloperWorks ID
RTC ID
Link to original RFE
  • Attach files
  • Admin
    Diane Bowman commented
    August 31, 2018 12:19

    I am investigating this, and will respond once I have more information to post.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    August 31, 2018 16:38

    To provide some insight:  I am struggling to find a straightforward solution to identify and then deleting records from a database using the XML API exclusively.  If you have access to support case #00736378, you will see that support is unable to provide a way for me to use the XML API to accomplish the following:  1) retrieve a list of recipient records that match a particular criteria and 2) subsequently delete the recipients in that list.  This would not be necessary if I had the ability to define a test to be executed as a program exits that could delete a recipient when the program's path exits.  SUPPORT has suggested a workaround which seems cumbersome: 1) use XML API to create a "profile query" to produce a LIST ID, 2) use the "Export API" with the LIST ID to obtain a CSV file of matching recipients and 3) parse the CSV file and use the XML API to submit <RemoveRecipient> requests for each record in the CSV file -- all this necessary because I cannot delete a recipient when exiting the program's path. 

  • Admin
    Diane Bowman commented
    November 02, 2018 21:57

    So sounds like a configurable program Exit, where users could choose to either exit contacts from that program when they reach the goal, or exit and add them to a contact list or exit and delete them from the database completely is what you're looking for? do you tend to have a mix of needs or would you set this at the program settings global level e.g.delete all that exit? Would you expect an UNDO, where its not a complete delete but someplace you can go and see and potentially undelete?