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

Update Program Email Content in real-time without deactivating

Currently, when building an automation program, email content must be static - i.e. the template is built, uploaded and applied to the relevant program. If you want to amend the email content within a program you must make the amends to the template, deactivate the program, upload and apply relevant actions again, and then re-activate - a quite tedious and time consuming process.

It would be extremely useful to be able to update email template content & URL's in the template section and have the relevant program reflect these changes instantly (once content fully approved). With regards any 'click activity' that might trigger an action within the program; as long as the URL label / name remains the same, the program would not have to be altered at all - it would simply recognize the same URL label / name and continue to run accordingly.

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

The idea will be used to save huge amounts of time for automated programs whereby content is regularly updated which, in theory, should be the vast number of the programs, as non-one wants to use old content on a regular basis. You get to keep the main 'shell' of your perfectly assembled automation together (plus the numbers, rules, conditions etc) but can still update the elements within it without having to deactivate / reactivate all the time.

What is your industry? Financial Markets
What is the idea priority? High
DeveloperWorks ID
RTC ID
Link to original RFE
  • Attach files
  • Admin
    Diane Bowman commented
    19 Jun 21:45

    Thanks for this idea. We are researching and have a few questions.

    1. . Can you tell us what the expectations are for versioning, e.g. you changed the content in step1, how many contacts go version 1, how any version 2. is this needed?

    2. What if after applying a changes mailing across multiple mailings in multiple programs, you find an error, and contacts have aready been sent and proceeded forward, how would like that to be handled?

    3. Sounded like you also would like an approval process to part of the workflow from content to programs to accept pr changes prior to the program picking up the new content?

    4. And from a workflow perspective, Would you typically edit in the Content area and want to associate/select programs there or in a program have a "content refresh" option in that interface or both?

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    20 Jun 13:56

    1. I am less concerned about versioning and more about efficiency. Even for a simple typo, much must be orchestrated to resolve. 

    2. Not much can be done at that point. Again, the suggestion is meant as a means for quickly resolving errors. So it would not be all that different from what is in place now. 

    3. A nice to have, but not essential. 

    4. Not totally sure what you are asking... but if I change an email template, there should be an easy means to update it wherever that template is used. 

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    21 Jun 14:35

    1. Don't think this is necessarily required. Up until the content change, everyone would receive version 1. After the content change, everyone who hits that stage in the automation receives version 2.

    2. Again, I don't think this is too important - you would simply amend the email template again to remove the error and set it live. Hopefully you would spot it soon enough so that a minimal amount of people received the error version of the email. Within an automation program, this would still be more efficient than a standard mailing as once a error is made on that and it is sent, everyone would get the version with the error.

    3. I don't think you need an approval process as such - the way I envisioned it was to have a button within the 3rd stage of the sending process for an email (i.e. the CONFIRM AND SEND stage) next to the 'Send Now' button that simply said something like: Update in Program, ideally with this button only showing up if the system recognized that the original template was attached to a Program. The current 3 step email template process (build, test, confirm) is enough of an approval for standard mailings and so should be fine for those feeding into automations also.

    4. I would want to edit all content in the Mailings And Templates section, ensuring that, once built, (for some automations) you would rarely have to touch the program at all as all content could be amended, updated, approved, and set live, outside the automation itself.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    21 Jun 14:37

    Hi Diane,

    1. Don't think this is necessarily required. Up until the content change, everyone would receive version 1. After the content change, everyone who hits that stage in the automation receives version 2.
    2. Again, I don't think this is too important - you would simply amend the email template again to remove the error and set it live. Hopefully you would spot it soon enough so that a minimal amount of people received the error version of the email. Within an automation program, this would still be more efficient than a standard mailing as once an error is made on that and it is sent, everyone would get the version with the error.
    3. I don't think you need an approval process as such - the way I envisioned it was to have a button within the 3rd stage of the sending process for an email (i.e. the CONFIRM AND SEND stage) next to the 'Send Now' button that simply said something like: Update in Program, ideally with this button only showing up if the system recognized that the original template was attached to a Program. The current 3 step email template process (build, test, confirm) is enough of an approval for standard mailings and so should be fine for those feeding into automations also.
    4. I would want to edit all content in the Mailings And Templates section, ensuring that, once built, (for some automations) you would rarely have to touch the program at all as all content could be amended, updated, approved, and set live, outside the automation itself.
    Thanks

    James