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

Query that can reference several databases, instead of just one

Currently: A query can only reference one database. ex: If i want to send to subscribers in our main database, but also import a custom list of a few people, I have to do this all as separate databases & query.

Proposing: It would be more efficient if I could build one query that pulls from the main database and then also pulls in other databases (like the custom list upload). And then the mailing can just go out once, to the one query.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Jul 18 2018
  • Needs review
How will this idea be used?

It will allow more power to queries to be able to pull in from different databases and allow for simpler, quicker builds & sends

What is your industry? Other
What is the idea priority? Medium
DeveloperWorks ID
Link to original RFE
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    August 01, 2018 00:11

    This a great idea that can be usefull to simplify the process with other issues, for example. Mobie push is a dinamic database that is updated without control. An example: When a customer login into the app, the SDK send the MUID and other field like account number. If the mobile push resides into a different database, we cannot update every day the data base or inlusive use the Establish Identity API, just join into a Query and use the same query to contact customers for each channel without the necesity to have all data into a single database that is complex to updated every a lot of times. This idea works with SMS too.