Ticket Number of Unique Perfs - functionality

Are you using any other criteria with it?

I only ask as if you are using other Ticket criteria because they get added to the criteria for unique performances.

For instance if alongside Unique Performances <1 you have asked for anyone who attended a particular production season or came in a particular year then your list will show people who have 1 performance in that production seaono or year even though they have other performances outside of that.

There are two ways to get around this, one is to run a list of Unique Performances >1 and then set this as an exclude list in a second list - if you other criteria is ticket related then you don't need to exclude those with 0 as they will not be included, if it isn't then you will need a second list either an inclucsive ie list of everyone who has a performance or exclusive anyone who has 0 performances.

Personally, I always prefer extractions and as previously stated you start by excluding anyone with 0, or more than 2 performances in your first 2 segments then you know you are just working with people with 1 performance and can begin to break them down into various lists and prioritise them, this gives you a lot of flexibility as you can start breaking down by when they came, how much they spent, if they have memberships, where they live, when their record was created etc

Mark

Are you using any other criteria with it?

I only ask as if you are using other Ticket criteria because they get added to the criteria for unique performances.

For instance if alongside Unique Performances <1 you have asked for anyone who attended a particular production season or came in a particular year then your list will show people who have 1 performance in that production seaono or year even though they have other performances outside of that.

There are two ways to get around this, one is to run a list of Unique Performances >1 and then set this as an exclude list in a second list - if you other criteria is ticket related then you don't need to exclude those with 0 as they will not be included, if it isn't then you will need a second list either an inclucsive ie list of everyone who has a performance or exclusive anyone who has 0 performances.

Personally, I always prefer extractions and as previously stated you start by excluding anyone with 0, or more than 2 performances in your first 2 segments then you know you are just working with people with 1 performance and can begin to break them down into various lists and prioritise them, this gives you a lot of flexibility as you can start breaking down by when they came, how much they spent, if they have memberships, where they live, when their record was created etc

Mark

Thanks, Mark! That is in fact the only criteria I am pulling, because I suspected that element wasn't working quite right in List Manager and so I wanted to test it out.

My question though (and in regards to Dani too) if this element isn't properly doing a count of 1 unique performance, can I really trust it to count 2+ unique performances to use in a suppression list? So I tried an extraction where I suppressed >= 2 and =0 on the pull of =1, and still I am getting constinuents with multiple unique performances.

If that is the only criteria then it means that either there are limits in the criteria itself or that what it it is using to identify unique performances isn't unique in the data.

As Martin said, if it is using perf_no and you have imported data where all historical performances have a perf_no=-1 then it will see all those as the same performance. 

If you use show query in your list you should see what it is using

Select Distinct a.customer_no
From V_CUSTOMER_WITH_PRIMARY_GROUP a WITH (NOLOCK)
JOIN (Select a1.customer_no From LVS_TICKET_HISTORY_TRN a1 WITH (NOLOCK) Group By a1.customer_no Having count(distinct a1.perf_no) = 1) as e ON e.customer_no = a.customer_no
Where IsNull(a.inactive, 1) = 1

The bit in Bold Italics is the name of our custom view on Ticket History
The Having part in Bold shows you in this case that we use perf_no as the unique identifier.

Mark