Watson Campaign Automation Ideas

Submit new product ideas for Watson Campaign Automation, Watson Real-time Personalization, Watson Content Hub and Universal Behavior 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 IBM experts on the Watson Marketing and Commerce Community

Submit ideas for other Watson Customer Engagement Products:

•  Other Watson Marketing solutions
Watson Commerce
Watson Supply Chain

Allow nested queries to trigger programs

currently programs can not be triggered by a query that references another query inside of it, which Automated Message Groups and regular mailings allow. Please fix this! right now we have to either create one large complex query (which a change may necessitate multiple quries being updated) or trigger the first email that should be in a program with an AMG and then trigger the rest of the program on a simple of query of who was sent that mailing, but that splits reporting between AMGs and Programs

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Jun 26 2018
  • Uncommitted Candidate
How will this idea be used?

This would allow people to use nested queries to update multiple queries simultaneously (i.e. when a new product is added to a category, or when a new page is created that should trigger interest in a product type) with programs. current limitation of no nested queries in programs is extremely inefficient

What is your industry? Non-Industry Specific
What is the idea priority? Medium
DeveloperWorks ID
Link to original RFE
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    June 27, 2018 16:32

    Completely agree with this one. This was on the old Idea board too.

    They finally allowed RT criteria to be included in Program Entrance Queries. This is a logical next step!

    Our use case is that we have a standard suppression query and we want it included in the entrance criteria to exclude those people. Other option is to make it an exit criteria but why do i want all of those extra people entering the program in the first place?

  • Admin
    Diane Bowman commented
    July 30, 2018 15:46

    We agree! We need to look at performance impacts and what should happen if/when the "sub-query' changes.