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
BedrockMission!

Learn More

View all

Sign in to view all badges

Time Zone

Avatar

Avatar
Level 1
newUser2
Level 1

Likes

0 likes

Total Posts

1 post

Correct Reply

0 solutions
View profile

Avatar
Level 1
newUser2
Level 1

Likes

0 likes

Total Posts

1 post

Correct Reply

0 solutions
View profile
newUser2
Level 1

08-12-2020

Hi all,

There is an urgent requirement, but I am unable to find solution. Please help me in solving this issue.

I have recipients from different time zones. I have a custom attribute in recipient schema @recipientTimeZone (String) stores values like IST, EST, CST, MST etc.

 

Our Objective is to send an email delivery at 8AM in their respective time zone. So recipient-A who belongs to India will receive at 8AM IST, recipient-B belongs to CST will be receiving email at 8AM CST and so on.

 

How we can achieve this by using a single delivery in the workflow.

It will be great if I get an idea to achieve this by using a single delivery in the workflow, instead of using split and configuring different delivery for each time zone because we have 15+ time zones.

 

Thanks!

 

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Boost 250
MVP
DavidKangni
MVP

Likes

258 likes

Total Posts

372 posts

Correct Reply

152 solutions
Top badges earned
Boost 250
Validate 1
Give Back 5
Give Back 3
Give Back 25
View profile

Avatar
Boost 250
MVP
DavidKangni
MVP

Likes

258 likes

Total Posts

372 posts

Correct Reply

152 solutions
Top badges earned
Boost 250
Validate 1
Give Back 5
Give Back 3
Give Back 25
View profile
DavidKangni
MVP

08-12-2020

hi,

 

You can achieve this by playing with the time conversion.

Basically:

  • scheduler that will run several time (best to coincide with you time zone)
  • js activity where you will calculate (assuming your instance is EST if current hour = 10 then time= 10 and timezone=EST)
  • query using dynamic variables recipient timezone = $(vars/@timezone)
  • continuous delivery

Bonus: you can extend your delivery logs to save timezone for reporting perspective.

Thanks,

David 

Answers (2)

Answers (2)

Avatar

Avatar
Give Back 10
Employee
craigthonis
Employee

Likes

176 likes

Total Posts

273 posts

Correct Reply

158 solutions
Top badges earned
Give Back 10
Give Back 5
Give Back 3
Give Back
Boost 50
View profile

Avatar
Give Back 10
Employee
craigthonis
Employee

Likes

176 likes

Total Posts

273 posts

Correct Reply

158 solutions
Top badges earned
Give Back 10
Give Back 5
Give Back 3
Give Back
Boost 50
View profile
craigthonis
Employee

08-12-2020

Hello,

 

As far as I'm aware there isn't any way to proceed with the request as the delivery is configured to send based on a single timezone.  The delivery is then analyzed and prepared to be sent at the contact date defined.  Since we cannot define multiple contact dates/times for a single delivery there isn't any way to enforce specific sending per timezone.

 

Regards,

Craig

Avatar

Avatar
Boost 5
Employee
denisb91363072
Employee

Likes

8 likes

Total Posts

33 posts

Correct Reply

6 solutions
Top badges earned
Boost 5
Affirm 5
Boost 3
Boost 1
Affirm 3
View profile

Avatar
Boost 5
Employee
denisb91363072
Employee

Likes

8 likes

Total Posts

33 posts

Correct Reply

6 solutions
Top badges earned
Boost 5
Affirm 5
Boost 3
Boost 1
Affirm 3
View profile
denisb91363072
Employee

16-12-2020

Hi,


It is possible however the solution is quite complex to implement and engaging Adobe Consulting will be a well placed investment as it has been done for some of our customers and Adobe Consulting has developed a new workflow activity to answer this specific requirement. In a nutshell, the new workflow activity does the following

  1. Create one new subworkflow per timezone and append it to the current campaign. 
  2. Pick up records from the target relevant only to their timezone. 
  3. Set the contact date and Extraction date on the delivery taking into account the timezone of the sub-workflows

As said, it is all done in JS via a new workflow activity.

 

Thanks


Denis