Speaker 0: Session where we’re talking about how to bring Pardot capabilities into Salesforce flow. And, um, just some housekeeping things, if you have any q and a, please post them in the q and a tab, um, above the chat. And then, um, if you’re wanting to change sessions, um, you can do that below as well. Um, I’m gonna introduce you to, um, three great guys, Mike, um, Adam, and Jacob, and they’re gonna take over from here. Um, so, yeah, jump in and ask any questions you have along the way.

Speaker 1: Alright. Well, thank you everyone for joining us today. Um, let’s get started. So, uh, as Jenny mentioned, my name is Jacob. I’m here with Mike Kruser and Adam Mercedel. We are we’re here to kind of talk through some of our, um, a new solution. We’ve, uh, created flow actions for Pardot. So I am a prod the product manager for Circante Labs. Um, so Circante Labs, just as a little bit of background, is our in house solution for building custom apps and integrations to better connect Pardot with other systems and just kind of enhance what’s already there. Um, Mike is our partners Pardot partnerships and API integrations lead. So he’ll be kind of going through a demo of this solution with us. And Adam is our VP of technology who created this solution. So really excited to go through a little bit of technical, a little bit of high level, and get started with this. So before we go too far into this, thank you to all of our sponsors. The demo jam this morning was wonderful, and we really appreciate everyone, uh, to support this event. Um, we’re really, really excited to bring a marketing focused Salesforce event to the community. Alright. Um, so high level, we wanna go into this again from the top. When we look at MarTech, uh, solutions and when we talk about Circante Labs and whatnot, again, we’re trying to enhance, uh, what we already have. There’s a lot of solutions out there that you can use in your MarTech stack, um, from advertising, content, social, um, data cleanliness, data management. Uh, there’s a lot you can choose from. Um, if you go to the next slide, um, what we’re seeing is that on average, there’s about, uh, organizations that have about 12 MarTech solutions in their tech stack. Um, however, I’ve worked with the orgs that have about 30 in their tech stack. But we also have, um, commonly about 12 of those solutions or 12 solutions that you have have some sort of efficiency impacting issue. Um, also a lot of times you get a system and it says, hey. We integrate with Pardot. You should download us and purchase us. And you get it because you’re really excited and then you learn, oh, wait. It doesn’t integrate with directly with Pardot. It integrates with Salesforce, and I have to rely on that Salesforce to Pardot integration to get done what I need to get done. Um, and while that Salesforce to Pardot integration is really, really cool, um, it’s sometimes a little bit lackluster. So on the next slide, uh, we talk about there’s a lot of ways that you can enhance either the Pardot to Salesforce integration or just really any integration with Pardot. Um, you have custom code, which is something that Adam and Mike are amazing at. There are SI partners, so Sercante Labs being one of them to help work with you to create and build said custom integration. Um, and then there’s ISV partners who create solutions and post them in the app exchange, and then they’re managed packages that you can purchase without having to have a contractual agreement with a SI partner. Um, so on the next slide, we wanna understand how can this API help me. How can we better connect and use Salesforce to Pardot and get them to talk better to each other? So just like any other integration, Pardot has an API that can communicate with Salesforce and other systems. That Pardot API has had leaps and bounds of upgrades with the v five v five API, um, connector. Um, they’ve talked about that in the different in the road map conversation yesterday. So if you wanna learn more about that whenever the event’s all said and done, you can go back and reference the recording. But within this API coverage, we can look at prospect management, segmentation, content management, so things like custom redirects and referencing email templates. Engagement reporting, I’m not gonna really highlight the organization and domains and account and user details because it’s a little bit more getting an org created kind of thing. But the thing that we’ll really dive heavily into in the demo today is gonna be external activities. We’ve talked about this in a few sessions throughout Marge Reaman, but external activities are gonna be really, really important for us in the long term of Pardot as we’re trying to find new ways to get integrations that don’t always have that in your face integration existing. So on the next slide, at a high level, what we’re looking at with this is we’re seeing that with connecting from the, um, v five conversation, we’re able to pull in content components, prebuilt content, as I said before, pulling in different apps as well as content from Pardot and pushing them into the system from Salesforce using that API connector. And then from there, we can track external activities, external actions inside of Pardot and through engagement studio programs. So that’s gonna be one of our demo use cases we’ll highlight later on in the session. So to get started with this solution, it’s really easy. So the first thing we have to do is creating a connected app. So the reason we do this is because it’s best practice and our recommendation that whenever you’re gonna have some sort of API integration between the system, you have a connected app and a unique user for that integration. You could theoretically use, um, one user and one app to do a lot of the things. It’s just not recommended because it could cause a lot of issues when you have overlapping systems talking from different platforms. So we create that connected app and make sure you have the ability to log in with the API through that connected app. We’re gonna talk through where to find some of the API documentation and how you you can use Postman to understand how the API pulls data from the systems and how it’s populated. And then finally, the thing that you’re most, uh, you’re more you’re here for for, again, the click not code solution, how to use flow actions for Pardot and build a flow using this solution. So it’s demo time. So we’re gonna go through first and talk through browsing the API docs. We’re gonna talk through of getting started a little bit with Postman, and then we’re actually gonna dive into a few use cases with flow actions for Pardot. So without further ado, I’m gonna turn it over to Mike Kruser and Adam Marcell.

Speaker 2: Thanks, Jacob. So like Jacob said, documentation’s good place to start. The documentation for the Pardot API is at developer.salesforce.com, and we look for, uh, Pardot and get started. And we can see that there’s a lot going on on this left column with all kind of options. Um, version three, version four, we’re not concerned about that anymore. We’re gonna focus on version five, and we can see scrolling through this, we have a lot of options. Basically, everything that exists in Pardot or nearly everything that exists in Pardot, we see we have available here, uh, in the the API. And we can see in this right side contents kind of the different subcategories of classes of of what’s available within that object. So picking something easy, custom redirects. Right? I can see custom redirects. I can create custom redirects, update them, delete them, and query search for them. And looking at the documentation, it shows me things like a URL that I can use because this is a REST API that’s URL based, and how I need to, uh, ask the the right questions to, uh, to use this API, what fields are expected, and so on and so forth. Normal API stuff that we see. So to use this, I like using a tool called Postman. Postman is is like a web browser, but for APIs. It’s it’s a code tool. It’s a geek tool. Uh, it’s a good place to start. And you can see I’ve got a bunch of different APIs that I work with. This part of API, this is a a collection. It’s a group of API connections that, uh, Circante has actually put together. It’s available at Circante Labs. And you can see that this is structured very similar to how the documentation is laid out because I use this for a learning tool, and I kinda wanna be able to jump between the documentation and testing, trying things pretty easy. So we’re gonna look at custom redirects, and I want to create a custom redirect. And when I click on create, you can see that it opens up a a tab, and we can we can do stuff. I wanna create a with the name, custom redirect API. I have a destination URL campaign and a tracker domain. So I’m gonna I’m gonna click send. I’m gonna I’m gonna do this API thing. And I I I get an error. Access denied. Oh, logins. I need to be logged in. So like Jacob said, we need to create that connected app. I’m not gonna show how to do that. That’s a different demo, uh, different, uh, there’s documentation how to create it. But with that correct connected app, I need to be able to log in. So I’m gonna go over to my login tab, and I’m gonna see that I’ve got a lot of the stuff set up, and there’s a, uh, permissions up here where, you know, those details are stored. And I’m gonna click send, and it’s gonna log in for me. And I could see that I get an access token and stuff like that. So now if I go back to my customer redirect and I click send again, I’m gonna get a I’m not gonna get a custom redirect. Darn it. So we should get a lot of errors with the, uh, API. So I’ve got an invalid campaign ID. Now if we notice this campaign ID doesn’t quite look like our Salesforce campaign IDs. So let’s go see what this can ID ought to be. So I look at my Pardot campaigns, and these are the Salesforce campaigns that have been copied into, uh, Pardot with, uh, our campaign sync. And I’m gonna be interested in this margining campaign. And if I look down at the URL at the bottom, I see that the last digits are 85339. Um, so I’m gonna go back to here. I’m gonna say 85339. And then I’m gonna just click send. And here we can see I’ve got a successful response. It was created by me. It’s got a, uh, it’s not deleted. There’s a URL and all that. So I’ve used the API to create a custom redirect. And if we look at our custom redirects created today, uh, it’s empty. So let’s reload the screen. And, uh, hi, Brandy. Um, and we should load you know, download are always fun because, you know, the Internet’s super fast on demo day. And here we go. We’ve got our custom redirect created. So how do we make this even easier? Well, we look at our Salesforce campaigns. We start campaigns in Salesforce, and we see I’ve got my March dreaming campaign, and I can open that up. And wouldn’t it be great to be able to create my custom redirects that I always use for certain types of events right here on the Salesforce campaign screen? And oh, look at this. I’ve got this little thing here called create social redirects. Got a name more dreaming that sends same as my campaign. I’m gonna I’m gonna create this. So it’s sercante.com/labs. And because I always forget the http s right? So I’m gonna click next, and we can see it’s thinking and it’s doing stuff and woah. We’ve got Pardot demo, uh, customer redirects. Let’s look back at our customer redirects. And reload the screen, and we’ve got more custom redirects. I know they’re coming. I’m confident with myself. And there they are. They’ve shown up. We’re able to create these custom redirects right from Salesforce, right from the campaign object. Makes it easy to create these.

Speaker 3: That’s ridiculous. How do you do that, Mike?

Speaker 2: I’m glad you asked, Adam. So I used a flow. Flow is like engagement studio programs, but in Salesforce and for automation. Data automation, business process automation. It looks very similar, and it it works kind of similar. So we have a start, and this start, um, screen flow. Uh, well, this is a ScreenFlow style flow. So there’s a couple different flows. This is ScreenFlow file flow. And I’m gonna first thing I do is get that Salesforce record. And what getting this record ID does is it allows me when I create the screen, so click edit edit element, I can get that name right from the screen. So if we remember how the mar dreaming auto populated here in the name, that’s how we made this happen. And then I was able to type in my target URL. So this ScreenFlow screen allowed me to create that user interface that we embedded right on the, uh, campaign objects. Then remember when I did the postman, I had to, like, grab that part ID instead of the Salesforce ID. Yeah. We gotta do that same thing. So we have a flow action here that allows us to get the campaign part ID based on the name, the Salesforce name of the record. So we grab that value as well. So we do the look up into the part out data, and then we’re gonna create a Twitter redirect. So we look at what’s going on here. We’ve got that redirect name. We’ve got our Salesforce or our Pardot campaign ID. So we’re gonna create it to, uh, Pardot. This Pardot wants that Pardot campaign ID rather than the Salesforce campaign ID. And that target URL I’ve typed in. And there’s a bunch of other things going on here. Here’s our Salesforce campaign. Oh, it’s automatically created our UTM parameters.

Speaker 3: Now you skipped over a couple of potentially important options there. So business unit ID and, uh, there’s another one named credential. When when you’re setting up this solution, you can specify some default values. So great if you have an org or just org business unit. But if you have multiple business units, those options are where you can say, hey. For this flow action or this particular custom redirect, I wanna make it in a particular business unit.

Speaker 2: Great. So we can see we’ve also done the same thing for Instagram, LinkedIn. So we’ve created those customer redirects, and then we have a new screen. We’ve created another screen. If we look at this, we just paste the final results into that screen. What gives us the right tab, that’s what gives us these results. So if I was to reload the screen, we’re gonna start that process over again, and we’re gonna get that screen, uh, creation, um, flow, uh, popping back up, and we’ll be able to create a whole new set of social redirects from that screen. It’s pretty cool stuff.

Speaker 1: I’m like One use case to call out with this is we’re using the example of this being an upcoming webinar and upcoming events, and we’re trying to understand promotion and having UTM parameters so we know where are people coming from. This same thing can be done for any other type of marketing campaign where you’re trying to push people to a landing page or you’re trying to understand paid ads. So say you’re trying to create a Google ad campaign, you start from Salesforce, you build the campaign. From this flow actions for Pardot ScreenFlow, you’re able to create all the necessary links for your Google paid ads and then get them into the system so that all you really have to do in Pardot is build the emails.

Speaker 3: And because this is flow. Right? The the example we have here is pretty straightforward. Pretty straightforward. Or, you know, to what Jacob was saying. You could have a decision element here that looks at, you know, what kind of campaign type are we working with. And then depending on the campaign types, you could have, you know, for one of them, maybe you’re creating one or two custom redirects. Right? So the the power that’s available to you is really is really on what you can dream up and what your skills are with flow maybe.

Speaker 2: The tool we used to create this, it’s called flow actions for PowerApp. It’s in the AppExchange. And, uh, this is it’s an AppExchange package. We grab that tool, and it’s got a lot of options available, um, more than what we’ve just shown. Speaking of AppExchange, a lot of our integrations are AppExchange packages. They integrate with Salesforce and not Pardot. So we wanna work with these, uh, in Pardot and having the data appear in Pardot the way we want it to appear. And one of the ways we can do this is external activities. External activities is a way that we can put our own activities right on that prospect activity screen. So we can see here, I’ve got it in a tech events, and I’ve registered for connections, and I’ve registered for margarine. And we were able to place that on the product prospect record. And we can use these activities just like we can, uh, any other type of activity in our engagement studio programs, whether it’s, you know, email opens, uh, you know, form fills. It all behaves the same inside engagement studio. So it’s a really powerful way to get our our almost integrations to work really well and and effectively a native lead side of Pardot. What this looks like is going back to the documentation. I’m a developer. Love my documentation. Reading it, not writing it. And see, I’ve got external activities. I can create, read, and read my external activities. And it’s the same thing, uh, where we’ve got, you know, the URLs that we can work with. And I’m not gonna bore you with the postman because we don’t need to worry about that. We have flow actions for Pardot now. To make these work, we need to create an event or a an app exchange package. So I’m gonna work with a a hypothetical app exchange package called Initech event, and it’s created custom objects and and a variety of, um, pieces. And we can see that in my Initech event, uh, custom object. I have a MarDreamin, uh, event. And if I wanted to create a new event registration, so I can click new. And we can see that, uh, for my dreaming, uh, email address, and I forget which email address I was using. I’m gonna use this email address. I’m gonna use that email address. So this doesn’t even need to be a Salesforce object, contact or lead object. This can actually talk to arbitrary things. This in a tech event can work with, uh, registrations that aren’t records in Salesforce, which is why we can’t use our normal Pardot connect to, uh, custom object capability. Um, registration date, you know, nothing like the last minute. Um, but, you know, I’ve attended today. So I’m gonna click save, and this is fired off an event. If we go back and look at our my record, Demo days are the best. Come on, Internet. I can see that I’ve got that new attended event. Setting this up. Um, we wanna set this up in marketing setup, and this is marketing app extensions. We see I’ve got the Initech events. And if I go into that Initech event, I can see where we’ve had to manually create this. So any AppExchange package we wanna work with this way, we have to create these marketing app extensions. And then we can also create activity types. So my registered and attended values show up showed up here. If I wanted to create a a new value, it was like a a no show or something like that. We’re able to do that in here. We can make it active and and and that type of stuff. We can send these two individual business units. So maybe one business unit gets one type of event, different business unit gets another.

Speaker 3: And the reason that we’re we’re going through this is, you know, some of the integrations that are out there might not have been in advance to take advantage of external activities. Right? So what we’re able to do is use, you know, our our flow actions for Pardot, manually build this marketing app extension, and we’re we’re basically gluing it together on behalf of that integration.

Speaker 2: Or if there is an integration that has some of these and we want more or we want something that’s more specific to our business, we can go and we can make those adjustments and and make this tool even more effective for us. So we’ve seen that we’ve created these events. And how do we make this work in flow? It’s really easy. So we look this is a record triggered flow. So this record trigger flow, instead of a screen flow that we saw earlier, which puts widgets on screens, this one just looks at data changes in on the record app. Um, so this one, we’re looking to see if a record is created. So this Initech event, uh, a new registration is a new record. So every time a new record is created, we’re going to do a send ex external activity flow action. Uh, pretty pretty simple to set up, and then we’ll see that we’ve got that activity type value that we set. And our extension name, this is in a tech events. We have, you know, other options if we have more than one, uh, event we’ve we’re connecting to. That prospect email address. So remember I had to type in just my email address. We can show it up in this case. If the record that we’re working with has, you know, more properly connected to, uh, contacts and object or lead objects, we can actually pull in a, you know, lead object or the the email address off that object and stuff like that. And then the event name that we’ve connected to. So this is, uh, the margining event. Um, again, we can send it to specific business units and stuff like that.

Speaker 3: Now knowing what I happen to know about external activities, I know that you can only send an external activity to HARDOT if the prospect already exists. How can we help make sure that in a tech events, which doesn’t work with anything? Right? How can we make sure that this runs nice and smooth?

Speaker 2: So what we can do is we can create or we, yeah, we can try to create that record in Pardot if it doesn’t already exist. And so we’ve got two sections of actions. We got Pardot data, Pardot admin, and we can see that we’ve got a lot of options within these, uh, create a custom redirects, queries, campaigns, static list creates. Uh, it’s not a product admin. So product admin is all the non prospect related actions that we have. So, uh, create a new pros product prospect that’s gonna be a product data. And we can see what we have here. So we can, uh, add external activities. Yep. That’s what we’re doing. Uh, form handlers, so we can create these by form handlers. Uh, query list, prospect delete. Oh, cool. I could delete prospects. That’s not what I’m looking for. Uh, prospect upsert by email address. That’s what I wanna do. So I wanna create that new action, and I can create that new email address. And, uh, that’s coming in, uh, record

Speaker 1: email.

Speaker 2: So I can create that email address here, and I’m not gonna, uh, do any of these other things because I don’t have it in this particular integration. And I could create a label and, uh, click done. Click cancel on accident. Yay. Demo. Um, but if I would have clicked done instead of cancel, I would have seen that, uh, new node here. We don’t need to see that. So pulling this all together using this, like, we’ve shown some pretty cool stuff, but how can we use this? Well, back to engagement studio program. Got a new engagement studio program, and I can see that I can check that custom redirect. One of the custom redirects that I created from Salesforce, right from that campaign object, I can check to see if somebody’s used that custom redirect. It’s pretty easy. We did have to jump back and forth between the different screens and and Salesforce to to be able to do that. And I could do my normal, uh, you know, Pardot engagement studio stuff. So, you know, add to Salesforce, uh, Salesforce, uh, campaign, you know, the normal the normal things we’re used to. The other thing we can do, the new thing we can do is we can see that we’ve got this new external activity, and we can see external activity. It was an InteTech events that, you know, registered. Well, maybe I want attended, and I can say Mar dreaming or whatever the event is. Um, so I can, you know, do these types of schedules, and then I could send that email. So we can send that email saying, oh, thanks for registering and happy to see you. So we have simplified a lot of our actions, and we’ve expanded the capability of of Pardot.

Speaker 1: So the one thing I wanna call out really, um, with that benefit, um, and you can go to the next slide, uh, Mike. Um, when we’re looking at this, I think that I’ve mentioned earlier some of the the what we can see in the app exchange and what we can get access to from connecting those apps. One of the things that I’ve experienced and have struggled with in the past is whenever we are getting these apps, um, out of the box, when we’re looking at some of this stuff, we wanna potentially use the custom objects functionality inside of Pardot to be able to pull in this attribution information. What we are not always, um, getting when we’re doing this is not all apps are having that connection of contact object to the custom object you need. For information of those custom objects, just native which is a native feature to pull over, um, is from sorry. I realized there’s a little bit of an audio issue. I’m trying to fix that. What we’re seeing with those issues is that those actions that you’re trying to trigger in the engagement studio program won’t pull into Pardot if there’s not a connection between said custom object and the contact object or the lead object. A lot of times you’re gonna have this app book coming through from the AppExchange, and it’s just gonna pull in email address or first name, but it’s not relating back to the records you need for Pardot to sync information over. What we’re doing is bypassing that. So you’re capturing all the necessary information regardless of whatever object relationships may or may not likely may not exist and being able to bulkify engagement studio programs with these kind of integrations that exist. So with that being said, we have a lot of resources. We’ve talked about a lot of stuff. Um, so here we have links to the documentation, um, to understand how the API is organized, linked to the postman collection that we’ve created for the, uh, flow actions for product Pardot tool. Um, we’ve also, uh, provided a link, um, here. Um, we will provide a link in chat as well to the flow actions for Pardot, um, AppExchange package. If you want to go to it now, you can just go to the AppExchange and search flow actions for Pardot. And then lastly, if you’re interested, we have a few other account engagement apps on the AppExchange as well if you’re interested in learning more. So with that being said, we have a few questions, and we have a little bit of time. We have about ten minutes left, um, in the session. So I will have us go through some of those, uh, questions right now. So the first question and, Jenny, if you’re able to I’m I don’t have the access to throw the questions up on screen. Um, if we could throw some of them up there.

Speaker 3: I think you’ll need to stop sharing your screen so that we can there we go.

Speaker 0: Yes. Um, so in the q and a, um, we had, um, what exactly does the Flow app include? That was a question that came in on the q and a channel.

Speaker 3: Yeah. So the, uh, the managed package that we have for the solution, it pretty much just contains some invocable actions. Right? So when you’re in when you’re building your own flow and you click add action, our solution adds some of the options that you can pick from there. But in itself, this the solution is really like a it’s a toolbox with different tools that you can use, and then it’s it’s up to you to figure out, you know, how do I want to use some of these tools to accomplish my own business goals. We do have a couple of examples and some, uh, walk through videos with our documentation that’s linked in the package, um, to help maybe spur some of that creativity.

Speaker 1: Yeah. We’ll be working over the next few, um, over the next month or two to start, uh, having more specific use cases available to everyone. We recognize that, um, there’s a lot of creativity that can be can be done, but we all be sure that, uh, everyone can follow along. Um, so next question. What is the difference between flow actions for Pardot versus the flow automation in Salesforce in terms

Speaker 2: of functionality? So this

Speaker 3: is actually a really good question as flow actions for Pardot is adding to the flow automation that’s available to you in Salesforce. Right? The flow automation that’s available to you in Salesforce really is relying on working with Salesforce objects. Right? So if you want to use, um, out of the box flow functionality, you’re really relying on those objects being connected to your contact or leads so that data gets pushed into Pardot. Whereas with flow actions for Pardot, the extra things that we’re adding, you don’t necessarily need that particular data link in order for things to work. Right? So some of the examples that we’ve seen in the past is, you know, I have a a set of leads that aren’t synced to Pardot, and I want to have complex business logic to determine when that should happen, the flow actions for Pardot solution will let you build a flow that, you know, has logic and then at a certain period of time, will actually send the record to Pardot to cause the sync to happen. Um, there’s a bunch of other examples, but I hope that answered the question.

Speaker 2: I love using analogies. So I think of flow automation, that’s that’s a auto garage. Right? You could do so much with flow. You could fix all these business processes. You could fix your cars. Right? And flow actions for Pardot is just a box of new tools that allows you to do even more. So cars, you know, it’s it’s those metric socket sets that allow you to work on the foreign cars rather than the American cars. So that’s one of the ways I like thinking about it.

Speaker 1: Wonderful. So the next question, which I think, uh, I think we answered in the chat, but I wanna throw it in here because I this is a question I even had. Do the external activities in Pardot show up inside of the engagement history component for Salesforce users?

Speaker 3: No.

Speaker 2: But with that but with that being said, that data is already in Salesforce. So it’s not in the engagement history for Salesforce users, but it’s already in the existing, um, AppExease provided, uh, screens, reports, and stuff like that that you’ll get. So it’s not in that one spot, but we still have access to that data in in Salesforce.

Speaker 3: And there’s other creative ways that you could look at putting a solution together. Right? So let’s say the the thing you’re trying to push or put into Pardot is the fact that someone registered for a webinar. Right? If you really want that particular event to show up in engagement history, you might want to consider using a form handler to capture that information so that when flow actions calls the form handler, right, the form handler does show up in engagement history on the prospect record, which is which becomes visible to the sales user. Right? But you’d really wanna think about, you know, when’s the right time to do that. I wouldn’t take advantage of that pattern for, like, oh, they attended, they didn’t show up. Right? Because it’s less less activity.

Speaker 1: So there was a piece there’s a a comment or question, um, behind the scenes. Someone was asking, uh, can it appear under just traditional Salesforce activities? And realistically speaking, it just depends on how the app is connected to the, uh, Salesforce system. So to to Cruisers and Adam’s point, um, it it’s just very dependent on the app that you’re using, and it depends. There’s a lot of ways you can also get the information without having to rely heavily on that feature free lightning components that’s around um, just how it’s connected, whether it be to campaigns. So this actually kinda goes into the, uh, next question that we have. Um, we use Cvent exclusively. Anyone using external actions or external activities with Cvent registrations. So I personally have used cvent many a time in the past to connect data from, uh, cvent to Salesforce and then having to rely on that integration to push into Pardot. So out of the box, that integration is basically just updating the campaign object inside of Salesforce. There are APIs and other ways you can connect the data in as its own custom object or as its own records so that you can use external activities for this. Or you could use flow to look at campaign member information to populate external activities. So there’s a few examples that can be done with when it comes to Cvent. And, again, it ultimately comes back to since this is Flow, Flow’s the kind of brainchild of this, and we are just adding capabilities onto Flow to bulkify, um, with Pardot capabilities. It really is dependent on how that integration with Salesforce is set up. Adam, do you have any more color to that?

Speaker 3: Nah. Pretty much nails it. I think to, like, directly answer this, I I haven’t seen anyone tie Cvent with external actions or activities, but but this would be a really, really good use case for doing that.

Speaker 1: So we see in the the chat, Marco, so it’s a good point. If it’s already in the campaign object, we can use a dynamic lesson engagement studio program. There are, um, that is absolutely a perfectly good use case. Um, if depends on what your need is. There’s a lot of folks out there who are really loving external activities, and they want to see that information in the external activities At the bare minimum level of just having that visualization, um, there’s a few things you can do to be able to have the engagement history components on your Salesforce lead or contact record, and then you have that campaign history bucket. Some folks are only some marketers are only living inside of, um, part only living inside of Pardot. And so without having to go into the list tab and then see all of the dynamic list that you’re associated to, it’s a convenience to be able to see. Cool. Here’s all the forms, landing pages, and web page exit web pages I’ve engaged with. And then below that, here’s all of the other campaigns or activities I’ve engaged with. And it also allows you to, um, just have some of those capabilities within the engagement studio program. Again, you can accomplish it in the ESP with a dynamic list and campaign member. It’s just a nice extra feature if you’re trying to reduce the number of dynamic lists you have in your work.

Speaker 3: Yeah. And unless you have some really mad campaign or, uh, list naming skills, it’s gonna be tough to see when certain things happened and maybe more importantly, like, what has happened most recently. So the external activities panel that was on the side, if you remember in the demo, right, it had, you know, not only that Mike attended the, uh, Marjorieman event, but it also gives you a date and time stamp of when that happened, and that panel sorted based on recency.

Speaker 1: So it doesn’t look like we have any more questions in the QA, um, or inside of chat. Um, we have about four minutes left. So if anyone has any remaining questions, feel free to post in chat. Um, otherwise, we very much appreciate you taking the time to be in this session, learn about a cool new app to add Pardot capabilities to Salesforce. And if there are no questions, we’ll get a few minutes of your day back and get to the next question. But thank you all so very much.

Speaker 3: Thanks, everyone.