Solved

Abandoned checkout url link redirects to home page if not opened in the same window.


Userlevel 1
Badge +5

Hello,

The issue I'm facing is that the dynamic checkout URL in the received checkout email redirects to the homepage instead of the product checkout page when anyone triggers the abandoned checkout process in one Google window and receives the abandoned checkout email in a different Google window.

However, the same window redirects to the appropriate checkout product page if the abandon checkout is triggered and the received checkout email is opened in the same window.

Checkout url: {{ event.extra.checkout_url}}

This is my first time facing such an issue. Any help is appreciated.

Thank you!

icon

Best answer by eCom2Win_Agency 27 May 2024, 14:10

View original

2 replies

Userlevel 3
Badge +7

Hey, I understand your frustration.

The problem you're describing happens because the checkout URL is session-specific. When the abandoned checkout email is opened in a different browser window, it doesn't have the session data from the first window, so it redirects to the homepage instead.

Verify the Correct URL: Ensure that the checkout URL tag you are using in the email is correct. You can do this by previewing the email in Klaviyo and checking the dynamic data being pulled. This ensures that the correct link is used for each abandoned cart email. Here are some of the posts on the forum that have dealt with a similar issue:​ (Klaviyo Forum)​​ (Klaviyo Forum)​.

Custom Script or Persistent Links: This could involve creating a script that preserves the session data across different browser windows. One method is using Shopify’s Cart Permalinks, which allows you to construct a cart URL that remains valid across sessions. These might offer some additional insight as well:​ (Klaviyo Forum)​​ (Klaviyo Forum)​.


Hope this helps :)

Userlevel 1
Badge +5

Thank you @eCom2Win_Marketing for sharing the post on the custom scripts. I have found a custom cart link that I have modified according to the checkout trigger, and it worked.

Reply