Acoustic Ideas

Submit new product ideas for Campaign, Interact, Marketing Operations, Marketing Platform, Campaign Managed Hosted, interact Managed Hosted, Marketing Operations Managed Hosted, Digital Analytics, Experience Analytics, Exchange, Watson Marketing Insights, Content, 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 Acoustic experts on the Watson Marketing and Commerce Community

Submit ideas for other Acoustic Products:

Watson Commerce
Watson Supply Chain

Step Events Issue

Step events and regular events don't work together.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Jun 29 2018
  • Needs More Information
How will this idea be used?

Step events and regular events don't work together.

What is your industry? Insurance
What is the idea priority? High
DeveloperWorks ID
Link to original RFE
  • Attach files
  • Admin
    Rob Hain commented
    September 25, 2018 19:01

    Steve - We are investigating this, but the development team would like more information on this issue.  Can you provide an example workflow - what doesn't work and how it would - that we can use to clarify the requirement?

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    October 08, 2018 21:56

    “Make step events and regular events work together.”


    • We have seen a positive for a Step hit attribute (HA) result in a negative for the TL Event. An obvious error or bug.
    • Does the concept of a ‘hit’ consistently apply to both full roundtrips between client & server and to client-side UI captured events?
    • I see Step HAs and Events, but I do not know the scope or context. Are they for a single bracketed UI event (JSON record), or for a set of UI Events in a single request buffer/view/hit?
    • Do Tealeaf Event's ‘sequence’ or ‘distance’ logic work with Step HAs & Step Events?
    • A hit identifier in the EventTester does not match the hit id number in the BBR or in RTV. Can this be made consistent? It’s quite important when debugging an event.
    • The ‘hit count’ in a session list does not reflect the actual count of hits & UI Events in a session.
    • Do “TealeafTarget” (collection of the UI Events payload from client) need to be displayed in the navigation list? Are they a “hit” or something else? It seems to depend on how you represent and count a UI Event.
    • We have seen the first few ‘hits’ in a replay view of the BBR, do nothing in replay mode/view. They seem to be placeholders that are followed by UI Events. Are they a hit or not? They are currently distracting. Do they need to be displayed in the BBR navigation list?