Product ideas | Community
Skip to main content

10000 Ideas

Selliers
SelliersNew Participant

Administration and maintenance of TagsApproved

We are experience that maintenance of Tags is hard do to access rights, especially deleting Tags. It must be easier to change the name and/or to delete a Tag that is not wanted or not just any more. It the Tag feature shall work and be trusted by the users the Tag must be spelled right be generic and have some sort of structure. This is work that is always going on - and the need of change and maintenance will always be there. We see misspelled words, not generic enough  and the list includes many tests. This is hard to change and make the tool full of "bad data" - and the user experience will drop over time.  During the development of AJO there has come better features regarding deleting audiences. When deleting a audience it will be checked it this audience is connected to another audience and/or a journey. If so you get a error message and info about that connections there is regarding the audience you want to delete. We see the need of the same mindset here regarding Tags. All user should be able to change or delete a Tag, but when deleting there should be a check if the Tags is been used somewhere before it is deleted. Changing name should be able as is since this is dynamic data. Is should be able to delete Tags without disable the Tag first. Use of Tags and the need of using Tags is growing along with the extend use of AJO. And if Tags should be used Tags must also be able to be maintained fast and easy, like other features in the tool. With the possibility to also have a folder stricture it would even be more easy and more relevant to use.  Today we can create but in a real working environment we cant change and maintain the Tags easy - and will therefor not been used. I see that a good Tag strategy can help us working better with audiences etc where the Tags is part of how we find and target customer. 

Michael_Langell
Michael_LangellNew Participant

The Email Performance Report IS INACCURATENew

I discovered an interesting issue with the Email Performance Report that I will assume less than 10% of Marketo users are aware of.   This issue is detailed below in a note at the bottom of this help doc:  "Multiple sends from the same campaign to the same person are counted only once." Email Performance Report Help Doc   So does that issue mean?  For those of us who use tokens all across our Marketo instances and use them particularly to swap in/out content via those tokens for scalability and efficiency, (maybe in an automated nurture) this is a BIG problem.    When a person is sent an email from the same campaign multiple times over any timeframe, the Email Performance Report only records a single email send    Example Notice the three email sends below.  Two of the sends are via the same campaigns.     The below report only displays 2 emails were sent - and this is our issue   Solution To me, every email send in the activity log should appear on this report.  I am unsure what the use case is for the current methodology, where email sends from the same campaign to the same person are grouped together.  I would think most customers would just want to report on all email sends and what the outcome of those sends were (bounce,open,click) over the course of time.  Two versions of the Email Performance Report would also suffice.    For now - it looks like the only solution to this is via API exports of your email activity.      For fun, feel free to include in your comments if you were aware of this!   Best, Mike      

Dawid_LamparskiNew Participant

Automated Backup and/or Restore option for Decisions/Offers/Journeys etc.Delivered

Description - We'd highly appreciate an option to restore key objects in the product. At the moment majority of users would like to have ability to modify objects like Decisions/Offers/Journeys etc., however there's no way to restore changes applied to them or even to lookup previous version/status of those objects.   Why is this feature important to you - since high volume of users has ability to modify all others objects (mentioned above), and there's no ownership of those objects it's very easy for someone to break others objects, either by accident or because of similarities in naming convention. We need to have this ability to restore to previous version, ability to protect them from others (sharing options) would also be useful.      How would you like the feature to work - many options:  1. simple     - API endpoint with lookup to previous versions of the object, and ability to append JSON response into another call to update that object to previous  version  2. complex    - restore button in UI (with a separate permission for Product profile or Role)    3. Optional remedy:    - ownership of the object, only creator can modify unless shared with other's (individuals or user groups)    - email to object owner (if feature available) about changes to that object in the Production sandbox, with option to subscribe and unsubscribe from Alert/notification   Current Behaviour - you can only see current status of above objects even when using API, there's no way to lookup previous versions of the object. Objects are owned by everyone there's no sharing  option so easy to break someone else's offers, decisions, journeys etc. There's currently only change log available, which is not very helpful other than finding a person to blame