Not clear what the Marketer role which you mentioned above, but to your question to access Marketing Automation module, you need to have the "Marketing Automation Editors".
You can refer the detail of each and every role in Sitecore documentation here
Campaigns are not treated as live events OOTB. Live events are only detected for page events and outcomes by corresponding processors:
Both of the processors check for ...
When does is it written to xDB
Like the other answers said, it is written when the session closes. The time it takes to be written is in the web.config, in the session config. In the xml below, it is the timeout. This number is in minutes.
<sessionState mode="InProc" cookieless="false" timeout="20" sessionIDManagerType="Sitecore.SessionManagement....
The Marketing Automation engine requires you to define custom facets that will be available when the contact is evaluated. You will need to patch in your custom facet to the IncludeFacetNames section of the sc.MarketingAutomation.ContactLoader.xml config
You would need to add the MemberInfo facet to the IncludeFacetNames. You could create a patch file sc.(...
You can not add anonymous contacts to Automation Plans.
You will need to identify them first. Additionally, if you are planning on sending this user an email, you have to know information about the contact, thereby making it a known contact.
It sounds like you need to add a Custom Submit Action to your Sitecore Form to identify the contact, set the email ...
Based on Sitecore documentation engagement plan enrollments are not merged. Hence you have to implement any required logic yourself. Be it purging the source contact from all plans before merging or enrolling surviving contact into the same plans that the dying contact was part of. Please refer to Marketing Automation API on how to do it.
I suspect you are running into a certificate issue where you have self signed certificates in the Trusted Root that need to be removed. Check out this blog post.
The main point of the post is to remove the non-self signed certificates in your root.
The plans a contact is enrolled in is stored in a built-in facet on the contact called AutomationPlanEnrollmentCache.
You can get the facet like this:
using (XConnectClient client = SitecoreXConnectClientConfiguration.GetClient())
var contact = client.Get(
new IdentifiedContactReference("Your Known ID Type", "Your Contact ID"),
So, I found the reason my listener wasn't firing. It turns out, the listener Sitecore.EmailCampaign.Activities.ClickListener listens for a specific ClickPageEventId.
The GUID that it's listening for 87431B9B-FA39-4780-BEB3-1047B9E61876 is the GUID of the OOB Click Email Link goal that has shipped with Sitecore forever.
I had no idea that any of the ...
I have experienced this issue first hand in the past. The Marketing Automation engine is the sole process responsible for determining whether the contact has met the requirements in order to enter or proceed through a Marketing Automation plan.
All of the Custom Listener rules depend on the Marketing Automation engine being able to load the Contact and the ...
Not sure of the underlying reason for it, however if you deactivate the message it will be unprotected and you can then move it to the dynamically created folder in the environment that you've moved it to. If you then activate it, the campaign will appear in the list of available campaigns in your Marketing Automation plan.
To get around this issue I retrieved the interactions from the Contact via the code below. If anyone can explain why, that would be helpful, but this should get you out of trouble.
Contact contact = context.Fact<Contact>((string)null);
if (contact != null && contact.Interactions != null && contact.Interactions.Any())
You need to include the PhoneNumberList facet which has a facet key of PhoneNumbers. You can patch it in by creating a new file that loads after the xconnect_root\App_data\jobs\continuous\AutomationEngine\App_Data\Config\sitecore\MarketingAutomation\sc.MarketingAutomation.ContactLoader
The PhoneNumbers Facet is not included as a default facet expand options in MA
I think I found this for you. The xml configuration file sc.MarketingAutomation.ActivityTypes.xml has a section called IncludeFacetNames that defines what facets to include when the contact is created. So if you update the section to include the PhoneNumberList facet, it will be ...
The Marketing Automation Engine supports constructor dependency injection for custom activities. So to use a dependency in your custom activity, add a parameter to the constructor of your custom activity matching the type of the service you want passed in:
public class SymposiumReminder : IActivity
private IOtherService _otherService;
This sounds like the Marketing Automation Engine webjob is not running properly. This is an executable that, in Azure Paas, runs as a webjob in the MAops app service (for XP Scaled topologies) and responsible for enrolling contacts in plans and activities.
You can confirm it's running status in the webjobs blade in Azure portal. You can also restart it ...
I hope you are following below points:
In Sitecore form, you have selected Update Contact Details before Trigger Goal. You can follow https://doc.sitecore.com/developers/91/sitecore-experience-management/en/walkthrough--creating-a-custom-submit-action-that-updates-contact-details.html this link. Update Contact Details submit action will create/update ...
In the end what worked for me was installing all the latest Windows updates. However, since I am working on an enterprise PC it was not enough to just "Check for updates" since that did not check outside the company for updates. I had to use "Check online for updates from Microsoft".
These are the updates that were installed:
KB4293803 - GDR 2002 for ...
In older Sitecore versions this code used to work:
AutomationStateManager manager = Tracker.Current.Session.CreateAutomationStateManager();
var plans = manager.GetAutomationStates().Select(s => s.PlanItem);
I'm not sure if it still work in the latest but it should be a good place to start.
Not sure if you are still having this issue but if you do, you can try the below steps:
Root cause: This error occurs when the marketing service tries to connect to xConnect but xConnect does not start up properly. Hence, the marketing service fails, and thus the installation. This can happen for several reasons in which the most common are: