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

Allow more than 64 session attributes

I have been to two customers that use session attributes that exceed the current limit of 64.  One customer used session attribute placed on different user group search templates and wanted to exceed the 65 limit.  This usage can easily exceed the current 64 limit.  Another customer wanted session attributes for AJAX variables. as well as, normal session attributes (Login ID, account #, etc.).  There were many AJAX values and this use easily exceeded the 64 limit.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Nov 8 2019
  • Under Consideration
How will this idea be used?

Used when customers have legitimate needs exceed the 64 limit.

What is your industry? Professional Services
What is the idea priority? Low
DeveloperWorks ID
RTC ID
Link to original RFE
  • Nov 8, 2019

    Admin Response

    Thanks for submitting this. Other similarly situated are urged to comment and vote!

  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    11 Nov 18:36

    If there's a technical concern(reporting/search database growth for example),  perhaps "non-tracked global variables" akin to session attributes would be a good solution.  This would be handy for eventing, data streaming, etc. without the need to use it for session searches, etc.