• Replies 3 replies
  • Subscribers 961 subscribers
  • Views 99 views
  • Users 0 members are here
Related

Membership Views in the Ticketing & Seats cube

Jo Bramley
$organization

Hi All, 

I wonder if any of you smart people have a suggestion for me! I have a widget displaying what type of membership level accounts for what portion of tickets purchased, presented as a pie chart. This part is fine - where I'm coming unstuck is the type of membership level displayed. 

We have 2 membership orgs - one for marketing which is, for want of a better description, a loyalty type programme & then another for the actual paid memberships. Some of our visitors have both types. 

I would like to be able to display the ticket purchasers for the 2 membership orgs separately. If I filter the widget to 1 membership org, the visitors with both membership types are removed. If I leave the 2 orgs in as they are, then those records with 2 membership orgs can display either membership type......how to I get the widget to display the particular membership type I'm after?

Thanks all!

Jo

Parents
  • $organization

    Hi Jo!

    The Seats and Tickets cube has both the CONSTITUENT SUMMARY elements for Current Membership Level for all constituents in the cube, and then SEATS & TICKETS DETAILS field for Membership Level and Membership Organization, which are only available against Membership Scans in that cube. Which fields are you using?

    It sounds like you're using the CONSTITUENT SUMMARY elements, and if so, those fields hold exactly one distinct value per constituent. In the case of memberships, like Current Membership Level, the default definition arbitrarily picks one membership for constituents who have multiple current memberships. You can impact that configuration in TX_ANALYTICS_DIVISION_ELEMENT by specifying a specific membership organization (e.g. adding "AND memb_org_no=3" to the data_where field). However, that doesn't fully address your issue as you still want to reliably report Current Membership Level on another membership organization. To do so, duplicate the configuration of Current Membership Level in one of the Custom Category rows, and change the memb_org_no to the other. With that, after your next Analytics load, you should be able to distinctly and collectively report on those constituents in the context of your purchased tickets.

    Best,
    Chris

Reply
  • $organization

    Hi Jo!

    The Seats and Tickets cube has both the CONSTITUENT SUMMARY elements for Current Membership Level for all constituents in the cube, and then SEATS & TICKETS DETAILS field for Membership Level and Membership Organization, which are only available against Membership Scans in that cube. Which fields are you using?

    It sounds like you're using the CONSTITUENT SUMMARY elements, and if so, those fields hold exactly one distinct value per constituent. In the case of memberships, like Current Membership Level, the default definition arbitrarily picks one membership for constituents who have multiple current memberships. You can impact that configuration in TX_ANALYTICS_DIVISION_ELEMENT by specifying a specific membership organization (e.g. adding "AND memb_org_no=3" to the data_where field). However, that doesn't fully address your issue as you still want to reliably report Current Membership Level on another membership organization. To do so, duplicate the configuration of Current Membership Level in one of the Custom Category rows, and change the memb_org_no to the other. With that, after your next Analytics load, you should be able to distinctly and collectively report on those constituents in the context of your purchased tickets.

    Best,
    Chris

Children
No Data