Skip to main content

OOTB Abandoned Cart Marketing Automation Campaigns Not Shown In The List

Hey All,

It has been little while now i wrote my last blog, i have so many pending blogs to write, i will commit myself to write those in coming months

But today, i will be sharing some small but useful information regarding marketing automation templates not showing even if all settings and installations are fine

Following is the whole scenario which i was facing and had no clue until i found the actual reason why those campaigns did not show up

Marketing Automation Campaign
Ok, so i had a task to modify and use existing OOTB Abandoned Cart Campaigns and utilize and change them to allow some customized business logic.

So generally when you install SXA tenant site with commerce they come installed by default and can be seen in the campaigns list.

But in our scenario everything was working but the campaigns were not coming in the lists, there was nothing in the log as technically there were not errors (which i came to know after troubleshooting which i will mention later in the blog)

Problem
Even if everything looked fine and all commerce abandoned cart templates were installed, still the OOTB campaigns were not seen in the list of campaigns in "Marketing Automation" list.

 

So i tried following things

  • I reinstalled those commerce campaign packages for my site tenant by removing them form the site and again installing it but no luck, it just did not show up, installation was fine, it was showing that they are installed
  • I tried running commerce installation script (partial script just to install that campaign packages script), but script was successful but no luck (My senior and multiple times sitecore MVP brijesh patel suggested me this, which was a good pointer to look into as well.)
  • Tried looking into marketing automation services logs,  Restarted it
  • Verified certificates but all things were fine
  • Checked config files for connection string to make sure the user is there and has access to marketing automation service and everything looked just good as otherwise all things of the sites were working just fine

Solution

After trying different things with no luck, i tried to see what AJAX call it is making to get the list and thought to see the DLL code from where it is getting the list.

If you observer the below screenshot, one thing caught my eyes were it was passing the culture with the AJAX request as en-US see below screenshot



And in one of our other environment it was showing the list, so i checked what parameters are being passed there, and surprisingly there was different language culture was being passed as "en" and not "en-US" like following

So just to try, i copied the URL in a browser and tried to hit it with only "en" as a culture and not "en-US" and it showed the json response with all the campaigns like following




So i concentrated my search around that to find from where it is passing that as that was the only difference i could figured out

and found out that it is the language setting of a user who is logged in, so i saw the setting in sitecore user manager for that user and surprisingly i found that for that only user the culture was "en-US"



I changed the setting to "Default" from "en-US" and saved and just refreshed the marketing campaigns list page and was happy to see the campaigns are back :)



As i said Small but very useful information

I hope if you come across something, this blog will at least save you some time

Comments

Popular posts from this blog

High CPU to completely normal CPU - SXA issue, SXA pages not loading in mobile device

  Hi Team, Today i am going to share one of the nightmarish issue with you all, We are having Sitecore 9.1.1 hosted in azure PaaS environment Our site was working just fine and no noise, but we have been working on a feature release where 7-8 months of development needed to be released to production, Big GO LIVE event right?  Also to make the development smoother we also introduced BLUE/GREEN deployment slots in the same release, so we can easily SWAP slots and go live Everything went well, we went live, we even did load and performance testing on our staging and pre-prod and we were confident enough of results Very next day we started getting "SITE DOWN" alerts, and also product owners and clients mentioned that site is very slow for them in US time and in our morning when we were accessing it, it was working lighting fast so we were clue less at start, but we started digging  1) First thing caught our eyes were HIGH CPU spikes, in US time, also without any traffic CPU u...

One or more exceptions occurred while processing the subscribers to the 'item:creating' event

I was recently installing the packages from one of the QA environment to my local Sitecore instance, "Media library package" to be precise, And it started giving me this below error One or more exceptions occurred while processing the subscribers to the 'item:creating' event Looking at the sitecore logs, it gave me more info on the context and the actual inner exception was following Solution: 'Name' should consist only of letters, digits, dashes or underscore Now it was evident that some of my file names were violating the naming rule, I could see in the log just before exception from where the installer stopped creating items, and that file name had round braces "(" and ")" at the end of it, with my surprise I was able to create the item with those name in the content tree, but below was the solution for it, Solution I am using SC 9.0.1 and in that Go to Sitecore.Marketing.config file residing in "App_Config\Sitecore\Mar...

An error occurred while receiving the HTTP response to This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details.

You have noticed many times that everything was working fine and suddenly the below error starts coming and you find no way to work it out An error occurred while receiving the HTTP response to This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details. The reason for this is the receiving size of WCF service is smaller then the data which is coming from service It was working before because it was small,So you will have to try to increase the receiving setting in your end point,Possible settings can be following maxStringContentLength="2147483647" maxReceivedMessageSize="2147483647" maxBufferSize="2147483647" maxArrayLength="2147483647" That would definately help you!!!