I guess, that’s not possible with a single test, right?
Correct. Views and conversions are aggregated across the entire scope of the test. At this time, it’s not possible to filter or break down the results by individual pages included in the test. The data reflects the overall performance of each variant within the full scope you defined.
What would be the best approach? Should I simply duplicate the test and modify the test scope?
Yes, that sounds like the best approach: duplicate your existing CSS test and configure it to target only the specific pages you’re interested in. This way, you’ll effectively get a breakdown of results by comparing each test separately.
That said, I should point out that running multiple tests on the same pages is generally discouraged, as different tests can potentially interfere with one another. However, in this scenario, it’s acceptable, because we’re dealing with simple CSS tests whose variant Bs serve the same purpose (i.e. hiding a badge).
Thanks, David. Will try the additional test and keep you posted if anything strange happens. 🙂
-
This reply was modified 4 months, 3 weeks ago by
cutu234.
I get a warning message. Should I ignore it?
Test “Siegel von vergleich.org (nur Produktseite)” (663339) can’t be started because there’s another running test that may be testing the same element(s): “Siegel von vergleich.org” (663039).
We’re talking about CSS tests, right? Yes, you should ignore it and start the test anyway. As I said, running multiple tests on the same page at the same time it’s usually discouraged, but I think it’ll be okay in this particular instance.
Yes, it’s a super simple CSS test. I’ve just started the test and will keep you updated.
