Eliminating cancelled subs from a list

Matt,

Are you using criteria in the “Subscription Summary” folder to pull your list?  If so, that’s why you’re getting cancelled subscribers.  Any rolled-over subscription order has a subscription summary in it, whether or not the package is renewed.  So if you used “Subs Summary Season” as your criteria, it would include those cancelled folks.

I’d recommend using the criteria elements under the “Ticketing” folder in List Manager.  There is a “Subscription Season” option which you can use easily to determine who has last year but not this.  The criteria elements in this folder come from the Ticket History tab in a constituent record – the good thing about that is that a subscription appears as Subscription History only if it’s been renewed.  Anything that’s been cancelled won’t appear (as long as your subscription history is updating correctly).

Hope that helps!

Christy

Seattle Rep

Hi all,

I was trying to pull a list of non-renewed subscribers - people who had a subscription last year but not this year. It seemed like a simple case of pulling who has one season but not the other - but cancelled subscribers snuck in to the list because they have an empty order with no season or package at all.

What's the best way to do this? What do other people do?

Cheers,

Matt

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Marketing Forum. You may reply to this message to post to the Marketing 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!

Hi Matthew,

We also use CSI’s to track this type of information.

Each year we do a rollover for all fixed and flexi subscription packages (the latter being a dummy package) if a subscriber informs us why they won’t be renewing we track that information against the specific season/package when deleting the subscription. Prior to Tessitura the Box Office used to record this info in an external spread sheet so it has been really useful.

Happy to share the categories prior to your set up if that helps at all.

Regards

Brenda

From: Tessitura Marketing Forum [mailto:forums-marketing@tessituranetwork.com] On Behalf Of Matthew Hodge
Sent: Friday, 25 February 2011 11:51 AM
To: Brenda Fehlberg
Subject: Re: [Tessitura Marketing Forum] Eliminating cancelled subs from a list

Hi everyone,

Thanks for all your suggestions. I realised that I should have explained what we were using them for. What we're trying to do is pull everyone who subscribed in 2010 who doesn't have a 2011 subscription, so we can try a last-ditch marketing effort on them. However, we want to differentiate between someone who hasn't bought the 2011 season yet because they're slack and someone who was rolled over as a subscriber and then cancelled.

The way we've currently decided to handle it is to add an attribute with a cancellation reason drop-down that's unique this to this year (e.g. Cancellation Reasons 2011), and that way we can just eliminate anyone with a cancellation reason.

Now that I'm thinking about it, a CSI might be an even better idea for next year, so thanks, Ryan. The answer I'm getting, anyway, is that none of the out-of-the-box criteria will work for excluding subs history, unless we add some sort of flag to the Subs History table or do something like what we're doing with an attribute or a CSI.

Hi Matt,

Good day.

how about you put a selection on the lt_sub_hist table?

in that table, you have all info you need to create a list.

have fun

Ben

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Marketing Forum. You may reply to this message to post to the Marketing 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!