Cases in which Modification notification fire?

#1

Quick question about when the ‘Modification notification’ fires.

Say we have a member whos paid subscription has expired and they have been demoted to subscriber level.

If they were to login to their subscriber account and go through and use a sign up for (not a modification form), would this still fire the modification notification, or would this fire the sign up notification? or would it not fire anything?

Thank you

#2

They should not be able to use a “sign up” form if they are already subscribed (which they are if they were demoted to Level 0). No one should ever use a registration form unless they are registering. That is why there are modification forms.

1 Like
#3

Thanks for the reply. So we have an fixed term membership for 1 year. when users near the end of their term, some of them login and visit the sign up page to renew. So what I’m guessing is that for existing members that complete the “sign up process” again, their transaction is marked as a modification?

I actually installed a fb pixel into the modification tracking section and it fired yesterday, so this seems to be the case as I didn’t change anything else.

#4

No, that is not the case. Their EOT will be set based on the new registrationt terms and/or their level changed depending on the form they filled out, but their previous membership will not be cancelled. Since it is expiring anyway that may not seem to be a big deal, but what if they fill out the form 2 weks after they bought their membership and then they are being billed twice?

1 Like
#5

Yeah sorry for the confusion. The only people who use the sign up form twice are members who are on a non-renewing plan that we have. What I do is have them login, then visit the sign up page again. Using the sign up form again in this way adds another year onto their existing subscription. I tried the modification form for this use case, but it does not add on to the remaining subscription, it just starts a new subscription from the modification date.

Using the sign up form twice for this use case seems to be firing the modification notification so I think I’ll just keep it like this.

Thanks