Q4-2024 Release

Features/UI

• If you build a segment using base segments (rather than profile properties), any inverse segment you create from it now works as expected and shows the correct number of profiles. With this fix, you can continue to use inverse segments to track lifecycle stages.

• When building a segment using a profile property with the Text data type, selecting the "has a value" operator now works as expected with all values properly displayed.

• When building a segment using a profile property with the Decimal data type, the graph now loads successfully once you set a range of values.

• When you manually refresh a timeline event rollup (from the right sidebar), a new event no longer gets added to the activity stream on the platform homepage.

• Profiles that share a unique identifier used for a merge rule will now merge, as expected, if they are within the same domain group.

• When defining completion criteria for a lifecycle, you can again access tooltips for the checkboxes "Select lifecycle completion event" and "Allow profiles to reenter the lifecycle."

• An issue was fixed on the Privacy page that disabled "Europe (GDPR)" from the list of legislation zones and prevented you from checking it.

• The Journey Recorder feature, which had limited customer adoption, was removed from the BlueConic Simulator to provide a simpler UI.

• The "Don't show on Segments tab" setting is now unchecked by default for three read-only, system-created profile properties so you can use those properties immediately to build segments:

  • Creation date

  • Last modified date

  • System has property

• To ensure consistent property values for both profiles and groups, you can no longer manually alter the value for the Creation date property or create additional values. If you currently have multiple dates for that property, you will only be able to export the first listed date moving forward.

• On the Profiles page, you can enter an extremely long value (i.e., more than 500 characters) in the "On unique identifier" search field without UI issues occurring.

• When creating a Send Email to Visitor Dialogue, apostrophes and quotation marks added to the email subject line now display as expected.

• When viewing an item from a table in BlueConic, such as a profile from the Profiles page, clicking the left or right arrow key on your keyboard opens the item that appears directly before or after it in that table.

• When sorting by Type on the Profile Properties page, properties with the Group ID type are now sorted correctly.

Connections

• Improvements were made to the way the SFTP Connection exports and downloads large files, resulting in better run times. Additionally, error reporting was enhanced to provide more details, enabling faster troubleshooting of configuration issues.

• Updates were made to the LinkedIn Connection that resolved access token expiration error messages from occurring.

• A fix was made to the Amazon Web Services (S3), Snowflake, and Braze connections that prevents unwanted authentication errors from being thrown.

• The Klaviyo Connection was updated to the latest API version, resolving incorrect export goal errors from being thrown.

• Cleanup now works successfully in the Adestra Connection when multiple goals are enabled or when a single goal has two or more lists selected.

• The Salesforce Marketing Cloud Connection no longer has version 2.24.0 incompatibility errors that were causing batch import goal matching issues.

• Optimizations were made to the Shopify Connection to handle large data imports more efficiently and avoid bulk operation timeouts. Additionally, the retry mechanism in the Shopify Connection was adjusted, resolving internal server errors. Both of these enhancements ensure smoother synchronization between both systems, even when substantial data volumes are involved.

• Error reporting was improved in the Snowflake Connection, now capturing and communicating IP-related authentication failures. Run logs accurately reflect IP blocking events, enhancing visibility and enabling faster troubleshooting of connection issues.

• An optimization was made to the Kafka Connection and its memory management, ensuring more efficient and stable connection runs, particularly for long-running or resource-intensive operations.

• An issue was resolved in the Webhook Connection where inverted section tags in Mustache templates weren't functioning correctly. This fix ensures proper conditional rendering based on property values, particularly benefiting scenarios involving identifier fields without a value set yet. Users can now reliably implement fallback logic in their request configurations, improving data handling flexibility and accuracy.

• A data collection issue in the Product Collector (SFTP) Connection was resolved that impacted Single Page Application (SPA) environments. Now, multiple product views are executed and logged correctly, ensuring accurate tracking of product view events for SPA environments.

• The Sailthru Connection can now handle empty values in matching criteria, preventing unintended merges caused by hashing empty strings. This refinement improves data integrity by only hashing non-empty values, resulting in more accurate profile matching and reduced risk of erroneous data management.

REST API

• A fix was made to segment refinements to ensure they always work as an implicit AND (instead of an implicit OR) over the base segment and thus return the correct results.

• Group refinements will return correct results with either uppercase or lowercase query values.

• When calling /profiles/{profileid}, a profile.segments expand option was added that, when used, returns both the segment name and ID. (If this option isn't used, only the ID is returned.) This update is now reflected in the Get one profile section of the REST API v2 documentation site.

• The Recommendations section of the REST API v2 documentation site was enhanced to include clearer specifications and examples of the filter options that are supported.

• compositionStrategy is no longer included in the Profile Properties section of the REST API v2 documentation site.

• The REST API v2 documentation site was updated to ensure that example API calls are formatted properly.

Python API

• In the Python API, "replaces" and "replacedBy" properties were added to the Profile domain object when requested as an include option (in a similar manner to Segments and Objectives). This allows you to analyze profile merges through AI Workbench without having to call the REST API directly.

• For domain objects in the Python API—specifically connections, dialogues, listeners, profile properties, segments, lifecycles, content stores, and timeline event types—the following properties are now available: 

  • Description

  • Creation date

  • Last modified date

  • Username of the creator

  • Username of the last modified user

  • Labels of the object

  • Status (only for domain objects that have a status toggle)