Hello,
Our Development staff would like to use the ProScore number produced by the Iwave screening in various development outreach initiatives. What we are running into is the fact that the scores exist on the individual level but they are reaching out to donors on a household level via contribution data. Has anyone figured out a way to bump this information to the Household level?
We are currently thinking of creating an attribute that can be applied to the Household but even then we are unsure of the best way to handle a situation where both the A1 and A2 have been scored differently.
Thanks!
Hi Tim,
We haven't embarked on this project ourselves yet, but probably will in the next few months, so I'm curious to hear what sort of solutions we can come up with as a community!
My first thought to the issue of reconciling iWave's individual-level scoring with Tessi's household structure might be to create a new local view that pulls data from LT_IWAVE_CUSTOMER_SCORE_DATA but also adds a new column for household_no (where applicable). That view could then be the foundation for any attributes, header elements, etc. by running a simple bit of logic - if two rows exist with a shared household_no, just grab the iWave screening results that are higher to reflect the household's max capacity. Perhaps that logic is too simplistic, but it may be a starting point at least.
Best,
Evan
Hey all,
Glad that I'm not the only one who has been thinking about this!
We've been beta testing the consortium integration of iWave since January and now that we're more comfortable with it, the fact that we record contributions to households but iWave only scores on the individual constituent is a pinch point for us.
I'll share this thread with my Tessitura developer contact to see if there's any thinking on their end about enhancing the current integration along these lines.
Thank you,
Brian