Hi everyone -
Has anyone successfully figured out the setup to use order information for criteria sets? We want to send out another email to patrons with a cancelled concert, ideally suppressing out people who have returned their tickets? Currently, if I just use Ticketing History, that still includes people who initially purchased this concert and then subsequently returned their tickets. Their ticketing history still shows as them having the concert (I'm assuming this is the way it's supposed to work?).
If I can use order information, that might make it easier to identify patrons to suppress (in more or less real time).
Thanks in advance!
Hi everyone! I just wanted to pop in with a few details on the standard behavior of Ticket History for the benefit of anyone in the community with a similar question.
When Ticket History is generated overnight, it selects certain performances, deletes their history, and rebuilds it fresh. In that process, returned tickets are removed. There are a few parameters that can be specified to control which performances are affected; they are described in the documentation for the routine database procedures. The procedure is commonly scheduled to only look at future and recently passed performances, since at a certain point after the event it's unlikely that a performance's data is going to change.
If you are not seeing returned tickets drop from ticket history, it's possible that the procedure is not rebuilding the performance's history because it's too far in the past for the parameters you've chosen, or you might be using a customized procedure.
Thanks!