Watson Marketing Ideas

Submit new product ideas for Campaign, Interact, Marketing Operations, Marketing Platform, Campaign Managed Hosted, interact Managed Hosted, Marketing Operations Managed Hosted, Digital Analytics, Tealeaf, Universal Behavior Exchange, Watson Customer Experience Analytics, Watson Marketing Insights, Watson Content Hub, Web Content Manager and WebSphere Portal solutions. 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:

•  Watson Campaign Automation
Watson Commerce
Watson Supply Chain

Ability to Export Event, Attributes and Dimensions from Tealeaf

There are times when we need to export our Events, Attributes and Dimensions in order to use for:

  • documentation to our user community
  • tracking down events and their components that are no longer firing
  • have not fired over a specific duration
  • to add to our own ticketing/issue tracking tool for distribution of work among the event admin team. 

It would be great if IBM had an export feature that would export our Event, Attribute and Dimension Data to Excel.

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

Currently, we must reach out to IBM in order to get an export of events, attributes and dimensions that are:

  • Inactive
  • Have not fired over a specific duration
  • New and need to be added to our documentation that we share with our eventers and our TL user community.

This information helps us when we open internal work tickets to have different team members triage inactive events or events that haven't been firing.  We can break the list down into chunks that can then be shared across the team.

As changes are made to existing events, attributes and dimensions or new items are created, we can update our documentation that we share with our end users to provide an index of what is in TL and what can be used for searching or reports. 

This information is also used to meet with our different groups to review flows and identify areas we need to add or modify our capture.

Being able to export this information will help us share what TL can do and allow us to use it within our own ticketing/issue tracking tools.

What is your industry? Telecommunications
What is the idea priority? Medium
DeveloperWorks ID
RTC ID
Link to original RFE
  • Attach files