Analytics Dashboard

Which you use is mostly based on what you're trying to accomplish.  If you want to see aggregate data, say "How many customers did X, and what was their average order total?" Then you would tend towards Analytics.  If you want to know "Which customers did X" then you probably want a List. Analytics and Lists can also be used together.  You can save returned sets of customers in Analytics to Lists, and you can flag Lists for use in Analytics as a way to filter results.  In the latter case, since Analytics only updates nightly (in most cases) you'll want to create your lists knowing you'll have to wait until at least the next day to use them as a filter.

The second bit of advice is that when you are using "Set" type questions, often the best way to set that up is to at least start with Lists.  Create a list of the first part of the question (e.g. "single ticket buyers for a season", then a list for the second part (perhaps here the easiest things would be "everyone who bought a ticket to show X).  Now, in a third List you say HAS (using HAS versus IN is important, for difficult to explain reasons) List 1 and HAS List 2 and that will give you ticket buyers for the season who have also purchased show X.

You can technically probably condense that into two lists, but while getting used to it this might be more clear.

For the second you would have List 1 be everyone who purchased a 22/23 sub, and List 2 be everyone who purchased a 23/24 sub.  Then your third list would be HAS List 1 and DOES NOT HAVE List 2.

Which you use is mostly based on what you're trying to accomplish.  If you want to see aggregate data, say "How many customers did X, and what was their average order total?" Then you would tend towards Analytics.  If you want to know "Which customers did X" then you probably want a List. Analytics and Lists can also be used together.  You can save returned sets of customers in Analytics to Lists, and you can flag Lists for use in Analytics as a way to filter results.  In the latter case, since Analytics only updates nightly (in most cases) you'll want to create your lists knowing you'll have to wait until at least the next day to use them as a filter.

The second bit of advice is that when you are using "Set" type questions, often the best way to set that up is to at least start with Lists.  Create a list of the first part of the question (e.g. "single ticket buyers for a season", then a list for the second part (perhaps here the easiest things would be "everyone who bought a ticket to show X).  Now, in a third List you say HAS (using HAS versus IN is important, for difficult to explain reasons) List 1 and HAS List 2 and that will give you ticket buyers for the season who have also purchased show X.

You can technically probably condense that into two lists, but while getting used to it this might be more clear.

For the second you would have List 1 be everyone who purchased a 22/23 sub, and List 2 be everyone who purchased a 23/24 sub.  Then your third list would be HAS List 1 and DOES NOT HAVE List 2.

This was SUPER helpful, thank you, Gawin!

Glad to hear it, and good luck with your analytics adventures!