A message from our CEO about the future of Stack Overflow and Stack Exchange. Read now.

Hot answers tagged

19

Is it needed to use dispatch server in case of using Sitecore Email Cloud? Yes, Sitecore Email Cloud is simply the mail transit provider. You still need dispatch servers to generate the emails and send to the Sitecore EDS service. The process of generating the emails can be taxing based on how complicated your emails are and if personalization rules are ...


15

Instead of changing the EXM.Enabled setting, try setting the following to no in your Web.config: <add key="exmEnabled:define" value="no" />


13

The question is: How does EXM track opens? During dispatch, EXM automatically embeds a tracking pixel to the bottom of the rendered email. The tracking pixels link's to RegisterEmailOpened.ashx on the Content Delivery server. The RegisterOpen process logs the open event as an Interaction on the Contact in xConnect/xDB. The first step to troubleshooting ...


12

As the product owner, let me confirm. In version 1.x --> 3.2 the Email reporting stack was built on a foundation that was inconsistent, inaccurate and not able to scale with the future of Sitecore. The reporting UI was poor and did not meet the expectations of nearly any of our customers. This means we had to take huge steps to make our customers happy in ...


12

Your problem is that the default settings i.e. the manager root has not been created. Go to the EXM dashboard, click the Default Settings button and enter the details. The settings are explained here. When creating the manager root, a Global Opt-Out list is created. This list does not exist in your environment, which is why you're seeing the error.


12

As EXM does not support CMS-only mode, xDB is required to run EXM. See the documentation on all the components that require xDB. When you send an email campaign, the Email Experience Manager (EXM) creates an interaction in the Sitecore Experience Database (xDB) for each of the following email events: Sent – one interaction for every sent email message. ...


11

Background information The answer depends on your environment configuration. If you have a single server setup (i.e. the server is configured as both CD and CM) the solution is simple (read on), if the server roles are split on multiple servers e.g. one CD server, one CM etc. the solution is a bit more complicated. That being said, Sitecore.Modules....


10

This is a pretty complex issue and question, but you have broken it down excellently to allow me to attempt and pinpoint the issue. I believe the issue you are suffering from is what I have called "The Library Computer Problem" Question 1 With the usage of ExM and Engagement Plans we are heavily relying on contacts and the relation from contacts to ...


9

It has been determined that List Manager in Sitecore 8.1 is not as efficient as it could be. Sitecore Support KB Reference Number 431777 assists with List Manager issues. With this installed, List Manager seems to function better, albeit still not as fast. Instead, the answer from Sitecore Support is that List Manager as a product is being overhauled and ...


9

Solution Posted on Git Gist Existing page emails Probably, it's better to use Existing Page email template for this purpose. If you really want to implement it with tokens, use explanation bellow. Tokens replacement explanation There is Sitecore.EmailCampaign.Cm.Pipelines.SendEmail.FillEmail processor in SendEmail pipeline. It uses GetMailFiller(args)?....


8

What about: shell -> desktop -> All Applications -> System -> License Details?


8

When you send a message and the body section of the message exceeds 102KB, your Gmail subscribers will see the first 102KB of content and then see the following: Gmail message clipped notification. Please have a look on these links: https://help.aweber.com/hc/en-us/articles/205678278-Why-is-my-message-clipped-in-Gmail- https://fulcrumtech.net/resources/...


7

Yes, they are both compatible. WFFM since 8.2 Update-3 (rev. 170413), and EXM since 3.5 (rev. 170810) More information about all modules compatible with Azure Paas can be found here: https://kb.sitecore.net/articles/201557


7

Sitecore EXM module support the Subscription functionality out of the box. There are 4 standard emails: Subscription Confirmation - will be sent after submitting Newsletter Subscription form and will contain a confirmation link with key. After successfull cinfirmation, you will be redirected to the page defined in the EXM Manager Root as a Final ...


6

There are several options. One of them is to add a processor to <getXdbContactRecipient> pipeline defined at 'Include\EmailExperience\Sitecore.EmailExperience.Core.config' and add custom user data there. In public void Process(GetXdbContactRecipientPipelineArgs args) method you can instantiate class with required custom profile properties e.g. public ...


6

I think the part you might be missing is that actual action of clicking a link in an EXM sent email message is that the link goes to a page that sits outside of the Sitecore item structure. That page is \sitecore\RedirectUrl.aspx. Because that's the case, there isn't an item in Sitecore that allows you to tap into that action through the Sitecore UI, ...


6

Let me start by saying that I believe that this is a bug in Sitecore, and the results of our peer debugging session have strengthened that belief. Solution/Workaround You should be able to work around this issue by adding an asterisk (*) to the hostName of the <site> definition node for your site, and leaving the targetHostName blank, as you ...


6

What @steve-mcgill said is completely correct, but I can offer a bit of background on the implementation. Assuming EXM 3.3/4/+: In the file \App_Config\Include\EmailExperience\Sitecore.EDS.Providers.XXX.Sync.config where XXX is the provider (Dyn/SparkPost), there are a number of agents. One of them, the PullComplaintsAgent pulls complaints from the ...


6

EXM is slated for delivery in the next update for 9.0. It was not part of the initial release. 9.0 update 1 should be available soon, but right now if you need EXM functionality today you need to use 8.2


6

There will not be a version 9 compatible EXM as it will be part of the core platform with v9 update 1.


6

EXM was not designed to support this. The (primary) CM is responsible for orchestrating the work e.g. changing the state of the message from draft -> sending -> sent. This runs as a task within Sitecore, so when your application pool recycles, it will never move the message to the sent state. Short of disabling automatic recycling of the application pool (...


6

Thanks for the comprehensive bug report. Sitecore have published a hotfix for Sitecore 9.0 Update 1 which fixes this issue. The decompiled code is hard to read but the issue stems from flag2 (as it appears here) being too strict. It has been adjusted to now simply check the Global Opt-out list for both Regular and Automated messages. Please ensure this ...


5

EXM requires an email to be associated with the contact. The contact has to be an xDB contact. Starting from EXM 3.1, Sitecore users are no longer supported. By default the contact should look something like this: { "_id" : LUUID("84ad2c30-71b9-a445-a424-a597867876b8"), "Identifiers" : { "IdentificationLevel" : 2, "Identifier" : "...


5

Upgrade Script: ConvertUsersToContact.aspx This script utilizes the standard Task Manager in Sitecore in order to process contacts. If for some reason, you have the processing\taskManager disabled, stopped, or otherwise not activated, the ConvertUsersToContact.aspx will hang on Task is waiting for processing. private string GetStatusString(...


5

If you are using EXM, then you can take advantage of Sitecore.Modules.EmailCampaign.ClientApi. Have a look at the the EXM ClientApi documentation for version 3.4 of EXM listManager.AssociateContacts is fairly low-level code, and contact.Tags.Set even more so. As the post you link to points out, it is risky to use these APIs directly and manipulating the ...


5

Background information During dispatch, all links are replaced with a link to /sitecore/RedirectUrlPage.aspx with additional query string parameters such as contact id and message id. RedirectUrlPage.aspx runs the redirectUrl pipeline, which is responsible for several things, e.g. adding click events based on the query string parameters. After running the ...


5

You need a new subscription for EXM 3.4, the old one is not good. You can find on EXM 3.4 documentation : Please be aware than when upgrading to EXM 3.4, a new subscription to the Sitecore Email Cloud is required. This especially applies to existing subscribers of the Sitecore App Center product; Email Delivery. Email Delivery subscriptions will no ...


5

First of all, you should disable List Manager on the processing server. The search messages in logs are likely caused by the Sitecore.ListManagement.Analytics.UnlockContactListsAgent class. It looks for locked contact lists every 10 seconds (configured in the Sitecore.ListManagement.config file) and tries to unlock them as soon as the real (indexed) ...


5

Just to clear up a common misconception. EXM uses List Manager to retrieve contact lists and contacts, but they are two different products/APIs. EXM is a module released separately, whereas List Manager is a component released as part of the Sitecore Experience Platform. So you don't want to look at the EXM API to do what you're asking, but rather the List ...


5

When you try to install a module or a package on Sitecore and it keeps 'installing' forever generally it means the Analytics (or specifically MongoDB) is not running. Some configuration file have not been properly updated. Try to compare your configuration files to another solution running with same Sitecore version.


Only top voted, non community-wiki answers of a minimum length are eligible