Schedule an update to an existing live Adobe Target A/B test

[#1]

Description -

Why is this feature important to you - Because occasionally we want to publish promotional (or other content) updates that are unrelated to an experiment but need to be published at a future time in a live experiment.

How would you like the feature to work - Same as regular scheduling except allowing for the current Activity to be live 

Current Behaviour - Presently if you schedule an update to a Live experiment it gets deactivated. This feature would allow for that to not happen.

[#2]

Thank you for sharing idea! I would love to understand your idea better, so I have a few questions.

• What part of the live activity are you wanting to edit?
  • Do you want to change the content? 
  • Are you wanting to scale the winner of the experiment to the whole audience?
  • Something else?
• Why do you want to update a live activity instead of creating a new activity?

I look forward to hearing from you!

[#3]

• What part of the live activity are you wanting to edit?
  • Do you want to change the content?  Yes
  • Are you wanting to scale the winner of the experiment to the whole audience? No
  • Something else?
• Why do you want to update a live activity instead of creating a new activity? Because if I have a change that goes out at 2am (say a promotion that gets updated) I don't want to be awake until then to deploy the change. And the scenario is that I still want to the existing Activity to stay active and collect data pre/post that 2am content push. So creating a new Activity wouldn't achieve that.

[#4]

Thank you for that clarity! One last question, what type of activities are you wanting to edit? 

[#5]

Ideally any type but at the very least a basic A/B test.

[#6]

Changing the content of an experiment mid experiment can skew the experiment results, is that a concern? Do you have a specific example of why would edit an experiment part way through?

Thank you for continuing to give us more understanding. Helps us decide how certain functionality should work. 

[#7]

I think I addressed it above. If it's content that is changing on the site anyway (not content you are specifically testing) then it's fine. External to the hypothesis and test in question. See my example of promotions above. The larger point is to be able to make updates by programming them to go live - why can't we do that to an existing Live experiment? Other use cases are bug fixes or other reasons where a change needs to be timed without turning off the current experience. This is functionality in other experimentation tools already.