We want to set a email limit for a campaign to 1 email sent per user every 4 days. We cannot use the auto-retry feature in Customer.io because it only supports a retry window of up to 48 hours.
We have decided to create our own re-try mechanism in the campaign using conditions.
How to interpret this? (screenshot above) Does this condition apply to "Email 1 - QT V1" in this specific instance of the campaign "Quick trip V1" or to ALL instances of the campaign "Quick trip V1"?
Best answer by Jordan
Hey
Does this condition apply to "Email 1 - QT V1" in this specific instance of the campaign "Quick trip V1" or to ALL instances of the campaign "Quick trip V1"?
It pertains to all “Email 1 - QT V1” emails sent, from the current journey or previous journeys.
The auto-retry feature you’re referring to, as part of our Message Limits feature, only applies to undeliverable messages that were not sent due to reaching the message limit for the day. Failed emails are, generally speaking — only occurring when Liquid variables are used without a value being declared. (https://customer.io/docs/journeys/message-failed)
You could consider using a Wait Until delay immediately after the message send, and the condition could be “… is delivered”, and another “max wait time” condition. (https://customer.io/docs/journeys/wait-until/)
NOTE: If you plan on handling retries on your own via campaign logic, you might not want to keep auto-retry enabled on your Message Limits.
Hey
Does this condition apply to "Email 1 - QT V1" in this specific instance of the campaign "Quick trip V1" or to ALL instances of the campaign "Quick trip V1"?
It pertains to all “Email 1 - QT V1” emails sent, from the current journey or previous journeys.
The auto-retry feature you’re referring to, as part of our Message Limits feature, only applies to undeliverable messages that were not sent due to reaching the message limit for the day. Failed emails are, generally speaking — only occurring when Liquid variables are used without a value being declared. (https://customer.io/docs/journeys/message-failed)
You could consider using a Wait Until delay immediately after the message send, and the condition could be “… is delivered”, and another “max wait time” condition. (https://customer.io/docs/journeys/wait-until/)
NOTE: If you plan on handling retries on your own via campaign logic, you might not want to keep auto-retry enabled on your Message Limits.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.