Description -In template rules for page delivery, add a note to the UI when multiple values can be accepted on different lines. In other Adobe products (e.g. Analytics processing rules), this is made clear in the UI. It is also made clear in the audience creation dropdowns. This makes it seem as though you can't do this in page delivery, otherwise you'd think the same message of 'Enter each value in new line' would be applied to the empty fieldWhy is this feature important to you -In Target, it looks like you can only have a series of AND rules or OR rules. By allowing multiple values in an AND rule, you're effectively adding in the option to use AND and OR. Currently, as it isn't common knowledge that you can add multiple values we have situations where we're deploying identical tests for slight variations in things like query parameter value and URL.How would you like the feature to work -Literally, just a note in the UI when you select an option from a dropdown to let you know if multiple values can be added as separate line items and it will function like an OR ruleCurrent Behaviour -No information provided in the UI so end-users unaware of flexibility leading to multiple tests being deployed doing the same thing
A little formatting could go a long way to help me read the operator list. It's hard to pick out the individual operators due to each true operator having an opposite false operator.It's a quality of life change that will save me a few seconds in segment builder, and make me feel fuzzy inside.Couple of ideas:List the trues first and then the falses (I don't really like this as it might move a popular false operator lower down the listFormat the false operators differently so that they contrast to the true operators. That way I can more easily scan the list to find the type I'm after, then pick the true/false.
Would be nice to be able to add another team member's calendar onto our own calendar view. Just like you would share your calendar in Outlook.
Hello,I searched the forum for similar topics but only found threads which were from at least 4 years ago and also without solution. As I have to export reports on regular basis, it would be more than helpful if the reports could be exported in xlsx-format. I think that many users would appreciate this feature, as Excel is still a standard tool.Kind regards,Patrick
It would be nice if when submitting a request through any request queue, a user could select a "copy request from" option and then find an old issue or project, then this information would feed into the new form (as long as the fields were the same). This would at least give a head start on some of the huge forms our requestors have to fill out. OR, if they could go to an old issue/project and there was an option there to "Submit request from" then they could select the appropriate queue (that way the routing would work as designed). If the fields would just go blank if they do not exist anymore, that would prevent issues with custom form changes. I know this is probably a long shot, but I get requests for it frequently.
Hello all, We would love the ability to attach documents when creating an expense. This would allow for us to attach expense pdfs and other items to the expense object Thanks, Al
Description - Currently there isn't an ability to configure CORS for tracking servers. Especially in the case of setting up first-party tracking, it would be great if more restrictive origin traffic could be specified.Why is this feature important to you - It could cut down bot/undesired tracking and it would flag fewer exceptions when probing a site for CORS compliance.How would you like the feature to work - During the process of engaging in discussions of first-party tracking and using first-party cookies, it would be ideal to provide both the necessary CNAMEs to reference the tracking servers as well as any additional configuration changes that would be needed on the client side. Ideally, we could limit origin to the specific site we expect to send data from, and maybe a less restrictive, non-public endpoint that can be used for any server-side API data insertions.Current Behaviour - Right now the following header is allowed "Origin: null". Every endpoint, including those that that are specifically set up for first-party tracking can recieve requests from any origin.
Currentyl the notification formattting of emails from Updates gets lost in the clutter of other emails, as well as the WF notificatins which themseslves we find useless (given they're a tiny number in the top right with no context of importance).An example of the issue is our team regularly send out important "Alert Updates" for critical info and milestones to several tagged teams of key stakeholders.The email notification just shows this as a "Comment" on <WF PROJECT JOB NAME>, which in their current formatting just becomes noise.We tend to put some bolded key words in the body of the update, such as *** ALERT.....blah blah blah *** to indicate the importance of the particular message that others need to pay attention to, but there's no chance for this to be seen in the email notification subject line (only visible once they open the email), which is the critical part of the message, with the Project name being secondary.What feels like might be an improvement, is if Updates had the ability to have a 'Subject" line, (much like emails do) which would become the title of the notification email, appended with the Project name for additional context. I expect this issue likely reaches beyond just Updates too...?!
When using color coded comments in the proof, make the comment color more obvious. Color code the initial circles with the assigned color.
With the new editor, the preheader has been completely redesigned. It's now editable as part of the email properties. The drawback is that there is no way to make it dynamic. This is an issue, especially of one wants to use the dynamic content to manage multiple languages.So, please Marketo, please make the preheader able to support segmentation based dynamic content in the pre-header.-GregP.S: the workaround is to set the preheader as an editable section in the email, and not use, but in the case, the user may make an error and enter in 2 places. See
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.