Most of the times our customers report issues while sending smart triggers set on the server to server (S2S) events. Most common problems are Smart Trigger communication is received with some delay or didn't get delivered at all.
Why this happens ?
It happens because sometimes, during hours of high traffic, we receive millions of events which are to be processed in a queue. This leads to certain delay in processing and in turn delays or hampers the triggers' delivery.
We realize that some of these events are very time sensitive for you. Hence, to prioritize the processing of your salient S2S events, you can use an additional key "real_time_action": "true" in the API request which can be added while sending the events to us.
PFB the sample request:
"action": "Set MPIN Failure",
The presence of this key in your request tells our system that these events have to be processed on priority and hence moved to priority queue which has nearly zero processing delay.
If you are still facing any issues, please write us at; firstname.lastname@example.org