Changelog

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.

The progress bar shown on Forms was overlapping when viewed on mobile devices. This issue has been ✨resolved ✨.

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

A new transform to more effectively support email sends, opens, clicks, and new ESP subscription types has been released. 

For more information about our Braze integration, you can read our Learn article here.

We’ve added 10 new standard attributes 🚀:

• Total Orders: Retail
• Total Orders: E-Commerce
• Total Orders Retail: Last 12 Months
• Total Orders E-Commerce: Last 12 Months
• Total Spend E-Commerce: Last 12 Months
• Total Spend Retail: Last 12 Months
• Average Discount Percent: Last 12 Months
• Order Channel Preference: Last 12 Months
• Average Order Value: Last 12 Months
• Average Spend Per Product: Last 12 Months

If you want to see all of the standard attributes we offer, click here.

The error messages for our CSV exports was a bit confusing. We’ve tidied these up and made them a bit more informative to help troubleshoot issues when downloading CSV’s. 

To learn more about our CSV export read our Learn article here.

Extended the standard email subscribe event schema to support the new ESP subscription statues transactional and undeliverable.

We've ✨ resolved ✨an issue where activations with double quotes (") in their names were not functioning correctly.

For more detailed information about Activate, click here.

✨ Resolved ✨ "Selected audience has no primary keys to use as linkage field" error in SFMC by disabling activations that no longer have associated lists. 

For more information about our Salesforce Marketing Cloud integration, click here.

DotDigital’s regression testing has been updated.

For more information about our DotDigital integration, click here.