Cross-Device Cart Abandonment

Cross-device cart abandonment happens when a shopper builds a cart on one device and comes back on another, where the cart isn't there. The usual form starts with a laptop session and ends with a tap on a recovery email from a phone.

What does it look like for the shopper?

A shopper adds three things to a cart on their laptop and gets pulled away. A few hours later your abandoned cart flow sends on schedule. They open the email on their phone and tap the button. They find an empty cart or a single product page, and now they have to rebuild the order from memory on a small screen. Some will. Others close the tab.

Why does the cart stay behind?

A Shopify cart belongs to the browser that built it. The phone has its own browser and its own cookies, and nothing passes between the two devices on its own.

That makes this a separate problem from getting the email sent. A longer-lasting cookie helps a store recognize the same browser later, and it does nothing for a second device. Two things have to be true for the cart to come back elsewhere:

• Something identifies the person on the new device. Klaviyo's click identifier on a tracked email link can do this, and so can a store login.
• The cart was saved somewhere the new device can reach. That means a server, since the first browser isn't available.

Why do brands miss it?

Klaviyo's flow report counts the click whether the shopper found their cart or an empty page, so nothing in the report looks wrong. The trouble shows up only when you test the flow on a second device. Practitioners have discussed it for years: a 2022 Klaviyo community thread notes that Added to Cart emails don't link to a saved cart, and the accepted fix is a custom permalink that takes "a fair bit of custom coding".

What are the options?

Approach	What happens on the second device	Limit
Link to /cart	Shows that device's cart, often empty	Only useful on the same device
Link to a product page	Shows one product	The rest of the cart is gone
Persistent cart app	Casper and Firecart describe syncing carts	Described for logged-in customers
Cart recovery page	Restores the saved cart for a recognized clicker	Needs a held cart and a known clicker

One more option under /cart: a cart permalink can rebuild the items on another device. Most brands don't set one up, since it takes custom template work, and by default it sends the shopper straight to checkout with limited room to edit the cart.

How does reOtter handle it?

Your Klaviyo flow keeps running and the button points to reOtter's cart recovery page. When reOtter holds that shopper's cart and knows who clicked, the cart goes back into the real Shopify cart on the phone. Carts are held only with analytics consent, for 30 days, and carts that were already bought aren't put back. In any other case the shopper sees the page with whatever cart that device has.

Key takeaways

• A cookie never crosses devices, so longer cookie life can't solve this problem.
• Cross-device recovery needs a person-level identifier from an email click or login, plus a cart saved on a server.
• Flow reports count the click either way, so a test on a second device is the fastest way to see what your shoppers find.

See how reOtter restores the cart → Abandoned cart recovery