I'm getting different numbers for a query with V_MEMBERSHIP_CURRENT/TX_CONT_MEMB/T_CONTRIBUTION than using the Campaign/Campaign element in Analytics. For the primary campaign I'm looking at I get:
Query: 1136 (or 1050 without Lapsed)
Analytics: 975 (no filters applied)
Of the three other, much smaller, campaigns, two are one membership higher by query, and one (the smallest) is the same as Analytics.
Hi Gawain,
In the Tessitura database, [BI].[VT_DW_MEMBERSHIP] is the source view for Memberships. I don't know that this is a factor in your specific scenario, but the Analytics BI View does some preliminary filtering to excluded memberships with a current status of "merged" and any associated with inactivated constituents. If you continue to have trouble validating your data, we can help more easily/thoroughly via support ticket.
Best,Chris
I checked, and the only entries for "current_status" are 2 and 7 (Current and Lapsed). Likewise, no inactive customers. I have a ticket open currently with Beth.
I'm going to have to dig in to it again, as the widgets as currently configured are also looking at some other things, so I need to double check that those filters aren't causing a problem.
I note that VT_DW_MEMBERSHIP uses VXS_CUST_MEMBERSHIP, not V_CURRENT_MEMBERSHIP. Not sure what differences that would incur or why.
Okay, I think the difference was that I was joining on TX_CONT_MEMB, and that returns multiple rows in cases where more than one contribution is applied to a Membership.
I'm still not 100 connecting, but 3 of 4 campaigns are now giving the same numbers, an the last is off by two.
Interesting note: when I save the one problem row now as a list, that list has fewer members than suggested in the widget, and it matches my query exactly.
Hi Chris,
To your point about the preliminary filtering, why are memberships with a status of Merged not included?
Thanks,
Stephen
Hi Stephen,
It was originally deemed too confusing to include them. They will be included in v16.