My idea is:
Currently when you do a campaign for example for an anniversary - you end up having to run a condition on the field value with the date operator and value Anniversary. Maybe there’s better ways but this is the only one I have found. But then you need a 1 day wait to then restart the campaign if condition doesn’t match. This is fairly non-intuitive and means anyone wanting to setup a birthday campaign is left scratching heads or Googling.
My thinking is that on the “on relative date” option for actions, we just allow an additional dropdown that is introduced as “Schedule this action relative to the” and options “current time” / “contact field: Date Field 1” / “contact field: Birth Date”. Then display the same relative fields but allow 0 day to be specified.
This would then allow you to:
- send an email
- on a relative date
- relative to contact field: birthdate
- being 2 days in the future
Of course the only complication implementation wise, is the need to reschedule the campaign for a contact when the date field changes.
I think these groups of people would benefit from this idea:
Anyone wanting to setup anniversary campaigns, which feel really hard to setup at the moment and not really intuitive or efficient as they end up calculating every day. And it feels really easy to make a mistake with the wait 1 day before condition check, and having to have the restart properly setup, which could then mean accidentally sending lots of emails if the send email path doesn’t hold them long enough.
I think also system admins will love the fact that each contact has a single schedule entry that waits for the anniversary, rather than checking every single day, so there’s not huge running campaign processes every day processing the condition for every single contact. Though this could be a misunderstanding from my side but it feels like this is how it is happening currently.
Why I think they would benefit from this idea:
Simpler process for anniversary campaigns that is more discoverable and flexible, and reacts super fast as the schedule time means extremely fast execution
Any code or resources to support this idea:
No
Are you willing to work on this idea?:
Yes
What skills and resources do you need to explore this further?
Just looking for feedback on this idea.