We had the same situation, and it makes a difference in visitation mapping to take into account the number of guests in a sales transaction. We use the SEATS cube in T-Stats to get the kind of report you describe. Hope this helps! Sue
From: Tessitura Ticketing Forum [mailto:forums-ticketing@tessituranetwork.com] On Behalf Of Curtis Bellfy Sent: Friday, August 18, 2017 12:58 PM To: Susan Carey Subject: [Tessitura Ticketing Forum] Survey Question, Question...
our Survey Question pop-up comes up and asks for the zip code...when we do the Survey Question Report we noticed its only counting each zip code as ONE even if there is a family of 6 checking in...I added a "count" as a second question but when we print the same report again the zip codes come up ONE per zip and a second line pops up with a total count...its not splitting it up by zip code. anyone have a work around that can provide number of people from each zip code? our marketing department loves the report showing all the zip codes...but asked, "well how many people from each came in?"
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Ticketing Forum. You may reply to this message to post to the Ticketing forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
Curtis, I believe the standard Survey Statistics Report is showing a count of orders per answer, not tickets (or scans) from those orders. That would explain why you see one rather than six even if six people may have entered.
If you are on Tessitura v12.5.1 and T-Stats v4.5, you could create a report in the Tickets cube to look at the people from each zip code, rather than just the number of orders. A handy thing about doing this in T-Stats v4.5 is if you have some orders under the General Public account using the survey functionality to capture zips, but also have some real constituents with their own account (and actual addresses), you can look at both at once in the Tickets cube, using the standard Postal Code attribute. This assumes you've configured T-Stats to tell it which question is the zip question (done in the load jobs). You can also determine "people" in the Tickets cube. If you're looking for tickets sold, use the Num Tickets measure. Or if you're using Membership scans too and only want people who actually entered not just purchased, you can use Num Attended in the Tickets cube and see how many entered which includes both scanned tickets and membership scans combined. Hope that helps.