The Sugar Market 25.12.6 release includes the following changes and fixed issues:
Changes
Logo update: Our updated logo is now featured on the login screen and across the Sugar Market experience, reflecting our SugarAI brand refresh. Learn more about the SugarAI brand evolution in thisSugarClub post!
Form code improvements: An option has been added to manually update forms which provides greater speed when forms are loaded onto pages.
Email sizing assistance: A size guide and optimization setting has been added to the email builder to help keep emails within size limits and prevent Gmail from clipping messages.
Fixed Issues
When attempting to view an email template's source code, users received unexpected errors. This has been fixed and the source code of email templates can now be viewed without issue.
A discrepancy between report results and SQL queries occurred due to how the system grouped items. This has been fixed and report results and SQL queries now match as expected.
A duplicate header for HTTP Strict Transport Security (HSTS) settings caused unexpected errors. This has been fixed and no longer causes these errors.
Web activity was not correctly associated with a contact or lead after a web hit and form submission. This has been fixed and web activity is now associated as expected.
When building a report for sending emails, GEO tags containing apostrophes (e.g., Côte d'Ivoire) caused emails to fail to send. This has been fixed and campaigns now send as expected.
When a lead is converted to a contact in the CRM, the lead in Sugar Market only updated three fields: Converted, Status, and Contact_ID. This has been fixed and the lead is now fully updated when converted.
Sync alerts contained a generic error that did not explain the problem. The alert message has been improved and now errors have better descriptions.
Customers were unable to set records to "unsubscribe" via the API. This has been fixed and the API now works as expected.
Clicking social media merge tags in emails caused errors instead of navigating to social media profiles. This has been fixed and these merge tags now work as expected.
