Customer Feedback

We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.

For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.

Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.

ADD FEEDBACK

All feedback

Showing 540

Multi-variable forced QA

Would like to have a setup so that when there are multiple variables, a QA cookie can be set for each variable so that each can be viewed in the browser independently. Right now a QA cookie set only seems to get you in to an experiment, not view e...
almost 2 years ago in Web Experimentation / QA 1 Future consideration

Make due date times optional

Hi! I would appreciate it if adding a due date "time" for tasks, workflow steps, etc. was optional! Not every task is that time-sensitive/specific, and having a due date time mandatory for every task makes it so that most people use it arbitrarily...
7 months ago in Content Marketing 1 Future consideration

Unique User Identifier

We need to find an element or variable that we can use to uniquely identify the ContentOne users. The best value would be an email address as this is always completely unique for everyone. However, it can also be something else like a company spec...
about 1 year ago in Content Marketing / Miscellaneous 0 Future consideration

Ability to @ mention watchers

It would be great if @watchers was a functional way to notify watchers of a task that there is a comment for them - especially useful when there are a large number of folks that need communicating to.
about 1 year ago in Content Marketing / Notifications / Tasks, Campaigns, and Events 1 Future consideration

Automated alert on the scheduler container (Linux).

Automated alert on the scheduler container (Linux). it seems not practical we have to check it every day. It will be great if they have alerts on container crashing/being not reachable similar to the ones for the website instance where Optimizely ...
about 1 year ago in DXP Cloud Platform / Infrastructure mgmt. 0 Future consideration

Need Notes fields in Work Requests

In our business, we end up with a number of Work Requests that are OVERDUE, and there are 4-5 of us checking on those. It would be great to be able to quickly see the last time someone reached out - in the list view - so we wouldn't have to click ...
8 months ago in Content Marketing 0 Future consideration

Feature Flag Lifecylcle Analytics

One of my goals as an administrator of feature flags is to understand the lifecycle of our feature flags. When it was created and the various data points for it's rollout. I struggle to maintain the lifespan of our flags without alot of manual work.
over 2 years ago in Feature Experimentation / Feature Flagging Workflows 1 Future consideration

Required Fields on Events

We'd like to ensure our events are tagged as thoroughly as our tasks and campaigns, but there's no way to set up required fields today.
almost 2 years ago in Content Marketing / Tasks, Campaigns, and Events 0 Future consideration

Sync CMS pages to CMP Library

Unless we select every page individually from CMS there's no way to see them in our CMP library, search for a page, and add it to a task.
8 months ago in Content Marketing / CMS + CMP Publishing 0 Future consideration

Use Content Proofing for CMS Pages

When reviewing content in a task, digital marketing teams regularly use the Content Proofing feature to leave comments directly on the asset being reviewed. This isn't available for CMS pages and the comments on tasks aren't linked to the page bei...
8 months ago in Content Marketing / CMS + CMP Publishing 0 Future consideration