> For the complete documentation index, see [llms.txt](https://community.commandersact.com/customer-success/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.commandersact.com/customer-success/expand-your-uses/audience-and-activation/recover-abandoned-shopping-carts.md). # Recover Abandoned Shopping Carts ### 1. Business Value: Guarantee actionable and certified data Automating follow-ups via CDP allows you to recover revenue that would otherwise be lost, with surgical precision. * **ROI Optimisation:** Basket follow-ups are one of the most effective marketing levers, with conversion rates well above those of traditional acquisition campaigns. * **Converting intentions into sales:** By combining the reminder with an incentive offer (discount, free delivery), you remove the final barriers to purchase. * **Seamless omnichannel experience:** The CDP centralises information to avoid re-engaging a customer who may have ultimately made a purchase in-store or via another channel. ### 2. Implementation methodology #### Step A: Abandonment tracking (TMS) The DataCommander tag identifies when an item is added to the basket and, more importantly, when there is no order confirmation event after a defined period of time, and transmits the information to the CDP. * **Action**: Configure the sending of product properties (name, image, price) to the CDP as soon as the item is added to the basket. #### **Step B: Segmentation and delay (CDP)** The CDP creates a dynamic segment of ‘Active Abandoners’. It waits for a strategic period (e.g. 1 hour) to verify that the purchase has still not been made. * **Action**: Automatically exclude from the segment any profile whose ‘last transaction’ attribute has been updated. #### **Step C: Omnichannel activation (CDP connectors)** The CDP pushes the basket data to your emailing or marketing automation tool to trigger the follow-up message. * **Action**: Use dynamic variables (image of the forgotten product) to personalise the content of the message. #### **Step D: Analysis and revenue increase** Measure the volume of recovered baskets and the revenue generated specifically by these automatic flows. ### 3. Typical use cases 1. **E-commerce (Email):** A visitor forgets a handbag in their basket. Two hours later, they receive a personalised email: ‘Your basket is getting bored... take advantage of free delivery to finalise your order’. 2. **SaaS/Services (SMS):** A user stops at the point of payment for their subscription. A reminder SMS is sent to them the next day with a direct link to resume their subscription where they left off. 3. **Luxury (Web Push):** Display a discreet notification when the user returns to their browser if they have not confirmed their previous order. ### Need help making your data flows more reliable? Automating shopping cart reminders transforms your dormant data into immediate growth drivers. Our experts will help you configure your CDP flows and activation connectors. **Contact our support team:** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://community.commandersact.com/customer-success/expand-your-uses/audience-and-activation/recover-abandoned-shopping-carts.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.