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

Exclude API URLs from Entry Pages in Journey Reports and Metrics

When I run a journey report for a funnel in the entry page section I see APIs are the considered entry page often.  This is inaccurate, and based on the UBX connection should allow some flexibility to the type of connection or data being sent over. I don't know if this is because we are a CXA customer who uses Tealeaf with the Akamai Connector or if it's by design.  I'm thinking that only SDK screenviews that are seen from the Tealeaf SDK should come into play here and an exclusion of Akamai page URLs is needed.  An api call should never be considered an entry point url.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Jan 29 2018
  • Under Consideration
How will this idea be used?

The business wants to use CXA and pull a journey report on a funnel from Sprint, VMU, or Boost web or native apps.  The events that are being sent over are page level events for a funnel.  The journey report works fine and pulls the right mappings and mindsets, and the business looked at the first journey report with me and was wondering why an API would show under the entry page section.  We would expect to see the entry page into the flow when a journey report is setup where the first touch point is emtpy and the last touch point is the confirmation page, with a report that is set to pull top paths.

What is your industry? Telecommunications
What is the idea priority? High
DeveloperWorks ID
Link to original RFE
  • Attach files
  • Admin
    ANA Cardenas commented
    December 19, 2018 20:06

    Thank you for your feedback! It sounds like this affects the data that flows to CXA journey and mindsets through UBX, mainly from Tealeaf. If so, we will want to work across capabilities. I will start that conversation.