The tour variant is resolved in the FTL thus caching doesn't have a clue about it.
We should either have all variants as different components in JCR or disable caching for whole page.

To reproduce:

1. On EE (with advanced cache for personalisation installed)
2. Visit the home page on public instance as first visitor, choose tour type.
3. Clear your cookies or use another browser to mimic another visitor.
4. Choose the other type of the tour type.
5. You get the tour type of the first visitor (cached home page created by the first visitor).