Salesforce marketing cloud Developer
InfosysVisual Studio
Netlify
SFMC
Query Studio
Jest
Git
GitHub
Jenkins
Postman
After that, I joined Infosys. And then I get trained on Salesforce admin platform development, and AWS. After that, I created a project. In there, I get chance to work as a Salesforce marketing cloud developer. And then I worked for, um, more than 2.5 years. And then I worked on 2 different teams. 1, team was One team was, like, um, developing, uh, uh, email campaigns from scratch, like, uh, creating email templates, journey builders, automation studios, um, and creating data extensions and, uh, developing those based on based upon the campaign requirements. And in another time, I was mostly worked on mobile post notification, and sometime get chance to, uh, make some small changes in the game templates. Like, they want to change the hero images, or they want to, um, change the CTA links. Uh, those things I can work. In creating mobile push notification, I worked on, uh, creating those push push notification message and added the preview to the Jira tickets for the plan. Once it get approved, I will then, uh, schedule the push notifications on the, uh, client requirements and then schedule it. Yeah. This is the overall work, uh, that I did in my
Uh, suggest a way to manage bonuses effectively using, uh, marketing cloud capabilities. Uh, there are many types of bones, uh, which we can see, like soft bones, hard bones, uh, technical bones, black bones. Right? But in some of the cases, uh, we are not able to do anything like in technical bones, it was, uh, due to some technical issues, data issues, uh, like that. In that cases, we're not able to manage do anything. But in the cases, like, if the, um, heartburns was like, the email ID is not found or the, the one is not valid. Uh, other cases, we can, uh, uh, make sure remove the make sure remove the subscriber key from the data attention to get the, um, percentage of click through and hide through. It will get high, and the and then we can effectively manage the Salesforce marketing cloud capabilities.
How could you release a AMS script to personalized content based on churn customer data in general? Yeah. Apps Script is a programming language that, uh, will that is used in Salesforce marketing cloud. Uh, mostly, it was used for personalization and for some we and it's used for to, um, segregate country condition based on the, um, subscriber attributes. Like, uh, we can, uh, personalize the content, uh, like, based on their preferences and based on their use cases. Like, if if, uh, we are sending a mail, um, the 2 different based on the general preference, like mail and payment, We can use the AMS script to, uh, send, uh, 2 different contents to, uh, to the customer based on their gender preferences. And, um, and, also, we can, uh, use a hand script in such a subject line to, uh, make sure to test, uh, with subject lines, um, that is used to to, uh, that is attracted by attracted the customers to open the, uh, communication from the marketing cloud, uh, so that we can get, uh, more than more of click through click through rates and open rates so that we can get, uh, high, uh, ROI in the campaigns. And also we used AMS script to personalize, like, uh, we can add, uh, some first names in the, uh, greetings, like, uh, thank you, the customer name or the dear customer name, and we are opening the email templates or the messages. And then we can add the, uh, contents, what are what are what are the messages, what are the needed. And also, we can add some, uh, references based on, uh, some cuts, uh, customer purse purchase. Or we can send some recommendations based on the search history of the, uh, customer. So AMS script, it, uh, is much utilized for to personalize the personalize, uh, separate contents for each and every customer.
What Yeah. Uh, in automation, uh, we can see there is, uh, there is an activity called file drop. Um, in that file drop, we can, uh, able to extract file, like upload or import, uh, files, uh, from and into marketing cloud. So, uh, whenever we are whenever we are, uh, syncing the CRM, like, uh, Salesforce CRM, we can indicate, uh, sales code or service code into the marketing cloud so that we can, uh, get the data from sales and service code. And then we can, uh, do some segmentation, filter the audiences, and we can send send communication to the customers. So by using the automation file drop activity, we can, um, drop files from various cloud, and we can use it. And another way is that we can directly sync those data from, uh, into the marketing cloud, like, synchronize in synchronization data extensions, uh, so that in the detection time, we have values, uh, that are, uh, get from Sales and Service Cloud, that are, uh, connected with the, um, Salesforce CRM. And, uh, how we can integrate, like, uh, in emails today, we can, um, go to that email studio and then configuration. In that, we can see there is an integration, uh, click button. Uh, once we click on that, we can, uh, integrate those cloud, uh, CRM login and password. And after that, it will it will get integrated, uh, uh, into the marketing
Let's take a complex segmentation strategy we would implement in Salesforce marketing cloud. Uh, okay. Complex segmentation strategy, I would say, like, uh, one time I get a chance to work on, um, sending air camera products to some customers so that, um, I have to, uh, get the content from 2 or more days, like, uh, their abandoned cart, uh, details and the searches are dated and the previous purchase details. So, uh, based on this, uh, 3 deck deck section, I have to filter out, uh, 2 or 3 products from the high priority one so that I can recommend so that I can filter those products and recommended to the customers, uh, based upon their, uh, preferences. So it would be, uh, bit difficult segmentation to get, implemented in the marketing tool. And, um, other than that, um, I used 1 automations like, um, I worked on, um, uh, a view called EMEA. It is consist of, uh, Middle East, Europe, and the Middle East, uh, Asia. Uh, in there, I have there are, uh, so many countries, and the countries are having, uh, different language preferences. So in order to send them a bit an email communication, I need to segment, uh, each and every country under their all, uh, under their language preferences. For that, uh, instead of creating 1 by 1, I used the automation tool, um, segment all the all the customers based on the countries and the language difference and store create and store in a new data extension. So it will be it will save my time and also, uh, it will become efficient to process.
Components of SIN classification. Explain what they are used for. Uh, SIN classification is used on sending email messages via marketing tools. Send translation contains, uh, 3 things, uh, central profile, delivery profile, and the can spam classifications. In that, sender profile contains the, um, sender IP address and the configurations of and the header and footer configuration. In delivery profile, it contains the from name from which the email is sent and also the, uh, reply email, uh, it contains. And after that, can spam application can spam classification, uh, which contains 2 type of, uh, emails, uh, transactional and commercial emails. Transaction email does not have does not need to have, uh, the answer to a mechanism or, uh, any other profile center article. But in commercial image, we need to add the unsubscribe mechanism, and they need to follow some of the rules that are provided from the, uh, scan can spam governance so that it will not get, uh, it will get follow the GDPR act, uh, so that, uh, the mail will not get into your, uh, spam folder or something like that. So, yeah, this is the uh
And the common mistake we're taking is for producing, uh, Salesforce market and your strategy our strategy to avoid. Uh, common mistake we can take, like, um, the sometimes the data extension names are, um, that report name will get different. So it is, like, uh, case sensitive so that we can we don't get the desired results so that, uh, we use the attribute tabs in the SQL query or when we are creating SQL so that we can drag the data action and directly use the attribute instead of, uh, writing manually. Uh, it will, um, avoid a common mistake that we are, uh, when we are writing a spell code. And other than that, uh, when we are uh, combining join when we used some join operations in, um, both in in a in 2 2 different data segment, We will make sure, uh, that the book of the days will contains a common attribute so that we can we will get yeah, uh, custom, uh, structurally key as power of reference like, uh, inner join, outer join.
How to set up multilingual dynamic email campaign? Uh, Uh, multilingual dynamic email campaign is inactive. It's nothing, but, uh, multilingual is, uh, preferred, uh, is in a single email template, uh, we can have, uh, different type of messages based on the language preference. Like, if we take in India, we can we need to segregate, like, different language, like, uh, Marathi, Gujrati, Tamil, Telugu, Malayalam. So that we though so based on the customer location, they will get their preference to mail. So how to set up a multilingual dynamic email? Uh, for that, uh, we can add the countries and language preference under the content for a subscriber, uh, should contain their country and their language preference. So, um, the dynamic contents are stored on, uh, different, uh, the like, uh, the English content, Hindi content, Tamil content, Malayalam content are stored on a, uh, different data access. So when you are integrating that, if a customer is in India who is preferred to get a English content, we'll get the English content from the data extraction and will it will get displayed on the email messages or the mobile communications. Uh, based on this, uh, for this, we use transcript to get the multilemic mail dynamic content from um, separate AEs and get inserted into the email
Uh, proposed solution for AB testing. Lifelong's subjecting with the same email Uh, for example, if we, uh, take a campaign like birthday campaign, so we can, um, one subject lines with the normal birthdays. Uh, happy birthday. Uh, you wish you good year ahead. Like, then we can give a subject there. And in another subject, then we use some personalization, like, happy birthday, the customer name. So that, um, we can, uh, test the different type of emails based on some rules or percentage like, um, first 10 10 percentage we'll sell to send on the DIAB testing. Uh, and based on the send, uh, based on the click through rate and the open rate, we will set the set the winner. And the remaining emails will set to the winning winning version of the winning version of the same email in the marketing flow. So, uh, based on the winning ratio, uh, we can schedule the
What happens if we take the day by an email? The bill that is not written and not expected in, uh, marketing. Uh, first, I like to, uh, uh, uh, console each and every attribute that are placed from data accessions so that we I can check, uh, whether the attributes are, uh, fetched perfectly from the data accessions. Like, like, if I use the, uh, where you want the first name, last name, and also email address and, uh, under their location. I want this for them from data extension. I mean, once I fetch the, uh, data extension from and I fetch the data from the data action, I used the HTML tags to get the get this attribute displayed on the email templates. If it is if it is displayed, fine means I will then work on some conditions or, um, some rules, uh, based on the attributes that I get from the deduction. For example, if customer having some membership like golden membership, silver membership, or some premium membership, uh, based on the subcutaneous, we have to uh, render the render the UA. For that case, I will first, uh, check for the status of the subscriber so that it will get rendered and display on the UA. So if it is get, uh, perfectly get displayed and rendered on the UEM, uh, so I then work on the other parts. Like, after that, the based on the standard, uh, state, um, status, what kind of, uh, percentage I have to provide for the customer in the email template. And then I worked on those if and the else conditions on the logics that I worked based on the
Indicate a personalized email campaign that sends out discounts offer based on a customer previous purchase system. It may help you to achieve this in the marketing flow. Uh, Yeah. 1st, I would, uh, I would segregate, uh, the I would segregate those customer, uh, who are all I want to send the personalized email. And then I used the Journey Builder to send those email, uh, to the customers, uh, for, uh, to send a email to the customer for based on their purchase history. So I used the addition speed. Uh, by using the addition speed, if the customer buys, uh, something above, uh, some amount means they will go on different path, and they will get a different type of discount, uh, that are that is added on the email template. And if the customer purchase something that is, uh, below the 1st decision part, and it is above some given amount. So it will they will get into different part, and they will get different type of discount on the email template. And the last 1 is default we can see. And then the 3rd part, uh, the customer will get some, um, 10 percentage of some moment of discount, uh, based on the requirements, and they will get a different discount offer. Uh, this way, we can segregate those, uh, process and messages for, uh, each customers. And other than that, we can say we can, uh, do this thing in, uh, automation as well, like, uh, based on their customer purchase, uh, based on their discount offers, we can segregate them on by using SQL query and create a new data extraction and add those required values like subscriber key name and the previous purchase. And based on the previous purchase points or the amount they have purchased, uh, we added the, uh, discount indirectly in that, uh, new data extension so that we can, um, use the newly created data extensions and send the the email by by using the journey bill by using the journey.
Different type of journey settings, plates, weights, engine. Uh, different type of entry, uh, different type of entity settings in training for, uh, and to enter settings is, uh, reenter anytime, uh, reenter only after existing. Uh, Uh, the reentry only once. Only once it will get to the attorney. It does not get into the attorney. Yeah. Reentry at, uh, really 1 only once will get entered the journey and does not get reentered into the journey again. Uh, reenter, uh, anytime is that if the subscriber is already in the journey, means also the again, the subscriber key will get added into the journey again. Um, and third one is reent only after existing is that, uh, the subscriber will get added to the journey only after the, uh, subscribe that is already in the process of the journey builder will get access to from the what are types of space? In journey, we can have, uh, decision split, random split, uh, frequency split, engagement splits, um, Einstein H2O speeds. These are the splits we have. Distance speed is, uh, worked based on the decision, the rule that we have, uh, given on the split. Standard split splits the customer based on some issues like 50, 50 percentage, 40, 60 percentage. Based on that, we can split those customers and send them 2 different emails. Uh, frequency split is, uh, splits based on the frequency of the email, like the open rate or the, uh, click through behavior from the customer. Like, based on the frequency, it will get a split. Engagement split is also, like, the open issue under the click click click through ratio based on this. The customer path will get split. What are types of waits in journey? Is wait by duration, wait until sometime, wait by attribute, uh, normal wait. Uh, these are the, uh,