Skip to main content

What capabilities is Sitecore EXM missing?

 I have been working with Sitecore EXM 9.3 for a while now. I have worked on a project with some pretty advanced requirements. EXM has some pretty great capabilities and those are easy to find as that is what all the marketing focuses on. But what are some core capabilities it is still missing? Here is my list. If you have more please leave a comment. 

Limited Subject line personalization

Ok, yes it does have the ability to personalize a subject line. You can put tokens into the subject line like first name and last name. You can even create your own custom tokens. But what if you want the subject line to change more than just by a token? This is something you cannot do, at least not out of the box. This can cause a challenge when you have a marketing automation campaign that sends a series of emails. The content gets personalized based on the series of emails they are getting. But it means the subject line for that email is pretty much the same. This is not ideal when talking about high levels of personalization. 

Recurring Scheduling for defined times

This is a huge one for me. You can schedule emails to be reoccurring, but given a huge limitation in Sitecore after the first send all other reoccurring sends will always happen at midnight even if you scheduled it to go every day at 3pm! This one is really frustrating to me. If you schedule an email to send every Tuesday at 3pm the first Tuesday after you set this up will send the email at 3 pm. However, every Tuesday after that the email will be sent right after midnight! To make things even worse once the email has been sent the first time the email is also removed from the list of "scheduled" emails in the EXM dashboard! So even though you still have scheduled emails you can't see them anymore. These two issues have reference numbers 443849 and 450635 to be addressed hopefully. This is a big miss that makes it hard to say EXM is in a space that can compete with other platforms out there. 

Compress the email HTML on send

In my opinion, this is a miss. It is pretty easy to implement and impacts your email's deliverability. Now, depending on what you are doing with your emails this may not matter much. In fact, you can argue that the smaller your email the better. So, with a short brief email, there may be no need for compression. However, almost all marketing emails are HTML emails. HTML has a lot of wasted space in it with all the white space between tags and the like. A lot of email size can be saved simply by compressing the email. This can be done easily by adding a processor to the SendEmail pipeline. Before you say it, yes, you are correct, this will create additional processing and slow down your email generation. So, like most things you have to weigh the trade-offs. 

Inline CSS that is in a referenced stylesheet

The value of this one really depends on your workflow for creating emails. If the emails are designed, developed, and deployed in isolation from other assets there is probably not much value in this to you. However, if your emails shared styling with other assets you manage, like your corporate website, it can help. It makes managed of styles easier if emails and the website can both reference the same stylesheets. This way everything updates with one change. However, most email clients will not work with referenced stylesheets. Having a processor that can take all the referenced styles in an email and moved them from the external stylesheet to inline in the email solves this problem. Out of the box you don't have this capability. Litmus and MailChimp have some online tools where you can do this conversion but at scale tools like this don't really work. PreMailer has an online version but also a Python and C# port of this code you can bring into your solutions. Again, this comes with processing time tradeoffs you need to evaluate as this can be an expensive process. 

Storing custom information about a send

This is a more advanced need, but if you are customizing pipelines to push additional information to your emails and/or the rendering process this can be a challenge. Sitecore's Pipeline and process architecture is amazing and goes a long way here. You can use the pipeline arguments custom data property to store and pass information down the pipeline. However, with EXM this process eventually makes its way into the dispatch task. This is an in-memory process. The challenge here is this dispatch task can be aborted (when sending an email, the send can be paused by the user or paused by the system if it detects too many exceptions). When an abort happens the task is canceled and the pipeline finishes. This means all the data stored in the pipeline arguments is disposed of once the pipeline finishes. Resuming the send does not recreate all the same pipeline arguments. You have also lost any state you may have tried to store in those arguments. To make this work you have to do some overriding to get at task data which can be tricky. I hope to get into some options here in a future post. 


These are the biggest gotchas we have found in regards to EXM. Your mileage on some of these may vary. If you have other ones please leave a comment and let me know. 


Popular posts from this blog

Excel XIRR and C#

I have spend that last couple days trying to figure out how to run and Excel XIRR function in a C# application. This process has been more painful that I thought it would have been when started. To save others (or myself the pain in the future if I have to do it again) I thought I would right a post about this (as post about XIRR in C# have been hard to come by). Lets start with the easy part first. In order to make this call you need to use the Microsoft.Office.Interop.Excel dll. When you use this dll take note of what version of the dll you are using. If you are using a version less then 12 (at the time of this writing 12 was the highest version) you will not have an XIRR function call. This does not mean you cannot still do XIRR though. As of version 12 (a.k.a Office 2007) the XIRR function is a built in function to Excel. Prior version need an add-in to use this function. Even if you have version 12 of the interop though it does not mean you will be able to use the function. The

Experience Profile Anonymous, Unknown and Known contacts

When you first get started with Sitecore's experience profile the reporting for contacts can cause a little confusion. There are 3 terms that are thrown around, 1) Anonymous 2) Unknown 3) Known. When you read the docs they can bleed into each other a little. First, have a read through the Sitecore tracking documentation to get a feel for what Sitecore is trying to do. There are a couple key things here to first understand: Unless you call " IdentifyAs() " for request the contact is always anonymous.  Tracking of anonymous contacts is off by default.  Even if you call "IdentifyAs()" if you don't set facet values for the contact (like first name and email) the contact will still show up in your experience profile as "unknown" (because it has no facet data to display).  Enabled Anonymous contacts Notice in the picture I have two contacts marked in a red box. Those are my "known" contacts that I called "IdentifyAs"

Uniting Testing Expression Predicate with Moq

I recently was setting up a repository in a project with an interface on all repositories that took a predicate. As part of this I needed to mock out this call so I could unit test my code. The vast majority of samples out there for mocking an expression predicate just is It.IsAny<> which is not very helpful as it does not test anything other then verify it got a predicate. What if you actually want to test that you got a certain predicate though? It is actually pretty easy to do but not very straight forward. Here is what you do for the It.IsAny<> approach in case someone is looking for that. this .bindingRepository.Setup(c => c.Get(It.IsAny<Expression<Func<UserBinding, bool >>>())) .Returns( new List<UserBinding>() { defaultBinding }.AsQueryable()); This example just says to always return a collection of UserBindings that contain “defaultBinding” (which is an object I setup previously). Here is what it looks like when you want to pass in an exp

WPF Localization - RESX Option

About a year ago I was building a WPF project in .Net 3.0 and Visual Studio 2005. I wanted to revisit this subject and see what has changed in .Net 3.5 and Visual Studio 2008. I will make a few of these posts to try and cover all the different options (RESX option, LocBaml option, Resource Dictionary Option). In this blog I will focus on using a resx file to localize an application. To show how the resx option is done I created a WPF form with three labels on it. The first label has is text set inline in XAML, the second has it text set via code behind from the resx file and the third has its text set via XAML accessing the resx file. The first thing that needs to happen to setup a project for localization is a small change to the project file. To make this change you will need to open the project file in notepad (or some other generic editor). In the first PropertyGroup section you need to add the follow XML node <UICulture>en-US</UICulture>. So the project file node w

Advanced Item Cloning

Cloning in Sitecore can be extremely useful. It makes reusing of content items and updating of those items very easy. The default capabilities for item cloning can usually handle most needs. The default behavior does have one thing that can really trip you up. By default clone, child items stay linked to the source cloned item and are not reparented to their new cloned parent. The first thing to understand is there are configuration options for cloning that allow you to change how cloning works. The configuration files have them pretty well documented but if you don't know what you are looking for you may not know they are there. <setting name="ItemCloning.Enabled" value="true"/> Specifies whether the Item Cloning feature is enabled Default value on CM and Standalone servers: true. Default value on CD, Processing and Reporting servers: false. <setting name="ItemCloning.NonInheritedFields" value=""/> Specifies a pipe-separated lis