Expired subscriptions do not auto-remove from assigned group
Posted: Wed Mar 24, 2010 7:50 am
A client of mine tested subscriptions this week for us. He created a 1-day subscription and then bought the product. The user was confirmed as being auto-added to the group after the purchase. 36 hours later, he checked the security group again.....
The good news: When you create a subscription, you can designate a group assignment for the user when the product is purchased. This works great.
The bad news: The user is never removed from that group once the subscription expires.
Ideally, there should be two groups assignable on the subscription. One for when the subscription is active, the other for when the subscription is expired. Otherwise, having both active and expired subscribers in the same group offers very little in the way of usefulness. From a data perspective, I'll always have to check the subscription itself as I cannot depend on group membership alone to determine status.
We can't use the group for email marketing - it's got both active and expired subscriptions. We can't use it control access to subscription-based pages in the store. Same reason.
The back-end processes need a routine to purge expired subscriptions from the subscription groups.
If we had two groups, we could leverage both extensively for both access control and marketing purposes.
The good news: When you create a subscription, you can designate a group assignment for the user when the product is purchased. This works great.
The bad news: The user is never removed from that group once the subscription expires.
Ideally, there should be two groups assignable on the subscription. One for when the subscription is active, the other for when the subscription is expired. Otherwise, having both active and expired subscribers in the same group offers very little in the way of usefulness. From a data perspective, I'll always have to check the subscription itself as I cannot depend on group membership alone to determine status.
We can't use the group for email marketing - it's got both active and expired subscriptions. We can't use it control access to subscription-based pages in the store. Same reason.
The back-end processes need a routine to purge expired subscriptions from the subscription groups.
If we had two groups, we could leverage both extensively for both access control and marketing purposes.