Hello Tessitura Community,
Has anyone worked with Dynamic Constituencies and/or Attributes?
I'm about to work on cohort analysis and I'd like to automate constituency/attribute updates based on behavioural changes within the cohort itself.
Eg: Cohort 1: New accounts created between dates x and y, that have an interest in contemporary music, who have purchased tickets to 1 unique performance. Constituency = XX1
Should any member of cohort XX1 purchase tickets to another contemporary performance, I'd like the system to recognise this and then apply the constituency XX2 (and close off XX1 with an end date)
If they purchase a ticket to a non-contemporary performance then apply constituency XX3 (and close off XX1 with an end date).
Our cohort/segmentation plan can be complex at times and removing the manual 'Manage Constituency' element would improve both time and efficiency in reporting.
Thanks all! Any ideas considered and if I've missed something or unaware of current functionality please tell me!
Aaron @ Melbourne Recital Centre
Hi Aaron,
We use the local procedure LP_CUSTOMER_RANK to apply and update constituencies and attributes. This runs any time a change is made to a customer record - which of course includes the ticket purchase. Feel free to shoot me an email offline if you're interested in more information.
frannie
Unknown said: Has anyone worked with Dynamic Constituencies and/or Attributes?
We use something I think of as "pseudo constituencies": the Box Office has access to a custom system table, where they add, inactivate and otherwise maintain several three-character codes which are associated with comp tickets sold for a ticketing production. A SQL view meanwhile lists constituents holding these tickets. When our custom constituent header is loaded by a user in one of our Box Office groups, custom header code checks the view, pulls the correct three character pseudo constituencies, if any, makes a comma delimited string of them, appends that to whatever actual Tessitura constituency string the constituent has, and the result is displayed in the header.
Wasn't really very difficult to set up, and the result is working out well all around: the Box Office can maintain these themselves, and our constituency table isn't cluttered with lots of very short-lived constituencies.
Happy to answer more questions, if interested.
Excellent, thanks Chris sounds very interesting indeed. I'm curious to know how you have set up the access to customer system table for Box Office access?
Hi Frances, I tried to contact you at the email on your profile. I wonder if it's still current?
Unknown said: Excellent, thanks Chris sounds very interesting indeed. I'm curious to know how you have set up the access to customer system table for Box Office access?
I've just granted access to the custom System Table in Security as I would for any other, i.e. within Security, navigate from Assign Rights to Groups -> System Tables.