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 32

Be able to use preset values for flag variables

As experimentation program owners, we'd like our fellow developers and experimenters to input "safe" values when filling out flag variables. For example colors and font sizes that match our design system. A preset list of values (created by an adm...
9 months ago in Feature Experimentation / Experiment Authoring 1 Planned

Exclude expired assets from our searches

Due to the lack of a Library Archive, we have decided to "expire" assets no longer relevant to our organization. However, in the Library, there is no way to exclude expired assets from a search. The only capability we see is to show expired assets...
over 1 year ago in Content Marketing / DAM/Library 2 Planned

Significance notifications

Customer wanted notifications when a test hit significance instead of having to check all the time
over 2 years ago in Experiment Collaboration and Management / Notifications 0 Planned

mparticle integtration

Sync Mparticle audiences to ODP for use with real time segmentation, web & feature experimentation as well as CMS visitor groups.
almost 2 years ago in Integrations 0 Planned

ODP <> Dot Digital Integration

Ability to send ODP Segments and customer data to dot digital Ability to send dot digital campaign event data back to odp
about 2 years ago in Integrations 0 Planned

Templated Metrics - No more manually adding same metrics each test

We use the same metrics in every test. (with a handful of unique ones) It takes my team 10 min every test creation to search through the 75+ metrics/events/pages to select the 10 we always use. It would be nice to select the default option and hav...
about 2 years ago in Experimentation Analytics / Other 2 Planned

Confirmation When Archiving Flag

Is it possible to have a confirmation box, or at least the option of enforcing one, when archiving/deleting a flag? I noticed that flags can easily be archived by mistake, and can be a breaking experience on the website.
about 1 year ago in Feature Experimentation / Feature Flagging Workflows 0 Planned

View Field Usage

Sometimes, when I make edits to fields or want to remove them, I would need to adjust logic on templates, routing rules, etc. It would be great if we could have a column in the fields area that would note where the field is in use across templates...
over 2 years ago in Content Marketing / Settings + Configuration 0 Planned

Ability to remove/delete the standard "Overall Revenue" Metric, and replace it with another metric.

Customer (Vistaprint): In our case, it (Overall Revenue) is certainly incorrect. We send multiple events for the same conversions with revenue so that we can target revenue for specific product categories as a metric. Overall Revenue will sum thos...
over 2 years ago in Experimentation Analytics / Metrics Setup 0 Planned

Mark Fields Mandatory at Field Settings (instead of on templates, workflows)

Some of our fields are designed to capture business-critical data and must be completed every time they are used. Setting the mandatory fields up at the template and/or workflow level is cumbersome. We'd like to be able to set a field as mandatory...
over 1 year ago in Content Marketing / Settings + Configuration 0 Planned