Sending an email one day after [filter with specific date] | Community
Skip to main content
J
jleskar
New Participant
August 14, 2020
Solved

Sending an email one day after [filter with specific date]

  • August 14, 2020
  • 1 reply
  • 3136 views

Hi All - 

 

Sorry if this has been answered too many times, but terminology is getting to be a little tricky for me: specifically when it comes to "in past," "in past before" ...etc.

 

We have a filter that calculates a specific date for a given user. I'd like to send those folks an email *one day after that date*, and enter them into a sequence of emails. 

 

For example:

- Calculated Date Filter = 10/1/2020

- Date I'd like to enter them into the next sequence of emails: 10/2/2020

 

What would be the correct smart filter to put on "Calculated Date Filter"?

 

I've seen people suggest using a combination of ([Filter Date] "in past before = 2 days" and "in past 1 day") and some people suggesting just using "[Filter Date] in past = 1 day". Would either of these work? Neither of them? I obviously only want them to be able to enter this sequence once. 

 

Thank you in advance!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Carrie_Chandle1

Hey there! Date filters are always fun 😛

 

The first example you gave of using a combination of the "in past before 2 days" and "in past 1 day" filters will cause a conflict.

 

The "in past before" filter lets you look for any activity before a stated time period. So for the example you gave using the two filters together, Marketo would be looking for anyone whose calculated date filter was 9/29/2020 (2 days before 10/1) or earlier AND in the past day, which would return no results.

 

If you use an "in past before" filter you want to combine it with a filter to make sure your date field is not empty. Otherwise, it'll pull in anyone with NULL values for the date field, as well as anyone who actually qualifies based on their date value. 

 

So.... to answer your question, using the "in past 1 day" filter should do the trick for you. 

 

You can double-check yourself by creating the smart list logic, viewing the "Schedule" tab, and clicking the "set to affect xx people" hyperlink and viewing their date values for your calculated date filter to ensure your logic is doing what you expect it to.

 

You can also use the Smart Campaign Settings to ensure a record only runs through the campaign once. 

 

 

Hope this helps!

 

1 reply

Carrie_Chandle1
Carrie_Chandle1Accepted solution
New Participant
August 14, 2020

Hey there! Date filters are always fun 😛

 

The first example you gave of using a combination of the "in past before 2 days" and "in past 1 day" filters will cause a conflict.

 

The "in past before" filter lets you look for any activity before a stated time period. So for the example you gave using the two filters together, Marketo would be looking for anyone whose calculated date filter was 9/29/2020 (2 days before 10/1) or earlier AND in the past day, which would return no results.

 

If you use an "in past before" filter you want to combine it with a filter to make sure your date field is not empty. Otherwise, it'll pull in anyone with NULL values for the date field, as well as anyone who actually qualifies based on their date value. 

 

So.... to answer your question, using the "in past 1 day" filter should do the trick for you. 

 

You can double-check yourself by creating the smart list logic, viewing the "Schedule" tab, and clicking the "set to affect xx people" hyperlink and viewing their date values for your calculated date filter to ensure your logic is doing what you expect it to.

 

You can also use the Smart Campaign Settings to ensure a record only runs through the campaign once. 

 

 

Hope this helps!

 

    Josh_Hill13
    Josh_Hill13
    New Participant
    August 14, 2020

    please refer to https://docs.marketo.com/display/public/DOCS/Smart+List+Filter+Operators+Glossary as there is a nice chart.

    Terms & ConditionsAccessibility statement

    Loading footer...