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

Enable duplicate search and merge functionality for databases greater than 1 million records.

WCA needs to increase the limit at which the "Find Duplicates" functionality is allowed or create a simple API solution for removing records from a master database and moving those records to an database for inactives. This will allow orgs to maintain their address lists and keep contact data updated

If an organization utilizes a single master database to relate multiple relational tables and keep contact records of various types (customers, prospects, partners) up to date, WCA disables the "Find Duplicates" functionality for databases with 1 million + records. This creates issues when a contact has the ability to enter the database from multiple entry points. For example, an existing partner is already in the database, but fills out a web form which opts them into an automated nurture email series. They now receive the series and any emails you might send to qualified partners. This can lead to dissatisfaction, opt-outs, and complaints.

The "solution" of downloading the database and finding the duplicates then purging is unrealistic from an Excel capabilities standpoint as well as the amount of time it would require. For instance, your database might exceed the maximum number of rows allowed in Excel (which would then require you to break your database down into more manageable queries for export...more time invested) and if it doesn't, sorting hundreds of thousands of contacts often causes Excel to error out. Plus, you would then have to aggregate any duplicates purge them and then merge the duplicate records and re-upload. This is a massive undertaking if you need to dedupe daily as an admin task.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Mar 8 2019
  • Needs review
How will this idea be used?

This will keep contact data accurate and allow for expedient processing for this database admin task. It will also allow orgs to remain with WCA due to it being a long-term solution for keeping, managing, and acting on database information. The current duplicate search and merge function does not allow for a company to grow past 1 million without sacrificing data validity.

What is your industry? Insurance
What is the idea priority? Urgent
DeveloperWorks ID
RTC ID
Link to original RFE
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    04 Apr 15:52

    I know part of the issue we have is because we integrate with SFDC. The core database must be a non-keyed database, which allows potential dups to be created. It's difficult to manage this and we try our best, but if the find dup functionality was increased to over 1mil it would help out a great deal.