Is there a way to have waves prioritize certain recipients? | Community
Skip to main content
kevind46959602
February 25, 2020
Solved

Is there a way to have waves prioritize certain recipients?

  • February 25, 2020
  • 1 reply
  • 3825 views

Hello,

I have a campaign workflow that is scheduled to send a delivery every weekday. I am utilizing waves within the delivery to throttle the number of sends per hour. At the end of the validity period, any remaining deliveries need to be carried over to the next weekday.

Is there a way to prioritize these carry-over deliveries during the next cycle of the workflow? I am trying to create a FIFO solution for deliveries that have waves and do NOT throw away deliveries that exceed the wave/daily capacities.

 

Thanks in advance,

- Kevin

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,

 

Waves are intended for IP warming, which they're not great at either- personalization is done at analysis and can get stale.

What you're describing sounds like ordinary continuous deliveries paired with broadlog check in the query, i.e. send to these recipients who are not in the broadlog schema for this delivery code.

 

Thanks,

-Jon

1 reply

Jonathon_wodnicki
Community Advisor
Jonathon_wodnickiCommunity AdvisorAccepted solution
Community Advisor
February 26, 2020

Hi,

 

Waves are intended for IP warming, which they're not great at either- personalization is done at analysis and can get stale.

What you're describing sounds like ordinary continuous deliveries paired with broadlog check in the query, i.e. send to these recipients who are not in the broadlog schema for this delivery code.

 

Thanks,

-Jon

kevind46959602
February 26, 2020

I tried using a capacity typology rule to throttle sends per hour, but was unsuccessful. That is why waves were being used. What would be the proper approach towards implementing a throttling solution?

Also I was able to get the query working as you described. But is there a way to set recipient priority in a continuous delivery?