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

FTP Enpoint to download events

IBM Offer toolkit that is very limited in the way that it works, create a duplicate files for each single event and works with SQL, ORACLE and DB2 only. A really simple way to download event is that the events will push to a sFTP destination. Today (a poor clearly specified) the FTP endpoint is only to share audiences. 

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Dec 14 2018
  • Planned for Future Release
How will this idea be used?

To simplify the events download process. Every company has a FTP site and much more an ETL tool to get the events and nurture a DB (to then create BIG Data Models)

What is your industry? Professional Services
What is the idea priority? Urgent
DeveloperWorks ID
RTC ID
Link to original RFE
  • Attach files
  • Admin
    Peter Mercado commented
    December 19, 2018 23:10

    Thank you Diego for your submission. 

    This is a requirement I have seen before and I am exploring it as a 2019 deliverable. However, I need additional input from you to help define this idea. From an experience perspective, would you simply want to register your company FTP site as a UBX endpoint that can receive either events or audiences? Are there any authentication/security considerations we should be accounting for? Finally, if sending events to the ftp side, is there any expectations of how the data should be formulated (i.e. payloads like the ones you see in the Toolkit are sufficient or something else)?

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    December 20, 2018 20:55

    Hi Peter

     

    Thanks for your answer

     

    Events or Audiences: Events from email, SMS and Mobile Push. (Actually exist an FTP endpoint to transfer audiences)

    Security: sftp is Ok

    Payloads: Toolkit use email, Mobile Phone Number and Mobile user Id as identifiers, ideally include some field from Campaign Automation Database, like customer id or some other custom field as identifier.

    File names: Actually, when we download events trough Toolkit, file names aren’t identifier the even type, will be more useful that the name begin with Event Type + Date (like: email_open_20181220_eventidXXXXX)

    File type: Toolkit download as json file, and then create a TAB file. I think that json file is OK to include into an ETL process. Of course, in a csv file or tab file with field names will be more easy.

     

    Thanks

  • Admin
    Peter Mercado commented
    December 20, 2018 22:05

    Thank you Diego. We will evaluate this and return with additional questions if necessary.