Another new-to-file/new buyer question in the seats & tickets cube

Hi all, 

I've been using the formula from Chris W. in the thread below to find percentages of new buyers to performances.

 https://community.tessituranetwork.com/tessitura_software_forums/f/tessitura_shared_reports-9/29202/first-time-buyers-in-analytics/78313?_ga=2.82097430.1692326623.1659480726-589410106.1655677821

I usually do additional filtering to see what types of performances or venues are driving the most new buyers, etc.

One question that comes up is the interpretation of a new buyer or new-to-file or new-record buyers.

I usually get asked:

Are they completely new-to-file as in a brand new constituent account created at time of order...Or, are they new in the sense that it's their first time purchasing a ticket, but their record already existed in Tessitura(perhaps they donated for a number of years and just purchased their first ticket).

I believe the formula in the above thread answers the latter, but I'm not quite sure, at least in Analytics, how to tackle the former.

Ideally I'd like to have a pivot table that can show a performance with these 3 values:

  1. all buyers
  2. new buyers
  3. completely new constituentrecord buyers

If anyone has a custom formula for the third option I'd be most appreciative.

I'm also curious, if others get asked the same thing about new buyers vs newly created constituent record buyers?

Thanks!

  • Hi Michael,

    For the cases where the new buyer is also a completely new constituent record, an approach may be to compare the create date of the constituent to their first order date, such that...

    IF ( MIN ( DDIFF ( [Days in Order Date] , [Days in Constituent Create Date] ) ) = 0
       AND MIN( DDIFF ( [Days in Performance Date] , [Days in First Performance Date] ) ) = 0

    And for new buyers who are not new to file...

    IF ( MIN ( DDIFF ( [Days in Order Date] , [Days in Constituent Create Date]  ) ) > 0
       AND MIN( DDIFF ( [Days in Performance Date] , [Days in First Performance Date] ) ) = 0

    This requires configuring a TX_ANALYTICS_DIVISION_ELEMENT Custom Date ## to allow reporting on the constituent create date in Analytics.

  • Updated comment above to recommend comparing order dates to create date.