Speaker 0: Who are joining for the first time in your first session, welcome. Uh, excited for you to be joining in on more dreaming. For this session, I would like to introduce you to our amazing speaker today, Timothy Zider, who will be providing some great insights on how to design and build custom journeys in the marketing cloud journey builder. So go ahead and take it away, Tim.

Speaker 1: Thanks, Chris. Uh, welcome, everybody. So I’m Tim Zider. I’m, uh, I work for Cervelo. We are a marketing cloud Salesforce partner with Salesforce and, uh, build out automated solutions for clients. So thanks everybody for taking the time this afternoon, especially on a Friday afternoon, to dive into Journey Builder. So let’s get started. So today, we’re gonna do a quick overview of our case study that’s gonna frame our build. We’re gonna go through a cup through a couple of MarTech tools, dive into our Salesforce CRM environment just to look at the setup there, and that’s gonna set up our build in, uh, Journey Builder. We’re gonna cover three different areas of Journey Builder, the entry event, two different ways, some canvas activities, decision splits, and object activity, and then more final, we’ll go through the content itself. We’ll leave our q and a session at the end of the demo.

Speaker 1: So digging into our case study, um, so so we’ve got Cervelo Bank. They’re looking to grow their commercial banking business. They’ve invested in this all out marketing blitz that has generated a ton of leads, but they’re just not seeing the client conversion on the back end. The problem is that sales is swamped. You know? They they don’t have time to follow-up on these leads. They’re unqualified. They don’t trust them. By the time they follow-up on them, they’re cold and they’re not productive. So marketing’s got a a they want an automated solution to solve that problem to qualify those leads and help with bottom funnel conversion. So they’re looking for four areas for this solution. One, they want a a solution that ranks and prioritize those leads in easy to understand it buckets. Two, they wanna nurture those leads. Three, they wanna notify sales when they’re to follow-up on those hot leads, and they want an always on solution, something that’s automated.

Speaker 1: So digging in with marketing, we put together this flow that goes through the two platforms. So here’s in sit in the sales cloud is where the leads are being created or uploaded by marketing. And here’s where we’re gonna wanna fold in that ranking system, not only from the lead standpoint, but also from the account standpoint as well. Once those leads are fed into marketing cloud, we’re gonna want to send them down three different paths based on that ranking. A hot path where we’re gonna wanna create a task for the that lead owner, and then also send them a hot lead notification that gives all the details about that lead. If you’re in a warm lead, we’re gonna wanna send an email to that lead to try to get that first sales appointment. If they engage with that lead, they’re gonna be fed up to the hot path. If they don’t, they’re gonna be fed down to our classic nurture path, our cold path, where they’re gonna be served up a variety of different marketing experiences. Those are emails. But before each email send, we’re gonna wanna make sure that that lead is still open based on the CRM environment.

Speaker 1: So to pull in our ranking solution, we’ve brought in two partners, uh, today, uh, to help build out that solution. So SalesWings is a fantastic lead ranking solution that right that allows you to to populate that lead ranking score right in the CRM environment. You can see it here down here. There’s a simple hot, warm, and cold. It’s based on intent tagging and a variety of different variables that we won’t go into today, but we’ve got Jeffrey Polley from Sales Wings in the chat if you have any questions throughout the presentation related to Sales Wings. We also wanna bring in Demandbase the top account based marketing, um, solution as well, where we’re gonna be gathering all this engagement metrics, not just on the lead level, but on the account level. How that account is being interacted by all those leads and contacts across the board, and bubble that up to a single tier ranking, uh, field, whether that’s gonna be tier one, two, or three, hot, warm, and cold as well. We’ve got Tara Quell from Demandbase in the chat if you have any questions related to Demandbase as well.

Speaker 1: So taking those two ranks, we wanted to put together a simple matrix for our presentation today. So if someone has a hot lead score from SalesWings and they have a tier one hot score from a demand base, we’re gonna rank that lead as hot. We wanna send them down the path that notifies sales immediately. If that if that, uh, lead has a hot rank lead, um, rank, but has a lower account score, then they’re gonna go down the warm path. Same thing for a warm lead with a top account lead, a warm path as well. Again, we wanna push those leads to drive, um, for that first sales meeting. And then all other leads will be in a cold, um, status cold ranking.

Speaker 1: Our last Martech partner is DE Select. I mean, at the heart of every marketing automation solution is, uh, you know, a complex SQL query, the real engine of the solution. And what d e select does is give you the ability to create those complex queries with clicks, not code, create them quickly and easily, make those modifications without knowing the SQL code. Um, so we’ve got Danny Kopack from DE Select in the chat as well if you have any questions related to DE Select.

Speaker 1: So let’s dive into the platform and, uh, go right into the Salesforce CRM environment. So here we are in Salesforce. Let’s go into the lead tab, into the lead object. So for this demo, we’ve got three different leads set up. We’ve got a hot, warm, and cold lead. Let’s click into the lead itself and just take a look at the details. Um, just like with any object, there are some basic information that’s provided outside of the, um, out of the box. But here’s that predictive score that we talked about from SalesLakes that we’ve got incorporated right into the lead object itself. So we’re gonna be using that throughout the solution. I also wanna call it this hot lead field. This field we’re gonna use to populate from our lead nurture solution to fire a hot lead notification to the owner of this lead. Um, let’s go over to the account tab and take a look at accounts as well. Again, we’ve got some accounts set up for this solution. And just like the lead, um, object, there’s some out of the box fields that are provided um, for for any account. And then here’s all the great detail that’s provided by Demandbase. Engagement minutes, engaged contacts within that account, all bubbled up to this account tier that we’re gonna use for the demo today. Here here we have an account that’s tier one hot.

Speaker 1: Before we dive into Marketing Cloud, I wanted to show you one section of CRM that’s always good to get familiar with. As we are gonna be creating a task, we wanna know what the settings are for that task object in the CRM environment. So we’re gonna go to object manager. We’re gonna look for the task object. We’re gonna go to these page layouts, and this is gonna tell us what fields that are required by the Salesforce CRM environment in order for you to create a task in the Marketing Cloud side. And those are all designated with these red stars. So we’re just gonna wanna make a mental note. When we set do our settings in the journey in the Marketing Cloud environment, we wanna make sure that we’re covering all four of these fields.

Speaker 1: Alright. So let’s jump into marketing cloud. We’ve got our journey set up, our lead nurture journey. Let’s take a look at what this is doing. So we’ve got our three paths. Here’s our hot path. It’s coming through. We’re gonna be creating a task. We’ll be going through that later. And then updating the lead just to fire the hot lead notification. We’ve got our warm path. Here’s that email that we’re going to send to try to get them to talk to sales. So if they engage with that email, they’re gonna get fed back up to the hot path. And then we’ve got our cold path. If that if that person engages if if they don’t engage, they’re gonna get fed down to the cold path or that traditional lead nurture path where they’re being fed, uh, different email communications and checking for that open status before they get sent those communications. Let’s hop over to the hot lead notification journey. So this one’s relatively straightforward. All we’re doing is sending to the owner of that lead an email that Hot Lead Notification. So we’ll go into that in a little bit more details in a minute.

Speaker 1: So let’s talk about the first section, um, so for the most important part of of, uh, of any journey and that’s the entry event. So what how are we pulling in those leads from the Salesforce CRM environment? So in this journey, I’ve got a draft open. Here you can see we’re on version 20. What I’m gonna do is I’m gonna remove this data extension entry event so we can recreate it and just walk through that process. So because we have an automation set up, we are creating a data extension that has those leads We’re gonna feed into this journey. So what we wanna do is we wanna click in that data extension. We wanna find that, uh, data extension that we’ve set up to that automation. So I’m just gonna select that data extension here, and we’re gonna hit summary and select that button there. When we select that, a schedule button pops up or a schedule block. We’re gonna click into here. We’re gonna connect it to that automation that we’ve got set up, um, in the back end. And so here it is, that automation that’s already created. We’re gonna select summary. And here we’re gonna, um, so so let me select that automation, select summary. And here’s our last step is we’re gonna wanna select how those records are gonna be evaluated upon entry. We recommend using the evaluate new records only. It’s a little bit more, um, more performant. And then for this example, we’re gonna use only new records added after journey activation. So clicking on that, we are should be all done to set up that automation, and there we go, uh, for that entry event.

Speaker 1: But that’s really just the beginning of it. That that’s just connecting that data extension. Now we need to dive into how are we creating that data extension. And to do that, let’s dive into the query back in marketing, uh, Automation Studio. So let’s take a look at this sample query. What we’re looking to do is we’re looking to pull in those leads from the Salesforce CRM environment, and that’s where this from statement in the SQL query is doing. So this lead underscore Salesforce is a synchronized data extension. So so what is a synchronized data extension? If you have the Marketing Cloud Connector, um, you’ll have access to synchronized data extensions. They get automatically created. You sync them over. Here are all of the objects that we have in this instance. So any object that you wanna bring over, you just synchronize over into the Marketing Cloud environment. So let’s click into the lead object. And here we’re seeing all of these fields that are available. You can sync over any field from the object over into the Marketing Cloud environment into the Synchronized Data Extensions. Take a look at these records. I I mean, here’s all that data. Look at all this amazing data. This is all being populated from the object in the Salesforce CRM environment, and it’s synchronized every fifteen minutes. So it’s real time data within that fifteen minute period. So going back into this, um, query, here’s that lead synchronized data extension. And these are all those fields we referenced that we’re gonna wanna populate. That’s what this select statement is doing. It’s populating all these fields into a date extension. So, for instance, we’re gonna wanna pull in that lead ID and use that as a subscriber key or that unique key for each email. We wanna pull in the email address so we can send them the email. This first name we’re gonna use for personalization. Here’s that SalesWings predictive score we’re pulling in as well. We also wanna pull in this, uh, uh, demand based account tier score as well. So to do that, we have to join the account synchronized data extension to the lead in our from statement, and that gives us the ability to populate that field there. Um, the last part of the query is a where clause statement. It just gives a filter. We don’t wanna pull in all leads. We wanna pull in leads that have a status of open, and then we wanna because we’re gonna be running this on a, um, on an hourly basis, we wanna pull in those leads that have been created within the last hour. So you do need to need do need to know a little bit of SQL here in order to use this date add function and the different syntax that’s required here.

Speaker 1: So this really sets up how deselect can make this a lot easier. So let’s click into deselect and take a look at how this similar query can be set up in their environment. So at the at the first screen, when you select a selection in the selection criteria, you’re gonna be setting up the from statement here. The great thing about this platform is they’ve got all of these data extensions here that are available in your environment. You just literally just bring them right over, click and drag them in. What’s really cool is this, uh, ability to link the two data extensions just with clicks. So for instance, I wanna link the lead synchronized data extension by the company name. All these fields are available. Just click on it. And I wanna associate it with the name of the account. I mean, really easy to set that up. Click Snowcode. Down here is that filter section or that where clause in that query. And, again, same thing. All the fields from both of those objects are here. You can just take a look at those. You drag them, draw and drop them over. You don’t have to use SQL. You can use select the calendar date. Very easy to do. Uh, clicks not code.

Speaker 1: In the second section, this is where we’re gonna be defining all of those fields that we wanna populate in the data extension itself. So just like in the the, um, the screen before, here are all the fields for the lead. Here’s the fields for the accounts. You just drag them over. And as you can see for the solution, we’re bringing over quite a few fields, uh, to populate the solution. Here’s that predictive score from SalesWings. Here’s that account score from Demandbase. Um, so super easy to do that. So one thing that we’re gonna be also doing to make this solution a little bit more simple is that we’re gonna aggregate both the SalesWings, uh, ranking and the Demandbase ranking into one ranking, this lead ranking symbol. So Demandbase excuse me. Deselect has this great tool, this custom value tool allows you to consolidate those two fields into one new field. So all you do is click in here, and you just set up your your requirements. So I wanna set a HotRank to somebody who has a SalesWings predictive score of Hot and an ABMT score of Tier one Hot. And it’s as easy as that. So here’s gonna consolidate those two fields down to a single field that we can drive our solution. The best thing about DE Select is you click run, and it creates the date extension and the query for you. You don’t have to do a thing. Super amazing.

Speaker 1: Let’s click into the date extension that was created. All these fields, uh, that we just selected. Let’s go into the data. Here are those three, um, leads that we’re bringing over. And I just wanted to point out that Lead Ranking Simple field that we had created. So here’s that field, those three different rankings. That’s a combination of that SalesWings predictive score and the ABM tier score. So all we have to worry about is this one field when we go into our our automation and feed that into our journey.

Speaker 1: Alright, let’s go over to the automation and take a look at, uh, what we’ve got going here. So we need to attach, uh, the, uh, query to the automation in order to feed that date extension into the journey itself. So when you create an automation, you’re gonna wanna schedule, in this example, a scheduled, uh, automation because we want this to be running every hour. And then all you do is just drag over the SQL query activity onto the canvas. You select the query that Deselected created for you. Once you’ve connected to an, uh, the journey, this journey entry, uh, activity will pop up automatically. So what we’re gonna do is we’re gonna pause this automation for now because we’re gonna be running this manually to feed in those leads into the journey itself. So let’s go back into Journey Builder, and there it is. That’s the end to end process of how to set up a data extension entry event, uh, for that use case, both in Journey Builder and in Automation Studio.

Speaker 1: So I wanna hop over to our hot lead notification journey to show you a different way to set up an entry event. This is gonna be an entry event that’s pulling in data directly from the Salesforce CRM environment. So in this journey, I’ve got a draft as well, which we can just go in here and delete this with no harm being done there. And we’re gonna bring over our Salesforce data entry event. So let’s click into that, and we’re gonna select Salesforce data here. So when you do this, you’ll have access to every Salesforce object. So we’re gonna be looking for the lead object to pull in. Um, whenever a lead is updated with a certain field, we’re gonna send them through a hot lead notification to the owner of that, um, to the owner of that lead. So all we do is select the lead object. We’re gonna select that here. And here’s where we’re gonna select the audience of who this this, um, email is gonna be going to. So So you can either send it to the lead itself, but for this use case, we’re gonna send it to the owner of that lead. So we’re gonna select the owner. You’ve got two options here for the subscriber key. For this use case, we’re gonna use the user ID as a subscriber key. So there’s our audience, the owner. And here’s where we’re gonna select that field that we only wanna pull in leads sent to this owner that have this field, this hot lead field. Here it is. We’re gonna drag that over here. And whenever they have this hot lead rank, uh, Syntex, sent hot lead email, select that there, and there you go. So whenever that field is updated for a lead to sent hot lead email, that’s signifying, hey. This lead is ready to be contacted by sales. It’s gonna be sent an email to that lead owner. The next section is filter criteria. You can add in a layer of complexity to bring in other objects like account or contact if there’s other fields that are dependent that you want to pull that over. But for this use case, we don’t need to do that. And then the last part is how to select all of that great data that we’re looking to personalize in the email itself. So for instance, we want to bring over the company name for that lead. We wanna bring over the email address in case that rep wants to reach out to the email. So it’s simple easy just to click. Here’s first name, full name, and then all you do is, um, you can see those being populated here, those field these fields that you’re selecting. Select next. And then this gives you the summary of what you’ve just selected here. So this, again, this is going to whom? This is going to the owner of the lead, the lead object. And it’s gonna be, um, sent and be brought in whenever a lead has a field, this hot lead field populated with sent hot lead email. And these are the fields that are being populated.

Speaker 1: So let’s go over and take a look at the data extension that gets created whenever you activate this type of journey. So here are all the fields that we wanna populate based on the selection that we did in the journey itself, and let’s take a look at the data as well. So here’s all that data get that gets passed. Again, this is just coming from the lead itself, all those objects, uh, directly as soon as that lead gets created. So it’s, uh, another way that the Salesforce, uh, uh, entry event creates this date extension for you automatically.

Speaker 1: So let’s go back to the journey. What we’re gonna do is we’re going to refresh this journey, um, just to clear out the changes that we had just made. Let’s go here to the the lead nurture journey. We’re gonna clear this out as well, and we’re gonna activate the automation and send those leads through and get some emails being sent. So we’re gonna come into this automation. We’re gonna run this once. We’re gonna select all these activities. It’s gonna run the query and, uh, send those hot leads through to the journey itself. You can click on the activity tab and see, um, see it running. Sometimes you have to based on Salesforce time, you have to see there it goes. It’s doing its work.

Speaker 1: So let’s go back into the journey itself. While that is is happening, let’s take a look and do a deeper dive into the the different, uh, activities outside of the entry event. So our first stop is gonna be how to create, uh, a task and update a lead in the Salesforce CRM environment. So here in Journey Builder, there’s a bunch of different activities that you can use to do that. You can see that, uh, if you wanted to create or update a lead or a task, they’re right here. We definitely recommend using this object activity as it’ll work for all objects, and it’s best it’s best practice. It’s the most reliable. So all you do is drag that and drop that over here in the Canvas. Um, but since we already have one created, let’s dive in and see how this is being built. So the first step you’re gonna wanna do in the object activity is to find the object that you wanna update or create. So we’re gonna be selecting task for this. We’re gonna be creating a new one. And then here are all those fields that we’re gonna look to populate in the task, again, based on the setup that’s in the Salesforce CRM environment. So let’s say, okay. I wanna assign this to to whom you go and you click on the pencil, and you wanna send this to the owner ID. So, fortunately, that’s one of the fields that we have populated here is that owner ID. So just give you an example of how that gets populated. You select that field in the data extension and creates this handle bars, uh, code here right in the in the platform. Let me give you another example of that. So down here in the subject, what we wanna do is we wanna populate to the the owner a message that says, attention. You have a hot, warm, or cold lead using this customization, and it’s for this company. So to do that, you have to do a little bit of workarounds. Let me show you how that’s done. So we’re gonna copy this static code. We’re gonna drop it into this, um, notepad. It’s other static code, and let’s copy that. We’ll drop it in this notepad as well. And then let’s click into, um, to into the settings. So let’s find that lead ranking simple field in the data extension. There it is. And it creates that handle barcode. As you can see, it replaces what was ever there before. So you kinda have to do this one at a time. So here’s where we’re gonna wanna put in that that ranking there. And let’s go back in here. Let’s find that company field. You see, again, a different code pops up there. Let’s copy that in here, and then we’re gonna paste that in there. And then you just copy this entire blog, and you paste it in this section. And there you go. That that’s how you can populate, personalize a field with multiple variables in there. So we’ll cancel out that. And, um, so then scrolling down through here, just like we looked at in the Salesforce CRM environment, we needed to make sure that we populated, like, the priority field and the status field just to make sure that we’re doing that so that these, uh, these tasks will be created in the CRM environment. Click next. It gives you an overview of all those fields you’re looking to create or populate and then the, um, the data that you’re looking to populate in there. And that’s it. That’s it. That’s how you set up an object activity for creating a task.

Speaker 1: Let’s, um, let’s just refresh this journey and see what’s going on. Hopefully, we’ve got some people coming into the journey, those leads coming in. Yep. And so here we go. Let’s go back to um, so yep. So we’ve got some people coming into the journey itself. You can see that, um, there there we’ve got, um, some records coming in. And, uh, this was a prior run journey where, um, I had one person coming through the warm lead and they actually have come through again. So let’s go into the my email and see if I’ve received an email. Yep. So here’s that warm lead. Let me click into this email. I wanna, uh, click in here to see if we can get this lead to move up to the hot path. So we’re gonna click in there, and, hopefully, we should see this two move up here and create this to be a four, uh, with the leads coming in here.

Speaker 1: So let’s dive back into the taking a look at the object activity for a lead updating functionality. So here we go. Let’s dive in here. So the first one we first object activity, we created a task. Here, we wanna select the lead, and we wanna just update a single field in that lead to send a hot lead notification. So here we go. Here’s the lead ID that we’d wanna select, and then we wanna select, in our case, in the journey itself, the subscriber key is the field that we want to, um, to designate as that lead ID. We click next, and then we wanna find that hot lead field here. Here it is. Here’s that hot lead field, and then we’re just gonna put in that static value sent hot lead email. So that’s that’s all done there. You hit next. Again, it gives you the summary of that field you’re updating and the value that you’re updating it to. Okay. So let’s cancel out of that.

Speaker 1: And then let’s go into that hot lead notification. I should have received one. Here we go. Here’s this lead is ready to talk. Let’s click into the email that I did receive. So here’s all that data that we saw in that data extension that came through that lead object. In addition, we’ve the way we set this up is the lead ID is clickable. So if you click on this lead, it should take you into the CRM environment to that lead itself. So quick and easy for the salesperson. They don’t have to go and copy that code and go in the CRM environment, uh, just with one click. And here’s that task that we generated, um, from the journey. So if we click in here, here here’s that attention. You have a hot rank, uh, for this company Kearney, personalized, uh, task using that, um, those that that solution. Let’s dig into the lead itself. And here’s that sent hot lead email field that is now populated as we saw it was blank before. So that’s what’s triggering the hot lead notification on that end.

Speaker 1: Alright. So let’s dive back into this journey. Let’s refresh this, um, the the counts and see if we’ve got, um, this hot lead path brought up to the warm path brought up to the hot lead. And still taking its time. So it’s still it’s still deciding upon it. So that should change to a two, and that should change to a four in a minute. So while we’re waiting for that, let’s go to our Hotly notification and see what’s going on there. We should have received at least one. I think I had started out with two here. So, yeah, now it’s three. That’s the email that I received, uh, just now, uh, for the test.

Speaker 1: And then the last part we’re gonna wanna dive into is the email content itself. So let’s click into the email content for both of these journeys, and we’ll take a look at what’s going on in the background for the email content itself. Okay. So let’s this is the hot lead email. Let’s take a look at the email itself. I’ll go preview and test this email. Okay. So to preview this email, let’s select the data extension that is being fed by that hot lead notification journey. So we’re gonna scroll down and find that date extension. Here we go. And we’ll just select the last lead that last hot lead that was, uh, created so that we can see here’s all that data being populated. Here’s that link. So I wanted to show you was how we set up this, um, this link, uh, that goes directly into the the lead in the Salesforce CRM environment. So to do that, let’s take a look at the URL that we clicked on. And as you can see in the URL in the CRM environment, there’s that lead ID right embedded in the URL. So what we wanna do is copy this URL, and let’s go back into the the email content itself. At the top of the email, I’ve got this code snippet that does this work, which basically what we wanna do is we wanna take that same URL, and we wanna cut it up into three pieces. So here’s the first part of that URL before that lead ID, and here’s the last part. And this concat function is sort of combining all three of these parts into one URL. And so to get that lead ID, we’re setting it up here. Here’s that lead ID that’s set based on the field that’s being populated by the data extension. And that’s how that works. You’re just gonna be recreating this URL, dropping in that custom lead ID for each time that it gets set. And then to render this in the, um, in the email itself, let’s go down over here and take a look in the HTML content where that’s being rendered. So here’s that variable, that at URL that is being redirected to when they click on it’s an a tag here, when they click on that lead ID. So that’s how it’s working, um, in the Hot lead notification.

Speaker 1: Let’s dive over into the, um, the email content for the nurture emails and take a look at what’s going on here. And, again, I’m gonna have to select that data extension for the nurture journey. So let’s go here. We’re gonna select that data extension, and that’s under here, under this folder, and let’s select this final. And then let’s select the warm lead here. We’ll select that. And, um, let’s go into the content to show what’s going on here. So I’ve got some basics personalization up here where we’re rendering the first name, and that’s that’s pretty easy. Just do the percent percent. The first name is the value of that first name field in the date extension. We’ve got a two different dynamic content blocks here. Here’s the first dynamic content block. It’s rendering different content based on the product that we pulled in that DE select statement, uh, DE select data extension. So if they have four zero one ks, they’re gonna get four zero one ks product or credit cards. The the second dynamic content block, it’s rendering a special call to action message that’s gonna be more offer focused for any lead that is either got that lead ranking simple as a hot rank or that lead ranking simple is a warm rank. And then the last block I wanna call out is this, um, custom signature block where it’s going to render the name, the phone number, the the email address, and the title for the owner of that, uh, of that lead, personalizing that. So let’s just take a look at how that is set up up in this code snippet. So what this is doing, it is pulling in the owner ID from the data extension. That’s what we’re being populated from the DE select, uh, query. And it’s doing a lookup to the user, um, synchronized data extension in in Marketing Cloud. So the user has all of that owner IDs information, their name, their phone number, etcetera. So if it finds that owner, um, um, in in that user synchronized data extension, then it’s gonna associate these values, name, title, email, and phone with that record. If it can’t find it, it’ll use default values, uh, as well. So there’s a consistent experience there. So let’s preview and test this content and see, um, what we’ve got coming here. So here’s that first name that’s being populated there. Let’s scroll down and take a look here at, um, so here’s that product. They selected credit card processing. You can see the credit card content coming through here. Because they are a warm, uh, a warm rank lead, they’re getting that special call to action button that we’re driving them to to get that first sales appointment. And then, uh, here’s that that custom signature panel that’s rendering, you know, I’m the owner of that lead. So that’s rendering my name, uh, title, phone number, and email address there. Um, so that’s it on the content side.

Speaker 1: Let me jump back into my deck and, um, just do a quick recap. So, hopefully, that gives, uh, a good overview and and gives a solution that accomplishes those four things that we’re looking from from our our marketing partners. One, we found a way, thanks to SalesWings and Demandbase, to rank those leads and using d DE Select to put them to easy, uh, easy, um, buckets. Second, we’re able to nurture those leads with an automated, uh, journey. We’re able to notify sales using that hot lead, uh, notification, and we’ve built an always on solution that is automated. And then within Journey Builder, hopefully, we’ll give you a good overview of, uh, the entry event, two different ways, both a data extension and that Salesforce data entry event. Those key activities, those decision splits, object activity, and hopefully a little bit of a dive into content itself. So that wraps up our presentation and, um, I’ll stop sharing and pass it over to Chris.

Speaker 0: Alright. Thanks, Tim. Uh, that was that was a great session. Learned a lot of good stuff in there, uh, things that I never knew you can make so easy inside of Journey Builder. Um, so we’ve got about ten minutes for some questions and q and a. So feel free to throw those into the q and a chat, and we will pull them out. Uh, I see we’ve already got a couple in there. So let’s go ahead and, uh, share this question from Kim. Uh, in the example of sending the email alert to the lead owner, does the lead owner need to first exist as a subscriber in SFMC?

Speaker 1: That’s a great question. And and no, it does not. It’s, um, as long as that is being, uh, synchronized over, um, in the the Marketing Cloud environment, um, if you it it should work, uh, when it’s being sent. It will create it as a subscriber when that is is being sent to that user ID will be the subscriber key and the email address. So so no. It does not need to be a subscriber in Marketing Cloud first.

Speaker 0: Okay. Great. And one more from Kim. Uh, can you explain again why it’s better to use the object activity item to create a task versus using the task item within the journey?

Speaker 1: Yeah. Great question. And it’s it’s something that we’ve, you know, seen within the in in the community that I think those, uh, task or lead, uh, activities were the first iteration from Salesforce. And that objectivity activity, I think, is the new Force. And that objectivity, I think, is the new the new version of that functionality. Um, so I think it’s just recommended. I think it’s more supported to use that object activity versus the versus those individual activities. I think the these individual activities might actually go away at some point. It’s also a little bit easier to support if you’re looking to document a process within your team and you’re looking to do, um, you know, set up that activity, if you’re following the same process where you’re documenting this object activity, so whether you’re creating a lead or a task or a contact, it’s always the same process. You bring out for the object activity. You create the you select the object at that point versus, uh, documenting for this is the task, uh, activity. This is the lead activity, um, might be helpful from that standpoint as well.

Speaker 0: Awesome. Awesome. Uh, we’ve got another one in here from Jenna. Uh, are there pros and cons to using the data extension entry source versus the method that pulls directly from Salesforce?

Speaker 1: That’s a great question, and it’s something that we, uh, work on all the time when we’re trying to find solutions for our clients. I mean, ideally, you’d wanna pull it from the Salesforce, uh, CRM environment, use those Salesforce data entry events, uh, because it’s just in time. Right? As soon as that lead or any of those objects get created, boom, they get pulled into the CRM environment. Using an automation, the the fastest you can get it is, you know, they run hourly. And you can put a wait step in so you can run it every 15, um, but there is that time gap. So there’s definitely benefits from the Salesforce data standpoint from, uh, a speed standpoint. But as you can see from the query that was created, uh, and also especially from d e select the d e select tools, The ability from a query to access a variety of whatever combination of synchronized data extensions or data points within the CRM environment, that’s where you’re gonna wanna lean to an automation fed journey. So in our use case, we were looking to pull in, um, lead fields and account fields for that lead nurture journey. Could you do that with, uh, the Salesforce data? You probably could, But sometimes the there is you’ll you’re sort of, um, relegated to the way that’s set up in Journey Builder. Whereas with a query, you’ll have full control, full visibility, and you’ll be able to see that data output. So I would use those in a combination. Definitely, um, you know, consider both options. Um, but if it gets a little bit complicated with that Salesforce data, I would definitely lean to the data extension query automation that based FedJourney side.

Speaker 0: Alright. Great. Great. Are there any other questions that people want to ask? Feel free to post them into the Q and A chat. If they’re already in the chat, we can answer them there. If there’s any questions for, uh, Tim’s guests, uh, we can we can certainly, uh, try and answer those as well. Alright. Well, if there’s no other questions that we have today, that’ll that’ll conclude today’s session. Um, thanks again for joining us, uh, and a special shout out to our sponsors for their support. Uh, without them, MarDreamin, it wouldn’t be possible. Um, so make sure that you pop over into the sponsor booths to learn more about what they all do, uh, and and to see what they can offer. Um, we have a lot of great sessions still left today. Um, the next one in this channel is gonna be how to deploy data for success, scale, and customer experience, and that’s gonna be coming up in just a few minutes. Uh, otherwise, if you wanted to check out some of the other channels or some of the other, uh, pieces that we have, head over to the agenda and check out the full list. Uh, so with that said, thank you again, Tim, for a great presentation on Journey Builder. Thank

Speaker 1: Thank you, Chris. Thanks for all the help, and thanks for everyone attending. And thanks for the partners that joined us on the call as well. Appreciate it. Alright. Thank

Speaker 0: you all, and have a good rest of your day.