See the latest features, improvements, and product updates.
A fully compliant, stable Google Drive integration
The previous Google Drive connection experienced authentication instability due to incomplete Google verification and a custom file picker that didn't meet Google's platform requirements. Users encountered "unsafe app" warnings and were blocked from setting up new connections. Google Drive Connection v2 resolves this entirely.
The new version is built on Google's official Picker API, aligning with Google's verification and security standards. Authentication is now stable, compliant, and sustainable — removing a friction point that directly impacted customer usability and BlueConic's integration credibility.
Benefits:
To learn more, read our documentation.
Improved performance and support for custom recommendation models in Open-Time Email Recommendations.
Open-Time Email Recommendations are now more reliable at scale — and more flexible by design.
We’ve introduced performance enhancements and fixes to improve stability during high-concurrency email opens. Screenshot rendering issues have been significantly reduced, helping ensure recommendations load consistently when engagement spikes.
At the same time, teams can now bring their own recommendation models into Open-Time Email Recommendations. Custom models appear alongside existing algorithms, giving marketers more control over how products and content are selected — without changing their workflow.
We’ve also expanded image and template settings, including support for transparent PNGs and more flexible configuration options. That means recommendation blocks can better match brand guidelines while remaining easy to manage directly inside the platform.
Together, these updates strengthen open-time personalization — improving reliability, expanding intelligence, and accelerating activation inside the Customer Growth Engine.
Benefits:
• Improves reliability during high-volume email opens
• Enables use of custom recommendation models for deeper personalization
• Expands image and template flexibility to match brand requirements
• Reduces manual configuration and troubleshooting effort
To learn more, read our documentation.
Q2-2025 Release
SDK version number: 6.0.4
Q2-2025 Release
SDK version number: 4.0.2
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.
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.
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.
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)
We resolved an issue in AI Workbench that caused notebook runs to fail due to insufficient memory. This fix also enhances the export feature from Release 92, allowing you to export up to 95 percent of your tenant profiles quickly and more efficiently (outlined in the article Enabling faster profile export functionality in BlueConic).
The BCReferrerOverrule cookie is no longer used by BlueConic after the recent removal of the Universe insight.
With this release, you are now permitted to add more than 1,000 objects to an objective.
With Timeline event types, entering an invalid date property value no longer results in an HTTP 500 error.
Dialogues only appear on specific pages as intended, even with an empty URL restriction.
Profiles with a "null" Timeline event value now load correctly on the Profile timeline tab.
We resolved an Android SDK issue to ensure that values are populated correctly in Behavior Listener rulesets.
We resolved an issue to ensure that your profiles merge correctly, with all properties displaying as expected.
Stopped batch-connection runs now correctly display as inactive, providing you with accurate status updates in the UI.
The Casing data processor now retains your selected casing method when applied to a connection.
Any selections you make to insert privacy consent into Dialogues (using the Privacy Management Components toolbar) now work as intended.
Improvements made to the Google Cloud Storage Connection prevent unexpected authentication errors.
In the Snowflake Connection, file linking now works as expected when the primary file is split; in addition, when Vault authentication is enabled, error messages now display correctly.
In the Interest Ranker 2.0 Listener, we fixed an issue that caused random characters to appear when adding a capturing method.
In the Klaviyo Connection, when an import goal has Timeline events configured and the matching property is empty, the import now runs with the next available row of data.
In the Webhook Connection, you can now create Timeline events seamlessly and avoid issues with event type names that contain special characters.
Mailchimp Connection imports now run successfully without any timestamp errors.
In the Facebook Advertising Connection, you can now take advantage of the push frequency "Only when the variables change" for real-time profile goals.
When looking at individual group pages, the "Profiles in group" tab now displays correctly.
With an update to the Salesforce Connection, there is no more mandatory mapping of all custom required fields in export goals.
In the Salesforce Marketing Cloud Connection, the Save button is now only activated when an unsaved change is made.
In the Braze Connection, you can now optionally import or export Timeline events error-free.
In the Reporting step of the Timeline Query Connection, the segment names now display correctly. Additionally, when previewing your query results, table names that start with a number are parsed without error.
Any errors in the ActiveCampaign Connection are now logged correctly in a downloadable log file.
The Behavior Listener now captures query string parameters correctly. For example, "washing+machine" would be captured as "washing machine," with the + sign parsed.
In profile export goals of the Salesforce Marketing Cloud (SOAP) Connection, data extensions can now be created.
The search profile endpoint now supports matching on multiple values of the same profile property. This update ensures that profile property values are added to an existing map entry without overwriting previous values.
Using the GET##{{ /segments}} endpoint now returns all expected data, including favorites and segment descriptions.
The date formats used in the OpenAPI specification (available at the top of the REST API documentation site) now work properly.
In the BlueConic Python API, we resolved an issue that caused errors when passing an array of filters to get_groups.
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.
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."
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.
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:
To remove a single value: | To remove multiple values: |
operation.add_rule( "email", blueconic.Strategy.REMOVE ) | operation.add_rule( "email", ["123@blueconic.com", "456@blueconic.com"], blueconic.Strategy.REMOVE ) |