Identifying $ Ticket buyers within a date range

Using List Manager I'm trying to identify (for example): People who bought tickets totaling between $1500 and $2000 in 2009.

I can't seem to figure out how to qualify the total ticket $ amount within a certain date range. It's giving me people who have ticket histories of that amount regardless of the date range.

I've tried: Ticket Total Amount along with a Ticket Performace Date range, Ticket Order Date Range etc. No luck.

Any ideas?

-Adam, Brooklyn Academy of Music 

Parents
  • Hi Adam,

     

    This is a little tricky because the ticketing criteria work based on the ticket history, which everyone customizes at least a little bit.  In general, I can say that the key to this type of list is using IN for your operator for both criteria.  Using IN assures that the amounts you are looking at come from the year you are entering.  If you are using HAS for either of the criteria then you are getting constituents who has spent between $1500 and $2000 in any season and spent any amount in the 2009.  So the first thing to check is the operators you are using.  If you are using IN for both criteria and you are still not getting the desired result, chances are one of your criteria is not set up correctly on the back end.  All the criteria you are using have be looking at the same table (or view) for IN to work.  It’s also possible that Ticket – Total Amount is not summing the amounts the way you want.  Out of the box it multiplies the number of tickets by the ticket amount and then sums that value for each row it counts (which when you use IN should only be the ones for 2009).  That only works though if you are storing a per seat amount in your ticket history.  If you are storing something like order total you are going to need to change the sum function so that it replaces that multiplication with just the order total.

     

    You might want to check out the Criteria Sets document for a more thorough explanation of the concepts behind IN and HAS.

     

    Kevin Sheehan

    Documentation & Learning Resources Specialist

    Tessitura Network

    1 888 643 5778 ext 329 Office

    ksheehan@tessituranetwork.com

     

Reply
  • Hi Adam,

     

    This is a little tricky because the ticketing criteria work based on the ticket history, which everyone customizes at least a little bit.  In general, I can say that the key to this type of list is using IN for your operator for both criteria.  Using IN assures that the amounts you are looking at come from the year you are entering.  If you are using HAS for either of the criteria then you are getting constituents who has spent between $1500 and $2000 in any season and spent any amount in the 2009.  So the first thing to check is the operators you are using.  If you are using IN for both criteria and you are still not getting the desired result, chances are one of your criteria is not set up correctly on the back end.  All the criteria you are using have be looking at the same table (or view) for IN to work.  It’s also possible that Ticket – Total Amount is not summing the amounts the way you want.  Out of the box it multiplies the number of tickets by the ticket amount and then sums that value for each row it counts (which when you use IN should only be the ones for 2009).  That only works though if you are storing a per seat amount in your ticket history.  If you are storing something like order total you are going to need to change the sum function so that it replaces that multiplication with just the order total.

     

    You might want to check out the Criteria Sets document for a more thorough explanation of the concepts behind IN and HAS.

     

    Kevin Sheehan

    Documentation & Learning Resources Specialist

    Tessitura Network

    1 888 643 5778 ext 329 Office

    ksheehan@tessituranetwork.com

     

Children
  • Thank you for the quick feedback.

    Ok. I think I follow. I did try using IN when selecting a years worth of Seasons or I tried Performance Date (or Order Date) between 1/1/09 and 12/31/09. Both seems to give me a lot of reults that don't have $1500 or more within 2009.

    Our Ticket History tab only has Amount though, not Per Seat Amount. If I follow, THAT may be the problem? I'm not sure how to change the sum function though. I guess what you're saying is I may need to discuss with our IT team?

     

     



    [edited by: Adam Sachs at 2:23 PM (GMT -6) on 6 Apr 2010]