51黑料不打烊

Transcript

Please feel free to drop at this point and we can make sure you get the recording. Thanks, Jimmy. And finally, we鈥檇 love to have you stay connected with the deep dive Marketo user Group it on the slide here that will be set out and then you can stay up to date with all of the wonderful content that the deep Dive program is putting out. You鈥檒l get reminders and updates about the events that are upcoming. A couple of upcoming opportunities. So save the date for the virtual skill exchange on August eight. Runs in the morning from 9 a.m. to 12 p.m. Pacific Time. Registration is opening globally soon. I don鈥檛 believe it鈥檚 open yet and it will be a great opportunity to get a ton of really peer to peer deep dive learning. I know about five current market champs are presenting and the content for this should be awesome. And additionally, there is a new resource that was put out by the Marketo team. This is the new instance Best Practice checklist. It鈥檚 great if you鈥檙e an admin who鈥檚 adopting the new instance. It contains tons of content about configuration steps, things that you can check and monitor in your inherited instance, and really just everything you need to get set up if you鈥檝e inherited a new instance. I know I inherited an instance a couple of years ago and a resource like this would have been fantastic. If you are joining us live, you can scan the QR code now and this will also be set out in the slide deck. So onto today鈥檚 content today with awesome deep dive all about program member Custom Fields or PMCs. For short, you鈥檒l hear us use that acronym a few times throughout the next hour or so. I know when PMCs were released about a year and a half ago, at this point it was one of the marketing features I was most excited for. PMC have allowed a ton of Marketo users to go from, you know, six, seven, eight events for a specific program that鈥檚 promoted across a variety of channels, namely web content in my use case, down to a single program where you can track all of the places that asset is promoted and get much simpler setup and far more granular tracking. I know I use these all the time in our instance at Terra and they鈥檙e super fantastic. So I鈥檓 really excited about this session. Joining me today, we鈥檝e got Katja and Andy. I鈥檓 going to let them introduce themselves momentarily and I鈥檒l go on mute and just kind of facilitate the session. But a couple of additional housekeeping items. We want our session today to be super interactive. Feel free to drop questions as you have them in the chat. I鈥檒l be monitoring and try and get it in Katja to answer them live time. And we鈥檒l also have time for Q&A at the end. And with that, over to you, Jim. Thank you, Jessica. My name is Chris. Okay. So I live in the Netherlands. And a little fun fact about me is that in Europe currently we鈥檝e got the European Football Cup. So as we speak, the Dutch team are actually trying to get themselves into the next round. So it鈥檚 exciting times And over to you, Andy. Kieran, I am the President at Revenue Pulse and my random more fun fact, if you will, is this summer I am attempting seven different varietals of tomato in the garden, so we鈥檒l see if any of them produce, but decidedly not green thumb. But we鈥檒l see if I can pull it off. I got five last year so it鈥檚 I can鈥檛 start from seed though. That鈥檚 my, that鈥檚 my, my foible. All right. Well, let鈥檚 jump in. All right. So we are can we go back just to two sides so we can kind of cover what we鈥檙e going to cover? So we鈥檙e going to look at definition and purpose, basic rules and engagement use cases, and then we鈥檒l have time for Q&A. So let鈥檚 dive into the definition and purposes for program. Remember Custom Fields. So PMCs stands for Program Member Custom Field. I tend to write it PMC off and then say program member Custom Field because PMC doesn鈥檛 trip off my tongue very well. So you probably hear me say program member Custom Field about 20 times today. I feel like probably turn it into some sort of a game. But anyway, so what does that mean? A lot of you have probably been using program member Custom Fields for years and not really thinking about it in the sense that, for example, an acquisition program field, which is unique to the program technically is a program member field. It鈥檚 just not a custom one, it鈥檚 a system one. So what this is, is a piece of data that is unique to that specific webinar, that specific white paper, and it allows you to attach unique information to the person at a program level as opposed to at a person level. And this has a variety of use cases. We鈥檙e obviously going to dig into those, but this makes it very useful for program data as opposed to person or lead data. This really allows us to have contextual data specific to that event content, whatever it might be stored at that level. You can jump forward. All right. With that, I will hand it over. Yeah. So now that we know what they are, there are some gotchas and rules of engagement with the program member Custom Fields. And I think I鈥檒l be mixing my acronym and my full name up and the it鈥檚 going to come up loads of times, but how do you create a program member custom Field You do that the same way. Do you do any custom fields that you would also do for the person in up in? You actually go to the field management and you can choose to set up a field either on the person or on the program member. But more about that in the next slide. It鈥檚 also important to realize is you can use all the same field types as you can for a person field. So the ones that you can use are here, but something that鈥檚 very glaringly obviously missing is, for instance, score fields. You can鈥檛 use those on program level, so either boolean. So yes, no field date and times, numeric string or zero. So also not a text area field. Also important to realize is on the person. You can create as many fields as you like really. But for a program in a custom field there is a limit. You can only create 20 of them, and a top tip therefore is to identify a couple that you will use consistently across many programs and give them a very specific, dedicated name, but also create a number of generic ones like PMC if string one, two, three, four and five that you can use for different purposes in different programs for different contexts. So that鈥檚 something to to think about. There鈥檚 basically three ways that you can get data into a program member custom field. One is list imports or imports into program member tabs form fills and flow steps. But important is that all of them need to be within the context of that program. So let鈥檚 have a look at how you create one of those fields. So as mentioned, you do that in admin under the field management tab and when you click on Create or new custom field, you can choose whether to create a field on the person or on the program member. So in this case, we will choose a program member. Then you select the field type and you will see that depending on the choice for person or program member, the list of field types will be different. And then you name your field to realize that you can鈥檛 change the field type or remove or hide the field after you鈥檝e created it. So what I said on the previous slide, think about how you want to set up those 20 fields. I would say for starters, don鈥檛 use all 20 of them, but think about the strategy, how you鈥檙e going to use them, how you鈥檙e going to name them before you get started, because there鈥檚 no do overs, but you can use them in each program, which you don鈥檛 have to. So they saw a unique value in the same field for a person within the context of each program, but they can be empty as well. And often they will be empty. They must be written locally in the program. So we鈥檒l touch upon some use cases later on as well, where we use, for instance, forms, field uses for a list, the Smart campaign. It needs to be inside the program for successful use of the program. In my custom fields you can import data into them on the program member tab and you can sync the information in the program. Member Custom Field also with your Salesforce campaign members, but you have to set that up in the admin under the program level. Salesforce Sync Now you can work with program or custom fields in smart campaigns in your flow and in smart lists, but they will differently than normal fields. So first of all, you can use a flow steps to change data in your program or custom field. You do that with the change program, our data flow step, where you specify which program, which field, and they call that attribute. And then in new value, you put the value that you want to put in there. It鈥檚 important to know that you can only use that flow step once a person is a member of your program. Obviously it鈥檚 called a program member Custom Field. So if the person is not a program member, that field is not suitable to to use just yet. So you often see a change program status flows that before a flow step like this, you can also reference information in the program number custom fields, but only based on how they were changed. And you see here that we use choices, we use the program. Data was changed as a as a choice, but you can only specify which field the program member data was changed or and not what the old or new values are. So usually in flow steps when we use a program or custom fields like this, we actually do that through members of smart lists, because in smart lists you have a bit more flexibility to be specific about what was changed. So if we go to the next slide, this is how that looks in in your Smart list, you still have program. Remember, data was changed or not was changed as a both a trigger and a filter. But with the constraints you could specify what the previous and the new value are and some other sort of more common constraints. So you got a bit more flexibility in setting your your criteria here. So usually when you want to do something different in a flow set based on program or custom data, you set up a smart list and you use member of smart list in your flow step choices because you have that added flexibility in this market. It鈥檚 also good to realize that in a normal, smart list person view, you cannot see the program member fields. You need to go to the program member tab of your program, and that鈥檚 where you can add those fields and you can get an overview of the values that are in there and also export the data from there. They work very similarly to the women. Are you URL field on a on a webinar so you can also use them as member tokens in your emails, landing pages and alerts. But we鈥檒l have a little use case about that a little bit further down now. And we can you show us a little bit about the different use cases that we prepared. Yeah. Let鈥檚 dive in. All right. So across use cases, we鈥檙e going to share for today, starting with UTM capture for parameters specific to your program. And we鈥檒l dig in on collecting event specific data around registration, communicating personalized codes, the list import, and then finally, time stamping. So let鈥檚 go ahead and jump into UTM. So just as a precursor to talking about collecting your teams or leveraging them inside of Marketo, let鈥檚 talk about UTM best practice first, because it鈥檚 not going to help you if you鈥檙e not following best practice to actually create the data in the first place. So I recommend using a UTM generator, a UTM creation and tracking spreadsheet unique to your organization or tool that makes it possible for you to have governance over UTM for your organization. The reason this is important is a things like case spelling, those types of things. They matter for the data. The output has to be consistent and accurate. If you鈥檙e swapping out social and LinkedIn on your source and medium. And sometimes it鈥檚 one way and sometimes the other, you鈥檙e going to have a hot mess on the back end. When you go to do data analysis for this, you鈥檙e going to want to append this across all of the applicable web and social posts, ads, etc. anywhere you can. And this is important because if you are creating them but not using them, then it doesn鈥檛 really matter. All right. So first, let鈥檚 talk about first time usage for programing. Remember, Custom Field, we already talked about creation, so you鈥檒l need to go in and create program member custom fields for each of the UTM parameters that you will be tracking inside of your admin section. So typically for our purposes, this is going to be a string. All right. We can jump forward. All right. So once we are ready to process those in, my preference is to use a global field. Typically attempt field to capture those as at a lead level so that I can still use global forms, then pull those in and process those on to the program Member custom field for each of the values. Now, you may not have your marketers using all five, all seven each time. So you processed what you have and that will write in. You could have blank values for some of these. And then my preference is to use a Boolean field at the end to kick off a global process. We鈥檙e going to touch on that just to give you a through point on what happens here. But this is essentially the basics of establishing this program. Remember, custom fields unique to that specific event webinar, whatever the case may be, so we can jump forward processing these. Then you鈥檙e going to still process that same temp field globally into your most recent or last you teams and then null them. The knowing of them for me is important. A That way I have it at my program level and I also have it at my global level. But then I鈥檓 not retaining old data. So the next time a marketer puts in only three teams, it鈥檚 only overwriting the three values and the other two, four or whatever are legacy and creating that incorrect cross-reference of data. So this allows me to have it blank 99.9% of the time. And then you can also leverage this data if you want to write into original UTM. All right. So we can jump forward. So it鈥檚 important to know that you can sync this to Salesforce. The process specifically for doing this is to go into the admin section under the as of DC Salesforce Sync. This is only possible with Salesforce, not with other CRMs. And then you鈥檒l need to. This is a one time process. Connect the dots between your program member Custom field and the custom campaign member field. On the FEC side, the fields do have to be same for same. So if you created a field on the program or rather on the campaign member and it鈥檚 not showing you with the ability to sync, it means that the field types are not matched. You can鈥檛 go back and change it. It鈥檚 based on what it was the very first time. So you would have to create a net new field. So just to know that, you need to make sure that that鈥檚 established early and for UTM fields, I tend to use a string field for most of those since that鈥檚 the easiest way to retain that data within the field structure. All right, so we can jump. Now, this, of course, assumes you鈥檙e using a program level sync. If you are thinking with a flow step to sync it over to the FEC campaign, this will not right. It will not carry the data over. But if you鈥檙e using that program level sync on the program tab, this will pull over. It will look something like this on your campaign member detail. So now you have the capacity to look at an individual record, to look at it at scale for the specific program. And because these are unique, it retains for each single time because the campaign member object is universal, it鈥檚 not based on lead or contact. You can run a single report on this inside of sales, which is very handy. So some of the reports that we can build off of this just to kind of pull that use case out to its final end and sort of the real value of having program member custom builds because this is the process to set up and maintain is that I can see from a brand perspective where the touches from medium and source are coming in. I can also see if we want jump to the next touches by campaign type. So if you鈥檙e thinking of campaign type, webinar, event, white paper, what have you as a tactic, you can then pivot that for, let鈥檚 say, our successful was the medium of email. How effective were my emails against regional events, so on and so forth. And you can even go on to pivot those two against each other at a more scaled level, especially with attribution data, which is really nice. I love this use case. I just want to chime in and say this was the one I adopted first in my instance. Previously we used to have like seven or eight pieces of content. We have like content on channel, content on Channel B, content on Channel C, etc. And then our content would come and say like, how is X, y, Z content performing? And of course our distributed marketers were naming their campaigns like ever so slightly differently or tweaking their asset title. And so I would always be like, Oh, it鈥檚 so hard to tell you. And now we just have one piece of one content program and then we capture where the content is promoted in these custom fields, and it鈥檚 so much easier to help them understand, one, what types of content are resonating on what specific channels and to align some of our like content by persona, by product line to specific channels, because we found certain content by buyer line works on different channels, it鈥檚 been really, really helpful. Yeah. Before this sync existed, what I would have to do is write it to the person, record, sync that over to Salesforce, then write it onto the campaign record. Fingers crossed that the timing was right to get it on the right campaign because if they did, you know, a bunch of different clicks, right. It could be misaligned and then nail it on the sales force side and then trigger that back into Marketo to know that it had been written. And that was the only way to have that information. Otherwise, you鈥檙e looking at a campaign hierarchy that is no fun to manage and really hard to scale. Well, absolutely. One of the strongest use cases out there. I think it鈥檚 now another use case that I alluded to a little bit earlier as well. And Andy did mention global forums earlier. This is a use case where you actually need to have your form inside your program. But before program member Custom Fields, I think every marketing ops person has had requests like I have an event and I need dietary preferences, I want a feel for that. I want the feel for the T-shirt size, I want the field for a session. And before you know it, you鈥檝e got a database that is growing completely out of control with program or custom fields. I tend to set up my life events because they were a use case where every event might require slightly different information on registration. So for life events, I really always put my form inside the program rather than as a global forum, and that allows me to put program member custom fields on the form. You see here what the what the user experience is. I鈥檝e got a breakout session, I鈥檝e got a question about are you coming by car? And if so, what鈥檚 your license plate number? Because you鈥檒l need a parking card. But it can be any sort of a question. And when the person fills out that information on the program member tab, you will see that I actually own the session picker. I think session B I filled out, yes, I鈥檓 coming by car and I left my license plate number so you can actually export that information and you can ask different questions for different events depending on the use case there. The only top tip there you can see that I鈥檓 using generic program member custom fields here, an ideal place to capture within every program which fields you鈥檙e using and what information you鈥檙e collecting in there is in your program description. I tend to always put a little list in there. I鈥檓 using Pmc鈥檚 upstream one for the session picker. I鈥檓 using a few teams if string two for my license plate numbers so that that information is also easy to translate and also easy to share with other Marketo users. I will echo this and say I love that description. TAP Katia. We used to do a similar thing with like temporary fields and we would check them out and have that whole maintenance process and notating in the program description where that what temp or what PMC field you鈥檙e using is such a great way that distributed folks across the world can know exactly what fields to pull on to this members tab. Yeah, exactly. Yeah. And another use case is personalized information that you get from external sources. As I mentioned at the beginning, you can import data into your program member custom fields either in the members tab or in a static list. Again, if that list sits within your program and then you can use your member token in this case, again, PMC upstream one to share that personalized information inside the body of your email. But as a as a tip, you see the redeem Now button in here as well. You can actually also integrate your PMC token inside the URL. In this example, I鈥檝e got it as a part of the query string, but you can even have a fully personalized URL, except the one thing that you need to keep outside of your token is the HTTPS. So remember to strip that from your PMC value and keep that separate so that Marketo can correctly track the link and recognize it as linked. All right, so we鈥檙e going to dig into the final use case that we鈥檙e sharing today. This is buying things like my 1.25 favorite spot for use cases. So this is around time date stamps and the two most relative event use cases specifically for this are around list uploads or delayed things. So I want you to think about how many times you鈥檝e had a list that you had to upload and it went through this crazy process and say the event was today and you don鈥檛 get the list even submitted to you until a couple of weeks out. Then it has to be cleaned, checked, given the green light to be uploaded, and by the time you鈥檙e uploading it, all the salespeople have gone in and created events. So any shot you had, any attribution from that event, even aligning with a last touch or prior to opportunity creation shot taken with having sync delays and trying to account for correct order within the engagement dates. So this is a solution for that. So you have the capacity to create a program member custom field that is a time date stamp. And so this allows you to retain correct or corrected information for when the engagement happened. So you can either log it at the time that the form is filled out inside of Marketo, knowing that you may have a delay for when that syncs to Salesforce. If you are prone to delays or with a list upload, you can set the corrected date and time of the event that the list is from and upload it there. The way to have this then process on the SFD side as an additional tip is you鈥檙e going to create two SFD custom campaign member time date stamps. These are going to feed your attribution for corrective engagement date. And so the first is going to sync to the pro Remember Custom Field and this is your corrected engagement date, accurate engagement date, whatever you want to call it. Marketo Engagement date doesn鈥檛 matter. This is not the field that you will use for reporting. The field that you will use is going to be logic based and this is your attribution date or whatever makes sense for you to call it in this system. The logic on this is going to look to see if corrected engagement date has a value. If so, it will pull that date in and if it鈥檚 not available, then it will default to the first respondent date from the FDC campaign member record. The beautiful thing about this is SFD does not allow you to edit a first respondent date you are stuck with whenever it hits the system and actually sinks into that campaign. So this allows you to actually overwrite that and have control over the engagement date, which is a beautiful thing coming from or cut out for the program member custom Field functionality. All right. I think with that we can jump to wrapping up and Q&A. Before we do, Andy, I just want to say I love this use case. We don鈥檛 do a ton of live events in my specific instance, but when we were doing them, it was always like a mad rush to get the listing soon as possible so that the campaign data and Salesforce would be as accurate as we could oriented around when the event occurred. And this totally eliminates that like frantic pace that happens after a live event and allows you to have clean and accurate reporting. So this is such a great use. Yeah, I鈥檓 a fan of it. It鈥檚 just perfect for when you aren鈥檛 able to convince them to use the form from to use cases that go with the custom fields on it. And you do have the list upload from, you know, the business card scenario. Exactly. It鈥檚 good to have in your back pocket. This is awesome. And with that, we鈥檝e got time, lots of time for Q&A from the audience here, so feel free to drop them in the Q&A section. Feel free to drop them in chat. Feel free to come off mute if that鈥檚 more your style. We want to help get any questions answered. So first one from the chat. We鈥檒l go ahead and ask live. So is there a way to report on the various values for the field across programs in Marketo or only in Salesforce? Just in Salesforce. Indeed, yes. And then are you able to use the data in RCA slash RC is so revenue cycle analyzer or revenue Cycle Explorer reporting? You know. Industry? That鈥檚 a great question. I, I hate to say it, but I don鈥檛 know the last time I had access to RCA, Have you had access? I don鈥檛. Know. Have TBD. We鈥檒l get back to you on that one because now I want to know, April, if that is actually about. It鈥檚 been so long since I鈥檝e been in there. Sorry. I feel like everything I鈥檓 doing is and in Tableau these days are Power BI? Yeah. What is needed to really use this? I think infrastructure, building up the fields and consistency. I think that鈥檚 what I would say as far as as use cases, although some of these are going to be instance based. So like specific to an event or specific to needing to correct a date. So you might not need to use it for every program, but when you needed it, it鈥檚 there. Although I will say with the time, date stamp and corrective action, you can do that retroactively. So you could go in and add the program Member Custom Field, validate the date of the event after having created the CFTC fields and then write that in and have it right into Salesforce and then have that as far back in your data set as you want to go. So if you have, you know, 100 events a year historically, you may not feel the need to go back and update all of them, but you might want to go update some of those banner events that tend to be your biggest revenue drivers, although discuss it with your revenue team before you do that because that could change some of the attributable data in your favor. And they might not like that historically, but. I think great question here is do you prefer to use automatic Salesforce Marketo sync setup or a flow step setup to update the PM? Or is there not a big difference? There鈥檚 a huge difference and my preference is the one that works because the flow step will not sync the data. So exactly. So that鈥檚 a really important one. And I think just to double down to leverage the native sync, the program in Marketo has to be connected. What you鈥檒l hear people say it鈥檚 on the top level. So on that main control panel of a program, you have to link it to a campaign. And that鈥檚 the only way this data passes back and forth. Um, Ricoh, if you royally screw up a PMS, you f at time of creation, I鈥檓 sure you鈥檙e not speaking from personal experience. There is this scenario where support could wipe the PMS the F for from the instance he鈥檚 imagining having tremors around the idea of a typo in a field for the life of the instance. Once it鈥檚 there, it鈥檚 there and it can鈥檛 even be hidden. And. It鈥檚 stuck. It鈥檚 also really important to get the field type right, the Salesforce field specifically. So it鈥檚 up. Like you have to just create a new one. Yeah, but on the Salesforce side, if you mess it up, you can create a new one on the custom member fields. Those the field type is set, it鈥檚 set, it set, it鈥檚 it鈥檚 you are, you鈥檙e carving this one in stone. Yeah. Yep. Yeah. My wife鈥檚 got one. Beta do the first one. If you have a bunch of use cases, go do one like create one and then make sure you got everything right and map it before you go nuts. I鈥檓 creating a bunch in both systems and realize you made a mistake. Exactly. And never create all 20 at the first moment because you will think over 21st. So that鈥檚 that鈥檚 why I go with generic so that you can use them for multi use cases. So you are you did hear correctly there is a limit of 20 that may change future state. I think there鈥檚 a little bit of a lobby out there to get some more but the limit is 20. It鈥檚 been 20 since they were introduced and I don鈥檛 know if it鈥檚 going to go up any time soon for a program member. Custom Fields As far as how many I create, I create one for each of the buttons that I need to pull into the program. Now, this gets prohibitive if your organization is using like 15 of them because there goes 75% of your program member custom fields to buttons, but audit how many you have, how many you鈥檙e actually using, and what is necessary in a value for marketing versus what鈥檚 interesting specifically for like GIA collection web analytics side of things perhaps. But yeah, it鈥檚 a 1 to 1 on each of the program member custom deals mostly for most people. When I鈥檓 creating them, I鈥檓 thinking it鈥檚 five or seven is what I typically say. Any other questions? And also feel free to come off mutant and ask the question if you don鈥檛 want to type it. And we鈥檙e happy to field them that way. Love to hear your voice This. Anyone have any cool use cases that we didn鈥檛 share about that you want to share with the class? No pressure or anything that you would like to try it on. I鈥檒l shoot. I鈥檒l. I鈥檒l. I鈥檒l jump in. If you have 1.1.25, the very last use case or the I guess augmenting of the dates, any pushback from I mean, like what what was the vetting process? You know, especially with like sales leadership or marketing leadership. I mean, you鈥檙e potentially going in there and, you know, maybe stepping on some toes, like maybe maybe a little bit if you have any insights into how that process occurred to get it approved, too. And those flows. Yeah. Are you talking about for historic updates or going forward or both? Both. Really? Yeah. So the course the go forward is going to be similar to the historic piece and I think it鈥檚 a little easier to get the go forward. But basically it is to say the purpose of attribution is for us to be able to optimize our portfolio of investments across the various marketing channels where we spend money. And if that is the case, we need to be as accurate as possible, knowing that events have lists that can take weeks or even months to get into the system. We鈥檙e robbing ourselves of accurate data by not correcting the engagement date. When we upload it, we have the capacity to do that. It鈥檚 a fairly simple, small, straightforward build and by doing so, we鈥檒l be better able to understand, audit and optimize the investment we鈥檙e making in these various events, since some of those have particularly high billing points as far as the totality of our marketing spend. And so if we know that one is effective or not effective based on having an actual engagement date versus the number of opportunities that open following that, particularly within a 30 day window, then that鈥檚 the whole point of what we鈥檙e doing with attribution in the first place. Why would we not be giving ourselves accurate data to actually be able to make up a proof point of that event being efficacious or not? And then historically, it would be to say it may change some data, but we鈥檙e actually is data correction not changing? We鈥檙e correcting it first. And then secondly, if we鈥檙e doing this going forward, having historic true 1 to 1 comparison on the efficacy of these events, historically, we鈥檝e already paid out commission. Things have already been done that鈥檚 in the rear window. But this is a data correction for us to be able to have a year over year comparison of specific events or what have you. Also along those lines, if you鈥檙e using attribution as a, you know, was it sales or was it marketing? Right. This is going to put stress on that, which maybe isn鈥檛 a bad thing because it really shouldn鈥檛 be sales and marketing, right? It鈥檚 not swimming in the Olympics where one person medals and the team doesn鈥檛 win. It鈥檚 soccer, right? Everybody鈥檚 going to get a medal, should win win. And so this may peel back that trauma a little bit, which is not great, but also, you know, I always like to say, if you鈥檙e not triggered, you don鈥檛 know there鈥檚 something you need to fix. I鈥檓 stealing that attribution analogy for sure. Andy, The other use case I鈥檒l say that we do in my instance is kind of like a flavor of the life event one and it鈥檚 custom webinar engagement data. So both interactive on 24 and a number of other webinar tech have the ability to capture engagement data live during the webinar. That may be time in the session, that may be poll questions, that may be assets downloaded, you name it, what have you. There鈥檚 a ton of different engagement data you can capture either natively via your integrated webinar provider or offline, and then upload into that those fields and for many sales orgs, hopefully that engagement data is a goldmine of information on things that the prospect was asking about doing during the webinar vs versus they downloaded etc. and can be really helpful for the sales team in personalizing their engagement and outreach with that prospect. In my instance, we have that all is a couple of different program member custom fields. One question we ask is do you want a personalized demo? And we use that as like a additional alert or indicator for our sales team. In addition to having that on their layout, they get a special alert process if the person indicates yes. But we also capture the time they spend in this session. The resources they downloaded, and depending on the questions we ask, some of the questions that we asked during the webinar and in my instance, we can automate all of that into a bigger text field except for the one like, do you want to demo a hand razor thing that we do separately and pass that? And we鈥檝e adjusted our page layouts of the campaign members. So the big text piece of information is right on their layout and we constructed them that they can go read and engage and look at it right there. And the sales team has found it super helpful previously, our marketing team was like managing a spreadsheet and handing it out to the sales team and we took their IT our spreadsheet management process and got it down to about 15 minutes with a spreadsheet to concatenate all that information, upload, etc. So it鈥檚 been a huge time savings on the marketing side and a huge benefit for our sales folks. So that鈥檚 another one I really like. I actually don鈥檛 know, so. I don鈥檛 see why not. In just a moment. And as long as they鈥檙e local to the program, I feel like you could you couldn鈥檛 do it in a global interesting moment now, or could you, with executable campaign. I was just wondering that same because you can carry forward the data and. If a parent contacts. Me, that would actually. It might, but you would have to then have your interesting moment globally be executable. And make sure that you put a parent campaign token consider. Correct. So answer is definitely yes. If it鈥檚 a local interesting moment program and we all think yes, if you have an executable interesting moment and inherit your parent campaigns from the campaign that you鈥檙e executing. That鈥檚 a proof of concept test. I think it鈥檚 like, yeah, All right, awesome. Any other questions before we maybe give you guys some time back and let鈥檚 have 15 minutes to go do your own proof of concept around program or custom fields. In your instances, you have sandbox play with them. Their first. Exactly. Don鈥檛 count against your against your pride. And everyone check your spelling before you create them. Yeah, sorry. Go. Well, thanks everyone. Great session. All right. Thank you.