As soon as a user adds a product to their cart, an add to

[tapeya6238]

cart event (“add_to_cart” for example) is sent to Batch via the SDK integrated into the mobile app or website. This is part of the tagging plan set up by the client.

The add_to_cart event is enriched with information that will be important to know which item has been added: the name of the item, the link to the product sheet or even the image of the item, etc.

Controlled triggering of the Automation Trigger
All this information relating to the cart addition will allow to send a first event to Batch. This will allow to trigger an Automation Trigger which is an automated and personalized scenario in which the user enters as soon as he adds to the cart.

Batch's Data Platform has different elements accurate mobile phone number list that, combined, meet the technical requirements of this use case:

Timer: For example here 30 minutes, which starts from the add to cart event. The message is queued for this duration before being sent. If another add to cart event is received, the timer is reset.
Cancellation Events: If the user completes their purchase during this waiting time, a purchase event is sent by the Batch SDK (via the tagging plan), allowing the sending of the reminder message to be cancelled.
Capping: We have also implemented a system for limiting sendings (here 2 pushes per user), to reduce any excessive commercial pressure.
Then, regarding the delivery of the message, it is of course the Batch platform that is responsible for determining the devices to contact. We target the push tokens by calling on Apple or Google's push services, which will then deliver the message to the final device.

Feedback loops for continuous use case optimization
Batch has implemented a feedback system that tracks user interaction with notifications. This is essential for evaluating the effectiveness of the messages sent.

picture
Several return flows are maintained by Batch (represen