Add querystring parameter targeting at the url level for multi-page tests. Other stuff would be cool as well (like checking js variable value), but querystring is what's causing us pain right now, so I won't be too greedy ;-)
Here's the current scenario:
Since I believe the following are true
- targeting conditions other than the url don't apply when the test code is actually run after the user has already been slotted into a test
The following is not possible in a single multipage test:
- targeting changes to a dynamic page where the only difference in the url are querystring parameters and values. In other words, where what loads on the page is determined by what's in the query string, not the base url.
I just had to create a test that was essentially 4 optimizely tests, that could have been a single multipage test if the url parameters were available in the url targeting.