The first part of a new series on choosing the right CMS system has published on the sitecore.com site! This first article delves into some of the reasons you might be thinking you need a new CMS, and some other situations where you might be okay to just incrementally improve on what you already have.
With the latest Sitecore 9 release, a completely new Marketing Automation tool is available for users to quickly plan and extend their automation activities with an intuitive drag-and-drop interface.
Also, a new fully-scalable engine architecture is now available so that you can make sure to process new activities as quickly as you need to.
I have put together a video series as well as a blog post on the new capabilities in Sitecore 9 and published it to the Sitecore Technical Marketing blog!
Just over one year ago, I wrote about a big change in my career as I joined the Sitecore Technical Marketing team to work as the North American Technical Evangelist. Over the last 12 months, a lot has happened, and in typical agile fashion I’m looking back at what has been happening, what worked well, and what didn’t!
FAIR WARNING: This is a long read, there is no TL;DR, this is mostly for me. Read at your own risk!
TL;DR: I lied. The short version is I had a blast all year and am way too excited about more big things this year!
Have you ever wondered what is going on with those new Shard databases in Sitecore 9? This is the new xDB! The new Shard Manager stores data based on the contact ID. A contact ID is a GUID identifier that is unique for each contact. It looks something like this:
The xDB scales out by splitting these contacts across the various shards based on their contact identifier. A 16-byte hash of the GUID is used and assigned to each shard to ensure distribution.
Did you miss out on my Montreal SUG presentation a few weeks back? Not to worry, I got your back!
I recorded a run-through of my presentation and uploaded it so you can hear my thoughts on how we can continuously improve and invest in DevOps practices for our Sitecore projects. It’s not exactly what was in Montreal, but close enough 🙂
Want more? Come hear the Effective DevOps for Sitecore panel at Symposium 2017 on Wednesday, October 18th, at 11:15am. I’ll be moderating panelists Kam Figy, Derek Hunziker, and Joe Bissol. Great panel, great content!
When you are doing local Sitecore development, you might need to setup a local SOLR instance to host your indexes. This is especially important if your project isn’t using Lucene indexes in production and you need to replicate the environment. When replicating production for troubleshooting, it is also useful to replicate the security setup as well, including SSL.
In this article, I’ll cover how you can take your SOLR installation and get it running on HTTPS in 11 easy steps!
Sitecore’s Customer Experience Maturity Model has been around for a while and it is still as relevant today as it was when it was first released. The model helps a team to understand where they are right now and where they could possibly be with customer engagement.
However, it isn’t easy to keep improving. I’ve written a lot in the past about using baby steps to continuously improve your software delivery. The same is true for marketing efforts. As teams we often focus on big-bang improvements: a new redesign, content re-work, big integrations to our back-end systems to better leverage our digital assets. All of this is awesome work to get us started.
Unfortunately, it often stops there. We lose the momentum to keep iterating and improving on how we engage with our customers. We need to have a plan that will allow for small incremental changes to our content and marketing automation. This ensures that we can give customers a better experience and ultimately help them with their problems.
How do we increment?
- Analytics. First off, we need to be tracking data. Whatever your analytics platform, make sure you know what’s happening on your site. Also, if you are using Sitecore xDB, make sure you have your xDB tracking enabled. You’ll need that data in the xDB for later steps.
- Content Tagging. Learning about visits is great, but we need to know more about what type of content engage people. Start by adding a few tags so you can get a baseline to learn about user behaviour.
- A/B and Multivariate testing. Once we have learned a little about the types of content our visitors view, we can start focusing on which variations of content are working for our visitors. This testing will greatly inform further improvements we make to the site. Keep it small, just a few tests so you can manage it.
- Personalization. Add a few rules-based personalizations into your website based on what you are seeing from analytics and results of testing. Again, focus on some big win personalizations: a hero banner, or a call-to-action button. Sitecore can even suggest personalizations based on analysis of your tests.
- Engagement Levels and Campaigns. At this point, we should be learning enough about our customers to start determining their engagement and moving them through a campaign. Our personalizations should start becoming less rules-based and more about where they are in our engagement level. Leverage your calls-to-action!
- Omni-channel. Start reaching out to your customers in different ways. Add a mobile app. Tap into your onsite kiosk. Develop email campaigns. Build a game app to complement your messaging. Keep making iterative improvements to add more sources to feed information back to your central xDB data. How can we reach the customer in a new way?
- Machine learning. At a certain point in the continuous improvement cycle, the data is just getting too big to handle by hand. Automation is required to process the information and look for trends. Microsoft Cognitive Services is one way to start adding some intelligence to the mix! You can read more on machine learning Sitecore’s “The Mind in the Machine” series.
- Learn. At this point, we probably need to take a moment to learn about what worked well and what didn’t. Time to improve our tests and personalization with the new information we have!
Want to see the original Customer Experience Maturity Model information? Check out the full PDF doc here: