Hello All,
I just came across something that I wasn't expecting in T-Stats. I wanted to use Appeal as one of the criteria in my report, but the Appeal I wanted to use wasn't in the pick list. Long story short, I found out that if there aren't any "Successful Contacts" in your Appeal (or Source for that matter) that Appeal won't come up in your pick list. I've never tried to use Appeal in T-Stats, but we do use Appeals to keep track of several non-response type efforts (such as a postcard about an upcoming exhibit opening) so I was wondering if there anyone out there knows of a way to make Appeal usable by Successful Contacts and, separately, Contacts?
Many thanks!
Jenny O'Neill-Englund
Jenny,
Yeah, I think I understand the problem. The Appeal element in T-Stats is looking at transactions which were recorded with a certain source and then finding the values--and the people--connected to that transaction.
You might be able to get some useful information if you turned things around a little bit and instead of looking for specific transactions with a certain appeal you could look for specific people who have a certain appeal promoted to their account and then find their transactions.
What I mean is you could make a list of constituents to use as a filter in your T-Stats report. The list criteria would be based on the promoted appeals in the constituent accounts. You could even narrow it down based on the promotion response which would tell you if a transaction was processed or not. If the promotion response has a transaction processed then that constituent is a successful contact on the appeal.
Good luck.
Jared
Hi Jennifer,
What you're describing is expected behavior. In T-Stats each cube has a specific focus, for example everything in the Contributions cube revolves around contributions, the Tickets cube, all tickets. In order for an Appeal to be visible in a particular cube it has to be associated with that focus of the cube. So the only appeals available in the Contributions cube are appeals that have been used in at least one contribution. The only appeals in the Tickets cube will be those associated with either a ticket lineitem or a ticket order. Consequently if an appeal or source has not been used in the context the cube is reporting on, you won't see that appeal or source in the list because there would be no results for that appeal in that cube.
If your goal here is to report on constituents who were promoted a particular source (or the appeal associated with it) but purchased a ticket or made a contribution using a different source or appeal, then Jared's suggestion should allow you to cross reference those constituents associated with the appeal or source in question, and see what they actually purchased/contributed. If your goal is to do a more source-centric analysis, of all sources and appeals independent of their "success", that would probably be better suited a custom cube.
I hope that clarifies a bit for you!
We've also been increasingly looking to report on all contacts promoted to the Appeal Sources regardless of that source being applied to their transaction or not. Particularly as more and more transactions come via web and almost always all have the generic web Source code. I've been doing what Jared suggested and creating List Manager lists and using them as filters in T-Stats. This can be time consuming depending on how many Source codes you have in your Appeal and if you want the reporting to be that granular (we do). Some of mine have up to 70 Sources so I've made one list for each and then copy my T-Stats report that many times to report on each Source. In the end this is obviously time consuming so we are having IT write a custom report to report to achieve this. If you have questions feel free to reach out.
Chuck Buchanan
buchananc@nyphil.org
From: Jennifer O'Neill-Englund <bounce-jenniferoneill4251@tessituranetwork.com>Sent: 12/13/2016 1:14:03 PM