Highlights
â ď¸ Please note there are breaking changes in this release.
|
Please remember to perform a hard refresh in your browser after upgrading your environment.
Note: There is no Release 103
New Features and Improvements
Limio Analytics
Introducing Limio Analytics! Limio Analytics is a new area of focus with the goal of making it easy for our customers to understand how their experiences are performing - with no code required.
Keen to understand what your most popular offers are?
Want to evaluate how successful rescue campaigns might be?
Curious to learn the what the most enticing switch offers are from your customer base?
You can achieve all of this through Limio Analytics. Watch our intro video below:
You can also learn more on why we built this product in our blog: Why we launched an analytics product.
We are introducing 3 reports, all of which are considered to be in Beta currently. Please reach out if you have feedback on ways to improve these reports!
Limio Analytics: Orders Report (new and renew)
Our new Orders report displays order data for all new and renew order types in the last 30 days. This table is exportable so you can analyse the data with your preferred method. In the future, we plan to show key insights and metrics based on this report so you will not need to analyse the data external to Limio.
This report displays offer information as well as the source, plus any of the standard utm tags on the order.
This report can help answer questions like:
- What is the breakdown of new orders coming from customer service (Limio for Salesforce) versus online?
- What is the total value of new subscriptions over the last month?
- What is the most commonly purchased offer?
- Where do most of our customers come from before they reach our offers page?
Please note that if there are no utm or lmo tags on the order, it will appear as blank in the table.
Screenshot: Navigate to Analytics > Orders to see this new report. The table can be exported by clicking the cloud icon in the top right corner.
Limio Analytics: Cancels and Saves Report
Our new Cancels and Saves report displays order data for all cancellation order types in the last 30 days. This table is also exportable.
The report displays the offer being cancelled, as well as the offer being switched to if the customer proceeded with a rescue offer. It also shows the cancel reason if one was configured and selected in the cancel journey.
This report can help you answer questions like:
- What is the most common cancel reason?
- How many customer-initiated cancels resulted in save offer being accepted?
- What is the most successful save offer?
- What is the breakdown of saves online versus with customer service (Limio for Salesforce)?
- How much money did we retain via successful save offers?
Screenshot: Navigate to Analytics > Orders to see this report. The table can be exported by clicking the cloud icon in the top right corner.
Limio Analytics: Switch Orders Report
Our new Switch report displays order data for all switch order types in the last 30 days. This table is also exportable.
Similar to Cancels and Saves, this report displays both the original offer and the new offer being switched to. It also includes the price information, switch reason, and source.
This report can help you answer questions like:
- How much money did we make or lose from customers switching their subscription?
- What's the most popular switch subscription?
- What is the offer most customers switch away from?
Screenshot: Navigate to Analytics > Orders to see this report. The table can be exported by clicking the cloud icon in the top right corner.
Note: For both the Cancel and Saves report and the Switch Orders report, orders with source = salesforce will not show original offer information. We are currently working on closing this gap for future releases. Additionally, note that there is an additional object in the event payload that will be visible in the Events tab which was added to support the analytics implementation.
Allow customers to log in or signup from the checkout page
This feature allows users to sign up or register directly within the checkout page, via an iFrame. This streamlined process offers several benefits, including reduced friction and increased conversion.
This leverages the anonymous authentication functionality we introduced in Release 99.
Screenshot: Customers could login or sign up without leaving the checkout, which is proven to reduce checkout abandonment rates.
If you'd like to try this feature, following this guide: How to allow customers to log in or sign up on a checkout page (beta)
Improve Add to Cart event to better support adding multiple items to basket
We have improved the functionality of the add_to_cart event to better manage the addition of multiple items to the basket. From now on, when the add_to_cart event is triggered, it will only include information specific to the newly added item, rather than the full contents of the basket.
For example, if item X is already in your basket and you add item Y, the event triggered will now only capture the details of item Y. Previously, both item X and item Y would have been included, even though item Y was the only new addition. This change ensures more precise tracking, making it easier to understand what exactly occurred in each add_to_cart event, in line with analytics best practices.
This will be especially valuable as more of our customers leverage Add-Ons (introduced in Release 91) as part of their acquisition journeys.
Now, when an offer or add-on is added to your basket, the add_to_cart event will do the following:
- The
add_to_cartevent will only capture the offer and/or add-on information for the items that you just added to the cart- When you add an add-on and an offer at the same time, the add-on is included in the event
- When you add an add-on by itself, it triggers the event
- When you add multiple offers or add-ons at the same time, the total value reflects the sum of all items added, as the date will be logged in the same event.
Read more about the add_to_cart event here: How to Configure the Limio Data Layer to Collect User Events for Analytics
Improved data layer events to support add-ons
We have made the following changes to our data layer events to accommodate add-ons.
-
page_view: If an add-on is visible on the page, it will be logged in the page_view event. -
add_to_cart: If a customer adds an add-on to their basket, it will trigger this event. The total price logged will also include any add-ons. -
remove_from_cart: If a customer removes an add-on from their basket, it will trigger this event -
begin_checkout: If a customer has add-ons in their basket when they initiate a checkout, add-on information will be logged in the begin_checkout event. The total basket price logged will also include any add-ons. -
order: If a customer submits an order from the checkout with an add-on in that order, this event will now include add-on information as well as the total order price including the add-on. -
order_complete_view: The order value will include any add-ons when applicable.
Read more about how to collect our Limio data layer events here: How to Configure the Limio Data Layer to Collect User Events for Analytics
Pass tracking tags for all order types
We now persist tracking tags (utm, ltm, or lmo) for all order types. When a user hits a URL with any tracking tags, the order posted as a result includes the tags in the tracking object.
If the parameters are present in the order object and the custom field exists in Zuora, they are passed into the Zuora order as well (for all order types that have Zuora orders).
Read more about managing tags here: How to configure Limio Analytics for Tracking and Attribution
Pass LinkedIn and Pinterest click IDs
We made a change in Release 99 to add click ID as a parameter to be passed through domains. We now capture click ID from Linkedin (li_fat_id) and Pinterest (tid). The full list of sites that we now capture Click ID for includes Meta, Google, Reddit, TikTok, X, LinkedIn, and Pinterest.
Persist URL query parameters when a Limio page is being displayed in an iFrame
We have made an adjustment to ensure that all query parameters that are available from Limio pages also appear when the Limio page is wrapped in an iFrame. This will be valuable to all who want to pass the same information from their iFrames that they do from standard Limio pages.
Added email to the stored basket as soon as we have an email
The Modular Checkout now saves a customer-entered email to the basket object as soon as the customer clicks away from the Email Field input.
This is especially beneficial for customers currently using anonymous authentication (introduced in Release 99). Anonymous authentication does not require that the user logs in with an email, so before this enhancement there was no way to capture that email if the basket was abandoned - making it impossible to follow up with that customer later on.
By adding the email to the basket, it is now possible for you to use abandoned basket or purchase links for any user who has provided an email during the checkout, and does not require them to have authenticated with Limio first. This functionality works for checkouts which are not authenticated, anonymously authenticated, or classically authenticated.
| â ď¸ Note: This enhancement has a breaking change if you are using the Abandoned Basket API. |
If you are using the Abandoned Baskets API, the API now needs a bearer token rather than being API token authenticated.
Please review this documentation for details: Abandoned Basket API Docs
Simplified tax settings
We have simplified the way we handle tax configuration for tax-exclusive countries and removed the setting called "Display prices for tax exclusive countries with tax in the countries selected below". Users will only need to select which countries they want to exclude tax for in all components which display price.
Limio identifies a given end user's country by their billing address. If a subscription is bought and the price includes tax, it will show the price with tax inclusive across all these components by default unless the end userâs billing address is in a country listed in this setting.
If you want tax to always be included in your total prices for all countries, there should be no countries selected in this setting.
These components which display price are:
- Payments Table
- Switch Subscription
- Cancel Save Offer
- Order Change Success
- Orders Table
- Subscription Description
- Subscription Info
- Change Order Table
To see these settings in your Limio environment, navigate to:
Settings > General Settings > Localisation > Tax Behaviour (Tax-Exclusive Countries)
Screenshot: The simplified tax settings in the Limio General Settings.
To read more about tax behaviour in Limio, please read this article: How to configure tax behaviour for tax-exclusive countries
| â ď¸ Note: This enhancement has a breaking change if you were previously had "Display prices for tax exclusive countries with tax in the countries selected below" set to true. |
Any existing countries that were previously listed in this section in your environment will still be there, which means you will need to remove these countries from the list if you previously had the toggle above set to true. Please remember to save the setting and rebuild and republish your pages.
Added CRM ID to Sync API
We have added the CRM ID to the Sync API.
Now, when you use the Limio Subscription Sync API, Limio will automatically detect if the CRM ID is present on the Zuora Customer Account and add it as a Salesforce Identity on the Limio Subscription and its parent Limio Customer.
This allows you to use Limio for Salesforce more easily for subscriptions that are not Limio initiated or for subscriptions where a Salesforce Identity has been changed or is missing.
Read more about the Sync API here: Sync Zuora Subscription
Limio session length now configurable by users
Historically, the session length for any authenticated page in Limio was fixed to 1 hour, which led to issues when a user spent longer than an hour in an authenticated page (such as the checkout) and then proceeded with their order.
To address this, we have now surfaced session length as a configurable setting in the Authentication Providers settings. This allows Limio Commerce users to define how long (in hours) they want the session to last.
This is supported for Basic Auth, JWT Service, OpenID Connect, SAML, and Zephr Session.
Screenshot: Navigate to Settings > Authentication Providers and open a configured authentication provider to see this option.
Configure authentication per page
Previously in Limio, users could only configure 1 authentication provider per domain. Users configure these in Settings > Authentication Providers.
In order to allow our customers to A/B test different types of authentication methods and to meet the needs of different types of authentication pages (eg self service vs checkout), we now allow for authentication to be set per page, as well as per domain. For example, say you want to use anonymous authentication (introduced in Release 99) for a fast checkout experience, but classic authentication for access to the self-service views, this is now possible with this change.
To do this, go to any page that you want to apply authentication to, and when you toggle âRequire Authentication?â to on, you will be able to select any of the authentication providers you have set up in the settings.
The content of this dropdown will be determined by whatever is configured in Settings > Authentication Providers. In the above example, the following auth providers have been configured:
The âDefaultâ value in the dropdown is whatever Authentication Provider is configured on the domain level in Settings > Authentication Providers.
Please note you must have routing v2 enabled to use this feature.
Read more about this new feature here: Authentication provider per page
More control when bulk editing multipicklist attributes
When users select an attribute to bulk edit that could have multiple values (eg multipicklist type), they now have the following options: ââ
-
- Replace: replace existing value with new values
- Add: keeps existing value but adds new values
- Clear: replaces existing value with empty
- Remove: removes the specified values
This is especially useful for handling offer labels or allowed countries, as there are generally many values selected and you likely do not want to overwrite all of them.
Screenshot: In this example, the user bulk editing an offer would be replacing any existing values in the campaign label attribute with "gift". If they instead wanted to add a new label to their offers, they would change the Change Type to "Add".
See the below video for a demo of this new functionality!
More attributes available in bulk edit
There are now more attributes available to edit in our bulk edit feature:
- Offers: Product, rate plan, split
- Pages: Require authentication, attached offers label, attached add-ons label
- Add-ons: Product, rate plan, split
You can also now bulk update which template is being used on offers, pages, add-ons, and products.
Screenshot: There is a new option in bulk edit to edit the template being used in your selected offers, pages, add-ons, or products.
Page history will only include saves when there has been a change to the page
Users are able to see the history of page changes in Limio Commerce, including what was changed, who changed it, and when the change happened. We have made the change editor more focussed to only log entries when an actual change has been made to the page. Previously, a change would be logged to the history whenever the page was saved.
Screenshot: Find the Changes Editor by navigating to your page, clicking the orange down button in the upper right corner, and clicking History.
Accessibility enhancements
We have made some small accessibility enhancements to the app:
- FAQ Banner: When using the âtabâ key to navigate the page via the keyboard, the images which control opening the accordion now outlines when selected - which is the same as other links/buttons on the page.Form
- Form: The Windows Narrator can now interpret the tooltip and convey the content to its user.
Removed pending change banner from Payments Table
Its common for Limio Commerce users to configure the Payments Table component alongside the Orders Table component in self-service pages. Currently, both of these components independently check if there is a pending change on the subscription and both separately show a banner accordingly.
We have now removed the pending change banner from the Payments Table component, and it will now only apply to the Orders Table component.
Screenshot: The pending change banner will only appear with the Orders Table component.
Read more about the Payments Table here: Component: Payments-Table
Read more about the Orders Table here: Component: Orders-Table
New prop for validation on customer name field in Customer Table component
We have made a small adjustment to the Customer Table component to allow Limio Commerce users to define regex validation for the customer name field.
Screenshot: The new prop is called "Name validation regular expression".
Read more about the Customer Table component here: Component: Customer Table
"Limio Field Name" now displaying correctly in Subcomponent Manager
In the Subcomponent Manager, all Field subcomponents previously displayed the same field name, making it difficult to distinguish between different Field subcomponents. The label now reflects the specific Limio field name, making it much easier to differentiate between fields.
Before:
After:
Coming soon: Journey stability improvements
We are currently working on a series of enhancements to Limio journeys which aim to improve the stability and reliability of journey configuration. In order for Limio developers to test the new Journey features, we have added a toggle to the Beta settings.
This feature is not yet available to customers, so please ensure the toggle is set to off! We will inform everyone when the new Journey functionality is available, with details of the improvements made.
Screenshot: Please ensure you do not set this toggle to on, it can be found in Settings > Beta.
Bug Fixes
Resolved indexer failures on Add-ons
A syncing error was identified with Add-ons, which was resolved by adding a missing record_type.
Column configuration is no longer saved on cancel
When amending tables in Pages, Offers, Add-ons, and Products, the Cancel and Confirm buttons previously performed the same action. This has now been corrected.
- Cancel will discard the changes made
- Confirm will save the changes
Fixed visual bug when managing columns in column selector
A bug in the column configuration pop-up in the Offers, Pages, Products, and Add-ons tables caused a large gap between added and removed columns. This issue has been fixed.
Fixed issue with removing filter when attribute is string
When applying a filter in the Offers, Pages, Products, or Add-ons search, clicking the 'x' to remove input text did not clear the text or the search. This issue has now been resolved.
Injected hreflang Link HTML tags werenât added to built pages (#109655)
Previously, when hreflang tags were added via a Global Inject script, they did not appear on published pages. This issue has now been fixed, ensuring that hreflang tags defined in the Global Inject script are correctly included on published pages and can be utilised for SEO purposes.
For example, "en-us" indicates a page intended for English-speaking users in the US, this ensures search engines display the correct version of the page to users based on their location.
Some users could not edit their delivery address (#109824)
Previously, if a saved delivery address was missing a Limio required field (potentially due to a migration error), the user was unable to edit the address later. We have refactored the validation function to resolve this issue.
The expected behaviour will be seen in the following components:
- Edit Address
- Orders Table
- Payments Table
- Switch Subscription
Fixed issue with builds marking pages as publishable (#110161)
An issue was identified where, in certain cases, pages were incorrectly shown as ready to publish, even when the build process had failed. To address this, weâve made the following updates:
- Status Accuracy: Pages will now be marked as âbuiltâ rather than âsucceededâ after the initial build phase, ensuring only fully successful builds are marked as ready to publish
- Error Detection: The build process will immediately stop if any errors occur, preventing incorrect status updates
- Final Verification: A new post-deployment check ensures that only fully built and deployed pages are marked as âsucceededâ
Filtering and inline edit improvements
- Fixed the UI of the Discount attribute, which was previously shown as a field split across two lines making it difficult to use
- Removed the âxâ from attributes of the Picklist type that could only have one option
- Added logic to automatically close the Date modal after selection
- Ensured that the Any/All filter options are only available in attributes that allow for more than one value to be selected
Custom fonts werenât rendered in Page Builder v2
We resolved an issue where custom fonts were only visible in published pages. The Page Builder now accurately mirrors the fonts displayed in the published page.
Page incorrectly adopted component styling when page name matched Limio component (#110127, #110134)
If the page name matched a component name, it caused unintended styling issues where component styles applied to the entire page. By appending â-pageâ to the page name class, we have avoided conflicting class names.
Fixed issues with Offer table exports
The Offer table export was failing due to the absence of a region in the upload function, which has now been addressed. Additionally, an issue where clicking export redirected the page to âThis site canât be reachedâ and the export would fail to download has also been fixed.
Comments
0 comments
Please sign in to leave a comment.