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

Pressure rules on rtEvents

gunjans6748888
Level 3
Level 3

Hi All,

We are trying to limit 5 messages per day for a customer. The data will flow from PushEvent API.

How can we do that.

1 Accepted Solution
Vapsy
Correct answer by
Employee
Employee

Hi Gunjan,

Since you said PushEvent API I can infer that you are using Campaign Classic.

This appears to be an invalid use case.

MC is designed to be used for transactional messages i.e. password reset email, temp password email, sales invoice etc.

They are triggered as part of an event.

If your requirement is to limit it to 5 emails per customers, these are too many emails and work against the transactional structure itself. I'd suggest you to rethink it.

Additionally, MC works on event data and is not linked to profile database. So, transactional emails have no way to determine if the current ctx data belongs to a customer who has already received an email.

Additionally pressure rules can only be applied to a delivery which has a contact date set and enters Target ready state. Both are not true in case of a transactional email.

Based on above comments, the answer to your question is that it is not possible and in an ideal scenario there should be no reason to apply a limit on transactional emails.

Regards,
Vipul

View solution in original post

0 Replies
Vapsy
Correct answer by
Employee
Employee

Hi Gunjan,

Since you said PushEvent API I can infer that you are using Campaign Classic.

This appears to be an invalid use case.

MC is designed to be used for transactional messages i.e. password reset email, temp password email, sales invoice etc.

They are triggered as part of an event.

If your requirement is to limit it to 5 emails per customers, these are too many emails and work against the transactional structure itself. I'd suggest you to rethink it.

Additionally, MC works on event data and is not linked to profile database. So, transactional emails have no way to determine if the current ctx data belongs to a customer who has already received an email.

Additionally pressure rules can only be applied to a delivery which has a contact date set and enters Target ready state. Both are not true in case of a transactional email.

Based on above comments, the answer to your question is that it is not possible and in an ideal scenario there should be no reason to apply a limit on transactional emails.

Regards,
Vipul

View solution in original post

gunjans6748888
Level 3
Level 3

Hi Vipul. One more question.

How can we read deliveries using query and apply pressure rule in a workflow?