Hello all,
Two semi-questions:
1. Can I use a promoted source code as a filter in a dashboard? These source filters I see appear to be line item or order filters, but I was hoping to filter the dashboard to everyone who was promoted with a specific source.
2. I'm struggling with using lists to filter dashboards as well. I have the Analytics box checked on the specific lists in question, and our backup was at 1am today, so the lists should be available in Analytics. I'm also using the list as filter in a widget with the list number surrounded by commas.
What am I missing?
Thanks,Lesley
Hi Lesley!
What is the cube for your dashboard widgets? For instance, in Seats and Tickets, a filter on a source is going to limit you to tickets that had that source attached to them (or their order), not customers for whom the source was promoted.
As to Analytics and Lists, it sounds like you're doing the right thing. Here's one I did recently:
A caution is that lists are not regenerated by Analytics, so if you don't manually keep it regenerated, the data in the list will be stale when Analytics loads it. Yes, I'm going to flog this Idea again!
community.tessituranetwork.com/.../analytics-should-honor-dynamic-lists
Hi Gawain - I was just thinking that I hadn't talked to you in a while.
I am using the seats and tickets cube, so now that you've said it, that totally makes sense. Is there a way for me to gather those to whom a source was promoted?
As for this list, it's weird that I'm not getting any patrons in the preview:
My list setting looks like this:
Lesley Chaney said:I am using the seats and tickets cube, so now that you've said it, that totally makes sense. Is there a way for me to gather those to whom a source was promoted?
A List!
It looks clear that the list in question didn't get uploaded. I'd make a spot check of the last load date (at the top of the analytics dashboard), that the id of the list is correct (below your screenshot in the List edit page). Then I might kick it to support.
OOOH, I get it... a list of those with the promoted source code. <Sigh>
Thanks for your help!
On more thing to add: be sure to regenerate your list AFTER you click the Analytics toggle or it won't get picked up by Analytics until you do regenerate.
Oh, wow: that's useful information. And it looks like that would cause an issue here, since Lesley's list was built in 2022. What if it's not a criteria list?
For that case, I've made a list based on a list (criteria under Other unless it's been moved in your installation) and generated that new list.
Also, I learned this way back when I first switched from T-Stats, so maybe it's artifactual. I'll have to test to see if it still holds, but my understanding at the time was that it was the generate function that loaded the list into the data warehouse pool. A Freeman's reminder of the T_DEFAULTS List Generated Months Back setting seems to confirm it's (re)generation that moves the list into the data warehouse, in which case my workaround for an old non-criteria list ought to work (and my past experience was that method did work, noting flip the Analytics toggle, and then (re)generate. )