How to cope with send time optimization? | Community
Skip to main content
bnawijn
March 24, 2021
Solved

How to cope with send time optimization?

  • March 24, 2021
  • 2 replies
  • 2383 views

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?

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 Jonathon_wodnicki

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

2 replies

Jonathon_wodnicki
Community Advisor
Jonathon_wodnickiCommunity AdvisorAccepted solution
Community Advisor
March 25, 2021

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

bnawijn
bnawijnAuthor
April 1, 2021

.

Sukrity_Wadhwa
Community Manager
Community Manager
March 30, 2021

Hi @bnawijn,

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

Thanks!

Sukrity Wadhwa