Those who are new onto Salesforce always have the confusion as to how to use it effectively and what best they can do with it. With solid support, it is easy for the users to speak to the account managers about the process of installation of Marketing Cloud Connect or the process of upgrading the existing Salesforce to the v2 in order to benefit more from its additional features and compatibility. It is easy to upgrade to the Marketing Cloud Connect based on the below processes.
- You can easily download the managed package releases and install them for the Service and Sales cloud org.
- The users can also make use of the Marketing Cloud releases, which comes packed with many new features and can apply it automatically to the Marketing Cloud account.
Let’s explore the latest releases of the Marketing Cloud and the features.
Managed Package Releases
- Version 219
Version 219 of the managed packages includes a brand-new approach that will help reduce data inflation by cleansing the tracking table for open email rates. The package can also help to fix the bugs which trigger email notifications incorrectly to the customers.
- Version 216.2
Another release just before 219 as 216.2 will help to fix the authentication of broken business units by availing the healthy tokens within an account. Before this, you were supposed to do the re-authentication of the users of the Marketing Cloud Connect API when someone fails to connect with the cloud.
- Version 216.1
This is the managed package version which was released to fix a bug which incorrectly triggers the email notification to the customers with content as their integration is broken.
- Version 215
This version release was to review the latest features for Marketing Cloud Connect back in the release of October 2018. This version for the managed Marketing Cloud Connect package consists of some minor fixes for the bugs and further enhancements. This managed package is made available after the October 2018 release.
Auto-Upgrade Packages
At the beginning of 2019, Salesforce automatically updated the managed package of Marketing Cloud Connect in the org further to each release, and the providers like Flosum.com started offering the same. Doing such upgrading to the latest released version of Marketing Cloud Connect could further ensure that the users get an optimally secured connection with the latest features and bug fixes for the Marketing Cloud. Doing so will also give the users a complete cycle for further testing the new packages before updating the production org.
- New Enhancements and add-on Features of Managed Package Release Version 214
- Cloud Connect Package auto-upgrade
Back in the 2018 summer, the managed packages of all existing Marketing Cloud Connect packages were upgraded automatically to version 214. This was an upgrade that further ensured authentication of the Marketing Cloud with OAuth, which is a much more secured and reliable mode of managing the system access across all the clouds.
- Salesforce Data Extension A/B Testing
After Version 214, the Marketing Cloud Connect could now support effective A/B Testing while sending within the Marketing Cloud to the data extensions in Salesforce. The users can also choose the Content Builder mails and send them to data extensions of Salesforce while using the A/B Testing. Adding to it, you can also see that the Subscriber engagement data has come back to the Service and Sales Cloud.
- Update of WSDL/API Version
This update of the WSDL/API version is used in communicating the objects and features between different clouds. The updated version helps in enabling the Synchronized Data Sources to stream replicable and newer objects to the Marketing Cloud further.
- Version 213
The major upgrade noted in Version 213 of Salesforce’s managed packaged releases was that the providers redesigned the Lightning UI Tracking Data Cleanup Tool. This is a very useful tool that helps to remove any unnecessary tracking data from the expired tracking Marketing Cloud within the CRM. Users can easily upgrade the Marketing Cloud Connect to Version 213 to gain the benefits of cleanup of tracking data and other features as:
- Better managing the tracking data to optimize data storage utilization.
- Removing the individual level stats and better maintain send-level statistics.
- Choose the apt level of data to be deleted.
- Enter the email addresses for the cleanup and confirmation messages.
- Version 212.1 & 212
The major catch of this release was an updated service for the email thumbnails. Version 212 was released in January 2018, which includes the fixes for using the Salesforce Data Extensions as the audiences in the Guided mail Sends. With this, the subscribers recognize it as originating from the Service or Sales Clouds. Such recognition further pushes the tracking data to the Clouds along with supporting the Salesforce Profile Center. The tracking data then gets stored in a folder with the send time.
- Version 210.1.1
This is another such release that is aimed at bug fixing to makes sure that the OAuth API user tokens get saved using the custom domains. If you are aiming to upgrade to this version and have some invalid tokens, just follow the steps below.
- Just log in to the marketing cloud.
- Just go to the Developer Consuls in the Service Cloud, and navigate to Developer Console.
- Just click on the Debug option.
- Then Click Open the Execute Anonymous option.
- In order to clear tokens, just use the below code:
- Next, click Execute.
- In Sales Cloud, just navigate to the Marketing Cloud object; the same is applicable to Service Cloud too.
- Just click on the Configure Marketing Cloud Connector.
- Choose the Change API User option.
- Log on to the Marketing Cloud by using the API user of the installers and then retrieve the new API tokens.
- Next, navigate to the object of the Marketing Cloud.
- Just click on the Configure Marketing Cloud Connector.
- In order to confirm all the business units connected, just click on the Manage Business Units.
Other previous released of Managed Package Release include, but not limited to, Version 210, Version 209, Version 208.2, Managed Package Release Version 5.496.5, Managed Package Release Version 5.498, Version 5.496.2, etc.