Sitecore Marketing Automation features:  Automate repeated activities to free up time. Enroll and evaluate in session and in real time. Make decisions based on any data point, behavior or time. Perform visible and backstage marketing actions. True omnichannel orchestration

 

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.

Getting Started

It’s helpful to get a quick tour of how to use the new interface and what activities are available out of the box. Our new Marketing Automation video series will get you positioned to understand how to create a new automation campaign and understand the marketing actions and listeners available in the platform.

Marketing Automation - What is it?

Wondering about what Sitecore Marketing Automation is? Senior Product Manager David Hughes walks through the new product and some of its features.

[View:https://www.youtube.com/watch?v=-44xRa0ju2k:320:192]

 

Creating a Campaign

See how to create a new Marketing Automation campaign using the new Marketing Automation builder interface.

[View:https://www.youtube.com/watch?v=MG0aaBBRuXY:315:190]

 

Marketing Actions

In this Marketing Automation episode, I explore the available Marketing Actions that can be added to an automation campaign.

[View:https://www.youtube.com/watch?v=w_VYqTXVej0:315:190]

 

Listeners and Decision Points

In this Marketing Automation episode, I dive into the available Listeners and Decision Points that can be added to an automation campaign.

[View:https://www.youtube.com/watch?v=jiyVkUAa3g0:315:190]

 

Engine and Architecture

Software Architect Jacob Nielsen digs into the underlying Marketing Automation engine and architecture in this episode.

[View:https://www.youtube.com/watch?v=0HxUph2YLZc:320:192]

 

Extensibility and Customization

You can create custom rules, activities, and extend the Marketing Automation engine. One common customization is creating a new Activity Type, but what does that require?

There are several components that go into creating an Activity Type. Once you have the code implemented, you need to ensure the rest of the system is configured to make use of your new code.

Activity Type logical diagram

Step 1: IActivity implementation

Create a class which implements the IActivity interface. This class should have the logic you want to implement as an action or listener and should return a result that the engine can process. You can return a “Default” path, which is typical for most actions, or “true/false” paths which is typical of listeners and decision points.


Step 2: Activity Description in Sitecore

Your new implementation class needs an associated item in the Sitecore tree (/sitecore/system/Settings/Analytics/Marketing Automation/Activity Types). When you create it, make sure to specify the Implementation Type field as the full .NET type of your new IActivity implementation.

If you have parameters in your constructor, you need to define them in Sitecore as well. You will also need matching Paths defined.

Step 3: Add an activity type to the Marketing Automation UI

To work in the new Angular SPEAK 3 interface, an NPM project is required and it needs to be installed in the Marketing Automation application. The Marketing Automation feature does not come with an Angular JiT compiler therefore you need to configure an Angular AoT compiler to prepare your package. Once the plugin is deployed, it needs to be registered with a patch include file with the relative path for the plugin.

See the detailed documentation: https://doc.sitecore.net/developers/xp/marketing-automation/activities/activity-types/add-activity-type-to-ui.html

 

Step 4: Marketing Automation Engine configuration

There are three things that need to be configured in the Marketing Automation Engine:

  1. IActivity implementation type
  2. Dependent services
  3. Required facets

For the implementation type, we need to have an XML file in the marketing automation engine folder that defines the class and any options. The DLL also needs to be deployed to the Marketing Automation engine root.

If your activity has any external services that it consumes, these also need to be registered in the automation engine in a separate XML file. You don’t have to do this if you do not have custom services. The DLL with the services also needs to be deployed to the engine root.

If there are any facets that are used by the activity, the ContactLoader configuration file needs to be updated to include the required facets.

 

Diving Deeper

Check out the following developer documentation for an in-depth look into Marketing Automation.

Marketing Automation Engine

Activity Types

APIs