Expiring tags
The idea is: setup special tags with an expiration date, when the tag expires – remove it. Therefore triggering any actions in the CRM based on tag removal. I know, we can do this with fixed tags using a CRM workflow already. An example use case is: We use WisdmLabs Groups + LearnDash Groups + custom enrollment tags (Enrolled-<group name>) We don’t want to use WooCommerce (too much overhead), we don’t want to use any other membership/subscription plugins. The automation in fluentCRM (and others) relies on “hard-coded tags” to do their work, which means: one new automation workflow for every group that is created dynamically – this can be an issue. FluentCRM allows a trigger (when enrolled in ANY group start automation/workflow), which is great, but by the time we get to: remove tag X – there is no way to know what group actually kicked off the automation. Therefore, having a tag “expire” at a specific date time, then having wpFusion remove it on expiration, sounds like a workable solution. Just a thought – this probably is a huge engineering task.
Dan Linstedt shared this idea
Updated: January 10, 2025
This would probably be best left to the CRM since they can handle the conditions and scheduling more reliably.
Bento has a cool feature called Tag Decay that works like this https://docs.bentonow.com/knowledge_base/understand_tags
Hi Jack, Tag decay sounds like something I could use? i don’t know if you can create an add-on for wpFusion that does that, but if so, it would be awesome. Maybe it needs to be built into the core – because it’s pervasive system wide?? but yea, something simple like tag decay would be sweet.
And yea, we’d need to trigger stuff on each user that the tag is being removed from at the time the tag decays – so: scheduling “batch actions” to execute in the background on cron-jobs until finished….
Sorry, I ran into another business use case where this would be a really neat feature for us to have in wpFusion.
Ok cool. Yes it might make sense as an addon, because of the potential performance issues…. then folks won’t accidentally turn it on.
Then we can have a separate settings page where tags can be selected as “decaying” with the date rules.
It’s a big-ish job, I’m not sure when we’d be able to start, but I’ll mark it as Accepted so it makes it to our next planning session 🙂
Here’s another use case we’re considering that would help when woocommerce subscriptions seems like overkill and is not flexibile enough.
A woocommerce addon for wp fusion that allows us to setup tags that expire at a certain date. The tag is given at purchase and expires at the date on the product configuration page.
Our use case is selling live online classes that take place at certain times – people purchase prior to the class starting, but everyone should lose access at the same time.
We could then have product variations that allow for selling 1 semester at a time or full year – the same access tag could be used on both variations, but the decay time/expiration date for the tags could be set differently.
Hi Philip,
I agree with your use case. Today, because we use LearnDash, we also use LearnDash Groups (not Groups Plus). We couple that with Woo Subscriptions, and it works perfectly.
We sell a subscription to a group not a course. Then, the student buys a ticket to the group. When the subscription expires, the group is put in draft mode automatically by LearnDash Groups + wooSubs. This cuts the student access automatically.
Mind you, if you are creating LearnDash courses, you can hard-code start and stop dates right into the course too, but this means you are constantly creating new courses. Which is why we use the group approach. One course (always there), and moving groups (new groups, and deleted groups once done.
But I agree – Expiring Tags is a really cool thing to have.
Thanks,
Dan
Dan,
Thanks for the ideas. We have our LearnDash separated on another site, which is why the tags are the important linker between them and makes things a bit more complex.
Makes sense, and I totally agree.