Hi!
I feel awful even saying the words "Conversion Rate", but I'm going to go there anyway lol. We used to have a report that followed our in-house definition of Conversion Rate, but it might not be accurate anymore and the person who made it isn't here anymore. Additionally we would LOVE for this to be a self updating widget in Analytics if possible. Since people can't buy a membership and tickets in the same transaction online we widened out definition of "Converted" to people who bought a membership and tickets in the same day/all the people who bought any tickets. Our rationale is that they had a choice to buy full price tickets and no membership, or buy a membership and tickets. Even those who are renewing have that option so we include them too, not just non members. I know that this mixes Membership and Seats & Tickets data, but I thought maybe I could cobble something together with the data options that cross over into other areas. I have my eye on Campaign Category in the Membership cube. I have categories for Admissions and then two for our Membership categories? What I'm unsure of is how to I ask for when that happens on the same day. Likely I won't be able to get to the data I want, but I thought I'd drop a line in the water here and see what I come up with.
Jenny
Hi Jenny,
Might it work to look at daily figures in the Finance cube for counts of constituents with both a ticket and membership purchase? For example, with Days in Transaction Date on Rows, having a Value for
SUM ( [Constituent ID] , IF ( [Total Ticket Purchase Amount] > 0 AND ( [Total Contribution Amount] , [Fund IN your membership funds] ) > 0 , 1 , NULL ))
If you need to see it at a higher level, like monthly rather than daily, then we need to add Transaction Date in the formula...
SUM ( [Constituent ID] , SUM ( [Days in Transaction Date] , IF ( [Total Ticket Purchase Amount] > 0 AND ( [Total Contribution Amount] , [Fund IN your membership funds] ) > 0 , 1 , NULL ) ))
Thank you Chris, this is great. And they make total sense. For some reason though it doesn't like the greater than sign, in both cases. The formula is so basic though, I can't see why it's giving me the "unexpected token '>' in FunctionParameters definition" error.
Screenshot and copy / paste in here? Maybe attach .dash?
Sure! I'd share the .dash but I can't save as it is.But I can share these Sorry they're so shrimpy. The error, in both cases is "Function Syntax Error: Unexpected token '>' in FunctionParameters definition.
It might require a closing parenthesis before the ' > 0' portion.