Skip to main content

We have the potential for user to be in multiple journeys at once. I am trying to figure out the best solution for holding a user at a tile if they have recently gotten an email from us (say the last 6 hours) and delaying the send, not skipping it entirely, which is what the Frequency Management settings currently would have it do. 

We want to avoid a user getting multiples emails from us in a short period of time, but we also want to avoid the user not getting the email all together.

2 options we’ve considered - 

  1. “Yes/No split” to check for email sends in last 6 hours and adding a time delay for another 6 hours before sending the email. 
  2. Creating a Dynamic List of email sends in the last 6 hours and adding a “Wait Step” to check that a user is no longer apart of that list.

Is there another option I’m missing or does anyone have a better solution they’ve used in a similar scenario?

Hey ​@mtucker@taxslayer.com!

 

One idea might be to set up a utility workflow that runs when an email is sent and updates the customer profile with a property/field called lastEmailSent (datetime). With that workflow running and all users having the field, you could then use the “Wait until” tile with that field and some dynamic/relative time window to have users wait until lastEmailSent + 6h (or whatever). Would probably save you from a lot of clutter in your journey tiles. 
 

Let me know if that makes sense or if you have any follow up questions!

Hi ​@mtucker@taxslayer.com ! Thanks so much for your question and thank you ​@drakeballew for your response and recommendation. In my opinion all three ways mentioned would be a great way to go! The first one you mentioned ​@mtucker@taxslayer.com would probably provide the most clutter in your journey, while the second option you mentioned and then the option that ​@drakeballew mentioned would most likely be the same amount of work with the dynamic list and profile update components for each option, and they would get the job done with the least amount of tile clutter! Please let us know if you have any questions or run into any trouble while testing this out :) 

​@noa1udler ​@drakeballew thank you both for those suggestions! That definitely makes a lot of sense and was super helpful!

​@drakeballew I may be missing this, but what do you trigger the workflow off of if the “Email sent” event is not an option to start the journey?

​@noa1udler  Also, when trying to go the route of my second option, I’m unable to check for a user being apart of a dynamic list. The only option I’m seeing is to have the entry source being “schedule” and run it daily to add users from the dynamic list I created. 

Any suggestions I may be missing?

​@mtucker@taxslayer.com ah shoot - sorry about that! Didn’t check the interface before writing my reply. It seems like you’re right and Email Send isn’t a trigger out of the box.

There  are multiple ways to get the same result, and the best one will depend on your “stack,” but maybe the easiest option would be to:

  1. Create a dynamic list of users with Email Send events and Email Send Date with your desired parameters
  2. Set up a utility workflow to update the user profile as discussed previously, and set the trigger to API
  3. Use a tool like Zapier, Make, Pipedream, etc to trigger your workflow on a schedule with the list ID and time paramter created in step 1 (docs here)

Like I said, there are other ways to do this as well, depending on what tools you’re using, but this option is pretty straightforward and only requires a fairly cheap tool that most companies already have in their toolbox.

 

Let me know if that makes sense or if you have any questions!

Reply


Terms & ConditionsCookie settings