Q2-2024

Platform/UI

• In an advanced search, two filters in the left panel had the same label, “Status.” To avoid confusion, the second “Status” filter was relabeled “BlueConic hostname status.”

• An issue was fixed for profile properties marked as unique identifiers with the "Create new profile when identifier changes" option enabled. As expected, the visitor’s current profile will now switch to a new profile once the new identifier is set and will no longer require a refresh or navigation to another page.

• On individual channel pages, a formatting issue was fixed in the “Used by” dialogue box for a position when it lists several variants with very long names.

• On the BlueConic Support access tab (through BlueConic settings > Access management), system@blueconic.com will no longer display as a named account.

• For a Timeline event type, an “invalid” message will now properly display when you attempt to re-add and save a property as non-PII that had previously been saved as PII.

• An issue was fixed in which certain insights were unintentionally excluded from emailed dashboards.

• An issue was fixed that prevented a valid 13-digit Brazilian mobile phone number from passing validation.

• An issue was fixed with extended segments in which the facet count in the CSV export did not match the count displayed in the UI.

• On individual plugin pages, under "Plugin details," the URL field will now be hidden if there is a Version index URL listed. This ensures that you use the correct URL when registering a plugin from one tenant to another; registering the URL instead of the Version index URL would result in a specific version of the plugin being installed that is not automatically updated.

• Enhancements were made to URL mapping to better support the specific tracking of platform core features. In particular, when you open an object in BlueConic, the object's platform name now appears in the URL as a URL parameter.

• In the “Profiles and Groups” section of the platform, an issue was fixed that caused display issues if the name of a profile property included “< >” tags.

• An issue was fixed that was preventing profiles from completing a Lifecycle when the 'Select lifecycle completion event' option was set.

Plugins

• When using the mapping functionality in connections, it is no longer possible for a group property to be created with an identifier that already exists for a profile property.

• An issue was fixed in which plugin updates were not being reflected on the Plugins page or in the plugins gallery.

• File validation measures were added when authenticating a connection with Vault to display an error if formatting is incorrect.

• An issue was fixed in the Interest Ranker 2.0 Listener where the wrong font was being uploaded resulting in random characters appearing in the UI.

• In the Webhook Connection, issues were fixed that caused event type creation and mapping issues if they included non-text fields, date formats, or “< >” tags.

• An issue was fixed in the SFTP Connection that caused group import goals to disappear when the connection was upgraded to the latest version (2.17.0).

• The Casing data processor was restored to return the correct output after a bug was detected in the latest update that cleared the settings.

• The Privacy Management Components toolbar can now be configured to select objectives, change template settings, and assign visitors to be asked for consent.

• In the Klaviyo Connection, an issue was fixed that caused Timeline event imports to stop and throw an error when the matching profile property was empty.

• An issue was fixed in the Salesforce Marketing Cloud Connection that caused the Save button to be activated while creating an import goal.

• An issue was fixed in the Snowflake Connection that kept large primary data tables from file linking properly.

• Updates were made to the Braze Connection that fixed issues from occurring in the run history table and data mapping.

• The Timeline Query Connection reporting graph now displays the selected visitor segment within the connection goal rather than defaulting to the “All visitors” segment.

• The ActiveCampaign Connection was updated to support downloadable error log files.

• An update was made to BlueConic Recommendations to be compatible with the most updated version of Mustache (4.0.0).

• An update was made to the Behavior Listener so that it is able to capture URL string parameters that include the “+” character correctly.

• An issue was fixed with the Google Cloud Storage Connection that caused intermittent "BlueConic cannot connect" error messages to display.

• An issue was fixed in the Mailchimp Connection that caused imports to fail with the error message "Dates must be in valid ISO 8601 time format."

REST API

• In the REST API, an issue was fixed when you requested to remove a value from a profile property; if the property was empty, the value to be removed would be erroneously added to that property.

• An issue was fixed that caused an internal server error when an unindexed property was retrieved via the REST API.

• In the REST API, any incorrectly formatted Timeline request will now return an error code so you know the request needs to be revised.

• On the REST API documentation site, under Create interactive event, the documentation was updated to show that PAGEVIEW should not be an allowed “enum” type.

Python API

• When using get_lifecycles in the Python API, an issue was fixed that would only return the first 20 lifecycles.

• If you have a profile property that stores multiple values in the Python API, you can now remove one or more of those values. For instance: