Deprecations

Salesforce Field Deprecations

We will be phasing out our export jobs to Lead/Contact objects to simplify our integration and eliminate the need to export to Salesforce standard objects. The denormalized fields listed below will also be deprecated, as customers can obtain the same data from their Touchpoint objects. The timeline of deprecation is June 2024.

bizible2__Ad_Campaign_Name_FT__c
bizible2__Ad_Campaign_Name_LC__c
bizible2__Landing_Page_FT__c
bizible2__Landing_Page_LC__c
bizible2__Touchpoint_Date_FT__c
bizible2__Touchpoint_Date_LC__c
bizible2__Touchpoint_Source_FT__c
bizible2__Touchpoint_Source_LC__c
bizible2__Marketing_Channel_FT__c
bizible2__Marketing_Channel_LC__c

The fields which contain the same information on the Touchpoint and Attribution Touchpoint objects are:

  • bizible2__Ad_Campaign_Name__c
  • bizible2__Landing_Page__c
  • bizible2__Marketing_Channel__c
  • bizible2__Touchpoint_Date__c
  • bizible2__Touchpoint_Source__c

Required Actions

  • Create new Report Types for Leads and Contacts with or without Touchpoints.

  • Create reports which capture the functionality of any existing report which utilizes the removed fields. As part of this process you will want to change the fields in the report as specified below:

  • Remove Lead/Contact FT/LC fields:

  • Add Touchpoint fields:

  • The Touchpoint Position filter and any filters that use the FT/LC fields, including the Date Field, should be updated as follows:

  • Delete any pre-existing reports that utilized the removed fields from the Lead/Contact object to no longer reference those fields.
  • To stay connected to Dynamics, install our latest package version, v6.12. Old versions (<v6.12) will no longer be supported. This update optimizes historical record creation to reduce storage usage.

  • The outdated method of OAuth with a RefreshToken will be deprecated. Refer to this guide for updating your credentials to adhere to Microsoft’s best practices of using ClientSecret.

“custom_properties” Field

In our data warehouse, the “custom_properties” field has been serving as a storage for additional data points not covered by our fixed schema. Stored in JSON format, this field’s usage is limited and its integration with SQL queries can be complicated, affecting performance. Given these factors, we’ve decided to deprecate this field. This change will mainly affect the data processing layer within our Azure table storage and the data exported to our data warehouse.

What’s coming?

In-app Custom Reporting

Marketo Measure customers, for the first time, will be able to create and save their own reports right in the app. This will follow the release of the pre-built dashboards in early 2024.

Q2 Release

  • Salesforce Package Consolidation

We’re merging all Salesforce packages into a single, comprehensive package for an improved user experience and simplified usage. The V1, V2_EXT, and Reporting packages will be retired next quarter. The new package combines all previous features, allowing for more efficient tracking and deeper customer insights.

Customers who already have the V2 package installed must update it to the new consolidated version.

We’ve added two new fields to enhance your reporting capabilities:

  • form_name: Now available in BT/BAT objects, this field enables users to create reports based on form names.
  • user_touchpoint_id: This field enables users to create reports with unique user touchpoint counts.

This article includes guides on recreating reports and dashboards from the legacy Reporting packages.

  • Salesforce API Version Updates

All Salesforce API versions of Apex classes, including the UserActivityContext class, are updated to supported versions. (31.0 through 57.0)

  • New Package Installation

The new consolidated package installation link can be found here

What’s coming?

Changes in IP Address Storage

We will no longer store IP addresses in our system per privacy considerations. We will continue identifying and storing the geo-location of the IP address, but the format will change (e.g., “United States” to “US”).

Marketo Measure


Marketo Migration to the Adobe Admin Console - (Pre-Migration)

Experience Cloud Tech Sessions

Tuesday, Mar 4, 6:00 PM UTC

Join Adobe's Customer Experience and Identity Team to prepare for a smooth Marketo migration to the Adobe Admin Console. Learn key steps, best practices, and how to avoid roadblocks for a seamless transition.

Register

Marketo Migration to the Adobe Admin Console - (Post-Migration)

Experience Cloud Tech Sessions

Tuesday, Mar 11, 4:00 PM UTC

Migrated Marketo to the Adobe Admin Console? Join our webinar to master key features, best practices, and troubleshooting tips. Learn how to manage users,, settings, and more. register now!

Register