Changelog

Want to delve deeper into your campaign audiences from Emarsys, now you can with a more granular ability to differentiate audiences sent from Emarsys. Emarsys A/B testing campaigns for example were being recombined when sent to the Hub. We have adjusted this so all audiences have distinct names that differentiate them from one another in the Hub. Read more about this update and how these A/B splits are presented in the Hub in our Emarsys Learn article.

DotDigital activations will no longer automatically generate a new data field based on the activation's audience tag name. This change was made due to DotDigital's new restriction on the number of fields allowed per account, which affects the number of activations from Lexer.

The Facebook CAPI integration now supports including an “order_id” in the events sent to Meta. This includes order IDs which help Meta to deduplicate events. Check out the Learn article here.

Our Emarsys integration now supports loading Campaigns that are sent but not yet opened or clicked into the Campaign Event Attributes.

We fixed a bug preventing you from seeing the filtered list of NPS responses.

Fixed processing of Attentive campaign names that appear under the “SMS Campaigns Sent” and “SMS Campaigns Clicked” attributes.

Editing queues just got a whole lot easier! You can now edit your queue directly from the Contact workflow instead of needing to navigate to Segment. This is a huge time saver when you’re still figuring out the brief and details of you’re workflow. Once edited, your contact workflow will automatically regenerate any existing messages using your updated brief/configuration.

We have upgraded Google's API version to version 14.

Fixed a bug with the integration of Facebook Ad accounts that prevented some users who had “non-owner” access to at least one other Ad account from connecting the accounts they did own.

Fixed several issues that were preventing the Attentive activation from working properly. The Attentive activation is now more robust and every SMS subscribed profile imported from Attentive should now have a mobile/phone attribute.

Clients will now receive less account disconnection emails from the Google Ads integration.

Contact reports have been launched! 🎉 Measure the impact of proactively engaging customers with Lexer’s AI Messaging tool. Understand your team’s activity (messages sent, active users) and the impact to revenue (conversion rate, sales generated, revenue per message sent).

Updated the Google Ads API version: We have added additional terms and condition into Google Ads activation and upgraded Google Ads to use version 15. If you have a Google Ads integration, you will need to accept Google's new terms within the Hub.

Serve now makes it easier to look up customers in your Point of Sale (PoS) system. You can now click the QR Code icon in the top left corner of the profile page to view a QR Code that is scannable by most Barcode scanners. Scanning this QR Code will enter the customer’s email address into your PoS system for easy lookup.

We added a new “Surveys Conducted” chart to the Serve Team Engagement report. This chart counts the number of form submissions completed by each Serve form configured in this hub. It helps managers and head office understand which surveys are being used by their retail staff and the number of profiles that have been updated with new information collected in these surveys.

Serve Conversion Report has been deployed! Serve Conversion reports will empower you to measure the effectiveness of your sales performance and understand how retail store teams are serving their customers using different benchmarks eg. conversion rate, total orders etc.

Serve reports now have the ability to filter by:

• Team
• Location

These filters persist across report pages. You can also now use the URL to share reports. Anonymous visits are included on reports by inferring the client from the customer or the store location.

Our LiveRamp integration now appends a timestamp to the exported file name to LiveRamp. This should result in quicker processing of these files by LiveRamp.

Total Vistors and Team Engagement Serve reports have been added to the Hub 🚀

Measure and understand how retail store teams engage with their customers using our clienteling product Serve. We have a serve article outlining how these reports work 👉 here.

Added a new feature to the SHA256 “transformer” in Activate that allows any attribute to be uppercased before being hashed. This allows Activate to better support custom hashing strategies for things like email addresses.

Updated the example data in the lexer-schemas repository to demonstrate how to use the required email_id field in the email marketing event schemas.

We've improved the loading speed when you first open Understand > Segment. We’ve optimised how we retrieve all of the segments in your hub so it’s lightning fast ⚡️.

We ✨fixed✨ an issue preventing email notifications from sending when integrations become disconnected.

We encountered an issue in how we check the connection status of Facebook pages, this has been ✨fixed✨. Our status check was looking for a permission that no longer exists, which caused a number of pages to incorrectly appear as disconnected.

We fixed an issue preventing users from responding to Forms in Twitter message conversations. This impacted messages consumed using the new V2 integration.

We fixed an issue causing duplicate groups to appear on users in your team.

We made a few improvements to how Lexi presents errors and tooltips.

A new subscription status for Klaviyo has been rolled out.

You can now activate a list that will Unsubscribe clients from your DotDigital address book making it way easier to keep your address book up to date.

There was an issues showing when navigating Datasets as it was loading. This has been ✨ resolved ✨.

We've released a new feature that lets you activate to DotDigital more accurately using "Address Books". You can now remove customers from your DotDigital address book via activation.

Two form improvements have been rolled out 🚀: 

1. We've added a new colour option in the Design settings to color question inputs 🎨 This has resolve an issue some clients were having where inputs were not visible if brand/background colours are the same.
2. Exporting form responses as a CSV didn't include information about files submitted with the form. This has been ✨fixed✨ File attachments received in form submissions are now shown in the CSV Export.

We increased the searchable date range from 90 to 95 days 🔍 This allows you to query conversations across an entire 3 month period!

Datasets introduces an interactive view for individual records payloads. This feature streamlines the process of delving into extensive or intricate events, helping you quickly locate the specific field you need.

We gave our clients beta access to Lexi Insights in Segment and Track. Reach out if your want to join the Beta program.

To make it easier for users to add custom CSS, we've added additional class names for each question that they can use to target specific questions. These class names will be applied to the top level card, elements inside can be targeted using CSS. Check out the Learn article to read more about it.

We have also way scale questions display when resized on mobile devices.

We fixed a presentation bug that made it appear as though radio inputs were not selected.

✨Fixed✨ the account reconnection process for the Mr Yum Connect tile. The tile was creating new accounts rather than updating the tokens for the existing accounts.

Enhanced the Logs user experience with a subtle update that now seamlessly refreshes the table when new logs arrive or an existing log changes state. A nice little UI improvement.

In the "csv_to_ndjson" example script within Lexer-Schemas, we've introduced enhanced support for CSV files that commence with UTF "BOM" characters. This improvement particularly benefits CSV files exported from applications like Excel.

Improvements have been made to the Listrak integration to allow much larger backloads of data via the back-end.

To make sure we are in line with DotDigital requirements, and avoid rate limiting, the number of calls made has been reduced.

The Bronto integration has been retired.

The [.code]country[.code] field on Customer records in datasets now also supports countries encoded in ISO 3166-1 alpha-3 (e.g. “AUS”, “NZL”, “USA”, “SGP” etc).

We've updated how currency symbols are displayed in Segment, Compare, Track.

We've released a brand new feature, ✨Logs✨. Data monitoring in the Hub just became even easier with Logs. It offers a quick overview of your data loading and processing log statuses. But Logs isn't just for monitoring; it's a valuable troubleshooting tool too, ensuring faster issue resolution with our Lexer team. Prepare to revolutionize your data management experience!

Added “brand” as a default field for Products in Smart Search.

Users can now send forms to customers containing hidden fields in the form URL 🚀

• Removes the need to ask for known information such as the email address.
• Learn more here

We’ve improved the search logic in the attribute picker to better match and display what you’re looking for!

• Attribute matching and sorting has been improved to better match your keywords
• We increased the number of Matched Attributes to improve discoverability

We ✨fixed✨ an issue causing the Attribute Comparison in Compare to have a too much space between components.

New buttons have been added to Datasets to allow you to clear and load data.

• Clear Data: Starts a job that will remove data from the dataset, the dataset itself wont be deleted. This may take up an hour and can't be undone.
• Load Data: Begins a job that will load new profile data to your dataset. This may take up an hour. Once you start you can't re-run it until finished.

Implemented an enormous speed improvement for our Shopify integration. We are now able to backload 5.5M orders in 5 days. This was accomplished by removing the dependency on the "transactions" stream that involved making an individual GET request for every single order in the "orders" stream.

Implemented a new Store Name attribute for Shopify because Shopify deprecated the previous attribute

Added a capability to the Emarsys integration to allow bulk imported contacts to be pulled into Lexer.

Users can now add File Upload questions to capture files (images, pdfs etc) in their forms. Customers can upload a product image, receipt, or other document as part of their forms submission. Users can download these files when viewing the form message in Listen or Respond. Files are not yet accessible in the Form Summary CSV export or as Attributes in Segment.

We’ve made a few improvements to our Form Builder!

• Date questions have been updated with new types of input validation based on before/after logic.
• All questions updated with more dynamic validation error messages to explain submission errors.
• Dropdown questions now support ‘other’ option to capture free form responses.

Compare results were being displayed as a profile count. To improve the readability of these stats, this was changed to percentage of the total profile count for the attribute. For example in the data shown above, 53% refers to the 3,648 profiles that are considered high value last year out of a total of 6,932 profiles with this attribute across all time periods.

✨ Fixed ✨ an issue preventing some attributes from appearing in the attribute picker.

Fixed an issue causing templates to insert without new line formatting.

Lexer's [.code]lexer-schemas[.code] Git repository was published 🎉. This repository describes Lexer's public data ingestion API's and will be a great resource for anyone wanting to upload their own data. This repository also contains example Python scripts explaining how to validate your data against the schemas and upload them using the bulk write API.

You can access these schemas in a few different formats:

• Human Readable webpage
• Markdown
• JSON schema
• Python Pydantic models

We have upgraded Facebook APIs across all Lexer products (Activate, Respond, Conversions API) to v16 as part of regular maintenance.

Improved the 12 month Spend Decile attribute so that it no longer includes profiles with a $0 spend in the last 12 months.

• These $0 spend profiles were highly skewing the distribution resulting in gaps in the 1-10 spend decile range.
• This has begun to be rolled out to clients.
• It will also automatically be applied for any new clients setup from the 27th July 2023 onwards.

We have backloaded all missing Yotpo data for all clients as a resolution to Yotpo’s API service disruption dated July 14.

Some WooCommerce data was missing for some clients. This issue has been ✨ resolved ✨ and all data retroactively updated.

We've fixed an error with Emarsys that appears when the data files we receive are empty.

We've upgraded the Facebook API we use for Conversions to version v16 as part of regular maintenance.

Segment queries are now much faster. Searches in the Segment builder should show summary results in a few seconds. This update has been deployed to all Hubs.

We updated the default display type for Spend, Orders, Counts, and Percentage attributes to show the average value instead of the percentile chart. The goal here is to make it easier to quickly analyse your search results.

We fixed an issue causing templates to insert into the rich text editor with incorrect formatting.

We fixed an issue causing the labels on some tabs (eg in Settings and Respond) to be pushed out of view, cutting off the text.

The LiveRamp activation has had a whopping 30% reduction in median activation time due to some clever improvements to the Elasticsearch. A huge win for any LiveRamp users!

Facebook has recently made updates to the Facebook Conversions API, introducing a new feature called "Facebook Datasets". As a result, Lexer has also updated their Conversions API activations to align with these changes.

Small bug fixes were carried out to improve the functionality of a few integrations:

• ✨ Resolved ✨Updated Mailchimp integration to enforce ISO8601 dates.
• ✨ Resolved ✨Updated references of “Offline Event Sets” to “Facebook Datasets” in the Hub to reflect changes to the Facebook Conversions API.
• ✨ Resolved ✨ Fixed an issue with Nosto(beta) activations that was sending all the profiles in a segment, all the time.
• ✨ Resolved ✨ We now more gracefully handle intermittent errors from the Nosto(beta) API, so it's more stable.

We’ve upgraded the Shopify integration to use API v2022-10 as part of regular maintenance.

As a part of the Facebook Conversions API changes, we now correctly raise an error if the Facebook Dataset ID is invalid.

An iterative approach to product design means more updates just the way you need them 😉

1. We’ve updated the Net Promoter Score (NPS) question type to display with a scale of 0-10 instead of 1-10. This follows the standard methodology for capturing NPS feedback.
2. We’ve updated the Scale question type to provide improved controls for the min and max values. You can now create a Scale question with a minimum value of 0-1 and a maximum value of 2-10.
3. We’ve updated the Image block to have additional context about the recommended image size and dimensions making exactly what is required clearer.

Small bug fixes were carried out on Forms:

• ✨ Resolved ✨ We've improved unification of email addresses submitted with uppercase characters.
• ✨ Resolved ✨ an issue where submission volumes were double counted causing inflated metrics.
• ✨ Resolved ✨ a styling issue with the required asterisk on Legal question blocks.

The Respond rich text editor was cutting off content. We've ✨ resolved ✨ this by making it resize as content is inserted, allowing user to view their entire response without needing to scroll.

Datasets provides customer-centric retailers with the tools to take control of the data powering their CDP. 

Datasets unlocks:

• More visibility and control
• Greater insights and analysis
• Faster validation and troubleshooting

Learn more about Datasets here!

Yotpo now has a brand new standard transform! Every Yotpo deployment will now have a dataset, standardized attribute names, and separate enrichments for loyalty and reviews.

Learn more about Yotpo here.

You can now get email event data sent from Attentive to your Lexer Hub. All you have to do is contact Attentive to let them know you would like your email events sent via your Lexer SFTP feed. 

Learn more about Attentive here.

Group hubs can now view their Brand Hub data and vice versa by viewing a shared group Hub, Elasticsearch index! This allows large clients, with diverse brand and region combinations, to have a more seamless experience moving between Hub and Brand data.

Authentication error messages related to the Google Ads integration are now clearer. 

Learn more about Google Ads here.

Mr Yum adjusted their API rate limit. To make sure there are no hiccups, we’ve made sure that our API aligns with their new standards.

Learn more about Mr Yum Connect here.

We’ve added rich text editing to form text blocks, question descriptions and thank you page text. The main value in rich text editing is the ability to add links to your website / ecommerce store to drive traffic and sales.

For more detailed information about Forms, take a look at our Learn article The Form Builder: Getting started guide.

The default character count on long/short questions was a bit too short so we’ve increased this to 2,000 characters. 

For more detailed information about Forms, take a look at our Learn article The Form Builder: Getting started guide.

A few fixes were implemented:

• ✨ Resolved ✨ an issue where users were unable to submit forms after encountering validation errors.
• ✨ Resolved ✨ an issue where users were unable to edit character count rules after publishing forms.

For more detailed information about Forms, take a look at our Learn article The Form Builder: Getting started guide.

We’ve made a few improvements to our Form Builder!

We have:

• Improved the general performance of loading forms with lots of questions.
• Improved the way we display the number of questions on a page.

‍

• Added a confirmation window when deleting a page - just to make sure!

For more detailed information about Forms, take a look at our Learn article The Form Builder: Getting started guide.

A few fixes were implemented:

• ✨ Resolved ✨ an issue that submitted a user’s form multiple times when they clicked Submit. 
• ✨ Resolved ✨ an issue with form favicon images not displaying at the top of your browser.

For more detailed information about Forms, take a look at our Learn article The Form Builder: Getting started guide.

Movio made some adjustments to their API that required a small update to the integration. 

Learn more about Movio here.

Some changes were made to the way we record scroll start and scroll finish times in Activate. Now we can more accurately capture the duration of time spent on all queries when loading data.

Learn more about Activate here.

The Summary page in Forms allows you to measure the submissions received from your customers at a glance! You can analyze the total volume of submissions, filter per quarter, and export submissions as a CSV to perform further analysis.

For more detailed information about Forms, take a look at our Learn article The Form Builder: Summary tab.

We made some improvements to image blocks on your forms that'll make your life easier. Now you won't need to rely on custom CSS to make your forms look fantastic. All you need to do is upload an image to the design tab in the Form Builder, and voila! Your forms will have the perfect images without any resizing issues. Enjoy better presentation of image blocks!

For more detail about the form builder, you can read our Learn article here.

✨ Resolved ✨ an issue where the "Responses" table, in the SLA tab, was unable to be downloaded. 

Learn more about Activity here.

Added a dataset recency alarm, for datasets that have not updated recently.

Small bug fixes were carried out to improve the functionality of a few integrations:

• ✨ Resolved ✨Braze had a small validation error that has been resolved. 
• ✨ Resolved ✨ Braze transforms were failing if they contained no data. 
• ✨ Resolved ✨ Marketplacer tile was raising an unexpected error message. 
• ✨ Resolved ✨ WooCommerce had an issue with memory impacting daily pulls.

Fixed an issue with some Emarsys missing some email engagement event data.

For more information about our Emarsys integration click here.

You can now get email event data sent from Braze to your Lexer Hub. All you have to do is contact Braze to let them know you would like your email events sent via your Lexer SFTP feed. 

For more information about Braze read our Learn article here.

3 Clients are currently trialing our new Nosto Integration. 

For more information about our Nosto integration, read our Learn article here.

The way segments query sources was taking a bit too long for larger searches. We’ve made this a bit more efficient, making searches even faster!

Learn more about Segment here.