Patron activity report

Hello!  I hope someone can help point me in the right direction.  I've been asked to provide some historical stats about our patrons.  It seems I should be able to accomplish this with a dashboard- but I'm honestly not sure where to start with each widget.  

1 - How many single ticket buyers (not subscribers) saw more than 1 production last year?  In 2018/19?

2- How many single ticket buyers (not subscribers) saw more than 1 repertory production in the same week last year? In 2018/19?

3 - Many of our patrons live here seasonally.  How many of our patrons are here (or have an active address) in June?  July? August? September?  Also, these numbers should be broken down by subscribers vs single ticket buyers. 

Parents
  • Hi Mark,

    For that count who saw more than one in the same week... do you mean more than one distinct production, or does coming to the same production twice in one week count? 

    SUM ( [Constituent ID] ,
      MAX ( [Weeks in Performance Date] ,
          IF ( [# unique Production Season ID] > 1 , 1 , 0 ) ) )

    For each constituent, look at each week in which they held tickets, and if they had more than one unique production in any given week, return a count of 1 to the overall sum.

    For the last item, I'd set up a Custom Category constituent element the looked at the address and logged their address months as a comma string of month numbers... e.g. ",6,7,8,9," or ",4,5,6,9, or ",8,9,10," for the months they're in town. Then as with Lists filtering, you can filter on those with [Custom Category 01] Contains ,6, for those who are in town in June.

    That said, some of this certainly easier in Lists and Extractions for a one-off assessment, but for ongoing use it might be better to invest in the dashboard design.

Reply
  • Hi Mark,

    For that count who saw more than one in the same week... do you mean more than one distinct production, or does coming to the same production twice in one week count? 

    SUM ( [Constituent ID] ,
      MAX ( [Weeks in Performance Date] ,
          IF ( [# unique Production Season ID] > 1 , 1 , 0 ) ) )

    For each constituent, look at each week in which they held tickets, and if they had more than one unique production in any given week, return a count of 1 to the overall sum.

    For the last item, I'd set up a Custom Category constituent element the looked at the address and logged their address months as a comma string of month numbers... e.g. ",6,7,8,9," or ",4,5,6,9, or ",8,9,10," for the months they're in town. Then as with Lists filtering, you can filter on those with [Custom Category 01] Contains ,6, for those who are in town in June.

    That said, some of this certainly easier in Lists and Extractions for a one-off assessment, but for ongoing use it might be better to invest in the dashboard design.

Children
No Data