Product ideas | Community
Skip to main content

Filter by idea status

10000 Ideas

MOPs713New Participant

Email version identification and test increment #s appended to SLs for Sample Test EmailsNew

I've looked throughout the knowledgebase for this but maybe I'm not searching with the right keywords?   Today when we send sample test emails the word "TEST" gets appended to the beginning of the Subject line of that test email.  What would be a great integrated feature to the sample email sends is to automatically increment the test in the SL i.e. "TEST1", "TEST2", "TEST3" each time a new test gets sent out. We have many hands in the cookie jar in our marketing department who have a lot of input on our email communications (nature of the beast I guess) but it means we send many many tests for email review and confirmation. It can get mind-boggling but what would be great is if Marketo incremented the test so I can go back to my stakeholders and say the latest test is "TEST3" or please review "TEST2" for the latest update to x section of the email..    In addition to this, some of our nurture campaigns have multiple versions we are sending depending on the goal of the campaign. And those emails can be so closely similar that it becomes difficult to identify which version you are reviewing.  it would be great for a program that has many email versions to be able to append a version value after the word "TEST" for the sample test email (i.e. Version A, Version B, Version X, etc) but really it should be any value the program creator/manager deems meaningful to the sample email recipient.    Does this feature already exist in Marketo that can be leveraged? Maybe I'm missing it. If not this would be a feature request I have.    I had used an ESP called Emarsys which had this capability built-in but in that prior life it was used for consumer marketing where we always had multiple versions and numerous test emails sent out. I'm now in a B2B (ABM) organization using Marketo but it would be nice to have and add a level of transparency for our stakeholders when we send out test emails for review. 

tony_papousek-e
tony_papousek-eNew Participant

Merge Launch LibrariesNew

Description -  Since Libraries are just collections of changed resources, I want the option of merging two+ libraries together (similar to merging git branches) in dev and/or merge a library from dev into an existing staging library. Why is this feature important to you -  Graduating features from dev to stage while awaiting a production push is a pain.  Combining resource sets from two different dev libraries is a pain.How would you like the feature to work -  In publishing flow:Click the meatballs menu of a librarySelect "Merge in libraries"At this point, the libraries that can cleanly merge would swap out their own meatball menu buttons for checkboxes"Build" would be replaced with "Merge and Build"Check all libraries you want merged inClick "Merge and Build"A confirmation modal/warning dialog pops up, with the option to rename the new library.Click "Confirm"Libraries merge into one, then build.    Similarly, when submitting a dev library for approval: if a library is already in staging, prompt the user to merge dev library with existing staging library.  Production libraries don't need this feature, as they can already merge staging into dev via publishing flow.Current Behaviour -  Staging libraries have to be yoinked back into dev and resources added one-by-one (if they're not all ready).  Dev libraries can't be easily combined, a user has to manually track (using their own notes) which versions of each resource to merge by hand.