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
For orgs with many applications, adding an optional criteria for which application to apply hit attributes to would greatly decrease the complexity of creating privacy hit attributes where the mark-ups are different enough between domains to cause unintended consequences.
How will this idea be used?
The Macy's and Bloomingdales sites use "just different enough" in use of class names and ids to make privacy hit attributes complex. Both domains are under the same Org. If the application defaulted to ALL but had the option of specifying one or multiple, this would ensure the privacy blocking would not have unintended blocking on the other application.
|What is your industry?||Retail|
|What is the idea priority?||High|
|Link to original RFE|