Hi Gregoire,
I've recently run into many issues with A/B Testing:
A. I set up an A/B test program but once you've approved the program, you need to change the name of the email if it's referenced anywhere else before the test occurs.
B. Once you approve the A/B test you can't make any changes, and you can't delete the program either. The only way to STOP an A/B test is to contact Marketo support or hope that deleting the Smart list after it's approved will stop it from sending.
C. I sent a test version of the email to my marketing department and it now shows their results as the Test results even though they weren't part of the original smart list...
D. If you sent an A/B test and then declare a winner to be sent to the rest of a list, it won't recognize a duplicate email from the test and if there is a duplicate, they will receive the winner.
Hi Amanda,
Enter the A, C and D as ideas, so that I can reference them
-Greg
Greg, thank you for putting this list together. It's incredible.
I've recently run into issues with improper field management that is both an error-driver and time-waster. Obviously, the best practice is to limit permissions but would love to be able to audit and find the culprits for creating unneeded fields.
HI Nick,
As you found out, limiting the right to create fields in Marketo is not an option. I like your idea and voted for it, but it's a bit like closing the barn door after the horse has left... I see too many instances in which many people have been given the admin rights, by lack of knowledge on how to properly configure the rights. Hint on this : do not use Marketo std roles, create your own, and progressively open the rights are needed.
-Greg
I added it to the list, together with a few others, in item 5-7.
-Greg