Q1-2024 Release

Q1-2024 Release

A new Timeline Events filter was added to the Timeline Query Connection, allowing you to retrieve only configured properties, as opposed to all properties, when running queries against Timeline events. Queries can be run as frequently as every three minutes, and once configured properties are retrieved, they can be stored as profile properties.

Q1-2024 Release

When scheduling a Marketo Connection to run, you now have more frequent run options. While the default is once a day, you can now choose 8, 12, and 24 runs as a scheduling option on the Set up and run page.

Q1-2024 Release

In The Trade Desk Connection, you can now enable an optional step within your export goals to remove profiles from The Trade Desk audiences when the profiles are no longer part of the exported BlueConic segment. Previously within this connection, when BlueConic sent segments of profiles as audiences, the profiles would stay within The Trade Desk until the time to live expired (default 30 days).

Q1-2024 Release

Based on updated functionality and terminology in Google Analytics 4 (GA4), the old method of sending BlueConic data directly to Universal Analytics Dimensions is no longer applicable. Now, in the Google Analytics 4 Connection, BlueConic data is mapped and exported to custom event parameters. These event parameters can then be used within the Google Analytics 4 platform to create Dimensions, which are primarily used for reporting.

Note: In 2023, Google replaced Universal Analytics with GA4; as a result, the Universal Analytics Connection in BlueConic was deprecated.

Q1-2024 Release

jQuery version updated

To enhance platform security and improve performance, the BlueConic user interface was updated to the latest version of the jQuery library, 3.7.1. In addition, the jQuery Migrate plugin was updated to the latest version, 3.4.1.

Note: If you have developed custom plugins and referenced these platform versions, you will need to update your plugins to work with the most recent jQuery version.

X-CSP removed

The deprecated X-Content-Security-Policy (X-CSP) header, which was in place for older browsers and overlapped with the original Content Security Policy, is now completely removed from the platform. This aligns with industry security standards and reduces security risks associated with having multiple CSP headers. 

Referrer-Policy header implemented

To better ensure user and website privacy, "no-referrer" was implemented as the Referrer-Policy header in BlueConic.

D3.js upgraded in Segment Over Time insight

To reduce security risks, the Segment Over Time insight now uses the latest version of the D3.js library, 7.8.0.

Q1-2024 Release

To reduce time to value, enhance data accuracy and efficiency, and reduce operational cost, the Python API now allows you to filter groups—in a similar way to how you filter profiles. When you use these new filtering capabilities, the system will only process relevant groups that meet your specified criteria, ensuring optimal system performance (without compromising security or scalability).

For more information, review Filtering profiles and groups on the BlueConic Python API documentation site.

Q1-2024 Release

To preserve data integrity during the merge process, BlueConic introduced a new set of out-of-the-box profile properties that are read-only with non-editable merge rules. This ensures that users cannot modify specific property settings and that no unexpected profile changes occur when a merge strategy is applied.

There are currently five designated read-only properties:

• Creation date

• Last visited

• Domain group

• Last modified date

• System has property

If you have a property in your system defined with the same ID as one of these read-only properties, then your original property:

• Was updated to be read-only, too, and now uses the configured settings of that read-only property.

• Now uses the data type of the read-only property (in the unlikely event your data type was different).

• Is now marked as "Created by BlueConic" on its property page.

• Has the same property name and labels you previously assigned (which can be edited).

Property values stored in your profiles were not affected.

Note: These read-only properties are automatically generated by the platform, appearing in read-only state on the Profile Properties page (More... > Properties).

UI updates

All read-only properties are listed in gray in the table on the Profile Properties page, distinguishing them from other properties. They are all clickable and lead to the dedicated page for that property.

When you open one of these read-only property pages, "Created by BlueConic" appears in the metadata section at the top, indicating that it is system-created.

Almost all fields under "Settings" and "Expert settings" are grayed out and uneditable. You can, however, edit the name of the property at the top, as well as the fields in the metadata section: Favorite, Labels, and Description.

Note: The one setting you can configure is "Hide from UI" at the bottom; when this setting is enabled, the profile property can be used for creating segments from server-side plugins but not from the Segments page.

Merge strategy

Read-only properties do not follow normal merge strategies. The merge strategy for these properties, which you cannot edit or alter, involves a "leading profile" that the other profiles get merged into. When a profile merge is enacted involving any of these read-only properties, the system automatically determines which is the leading profile.

For the properties "Creation date," "Last visited date," and "Last modified date," the value of the leading profile is always kept. The properties "Domain group" and "System has property" do not need to be merged.

For full details on these read-only properties and how they are merged, review the article Managing read-only, system-created profile properties.

Sample ID

Sample ID is another system-created property, but this one is not read-only (i.e., you can still edit its "Settings" and "Expert settings"). It is not listed in gray on the Profile Properties page like the five read-only properties.

Sample ID is calculated whenever two profiles are merged. It is never saved to the database and never involved in the merging process; thus, the Merge strategy setting is hidden from its property page.

Q1-2024 Release

The Shopify Connection now supports importing timeline events and custom fields (i.e., metafields) on an hourly basis. Additionally, both types of import goals have been merged into one import goal to streamline the way data is imported from Shopify. If interested in adding these updates to your tenant, please contact your Customer Success Manager.. 

Please note: With this update, all existing Shopify connections will need to be re-authenticated in order to continue usage.

Q1-2024 Release

When sending a group type to Salesforce Marketing Cloud, users now have the option to only export groups that have changed since the last run. By only sending groups that have changed, customers reduce runtime and data operation costs.