Acoustic Campaign Ideas

Submit new product ideas for Acoustic Campaign, Real-time Personalization, Content and Exchange. Before you submit, please review existing ideas; if an idea close to yours already exists, it's better to add comments or vote on the existing idea. We will review your ideas and use them to help prioritize our product development. Best of all, the portal will automatically update you when the status of your idea has been changed.

Connect with your peers and Acoustic experts on the Acoustic Marketing and Commerce Community

Submit ideas for other Acoustic Products:

Other Acoustic solutions
Watson Commerce
Watson Supply Chain

Add logic in programs/send queue to block null or Not Applicable fields in database

We have program entry queries in place to add records to look for notification date = today (see full criteria below). There are times where the harvest fails and "bad" records are put into programs. Since we have a nightly ETL process that updates the Main Database, so if a bad record makes it into a program and the date doesn't = today, then the user receives a notification with text that says "Not Applicable" (this is the text in the database when a user shouldn't get a notification). I'd like to suggest a product enhancement of adding logic to block sends where the fields are null or say "Not Applicable" so bad records don't reach the end user.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Aug 3 2018
  • Already exists
How will this idea be used?

As a marketer, I want to prevent bad records from sending to end users.

What is your industry? Telecommunications
What is the idea priority? High
DeveloperWorks ID
Link to original RFE
  • Attach files
  • Admin
    Diane Bowman commented
    September 28, 2018 13:37

    We do not prevent entry for bad data, but once a contact reaches a step if the email address value is null or for SMS or Mobile, the phone or Mobile ID is null we do exit those contacts from the program automatically so they do not proceed and send.