I once created a similar problem. I built a tracking and split testing system designed around a list of features activated during a page load. So a single page load might be described like:
root,signin,bluebutton
Where bluebutton was a design we were testing for our signin page. Of course once bluebutton worked and had run for a while everyone was afraid to change it in case there was a dependency of some kind. So the Facebook login that replaced the old signin would look like:
root,signin,bluebutton,fbookredirect
Even though no sign in page was shown let alone a bluebutton.
root,signin,bluebutton
Where bluebutton was a design we were testing for our signin page. Of course once bluebutton worked and had run for a while everyone was afraid to change it in case there was a dependency of some kind. So the Facebook login that replaced the old signin would look like:
root,signin,bluebutton,fbookredirect
Even though no sign in page was shown let alone a bluebutton.