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

Recurring delivery

mmbb110
Level 8
Level 8

Hi Community,

For recurring deliveries we use no aggregation and test proofs via profile substitution, however there are child deliveries that get generated automatically, can we stop these from generating?

Also if we remove the request confirmation of the parent delivery, will that also send out the child delivery available?

 

 

1 Accepted Solution
mmbb110
Correct answer by
Level 8
Level 8
@craigthonis, Correct, so when we create a recurring message and check proofs via profile substitution from the first child delivery available and then again for some obvious reasons have to rerun the workflow, it again generated a child delivery, so if we have done such thing five time we end up with 5 child deliveries. Anyways this can be stopped, it should be okay if it only created one regardless of the rerun.

View solution in original post

0 Replies
craigthonis
Employee
Employee

Hi,

 

Just to summarize my understanding of the request.  You want to use the recurring delivery and for each execution you want it to use the original parent delivery and not create any child deliveries for each send?

 

If so, I'm not sure that is doable in Campaign Standard.  I know in ACC we have the concept of a continuous delivery but this doesn't exist in ACS.

 

Regards,

Craig

mmbb110
Correct answer by
Level 8
Level 8
@craigthonis, Correct, so when we create a recurring message and check proofs via profile substitution from the first child delivery available and then again for some obvious reasons have to rerun the workflow, it again generated a child delivery, so if we have done such thing five time we end up with 5 child deliveries. Anyways this can be stopped, it should be okay if it only created one regardless of the rerun.

View solution in original post