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 1836 of 1836

Choose Thumbnail for Video File

We would like to choose a thumbnail for a video file so that we can ensure we always have a quality image to represent the file. This is crucial if we plan to share our collections with prospects (we have to protect our brand image), but important...
over 2 years ago in Content Marketing / DAM/Library 0 Future consideration

Full support for CMS language settings

It should be simple to get language behavior consistent with CMS language settings around fallback and replacement languages.
almost 2 years ago in Optimizely Graph 0 Future consideration

Capture AVS response from PayFlowPro payment gateway

We would like to capture AVS response from PayFlowPro payment gateway to prevent fraud orders. Here is an example of the API response RESULT=0&PNREF=EFHP0D426A53&RESPMSG=APPROVED&AUTHCODE=25TEST& AVSADDR=Y &A VSZIP=N & CVV2...
5 months ago in Integrations 0

Cart History Status Option for PunchOut

When the status is "PunchOutOrderRequest", the only option is to "Resubmit to ERP". However, if the orders we called in/manually submitted to the ERP, I can attached the ERP Number to the "ERP Order Number" input but can't update the status. There...
5 months ago in Configured Commerce / Orders & Payment 1 Investigating

@mention multiple users

It'd be nice to be able to @ mention everyone assigned to a step in a workflow of a task. Similar to slack's "[at] here" functionality.
over 1 year ago in Content Marketing / Notifications 1 Future consideration

Set Asset Expiration Date from Task

I'd love to be able to add the asset expiration date at the same time that I do the rest of my asset tagging, on the task. Sending the asset to the Library and then navigating there to set the date takes longer than it should and is clunky.
almost 2 years ago in Content Marketing / DAM/Library 0 Investigating

Limit the number of workflows/briefs visible to different teams

Currently, every user has access to all active workflows and briefs in Welcome. However, we would like to restrict the visibility of workflows and briefs to specific users or teams. For instance, the content team should only see content-related wo...
over 1 year ago in Content Marketing / Settings + Configuration 0 Future consideration

Support geo-point and geo-search

The Graph should support the geo-point type that consists of coordinates. Then I want to query with this field type with the following new operators only for the geo-point type: distance and boundingBox. I also want to sort the results by distance...
over 2 years ago in Optimizely Graph 0 Planned

When adding multiple audiences to a rule, don't default to matching ANY

When you add multiple audiences to a new rule, the default is to match ANY of the selected audiences. We always want to match ALL of the selected audiences, but our users often forget to change ANY to ALL. They put their experiment live and don't ...
over 2 years ago in Feature Experimentation 0 Future consideration

Add support for restriction groups based on warehouse location

Please add support for restriction groups based on warehouse location. Here is a scenario that was given to support. We have customers who buys from different warehouses. They only have one default warehouse mapping but they could pickup from diff...
9 months ago in Configured Commerce / Catalog & Assets 1 Gathering interest