Since we're not living and working in a perfect world, I think that having the flexibility to override the css selector that Target uses when we choose "Clicked an element" in the "Goal and Settings" step would be so welcomed by a lot of us.
Not all websites have a perfectly safe and sound DOM. Since Target decides by itself which css element selector string it uses, it is not always the best approach because it could result in having a lot of the html structure to never be changed... but that ain't always possible in real life. Having a "CSS Element Selector" field like the one in the A/B workflow, in the "Experiences" step would be perfect.
Of course you would need to add validations and alerts...
Is there anybody that see a benefit for this kind of feature?
