Maximising the Benefits of MCAE Forms with Script [Webinar Replay]

Foreign.

Good afternoon everyone. We hope you can see and hear us. Okay, just get into the chat and let us know if so. Chat is available in the bottom right hand corner. Thanks Hillary, appreciate that. Very interested to know where everyone's joining from today. I'm currently sitting in what looks like a studio but it's in my back office of the house in Dublin and Ireland. John, where are you based? Where are you working from?

I'm based out of Leicestershire in the East Midlands.

Excellent. So yeah, get in the chat everybody. Tell us where you're joining from. Welcome to Mark Cloud. Our event to maximize the benefits of marketing cloud account engagement forms with script. We're going to get started properly in about a minute. We start seeing the entries come up. Oh, all the way from New Jersey. That's great. Hampshire in the uk, another from Louisiana in the us. Amazing. Could be an interesting few days in the us but that's all that needs to be said about what's happening over there. Excellent, Keep letting us know. We've got 28 in the room so far. We've got over 100 registered. So we'll give it a minute. And we will have some polls to publish throughout the webinar. Just some questions would be interested in asking and hopefully can form part of the conversation and either even tailor some of the content towards the answers but just double check on the bottom right hand side. I think the polls may even pop up on the screen for you but do contribute when those come in and we're very interested in discussing and hearing your answers. I think we're about ready John and we can probably crack on with the content from here. Perfect.

Thank you Owen and a warm spooky welcome to our Halloween special. You'll see from the slides we've got a nice theme for Halloween we'll be looking at. As Owen said, we'll be looking at MCA forms and how to maximize these and get most benefit using script where appropriate and making the most of the out of the box functionality that's available. So we'll be looking at some of your horror stories. I'm sorry for all the puns. We're going to get as many in as we can as it is Halloween tomorrow and we'll look at some of the ones that you've actually shared with us as part of the registration process as well. So one thing we've we've put in here as well to keep in the Halloween spirit and to use the chat function, share with us your favorite sort of Halloween character or horror character. I'll share mine with you as Dracula character Dracula an interesting fact about Dracula is that apparently the inspiration for Bram Stoker was his boss for certain traits. So hopefully no one's going to put their boss's name in there and get us into any legal bother. But yeah, please do use the chat function, let us know your favorite horror character and we'll read them out as we go. I will start with a quick intro for myself so I'm John Chowdhury. I'm a Senior Lead Consultant at marcloud. I've been at Markloud for just over two and a half years. I come from a digital marketing background with 20 plus years of experience from a range of different organizations including education, charity, some B2C. But my last role was B2B in a maritime organization where I spent 10 years as a digital marketing manager and also product owner. As it says here. I joined Markloud way back in 2022, so it seems like a long time ago. During this webinar, the agenda is as follows. We'll be talking through MCA forms and form handlers, being sort of two two options you get with Marketing Cloud Account Engagement. And I must apologize if I refer back to Pardot. It's only because I've been working in the space for a while and it's a lot easier to say than we all do. MCAE or Marketing Cloud Account Engagement doesn't roll off the tongue so easily, but we'll be looking at the benefits specifically at the of the NCAE forms looking at completion actions and that change that happened summer 2022 where we had conditional completion actions and you know, the the bits that that gave us in terms of functionality, the the positive sort of functions that were added to the system back in 2022 and then we'll get into the real interesting part whereby we know that the out the box functionality sometimes doesn't meet all the complex needs and we'll use scripts to enhance functionality. So we'll do that through use cases and go through some examples sorry of how we'll do that. And then we'll finally go into a Q and A. So there is the questions function on the webinar, so please feel free to add in there. Owen's looking at that as we go through. So if there's some contextual sort of questions during the presentation and during the webinar, we'll add them in at the time and try and answer some of those. Let's start at the basics. We'll go back to basics of the two functions that are Available within Pardot Marketing Cloud Account Engagement, and that's forms and form handlers. So forms, they're the sort of probably our preferred way of doing things because there are some added features in there that we'll go into in a moment, but these allow you to really quickly create forms using the interface within Pardo, just creating fields and labels, layout templates and thank you messages, but it allows you to very quickly create forms. Those forms are then iframed in to your website or they can be used on a landing page within Pardot as well. And that's opposed to the sort of form handlers that you get. So form handlers, if you've got a lot of website forms that are already pre established, you may go for a form handler which allows you to still post the data into Pardot, make most of the completion action side of things, and the automations that you can run off it and get the information within Pardo, which is most important. They are ways of still maintaining the data and getting the data in there, but they're not going to be using all the functionality that's available on the form side, which we'll look at now. So with Martin Cloud Account Engagement forms, they are very quick to set up. You can, once you've got your field sorted within Pardot and you've mapped them across the Salesforce, they're going to integrate very easily. You can very quickly pick up a form, create a form, which could be a positive and negative because as we'll go into in the user cases, it can mean that sometimes you're grading a lot of forms which can be difficult to manage and know which ones are still relevant. But we'll look at that as part of our user case. Within the forms you get progressive profiling, which we'll look at in a moment as well, and you get built in bot protection, something you don't necessarily get with your form handlers unless your web team is doing something else. You also get to see metrics on the views and errors. The landing page integration is native, so it's easy to pull in a form that you've created and you can automate based on views. So these are some of the real good advantages that you can do. One thing to mention as well, because it comes up a lot with forms, there's a reason why not to use them most of the time. And certainly from our perspective, we haven't had any issues integrating a form onto a website and matching the styles of the website, making it responsive. So I know that comes up a lot As a reason why to use form handlers over forms. Yes, it may be easier to just keep it natively on the web cms, but in terms of us matching iframes so if it looks seamless we can definitely do that with a skilled sort of design team. They can make it responsive and make it seamless. So it shouldn't be the reason not to use forms. I would say this is straight from the mothership of Salesforce in terms of what Pardot forms and form handlers give us. So you can see that the ticks have and let's just look at a couple of the focus areas. This is an area for one of our polls. We're just going to ask you very quickly on the polls area, if you move over to there, just let us know what you prefer in terms of forms and form handlers. And if you're new to Pardot, there's an answer for that as well. So we'll have a quick look at those.

We're live with a poll. Please get your votes in. The question is which tool is powering your forms? Three answers. I use forms. I part of forms prefer form handlers or haven't used either.

Let's see what comes back while the.

Results we're at about 71% saying I use forms. So that's good. Moving towards a lot of folks agreeing part of forms are good, powerful and in use. That can help us shape a bit of the content. Obviously what you see on the screen is a kind of a by the book comparison. There's a lot of little nuances and different stories as to why you should use a form and why maybe a form handler would be preferable. That's sometimes fair too. And there was a question in the chat about well yes, the slides can be shared. So Peter, you're happy to do that. That's easy. But also a call strange for customizing forms to match site design. That's a really easy answer. It depends. Yeah, there will be a cost. The cost range will be how complex is your site design, how simple the form would need to be and the structure of it, et cetera, where it is placed, what the look and feel is like, how it interacts with the site. A lot of what ifs in that. But more than happy to talk to you about it if there's a need coming up in the future. But let's not dwell on that. So back to you John. We can keep moving forward.

Brilliant. Thank you Owen. Yeah, I saw a couple in the chat as well. Well where people are asking about using both, and there is definitely a case to use both and we'll come on to some scenarios around that. So yeah, just if you, if you were answering in the poll, choose the one that you've got most of. There is good reason to use both for third party integrations, for instance, on the form handler side of things. But let's look at some of those specifics. Let's have a. The progressive profiling, we talk a lot about this, but it is a really powerful part of Pardo and how you can enhance the data that you hold by asking different questions because you already hold information about a prospect. So for instance, if you've already got information on the company someone works for, you could ask an alternative question about their job title. So we know that asking too many questions means that the. The number of form submissions will go down. Progressive profiling is a way of managing that. So and still building up the data in the background, which is really going to be useful for things like grading and pushing sales from ready leads across to the team, because you know more about them. So progressive purifying, really powerful, real big advantage of using that and something that we work with, work hard with our clients to get the most out of it. As well as progressive profiling, the bot protection is a big part of it. So with bot protection there is out of the box protection in terms of the capture, conditional capture, whereby IP ranges that are known as spam are immediately sort of stops from submitting. There's also recaptcha available on Pardot forms and there's a honeypot out of the box sort of technique. So that honeypot is just a hidden field on the form, which would basically mean that if a bot saw it and filled it out, it could be distinguished as spam, because it could. It shouldn't have been filled out, basically. So there are some real advantages of using forms over form handlers, but there's still a place for form handlers for sure. So we know that both forms and form handlers have or utilize the automation of completion actions and had them since the beginning of Pardot. Summer 2022 was a big step forward in the world of Pardot, where for the first time we had some conditional completion actions, which meant that we could apply some criteria to the completion actions that we're applying on the form submit. So it could be something like, as the example here, if you can see that if it was on assignment status, if they're not assigned, you could push them through to another team to be notified or to be looking at as a, as a result of it and differentiate them from the prospects that you had assigned which could go through to a different process. There was lots, lots of actions in that list where you can do something different based on the criteria that you're setting. And this was a real game changer if prior to this being around we would have had to do automation rules to run in the background across these things. So really good change. It meant that we could do a lot more within the forms in terms of adding conditions and pushing them to different places or adding different lists and potentially running engagement studios off the back of them based on the criteria that was running. But there were some, and there are some limitations with this. There's only six conditional groups that you can put on there which you can get to very quickly when especially in more complex sort of requirements from our clients that we often get and we'll look at some of those in the use cases. But also in terms of the criteria logic, it's quite simple. It's not and or statements, it's just a line of things so you can't build up those things. So it is the case that sometimes, and certainly with our clients, as good as the out of the box stuff is, it still doesn't really take us all the way to what we need and to meet the needs. So yeah, sometimes the out the box functionality, as great as it is, as many of the issues it solves, sometimes it's not enough. So those completion actions, the other sort of automations that are available, they provide some bits but maybe not enough. This is where scripts can be that magic potion to stick with our theme to open up new possibilities. We use that either in the form layouts or within the form itself to really push things through. Now what that may mean is that you need a developer to help work out those, those bits of script that you need to, to do the, the work you need or, and apologies for the shameless plug here, you could contact a leading POD or NCAE consultancy to help you and mark Cloud being one of those. So it's definitely an area where we work very closely with our clients. They'll come to, to us with very specific sort of needs around. We need a form to do this and we will work around the out the box functionality and where we need to fill in the gaps with scripts and other things we need to do. If you're lucky enough to have a dev team on hand, they can pick up some of these things. But again, this is something we would do a lot with our clients and really optimize what we can get out of those forms. There's time for a another poll. We're going to look at a use case around spam because this is a, this is an issue that comes up quite a lot. So despite the spam protection and the bot protection that is built into forms, we still experience from time to time with clients where Recaptcha and Honeypot still have, despite those those functionalities, the forms still have spam entries come through. And sometimes with this spam it's quite hard to identify it as spam and you have to sort of do analysis of it to work out, okay, is there any patterns in the submissions? Is there anything that we can utilize to see it as spam? So the poll is really about this. Despite all of the spam protection, do you guys still experience issues with spam? And then we'll look at this particular use case where we've done some front end clever sort of front end scripts to try and stop it at entry point points and then also some criteria based things to further analyze it and put a barrier between marketing and sales so that any of these suspected spam submissions can be analyzed before they hit sales and credibility can be lost when sales receive a spam sort of entry on those forms.

Might be good just to call out the the poll again. We've got a good few answers through already but the question is how many active forms are you managing right now the leading answer is somewhere between 20 and 50. Oh, it's, it's moving a little bit now. I'll hold my breath. So we're about 30. 30 split almost between less than 10 I think is quite good. 50 plus which is.

Hey. Oh, and I think the, the order of the polls may have got mixed up there. There should be a spam one which probably is the fair.

Yeah, we will publish now anyway. We'll get all the answers out. The easier question to answer while we're all looking at it as well. Have your forms form handlers suffer from spam submissions? I'm going to answer and say yes we do. Even we would get some but however we've got another poll rolling too which is around the active form. So when you're there get all the answers in. We'll just make sure we call cover it contextually when we get to that part of the presentation. But so far we're about 50, 50 between yes and no here John. So.

Right.

Definitely some pain being felt around spam submissions. Maybe people are getting sold Salesforce users as a list or Dreamforce attendees like I am all the time. But yeah, we've got about 50, 50.

Split still and that's probably true of our own clients. So not all of our clients would actually suffer from it. What we find is when they do it happens and they get a few through. I think there's a question from Hillary around how we would define spam. Yes, I would agree with you. Fake clicks could be seen as spam bad submissions. Absolutely. What we've found, and we'll talk around it with our, with our client case study was it wasn't necessarily strings of random characters. It was actual words, company names and even email address strings that were brought through. So we'll have a look at an example of that. We'll actually show you on our dev environment how we've tackled that and the success of that sort of broad. So this is the use case again despite all those honeypot recaptcha all of these things were in place with these forms. There was an indication that there was still spam submissions. So that was identified on analysis that it was the same company name coming through and each time it was sometimes the email domain there was an example and even in the email itself there was an email string and they were very helpful because they actually wrote fake email on their email address to help us identify them. And then further to that there was also during the analysis with, with the client the time of submission was always between certain very early, sort of in the morning. So between 1 and 4am in the morning they were getting these submissions through. That meant that we could look at that as a potential sort of marker for, for our analysis of spam. With the time of submission obviously it wasn't enough for us to say this is definitely spam. So rather than, you know, stop that from being entered into the system we used the hidden field which was basically called check check for spam where we would through script analyze the time of submission based on the client time zone and we would put a marker in there which meant that we could run automations off the back of it, use conditional completions. In this case we actually used an engagement studio to identify possible spam and then it would go through a further sort of check before going on to the sales team. So just as ways of example, I'm just going to nip over to the. Dev environment. We're just going to show you how this sort of front end script that we've added to to the site could help. So I've got an example fake company of Duff Beer. If I Put that in. It's not going to let me submit. We've put a validation on that to stop it from going through. We've got a look at the domain itself and again we've got a list of all these domains that have been analyzed and marked as spam. We can add to that list over time and actively keep on top of the spam submissions coming through. The other example was it wasn't just the domain so we would actually check for words in here, here. And again these are all lists that we could, we can add to, to maintain a list of possible spam that comes through. As I say on this form as well, there was a further field, a hidden field for check for spam. The code on the layout template is looking at those submission times and it would mark a, a marker in here to say check for spam because it was during these, these times of submission and it just puts in the extra sort of check in because the, the biggest worry here was sending stuff directly to sales before checking it off and before validating it. So not everything would go through validation through to a first sort of line marketing team. But the ones that were during a particular time were there. I think there's a couple of questions on here.

I can help you with those. We've got does the script delete these submissions before they're created in Pardot? So that was to your example a minute ago.

Yeah. So the ones that we saw aren't actually submitting at all. So we're just telling them on the screen. So they wouldn't actually make it to piled up for those front end ones, the ones where we're checking for span because of the timing they would go through. But we've got a process because we've marked them, we can send them through a different process to the one that we would use normally so they can have a further check.

Super. And we've got a tip in from Tom, who might be well known in the marketloud world. Tom is our founder CEO, still heavily engaged in this kind of work. Tom. So thanks for the tip. If your forms are somewhat set up to promote spam, is the question an example being if you have too many fields so you kind of prompt people who are filling in good quality data in field one and field two to get a bit fed up and just crunch the keyboard to try and get the form form completion to get to the asset they're looking for and in which case you can be creating a problem for yourself which is easily solved by using conditional fields or Progressive profiling. The next time that person may come back to to get the next asset, the next valuable piece of of content from you is just to avoid setting yourself up as part of a kind of meta process to get bad data in is just look at the little tactical steps sometimes as as well it's not always that there needs to be a technical solution. It can sometimes be more about the process.

Absolutely. That's a really good tip and a really good use of progressive profiling as well and how it can be used to avoid getting too much of the fake data through all at once. So use case 2 is now on the screen where with our forms we've had these scenarios where quite often the client because of the ease of creating forms, you can create loads of forms. Now what's important in this is our usual sort of clean house sort of message around Pardot. You've got to make sure your naming convention is in order so you know exactly which form are active, especially if you're putting them and iframing them onto your website because you may not know just by looking at them in part or whether you have an iframe on the website for them. So keeping naming conventions, making sure you're on top of the active ones and archiving old ones is really important for forms, but there is ways we can look at to consolidate and sort of reduce the number of forms you have. So this was the question I think Owen, we put in the poll, I think you mentioned earlier, where we're just looking at the sheer volume of forms out there. So it'll be interesting to see some of those results and how how many the the audience have there for that.

So far again we're about a 30, 3030 split almost and then 20 but less than 10 is the top answer or shared top position with 50 plus so quite a quite a gap in the audience between those two. 50 plus is a loss and therefore a lot to handle. Less than 10 might be very nice and tight. You've got multiple uses for forms or it's just more focus on data acquisition then we've got 20 to 50 down to 23, 10 to 20. So yeah, quite a split in the audience between those using a lot and those using a few.

And yeah and that that can be down to the the type of orgs that you're working on especially. But it for those of you who have lots, if you ever have to edit or add a new field or so to them, this may sound very familiar. It takes ages to to go in there and have to update them all. So what we tend to look at from a consultancy point of view is looking at those in terms of top level categories. So usually they fall into one of these sort of categories, the sign up, the webinar, the download, the contact us, the event form, maybe demo requests. So we could look at the similarities between them. Is there any differences and is there a way that we can consolidate them? So one of these forms that is often at the top of it is the download form. Because traditionally you probably would have used a different download form for every bit of collateral you've got, which can result in lots and lots of forms, depending on how your content strategy is. But with this solution we can use hidden fields and query those hidden fields within the iframe. So as this example is, so we've got hidden fields for download name, download URL and we can parse those bits of information and fill them in as part of the submission and then do something off the back of it, give them a link to download the appropriate download on the thank you page, send them an email with those bits in using merge fields. We can take this a bit further with script. So we have a lot of clients who use some of the big web content management systems in terms of WordPress, Drupal, Optimizely, Sitecore. And we can create, or working with the web team, we can create ways of making adding iframes to your website much easier. So you'd have a block for your form where you would add your iframe and for a download form you'd have two fields within that block on your website content management system for the name and the URL, those hidden fields. And then through script we can make sure that those bits of data get pushed in. So managing that becomes much easier from a sort of novice user point of view. And they're familiar with doing things on their website content management system, so it's easier for them to and the team to update those as they go. They don't have to worry about the getting these scripts or the sorry queries on the end of these URLs. Absolutely correct. And we can enhance that further with UTMs and hidden fields for UTMs. But let me just show you this in action again on our sdo org of how these hidden fields. So this is a download form for, well, for the slides for this presentation, for instance. And you'll see that the queries on here, if we were using a website content management system to pass these through, this would be done through script and we would just take Those details and as you hit download you're going to get this is the merge field for the title, the download name and then there's the download URL here. If I click on this, it's going to download the PDF of the slides so you can reuse that again and again for forms. And it helps by having less forms through other automations, you can still make the most of things that you may lose out on having separate completion actions for each download, but there would be other ways in which you could do that and consolidate it. So you're weighing up some of the loss of granularity, but the ease of management of forms going forward. And as I say, using scripts, you can really make the experience easier for people adding them onto adding forms and especially download forms onto the website.

I'm going to run an impromptu poll here and just ask if anyone who is in that cohort of 50 plus forms could see a use case for something like that. Simple script to cut down the number of forms or just increase the utility of a small number of high performing forms. Some cases that's what optimization is going to be. Drop your ideas into the chat or questions, let us know.

Perfect. Thank you, Erin. Further to that, and these are real use cases as well. So taking that download further, we were asked to limit the number of downloads for a client and this would mean that if someone was to download more than three, they would be pushed over to a different cta. So that could be to watch a product demo, to speak to sales to go on a free trial, but it would be a push to something else and they wouldn't be given the download at that point. Try and drive a different behavior. This really combined the most of what we can get out of the Outbox functionality within Pardot, within ncae, but also harnessing what we could do with script. So it was using conditional completion actions based on the number of downloads. We were using the increment function field as a completion action. So every time someone downloaded we would increase it by one and we were maintaining a number there so we could, we could do stuff off it using dynamic content within the emails we were sending to the prospects. So again we could change the messaging to the appropriate messaging based on how many downloads they had. So if they were over three, we would be pushing them to have a free trial. If they were within the limits they would get their link to the download. We also used script because the messaging on the actual thank you message still had to be appropriate because the increment would happen afterwards. We had to use script to make sure that it was on the fly, knowing how many downloads that there were. So it was really a thing to push things off. Jen, I think you've made a really good point there to say not to limit the number of downloads. I think you're probably absolutely right. I prefer the hey, we got people really engaged. This is a really fantastic thing, allowing things to go there. And yeah, I agree putting them onto an engagement studio is probably a better way to go. I understand from the client point of view because they were content heavy sort of organization. I suppose there's a feel of giving everything away for free. So it's, I think an engagement studio and pushing them to other things could, could have some similar sort of goals and results. But this was the sort of criteria and really it was quite an interesting one for us to work on because it brings all of those elements together and through script it opened up sort of the world of what we could do in terms of manipulating the messaging on the thank you. Use Case four, this is another interesting one and one that you may have experienced as well. And this is with Google Analytics. So with GA4 events we've had these scenarios where we're looking at how we can push different event types to GA based on the forms that are being completed. So a couple of examples of this was where there was different brands for a particular client and we were going to different GA accounts. And there was another further one where it's based on the type of products that were going. So we were able to use script and identifiers within the form to push these different events to ga, identifying where they should go and making sure that the analytics all sort of correlated correctly based on the forms that were being completed. So again this, for this particular client there was about four or five brands to contend with. So fairly complicated in certain respects because there was different brands and different events going for them. But through script we were able to sort of map those bits and make sure that the right goals or the right events were going to the right place. And then if we look at use case 5, this is probably looking at the more complex side of the forms that we get. And this one INFORMS involved having a long product list which was categorized. So you had a category for products and then a list underneath. And this was about reusing forms based on URLs to show different fields and different field values based on that. So using that website URL which was structured similar to this where whereby there was a product classification and then a sub product underneath it we were able to look at that and change the field values accordingly. So if they were on a, let's say a printer page, we could show the printer field and all the products that were associated in the form itself. We could manipulate that on a, on a page by page basis by looking at the objects that are here, the JSON objects that were used to categorize those different products and map them to what was shown in the URL, so we could change the values accordingly. So again, we were able to reuse forms, reuse the way things were done, but also show that this sort of contextual value according to the pages that people were visiting. So really powerful sort of scripts that opened up so much more possibilities than were available from the out of the box functionality. So again, good. I think you've probably come across areas where this could be used. One place that I'll look at on the dev. Org in a moment is the countries and states, which uses a similar thing. Probably not as advanced as what we were looking here, but it gives you an idea of how you can use scripts to change the values accordingly. So we'll have a look at that in a moment. I think this was actually from the submission form that we had for the event. So hopefully this is a useful scenario for you. This is the example of countries and states. So again, this is an area in Salesforce and Pardot where, whereby you have different fields for it and they're not that easy to map across according to dependent fields because you don't want to list every state that's possible. But using scripts we can list out the states within the script. We can display different things according to what's happening here. If I select United Kingdom, no states are available. If I select United States and I haven't added all the states, but you can see that these are relevant to the US and again, I can manipulate this according to the country listing so you can use scripts to fill those gaps. So if there's something that you're finding that's not available with some of the functionality, we can use scripts more often than not to fill those gaps and allow for these. And this could be pushed across to Pardot and Salesforce and make sure that we're matching the correct fields with it within there. So there would be a little bit of work to just check that we're, we're doing so, but you can see from a user perspective all those things are being pushed through. I've got one more slide before we check for any further sort of questions and that's just our recap slide.

So.

What I would say is if there's anyone on the call on the webinar that's new to mcie, there is still a balance of what works best for you in terms of form handlers and forms, and that's the consideration of how much work's involved, whether you need progressive profiling, whether there's other areas in terms of the bot protection that you feel you need because you don't have that capability within the web team. So there's definitely still a way up of those. There is times where form handlers are still required. So one use case for us would be something like a third party form, say a LinkedIn form, whereby we would through Zapier connect that to a form handler so we can still utilize conditional completions and completion actions and do automation off the back of it. So form handlers definitely still have their place. And if you've got another example would be if you had an extranet, potentially the registration form, you wouldn't want to recreate that as a part of form. You would use a form handler if you wanted that data to go across the part up. So it's definitely still spaces for form handlers, even if you're main focus would be forms. And as I say, it shouldn't be the styling that lets you down on the form side because we've certainly found we can match and integrate most of our forms with our clients onto their websites. That so much so you wouldn't know that they were iframed in. They're also responsive and would move with the side as well. What we would urge you to do is review those forms, keep on top of them, make sure you've got a good naming convention, you know which ones are active, you know which ones you can archive because it's going to save you a lot of time if you ever need to make changes on there. You can only you can focus your attention on the ones that are active. Consider conditional completion actions, although they've been around for a couple of years, still really powerful, really useful for doing things, we would still push for the out of the box things first. So any of the out of the box functionality we would go to first before we jump into scripts. But if all the out of the box stuff has been exhausted and you still got a need, that's where scripts could come in. And again, liaising with a consultancy or a dev team can help bring those things together and make sure that you can do the stuff you need to on your forms. So with that I'd like to say. Yeah, thank you so much for your attention during this webinar. Is there any further sort of questions?

Was a question, yeah, just to bring you back to start us off, I suppose around. I think it was use case four and is this. Or the question was is this before the Google Ad was clicked or after? So maybe if you take us back to the context and that might be a good question to answer with this on screen.

Yeah, so the. The would be. So in terms of Google Ads we. We would have taken them through UTMs as well. So they would have been passed through as part of this process. So it would tie up to the Google Ads. We would beyond Google Ads also with our clients. If attribution is a really important thing, we would really advise the UTM solution to be used whereby you know, any third party sort of activity can be be pushed through. So yes, it would be tracked as part of that ga or sorry the Google Ad itself and be able to be seen as the source of the form.

Fill a question I have which is really interesting in our lane is around phone number validation. Can scripts be used to augment or improve that experience? Thinking of salespeople want to hit click on a button and dial a number. They don't want to have to worry about the. The sort, the format, etc. Can scripts help there?

Yeah, absolutely. So we've worked with clients whereby. Well, for instance global clients where they have the code, we can integrate with other third parties to make sure that that's correct and then we can use validation to make sure that it's in the right format. So that may mean that we try and push it into the right format if the.