AS
an experiment builder in web

I WANT TO
be able to make changes to pages associated with the experiment and not have the visitor activate the experiment when those pages load

SO THAT
I can keep changes related to an experiment together while limiting activation of the experiment to a specific page or action

USE CASE
I have a change for a specific product display page that I want to evaluate. There are associated changes that I will need to make to the cart and every checkout page. In order to make changes to those pages to support this, I will either need to add code to project.js or add pages to the experiment and define changes there.

If I add code to project.js, it adds complexity to project.js. It makes it less clear what code and which pages are part of the experiment and adds unecessary processing for all pages.

If I add the pages to the experiment, I can keep all the code related to the experiment in one place but then I have activation points on all those pages which is not ideal.

POSSIBLE SOLUTION
Define pages as part of the experiment but do not have this definition list trigger activation. Have a completely separate activation mechanism that allows me to add pages and define specific conditions for activation. This would allow me to keep all the code related to the experiment in one place and limit activation to specific pages or actions.