With the May 2020 release finally finishing it’s arrival in all of our orgs, we can now look to the new horizon of July 2020 landing in our orgs in a few weeks time. In summary, it’s another slim form factor release - but that doesn’t mean it’s a bad thing. Skip to the bottom if you’re not interested in the details and just want the abridged version.
The navigation is continuing down the form factor of bundling everything to do with Emails/SMS/Push/Cloud Pages under the banner of “Journeys and Messages”. Big improvement from a UX perspective is now not all elements of the release include “Month Year Release Notes”. A minor bug bear but it didn’t do much to help keep the release notes readable.
So a big thank you to the documentation team for making a tweak like this!
InfoSec professionals rejoice! Multi-Factor Authentication has arrived in SFMC. Whilst the actual implementation of it and what permissions you would need to manage the MFA settings (I would assume that there’s something in the Marketing Cloud Security Administrator user role or in the standard Marketing Cloud Administrator use role). Marketing Cloud Admin will be able to send temporary code to any users who lose their MFA device, but until we see it live we can’t say a whole lot about how it works. Fortunately, a range of MFA methods are available (including the Salesforce Authenticator app, so if you’re already using that then you at least don’t need something else!) Once we see this popping up we’ll add some details, as a security and access change it’s completely understandable that you may not want to make the change without some confidence that you won’t end up locked out! Fingers crossed support are ready for an influx of people who’ve seen it and thought “cool! We need this” without having thought of how it affects the users of their org.
Thank goodness. If you’re using SFMC and need to use Internet Explorer 11 - Show your IT team this post and let them know that the HowToSFMC team is officially against the use of Internet Explorer 11. If Microsoft themselves can embrace Chromium in Edge - so can you. It’s almost 7 years old. Just upgrade. Please.
New REST API search operators for those who use the /asset/v1/content/assets/query endpoint for retrieving the Name, CustomerKey, Content and Subject Line fields within a Content Builder Asset. Whilst it’s historically been more difficult than you’d want it to be if you don’t know the folder of an asset, it should become a little easier with these new operators:
This is one of my favourite but also most frustrating elements of the release. Previously erroring for Journey Builder sending, Triggered sending or Job sending emails you wouldn’t necessarily find out straight away or event be notified at all. Now, however, you can input (this is the frustrating bit!) A SINGLE ADMINISTRATOR EMAIL ADDRESS to receive any and all alerts that are triggered around send alerts. It’s a cool feature and it’s one that I would have been grateful to have had in the past. I sincerely hope that we could include a variety of alerts for different reasons to different people & also different channels. Sometimes after a busy day at work (especially whilst we’re all on lockdown) I shock-horror turn off my emails for a few hours. There may be scenarios where an error is at the level of significance that an SMS would be more appropriate. But I’m still looking forward to trying it out and seeing how it works!
For those who have Interaction Studio, it appears to see that for all Interaction Studio customers will have another system user role created - Interaction Studio - Legacy & some new permissions to give users the appropriate permissions in the new version of Interaction Studio (previously known as Evergage). Make sure to take a look at these if you’re using it.
The second announcement about this for the A/B Testing via Marketing Cloud Connect. It relies on some Classic Content functionality (Which supposedly retired for creation of new assets just a couple of weeks ago) - So for Classic Content… This Ain’t Goodbye… Okay, well maybe it is - but thanks for your service. Long live Content Builder.
If you’re integrated with Salesforce CRM with Marketing Cloud Connect & you’re active in that side of the world - you’ll start to get some new banners appearing about the Business Units and Enterprise in the integration.
The release notes just say that they’ll “provide details” - Doesn’t specify what details. It might tell you how many people named Jason you have in your SFMC org or it might tell you something less useful than that. Maybe they’ll be customisable? Who knows, the release notes don’t in this case. Maybe there’ll be some screenshots added in the future to bring it to life (hint hint!)
If you’re in an integrated org, there’s a few more things to be aware of:
We have the first casualty of the release notes and the release notes are only a couple of days old.
So if anyone managed to catch what the Modify Permissions for Marketing Cloud SFTP Folders was - let me know! I’m curious.
You can set this up in Contact Builder based on hourly, daily, weekly or monthly cadences. If you choose daily or weekly you get to pick an hour, monthly you get to choose which day of the month. So… Scheduling like we’re used to in other areas of the platform.
If you’re using Audience Builder, you may find your refresh process is taking a lot of time some days. If you happen to be a user who has lots of dimensions, but you only use some on a daily basis - the refresh procedure and data loaders will now automatically detect which ones aren’t being used and will not get that data processed. Just one to be aware of - as the process runs daily if you do need the dimension at short notice you may need to work out the best way to deliver that with Audience Builder. If you’re not sure how best to manage this, the system will only deactivate a dimension if it’s not used. So if you use a dimension in an Audience Filter Segment or Exclusion, the data will be refreshed every day. Not sure if this is a good update but if there are dimensions that you’ll never need you may as well not wait for them to process.
It’s definitely a light one for Developers this time around. You’ll be able to Link journeys to transactional message REST API Send Definitions. Anything you’ve already got in place, you’ll need to use the options.createJourney JSON parameter by PATCHing the /messaging/v1/email/definitions endpoint with your definition key.
With all of the details around SMS from Kevin Ryan from the Technical Marketers Bi-Monthly Meeting on 25th June - it’s great to see that the SMS Status Codes will be available via the REST API and not just the Data Views. The API will return the “highest” status code from the carrier. More details are available here.
Unsecured HTTP Callbacks for SOAP Async API are being turned off. Just switch to HTTPS and you should be good.
Everyone's favourite cartoon genius (Sorry Dexter, your laboratory is cool and all - but I’ve never seen you ride a 3 person tandem bike with Astro who can’t reach the pedals and Codey who can’t reach the handlebars) is getting some new features!
Journey Builder is getting some great new features and considerations in the new release including:
For SMS - There’s now a loop prevention process in place for those times where you accidentally send to a system that automatically responds to you. So now, if you receive more 35 messages from a single number in a 5 minute period, outbound messages will stop being deployed.
You’ll be able to update the SSL selection after a page has been published, which should be nice and help those who have any legacy pages prior to purchasing an SSL cert. Rather than fully redeploying a landing page (especially a preference centre) that has been active for months just because of an SSL cert.
CloudPages did have their base template updated to remove an insecure version of jQuery. So if you have any jQuery on a landing page I thoroughly recommend you go and check whether you need to add it yourself manually now!
Have you been trying out the new CloudPages Experience PREVIEW? Any thoughts on it? Let us know!
Email feels a bit like the last kid picked at school this release. The only change at all is the addition of Interactive Email being able to accept a pre-populated field. So if you’re providing a contact with a form including a name or any other details - you could surface this information for them to confirm or reject it directly from the email.
Pretty neat, don’t think it’s massively a game changer but any improvement for Interactive Email is massively welcome.
Overall, whilst this is a pretty slimline release, there are some great call outs to be made but most of them aren’t on the super fun stuff we all love to play with. It’s definitely a release of practicality and it almost feels like SFMC is growing up and becoming more responsible for itself. MFA is a great addition for a security perspective, the Alert Manager is massively welcomed to any solo admin of a wide org & the journey removal process now being in the UI to make things a little easier. On the whole, this is a sensible release and fingers crossed it all lands before the release notes for the October release hit the internet!