[FEAT] Link click limits with redirects
For our marketing campaigns, sometimes a special offer is for the "next 50 people" and limiting clicks to just the first XX number of individuals would be great. then redirect them to another place after the limit is reached.
@cuhpajo maybe you are talking about this. right?
@cuhpajo maybe you are talking about this. right?
do you mean the current Dub limits? If so, no. I am referring to a specific feature similar to the one recently introduced, which imposes limitations based on a date. In contrast to the time-based restriction, I'm thinking a feature that would restrict a link based on the total number of clicks it receives. Once this predetermined click limit is reached, the link would then be redirected elsewhere.
@steven-tey If required, I can work on a feature to implement expiration upon reaching a certain number of clicks
@cuhpajo maybe you are talking about this. right?
do you mean the current Dub limits? If so, no. I am referring to a specific feature similar to the one recently introduced, which imposes limitations based on a date. In contrast to the time-based restriction, I'm thinking a feature that would restrict a link based on the total number of clicks it receives. Once this predetermined click limit is reached, the link would then be redirected elsewhere.
That's cool @cuhpajo! We can store the user's IP address with a cookie. This ensures that a user can't use the link a second time. Even if the user removes the cookie, we still have their IP address. What do you think?
@cuhpajo maybe you are talking about this. right?
do you mean the current Dub limits? If so, no. I am referring to a specific feature similar to the one recently introduced, which imposes limitations based on a date. In contrast to the time-based restriction, I'm thinking a feature that would restrict a link based on the total number of clicks it receives. Once this predetermined click limit is reached, the link would then be redirected elsewhere.
That's cool @cuhpajo! We can store the user's IP address with a cookie. This ensures that a user can't use the link a second time. Even if the user removes the cookie, we still have their IP address. What do you think?
that sounds like a reasonable way to make that feature happen for sure!
