I am trying to bucket different groups of constituents in Analytics. Members, Non-Members, and groups, but i am unable to accomplish this. I have tried using lists, but the list number is the only thing that shows, plus all the constituents are there in the list, but when pulled into analytics it seems to omit some and the numbers don't match. There has got to be an easy way to do this, i must be just missing it.
Thanks for any help or guidance.
Do you use Constituencies or different price types for these types of people? You could bucket that way!
Alternatively if you can use custom categories to break-by them out. It's useful it that's a distinction that you are going to use moderately often (if you need my set up let me know and I'll share the slideshow)
Yes and no. Some would have multiple constituencies that would be in the same group that i would want to bucket.
Hi Anthony,
In your reporting, are you expecting that a constituent would only be in one of the three buckets, or would you like to allow for a constituent being in both Groups and Members?
Adding on to Madeline's and Heath's suggestions... if you use Lists, you'll need 2-3 distinct lists. E.g.
The constituent element approach does allow setting multiple constituencies, and will then take the one with the most important (lowest) rank when a constituent has more than one of those configured on the element. For example, if Member had a lower rank value than Group, you could consider updating Custom Category 01 to use the same configuration as the Is Member field (Help Topic: TX_ANALYTICS_DIVISION_ELEMENT), and in the [data_where] change the b.id in (-1) to be your Member and Group constituency IDs. Then update the Custom Category 01 null_value to be "Non-Member", which would be the value applied to any constituent who didn't have the Member or Group constituencies.
The additional though to share is bucketing with existing fields using Filtered Values. In this example, Member takes precedent over Groups which takes precedent over Non-Member.
Members might be the count of constituents with a current membership level
( [# unique Constituent ID] , [Current Membership Level <> (none) ] )
Groups might be the count of constituents without a current membership level who have a group ticket in the scope of the dashboard/widget filters
( [# unique Constituent ID] , [Current Membership Level = (none)] , [Price Type Group = Group] )
Non-Members might require a Multi-Pass Aggregation formula as a count of constituents without a current membership level, who also do not have any group tickets within the scope of the dashboard/widget filters
SUM ( [Constituent ID] , IF ( [Total Ticket Count] , [Current Membership Level = (none) ) > 0 AND ( ISNULL( ( [Total Ticket Count] , [Price Type Group = Group] ) ) OR ( [Total Ticket Count] , [Price Type Group = Group] ) = 0 ) , 1 , NULL ))