Skip to Main Content
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 554

Edit the Requester

Users with Admin level permission should be able to edit the requester, in the use case that someone leaves the company or we want to make a request on behalf of someone.
about 2 years ago in Content Marketing / Requests 0 Future consideration

Add Event Status

We would also like to see event status capability, much like task status. This might be: In preparation / In progress / Completed. This again will enable us to see at a glance how preparation for events are coming on. We would not like to use task...
about 2 years ago in Content Marketing / Tasks, Campaigns, and Events 0 Future consideration

Auto-populate Name of Work Request with its Title

In work request templates, sometimes the title field isn’t necessary, as it just duplicates the name of the work request. E.g. we have a work request template specifically for users to come and request access to the platform. The work request itse...
about 2 years ago in Content Marketing / Tasks, Campaigns, and Events 0 Future consideration

Owner field for templates/multiple user fields

There should be a user field option that is able to populate based on CMP users and can designate as 1 user, team, or multiple. For example, we have a campaign owner field and instead of having an open text field, and we'd like to set that as one ...
about 2 years ago in Content Marketing 0 Future consideration

Automation wait node: support waiting for a recipient-specific date with executing next step in automation

The Marketing Automation has the possibility to wait a certain time with executing the next step. Currently it allows waiting X hours up to X months at a specific timestamp. The value for the customer would increase if the date and time the automa...
over 2 years ago in Campaign 0 Future consideration

Add calendar widget to the start page dashboard

As a User I would like to see my scheduled and recent campaigns in a monthly calender widget with some basic data shown at a glance.
over 2 years ago in Campaign 0 Future consideration

Flag When Updating a Step/Task Due Date to a Weekend

We need to up with some sort of flag/messaging that tells users to only select weekdays instead of weekends, or a message that warns them that selecting a weekend as a step due date may also cause other step due dates to fall on weekends.
over 2 years ago in Content Marketing / Tasks, Campaigns, and Events 0 Future consideration

"If Answered" Logic

It would be great if logic routing options could have a logic option for "if answered" ie if this question is answered, skip to question or section x or show these values in question Y. This would allow us to incorporate open text field questions ...
over 2 years ago in Content Marketing / Settings + Configuration 0 Future consideration

Private/Gated Collections

We would love to retain the flexibility of collections (one asset in multiple collections, cover photos, etc.), but with the option to add privacy to the link in order to share directly with smaller groups of people.
over 2 years ago in Content Marketing / DAM/Library 0 Future consideration

Handle the error the occurs when copying rules from another environment

When one environment already has an experiment in it, and you try to add a new rule by copying over the rules from another environment, the UI throws a confusing error that says "Updating production ruleset for flag <flagKey> failed. {"Inval...
over 2 years ago in Feature Experimentation / Feature Flagging Workflows 1 Future consideration