We've updated the sidebar navigation to make key sections easier to find. Bundles module has moved under Acquire, and Gift Subscriptions module now sits under Subscriptions.
Learn more about Bundles & Gift Subscriptions
Loyalty point redemption in Loop's customer portal is now restricted to users with an active Okendo account, keeping you aligned with consent requirements under loyalty programme regulations.
Users with a pending account still earn and see their points but are shown a configurable activation message in place of the redeem action, prompting them to activate before they can apply points. This message appears in the customer portal and the cancellation flow, and you can customize the text directly from Loop Admin Portal under Tools & Apps > Okendo Integration > Texts > Account activation message
We’ve enhanced the performance of Subscription activity logs, Cancellation logs, Transaction summary, Subscription sales, and Subscriber distribution reports, making them significantly faster and smoother to use.
We now add a suffix to duplicate campaign internal names when you save a campaign with a name that already exists. The suffix starts with _1 and increments for each additional duplicate, making it easier to identify and manage campaigns at a glance.
This applies to all new campaigns going forward. Older campaigns sharing the same internal name will also be renamed with suffixes soon.
You can now view and sync all your Shopify collections — including Smart collections — right from a new Collections page under Products in Loop admin.
When product mappings in Smart collections update on Shopify but don't reflect across Loop touchpoints like upsells, swaps, and selling plans, you can trigger a sync directly from Loop to bring everything back in line.
Every webhook request from Loop now includes an X-Loop-Signature header, an HMAC-SHA256 signature generated using a secret unique to that webhook. You compute the same signature on your end and compare it to confirm the payload is genuinely from Loop.
Without verification, spoofed payloads could hit your endpoint and trigger unintended actions. Signature validation closes that gap and keeps your integration secure.
You can now add granular conditions to your Recover failed payments quick action, targeting customers based on subscription value, order history, total spend, payment failure codes, retry counts, and more.
This gives you precise control over who sees what during recovery, so you can tailor messaging and offers to the right customers and recover more revenue.
We’ve added a new key, $is_hard_declined, to the Payment failed event in Klaviyo. When a payment fails, and the subscription is paused or cancelled based on the brand’s hard decline behaviour settings in Payment recovery, the value of $is_hard_declined will be sent as true in the event payload.
You can use this to build targeted Klaviyo flows specifically for subscribers affected by hard declines, separate from your standard retry-based recovery messaging.
The subscription/updated webhook now includes a previous object alongside the current state, so you can see exactly what a subscription looked like before the change was applied.
This is especially useful if you run automations on subscription events but don't maintain your own database. You can now detect what changed and trigger the right downstream action without storing or comparing historical states yourself. The previous object is available for line actions (swaps, quantity updates, product add or remove), discount additions and removals, and billing or delivery policy updates.
Preset bundles purchased outside the Loop widget now automatically include child items at checkout, matching the behavior you already get through the Loop widget.
Whether it's a one-time purchase or a subscription, bundle composition is now reliable across all checkout entry points.