I’m creating a sequence that delays first on a custom date field, then I want it to delay on time. So it goes:
- Delay 355 days after custom date field
- Send email
- Delay 362 days after custom date field
- Remove tag
- Delay 5 months
- Send email
- Delay 3 weeks
- Send email
- Apply tag
I cannot connect any elements that have one timer type on one side and another timer type on the other. I’m wondering if that’s a bug or by-design.
What I then tried to get it to work was change items 5 and 7 to custom field timers. Changing item 5 to “wait 17 months after custom field” works, but to pinpoint three weeks after that (or a week before 18 months) the timers won’t let me use more than 365 days, nor more than 52 weeks. Further, if I check “next occurrence” and try 5 months and 175 days, I get an error saying the timer is before previous timers in the sequence so cannot be allowed.
Finally, I tried to set the custom field timer to “when contact reaches this point in the sequence” at item 4 then use regular “under a year” time frames using the same custom field timers. That also did not work.
It seems the only way to do this is to create a second sequence, separating items 1-4 from items 5-9, cluttering up the campaign elements.