How to learn if it's the patrons first time donating tickets in Analytics

Hi Nathaniel,

Let's say I have a dashboard filtered to the COVID19 Campaign, and SLI Status = Return in Benevolent Mode. If we put together a Pivot widget, with Constituent on Rows, then we can create a formula to calculate whether, for each constituent, their first order (within the COVID19 Campaign that was Returned in Benevolent Mode) is their first order associated with ANY Campaign (but still where the ticket was Returned in Benevolent Mode). The formula would look like:

IF (
  [Min Order ID] = ( [Min Order ID] , ALL( [Campaign] ) )
  , 1 , 0
  )

Then use that value as a Widget Filter, limiting the results to constituents with a Value = 1.

If we add Grand Totals, we can set the widget to Jump To the _Constituents dashboard, Apply, and clicking on a Grand Total result, save a list from there.

Best,
Chris

Hi Nathaniel,

Let's say I have a dashboard filtered to the COVID19 Campaign, and SLI Status = Return in Benevolent Mode. If we put together a Pivot widget, with Constituent on Rows, then we can create a formula to calculate whether, for each constituent, their first order (within the COVID19 Campaign that was Returned in Benevolent Mode) is their first order associated with ANY Campaign (but still where the ticket was Returned in Benevolent Mode). The formula would look like:

IF (
  [Min Order ID] = ( [Min Order ID] , ALL( [Campaign] ) )
  , 1 , 0
  )

Then use that value as a Widget Filter, limiting the results to constituents with a Value = 1.

If we add Grand Totals, we can set the widget to Jump To the _Constituents dashboard, Apply, and clicking on a Grand Total result, save a list from there.

Best,
Chris

Curious about this. So in this example is the assumption that the Return in Benevolent Mode tickets have been returned in a new order with a source tied to the COVID19 campaign?  Otherwise, wouldn't the orders with tickets having an SLI status of Return in Benevolent Mode be tied to the campaigns selected in the original performance setup?

Or the source on the original order, I suppose...

Yes, it's a good point, Kelly. Analytics is using the original SLI for donations and package exchanges, as that's where the sales figures live, and then updates the SLI status based on what happened later, regardless of VTO/VOO. I imagined, without saying anything above, that perhaps the lineitem source would change to reflect the COVID19 campaign, as opposed to the whole, originally selected, order level source. But then, it would have to be changed on the lineitem for the original sale for that to come into Analytics as expected. Does that seem viable?

Oooo that is good to know, Chris, it is certainly not part of our users' RTB process to update the lineitem source on the original order, so my ship has sailed on that front, but I'll tuck that nugget away for a less crazy time.  Currently I'm trying to find orders via analytics that were returned in benevolent mode by our web user, but I can't seem to get away from the info on the original order.  There's no transaction trail, so I'm looking in seats & tickets rather than finance, but filtering on SLI status of Return in Benevolent Mode and solicitor Web User I can only see the original order info, in other words using solicitor to limit the orders seems to only be giving me orders that were originally purchased via the web user.  Any suggestions for me, or is this something I should try to find via another avenue?

Yeah... short answer here is that RET and RTB SLI aren't even extracted from Tessitura into Analytics. VTO/VOO are extracted, and then updated to to the status of their corresponding SLI. So for VOO, you'll only see the solicitor of the original order in Analytics and not that of the "other" order. We'll need to find another avenue for this. The Donated Seats report doesn't include solicitor as a standard field in its output. The code in the stored procedure behind it though it just inches away from what you're after and could make for an easy starting point to pull this data... even without customizing the report itself.