• Replies 4 replies
  • Subscribers 414 subscribers
  • Views 113 views
  • Users 0 members are here
Related

IWave Scores and Household Output

Tim Helmer
$organization

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!

  • $organization

    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

  • $organization in reply to Evan Cartwright

    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

  • Former Member
    Former Member $organization

    Hi Tim,

    I'm not sure where you're trying to pull the ProScore into, but if it's as a criteria within lists and extractions I think the Search Household checkbox might accomplish what you're looking for.  Checking the box for your contribution criteria will pull the household data down to the individual and like you said the ProScore is already on the individual.

    Then using the Advanced Relationship options you could replace individuals with primary household so that your list contains the household accounts.

    This doesn't help if your goal is to display the ProScore through an output set or on a header, but if it's simply to create lists of contacts it could work.

    Whatever solution you come up with, please do share as I'll have the same problem in a few months!

    Dorothy

     

  • $organization

    Thanks!

    I was thinking a view might be a good place to start but my SQL skills are in their infancy so it adds to the challenge.

    Tim Helmer

    Data Coordinator

    Ford's Theatre| Where Lincoln’s Legacy Lives

    Mailing Address: 514 10th St. NW, Washington, DC 20004

    Phone: (202) 434-9527

    Email: thelmer@fords.org

    www.fords.org

     

    From: Tessitura Development Forum [mailto:forums-development@tessituranetwork.com] On Behalf Of Evan Cartwright
    Sent: Wednesday, April 12, 2017 1:35 PM
    To: Tim Helmer
    Subject: Re: [Tessitura Development Forum] IWave Scores and Household Output

     

    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

    From: Tim Helmer <bounce-timhelmer8484@tessituranetwork.com>
    Sent: 4/12/2017 11:47:32 AM

    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!




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Development Forum. You may reply to this message to post to the Development forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!