• Replies 17 replies
  • Subscribers 966 subscribers
  • Views 1345 views
  • Users 0 members are here
Related

Booking churn Subscribers in Analytics?

Josefin Johansson
$organization

Hi, 

We are looking into the booking churn for our subscribers at Malmo Opera.

Parameters we want to look into on a seasonal level:

  • How many are returning subscribers season after season?

             In what packages? Other patterns?

  • How many are new subsribers per season?

             In what packages? Other patterns?

  • How many drop offs per season?

             In what packages? Other patterns for drop offs?

Anyone got any tips and tricks on how get started with this in Analytics, reports or in List Manager/ Extraction Manager?

We dont know if Analytics is the right place for this since there is no Data set for Subscribers?

 

Thanks a lot for your help!

Josefin

Parents
  • $organization

    Hi folks, 

    Thank you all for this detailed explanation -- it has been very helpful over at Lyric in Chicago.

    We're currently configuring this setup to count the number of packages, per the previous reply's instructions. 

    However, over here we define lapsed as...

    year 1 = had a package 

    year 2 = did not have a package 

    year 3 = had a package 

    This is the formula I've adjusted based on the above

    SUM ( [Constituent ID] ,
      IF ( ISNULL ( ( [Total Ticket Count] , [Package ID] , [Season Fiscal Current Year Offset = -1 (2023)] ) )
         and ( [Total Ticket Count] , [Package ID] , [Season Fiscal Current Year Offset = -2 (2022)] ) > 0
         AND ( [Total Ticket Count] , [Package ID] , [Season Fiscal Current Year Offset = 0 (2024)]  ) > 0
         , ( [# of unique Package Seat Key] , [Package ID] , [Season Fiscal Current Year Offset1 = 0 (2024)]   )
		, NULL )
      )

    It seems to be working on our end, though we're having a hard time getting it to match with a subscription summary report (on the Impressario DB side) . 

    Main Q: does this look like the correct adjustment to the previous formulas to capture "lapsed" based on Lyric's specific business definition? 

  • $organization in reply to Erik Dohner

    Hi Erik,

    Looks good. On option to simplify if you like is to consolidate the 2022 and 2024 statements into one

    AND ( [# of unique Season Fiscal Year] , [Package ID > 0] , [Season Fiscal Current Year Offset in -2,0] ) = 2

    meaning they have packages in both years.

    Are you using this with Season Fiscal Year on Categories? If so, each of these statements will be evaluated within the FY of the row... meaning each value in the formula may need an ALL ( [Season Fiscal Year] ) appended to it.

    What report are you matching? If it's based on the Subscription Summary Status/Type in Tessitura, have you tried matching bits of it in Analytics with the Package Subscription Status and Package Subscription Type fields?

Reply
  • $organization in reply to Erik Dohner

    Hi Erik,

    Looks good. On option to simplify if you like is to consolidate the 2022 and 2024 statements into one

    AND ( [# of unique Season Fiscal Year] , [Package ID > 0] , [Season Fiscal Current Year Offset in -2,0] ) = 2

    meaning they have packages in both years.

    Are you using this with Season Fiscal Year on Categories? If so, each of these statements will be evaluated within the FY of the row... meaning each value in the formula may need an ALL ( [Season Fiscal Year] ) appended to it.

    What report are you matching? If it's based on the Subscription Summary Status/Type in Tessitura, have you tried matching bits of it in Analytics with the Package Subscription Status and Package Subscription Type fields?

Children
No Data