Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

How to cope with send time optimization?

bnawijn
Level 1
Level 1

In Adobe Campaign Classic we have the ability to store a 'prefered sending time' of a customer (read: recipient).

We have (external) logic to calculate that prefered sending time, which will differ per recipient.

 

Expected behaviour is that the recipient will receive the delivery on the prefered sending time. If the prefered sending time is already passed (eg; prefered = 7AM, but workflow started a 9AM) then the business expectation is that the email is send out directly.

 

Question: how can I take the 'prefered sending time' into consideration when I want to send out the same delivery to all my recipients?

I've read that there is an integration with Sensei, but that (I think) it's mainly handling the calculation of the value (which is already done). I'm more interested in actually using that value in my campaigns. Maybe we can re-use ACC-Sensei logic here? Does anyone know how send time optimization is handled in that case?

1 Accepted Solution
Jonathon_wodnicki
Correct answer by
Community Advisor
Community Advisor

Hi,

 

Create a workflow with at least these parts:

  1. Scheduler that runs every hour or whatever recipients are bucketed into
  2. Query that selects all recipients with time preference below next bucket start, for hourly this would be '@timePreferred before Hour(AddHours(GetDate(), 1) and delivery log does not exist where this delivery was attempted to recipient this cycle'. Safe and allows for 'catch up' as there isn't a lower bound
  3. Continuous delivery. If this is a workflow that runs on a recurring basis and should have a different delivery per cycle it gets slightly more complicated

 

Thanks,

-Jon

View solution in original post

3 Replies
Jonathon_wodnicki
Correct answer by
Community Advisor
Community Advisor

Hi,

 

Create a workflow with at least these parts:

  1. Scheduler that runs every hour or whatever recipients are bucketed into
  2. Query that selects all recipients with time preference below next bucket start, for hourly this would be '@timePreferred before Hour(AddHours(GetDate(), 1) and delivery log does not exist where this delivery was attempted to recipient this cycle'. Safe and allows for 'catch up' as there isn't a lower bound
  3. Continuous delivery. If this is a workflow that runs on a recurring basis and should have a different delivery per cycle it gets slightly more complicated

 

Thanks,

-Jon

View solution in original post

Sukrity_Wadhwa
Employee
Employee

Hi @bnawijn,

Was the given solution helpful to resolve your query or do you still need more help here? Do let us know.

Thanks!