So I finally got my zip code dashboard built the way I wanted it (took freakin long enough). I added a fun area map to show the actual states where people were coming from. I though having CA when our org is in CT was a little weird, so I did some investigating.
There were 27 tickets sold under the 99999 zip code (which was our workaround in our old system and in v15/v16 for the required complete postal record). I knew those had to be constituent records because my front desk kids would never put that in as a survey question.
Anyway, I was right and that they were attached to constituents. I added the Constituent Display name as a row to find which exact ones. However, this is where it gets weird; in the Total Ticket Count Column, there are now entire rows with 0 in that column. My dashboard is set up so that if it is 0, it should not show up at all.
I also checked the Mode of Sale and all of these were done as Walk-Up Sales, meaning one of my front desk associates had to type each name into Constituent Search in QuickSale to process it. And if its GA, our GA performances are set to auto-attend. And I went back and looked at all of these records and their Order history. All the 0 tickets are from the same event, but all of them got marked as Attended. So those 0 rows should have a real number in them and they don't.
Can someone explain what could have happened before I open a support ticket?
Hi Chelsea,
Could those sales be made up of price layers of which none is a "Ticket Price" layer?
Only price layers in the Ticket Price price category are counted for this field. If multiple Ticket Price price layers exist for a performance, the Ticket Price price layer with the min start date and min price layer type rank is counted. If you break out counts by price layer, layers in all other categories will have a count of 0.
That note comes from the Ticket Count and Seat Count values, but isn't mentioned against the Attended Count value. It should be stated for SLIs (not membership scans) and I'll get a documentation update submitted.
And that's exactly what happened! We have a "Head Count" price layer, and my dashboard pulls our Ticket Price pricing layer. Thankfully it was a super small number (5 patrons total) so I'm not too concerned about fixing it. I'm just glad I know where the issue came from.