your choice step needs a smart list to check on people who haven't had those fields updated in the 9 day timeframe. That smart list doesn't have to be more than that.
Your campaign will be a daily recurring batch that takes in people who had the email sent in the past 1 day, only Once.
If I understand this correctly, you are looking to send a one-off email to those users who were sent 1st email in your main engagement program and since then did not have a specific date field changed on Salesforce for 9 days.
Here's what you can do - Bridge campaign.
Create 2 campaigns - let's call them "Bridge" and "One-off Email".
Here's what the "Bridge" campaign would have:
Smart List -
- Trigger: Email is delivered (select email used in engagement program)
- Filter: Member of Engagement Program X
- Wait - 9 days
- Request a campaign - "One-off Email"
& here's what the "One-off Email" campaign should be configured:
Smart List -
- Trigger: Campaign is Requested - Source is Marketo Flow Action
- Filter: Not Data Value Changed - Attribute Name and Date of Activity in past 9 days
- Send Email that you intend to send.
This should probably help.
So, for the one off email, and I forgot to include this, the Salesforce fields will actually need to trigger if field was updated on a date that could be even longer than 9 days. It would be before a certain date though. So, would this still work if I put the attribute name (SF Field) and Date of Activity before Aug. 1 (or whatever date I choose)?
Yes, using a Salesforce' date field instead of 9 days in wait time should be alright and you can also add Date of Activity as filter on the "One-off Email" campaign.
Also, if I don't want it to be sent after an email is delivered, but X days after a person enters an engagement program, would it be best to use a trigger or batch for the bridge campaign smart list?
1. Trigger: Added engagement program (which they will already enter through another smart campaign into the engagement program)
2. Batch: Was added to engagement program