Checkout recovery
Connect a non-Shopify checkout to recovery campaigns through your existing VYG pixel.
Use your existing VYG pixel to send recovery messages after checkout inactivity. You enable the feature, your developer connects checkout updates, and you choose the campaign delay and messages. VYG creates the event source automatically. No second tracking script, API key or custom webhook provider is needed.
Choose the setup for your store
| Your current setup | What to do |
|---|---|
| LiveRecover WooCommerce checkout plugin | Keep the plugin and your existing campaigns. It already captures checkout updates. Do not enable a second checkout feed. |
| Another working checkout integration | Keep your existing source and campaigns. This guide does not migrate them. |
| VYG pixel for visits and identity only | Follow the steps below. Existing tracking continues without changes if you leave checkout recovery off. |
| A custom website without the pixel | Install the pixel, then follow the steps below. |
1. Enable checkout recovery
Open Integrations → VYG Web Pixel in VYG and select Enable checkout recovery. Replace your
installed pixel tag with the updated snippet shown in the form. It adds data-checkout-capture="on"
to the same script and keeps your existing site key. Update the existing tag rather than installing it twice.
The setting alone does not capture a checkout. Your developer must connect the two events in the next step. Reading an email from a form or tracking a page visit does not supply cart contents or a recovery link.
2. Connect checkout updates and completion
Give this section to the developer who maintains your storefront. Connect your cart or checkout's existing callbacks or data layer to the following calls. Automatic platform detection is not included. If checkout runs inside a third-party frame, use that provider's supported callback or server integration.
When checkout details change
Send the complete current checkout after the shopper supplies contact details and whenever those details or the cart change. Replace these example values with your checkout's live values.
window.vyg = window.vyg || [];
window.vyg.push([
'checkout',
{
checkout_id: 'cart-123',
email: 'buyer@example.com',
phone: '+15555550123',
recovery_url: 'https://yourstore.com/checkout/cart-123',
currency: 'USD',
total: 49.99,
items: [{ product_id: 'sku-123', title: 'T-shirt', quantity: 1, price: 49.99 }],
},
]);These queued calls work before or after the pixel loads. Once loaded, window.vyg.checkout(snapshot)
is equivalent. Call from checkout updates rather than every keystroke; the pixel coalesces rapid changes
and ignores unchanged snapshots.
| Field | What to supply |
|---|---|
checkout_id | A stable ID from your cart system. Keep it across updates and completion; use a new ID for each separate checkout. |
email or phone | At least one contact identifier. Phone numbers use international format, such as +15555550123. Email addresses have a 100-character limit. |
recovery_url | An HTTPS link on the checkout page's own origin that restores this cart when opened from another device. Your storefront must support restoration. |
currency, total, items | Recommended for campaign filters and messages. Send amounts in major units, such as 49.99 dollars, and complete item lists. |
Each item needs a product_id and a positive integer quantity. variant_id, title, sku and
price are optional. Snapshots may contain at most 50 items and 16 KiB of JSON. Do not send payment
details. Respect your site's consent controls before sending contact information.
When the purchase completes
Call this from confirmed order success using the same checkout ID, including when success opens on a new page. Do not call it for a failed payment or merely for clicking the purchase button.
window.vyg = window.vyg || [];
window.vyg.push(['checkoutCompleted', { checkout_id: 'cart-123' }]);Completion stops recovery, including messages waiting in an existing campaign. It does not establish a paid order or billable conversion. Use a verified server order integration for purchase-based campaigns and revenue attribution.
3. Create the campaign
In Campaigns, choose Website events → Checkout abandoned, set an inactivity delay, and add your messages. A meaningful checkout change restarts the delay. Completion prevents further recovery.
Recovery only sends to an existing, unambiguously matched contact with an eligible subscribed channel. Sending a phone number or email through checkout does not create marketing consent or a subscription.
Disabling checkout recovery stops new enrollments and messages. Re-enabling it requires fresh checkout activity; it does not resume pending checkouts from before recovery was disabled. Keep your completion callback connected so purchases can cancel known checkouts.
Check the setup before enabling your campaign
Use a test store and a subscribed test contact you control. Leave the campaign paused while you connect the callbacks, then enable it for the controlled test.
- Change the test cart or contact details. In browser developer tools, confirm the pixel sends
checkoutUpdatedto/cdp/ingestwith your checkout ID. A successful request confirms delivery, not campaign eligibility. - Leave the checkout incomplete and confirm recovery follows the campaign's inactivity delay.
- Repeat with a new checkout ID, complete the order before the delay, and confirm no recovery sends. Also test completion while a campaign is waiting between messages.
- Open the recovery link on another device and confirm it restores the expected cart.
If recovery does not send, check that the integration is enabled, the installed tag has
data-checkout-capture="on", both callbacks run, the recovery URL is valid, and the test contact is
subscribed. An active WooCommerce or Shopify checkout source blocks a duplicate generic feed.
Existing installations
There is no automatic migration. Existing WooCommerce plugins, custom checkout providers and campaigns
continue through their current source. Existing pixel installations keep collecting visits and identity.
Only stores adopting this new recovery source need the setting, updated tag and checkout callbacks.
Events sent through vyg.track(...) are not automatically converted into checkout recovery events.