Can you get your Form Completion Rate (FCR) beyond 50%?
Learn about form analytics with Zuko using real Student CRM examples.
Find out how Zuko can pinpoint the friction points in your Student CRM Web Forms and show you where your prospects bale out.
Using Zuko you can make simple changes to increase your form completion rate and improve your recruitment.
Transcript:
Lene Raastad: Now it's definitely recording. I got the notification.
Dom: Thanks. Okay. Good morning everybody. This is a webinar. For one of ethics and we are partnering with Zuko, Zuko analytics. We've known for a great many years and they've got some really cool stats around web form analytics. So they do something way cooler than Google analytics can do way cooler than we can do.
So let her know this morning, I'll go into a co-host and talk you through a little project we've been running in the background. So the little project we're running in the background is in fact that. So Lana and Allen from Zuko and myself, we say Andy, but I think half of CS is here as well. So what we're going to do is I'll do a very quick.
And I'm going to hand over to Zuko and Lenne. And I am going to actually go through the project that we ran together then into Q and A, and then at the end, we've got next steps. So this will be a 30 minute webinar as usual. Um, however, if it wants to run over or we finish early, that's cool as well. And then we'll share the video with everybody.
So the background to this is that. Um, Ryan Taylor from city, university of London, very kindly agreed to participating in this as the, or it has a kind of a Guinea pig web form. So on the, um, The city website is this page. Okay. And embedded on this page is a link to a web form. So this is all about short courses.
Uh, and Ron and I had a look in the back and we agreed that one of these forms is mysteriously underperforming, and we don't know what it is. So why don't we check it out? So what we've done is we've found the form and we found the link. Okay. The link is here, curiously. We've also, uh, Found another link down here, which is an interesting finding we'll talk about later.
And this is inside, uh, runs form, which again, I've got permission to share with you. This is the form itself. Okay. And this is the location that's stored at, which has abated or showed you the most important thing and bewildering for anybody who wants high response rates is this, this is not cool. 1.9% completion indicates there is an issue.
And from our stats, you can see it's getting loads of views and you got the weekend troughs and the week peaks as well. So there's something going on here. Thanks to, uh, Zuko and learner. We have been able to dig a lot deeper into this. So, um, I'm going to ask Lana now to give a quick description of her Allan and Zuko and the part they've played, firstly, in setting.
Zuko tracking.
Lene: Sure. Okay, cool. So what I will do then is I will share my screen so that you can see everything as well. Um, okay. So if I click continue, now, I believe I will kick you out to screen sharing. Are you okay with me doing that? Please? Go ahead. Yeah. Excellent. Okay. Continue. And then I need to choose the correct one, which I think if there's one.
Cool. Cool. Can you see my screen? Okay. Yeah, we can. Perfect. So in, if we first talk about kind of how Sukkot works and how the setup was done. So basically the purpose of Zuko is to help you identify basically where and why people are dropping out of your form. And then once you've identified where and why that then gives you the opportunity to go and change.
And then increase your conversion rates on your forms. Right? So with the set up, it's pretty simple. So how it works, let me just move these faces out of the way so I can see here. So the setup is super simple. So how it works with Zuko for the setup is you have two different tags. So you basically just copy and paste these tags into your form system.
And we did this together, didn't we? Dom. And how long did it take you think? Was it five.
Dom: Uh, probably less than that. Yeah. It's well established. There's also help center articles in the help center if you want to set it up, but it's straightforward if you got stuck, um, chat with Steph and her team as well.
Thanks Lene.
Lene: Okay. So once you've set everything up, that's when you start getting the data through, right? So that's what I'll show you now. So incident go, you'll have these different databases. So, what we've got here is the form data. And this one gives you the kinds of top level data of your starters and completions and views to the forum.
Then I'll take you into the other reports later on that goes a little bit deeper into each individual field. Um, but first, if we look at the city form here, you can see the people that viewed the form, uh, removed the best. So based on the people that viewed the form, as you can see, it's a similar kind of peaks and troughs.
So we're looking at before. Then you can see the people actually started the form. And this is one of the things we noticed when we were looking at this data is that there's quite a big gap here between the people that view this form and the people that start this form. So this kind of goes back to what we were looking at before, when you looked at where on the page.
So, let me get my tub here
Dom: and the difference lender between your blue line and the red line is in line with the 1.9% completion rate that we're getting inside. Um, cities, web form itself, we run the stats and we're, we stop at 1.9%, but you can go much deeper so you can see the problem that we can see the differences.
You can go right into it and figure out what's going on.
Lene: Yeah, that's completely true. So basically, just to, just to show you this again, so basis where the form actually was. So what we noticed was that basically anybody that goes on this page, regardless of which form they're actually going on to, or if they go onto form at all, gets counted as a view on this form, which then of course contributes quite a lot to a very, very.
Uh, view to stops, right? And then again, of U2 to completion, right? So on average, based on our benchmarking stats that we have from the education sector, we're looking at around a benchmark and conversion rates of around 70% doesn't overall. Um, and then for applications is around six to two points. Um, and for inquiries around 77%, which is quite different to the kind of stats we're seeing here.
But yeah. So let me jump back to the farm itself. And then of course we have the completions and also the abandons here. So completion is of course, somebody that successfully completes the form and then abandoned is somebody that starts the form, but then leaves at some point. And these are the people you want to identity.
Why they abandoned. Right. But as part of the kind of overall data, we also have these things here, which is basically a conversion rates. So like we spoke about before kind of your view, proportionately who views the form starts to form. And of course also who've used the form, ends up completing the form as well.
And it's also quite interesting to look at the difference between the complete and abandoned sessions. So in this form here, you can see. Um, these are the average complete sessions to patients, and these are the average abandoned session durations. So of course, normally you might have a little bit, um, more data in here.
So we normally recommend having at least around a thousand sessions before you started. Proper conclusions, because of course you need, you need that number two, to make sure that you have statistical relevant evidence here. So what I'll do is I'll take you through the kind of data we gathered here. And then I'll also show you an example from another form that has a lot more data in it, so they could see how you can draw conclusions from this data.
Dom: Would you mind scrolling up just for a second? There was. So on the right-hand side at the bottom, you've got to start to do completion rate 3.75%. Now that may appear to other universities there's quite a healthy, uh, completion rate. However, in your experience, it's not as high as the average numbers you're getting from education for, uh, clients that use
Lene: That's true. So, uh, the average was around a 62% for application form. From starts to completion. Right? Interesting
Dom: inquiry forms.
Lene: Yes. An inquiry forms are even higher. There's 77% on average.
Dom: Okay. So that's something for all of our users to aim for. Um, and it's worth bearing in mind that if we don't. Web forms.
Uh, they are the lifeblood of feeding into students' CRM with your web forms. You don't have enough of them if they're not behaving properly, if they're not distributed in the right places, uh, your students are suffering from, you know, a starvation of fuel here. So what lenders from can do is to take the forms you've got and just increase the response rate, massively.
Everything else flows through the front of much better when you've got a lot more coming in. Okay, Linda. Thank you,
Lene: definitely. Okay, cool. So, uh, continue on. So here you have basically the difference then between the abandoned and completed completed session. So the session duration here, you can see that in this form so far, the average completed session duration is around six minutes.
Whilst the average abandoned session duration is around one minute. And when you see that kind of difference, then you can. Already kind of assume that the people that are leaving are leaving quite early on in the journey compared to the six minutes, it takes to complete the form, for example. Um, and here we have a field return.
So what we mean by field return is basically if somebody interacts with the field, um, then they move on and then they have to return back to that field. Maybe they had an error message or maybe they had to go back and change. Um, so, so normally it's quite good to, to compare the difference here. So if an abundance sessions are on average, returning a lot more, that can indicators of friction.
If they're returning a lot less back in indicate leaving early on in the journey, and then you have this one here, which basically shows you the failed submissions over time. So these are the people that make it all the way to the end of your form. And they try to submit, but they fail to do it probably because they had an RMS.
That meant that they hadn't filled in the phone properly. Cool. And then the next one we'll we'll dig into them is the field data. So after you've kind of looked at all the overall, uh, data, I forgot to mention actually you can, of course add any filters you want here as well. If you want to filter by a specific date range, and then out of the box, we do also have other filters to look at here.
So you can, um, look at different browser families, new versus returning user, for example, and device types are all there for you to kind of filter from. Cool. And then the next one we then have is the field data, which then shows you each individual field, uh, in your form. So how Sukkot works is it pulls these in, based on, um, HTML, uh, name or ID.
So I'll quickly show you also, cause this is. Um, you can customize this within Zuko so you can call it something else. If you don't want to call it what it comes in as, so where you see, there we go. So if we go here to the label fields, you can see that in this form have already labeled these fields. Out of the box.
These came in based on their, um, HTML names and IDs here, which is basically a student undisclosed first name you can see here, and it's, it's just been renamed to first name just to make it easier. Um, and that means you can also actually order all these fields in order how they appear in your form, uh, by simply dragging and dropping to customize the order of your fields here.
So let me go back to the data. And then what you see here is basically a graphical overview of where there might be some friction in your form. So what they show us too, it shows you the proportion of abundance. So which fields had the highest proportion of abundance. It shows you which fields have the most proportion of field time.
So that means how much time they're actually spending in the field. Normally, of course, that is text fields that spending more time in, rather than buttons, for example, Uh, and then also start to see which fields proportionately people are returning to the most. So you can isolate out and look at what you want to do.
And the rule of thumb here is basically the longer the bar is. The more likely there is to be some sort of friction with them.
Dom: Could we infer Lana from that extremely long bar on inquiry message at the bottom. Can we infer that clients are sufficiently invested at that point? They're not in, they're not abandoning from that field typing along message and they're submitting and they're going back a little bit, the yellow bar at the end.
They're going back. Certainly not as much as they are in other fields.
Lene: Yeah. The field time. Of course, the majority of field time is spent in that field, which does make sense from the nature of the field, because it's probably a field with a type in maybe even a sentence. Right. So,
Dom: so that's really interesting to see that when they're down to their, they're investing their time in the form and then abandoning that or after if you show abandoned.
Lene: You have a couple of abandons on the submit button and then a couple of abandons here, but in this form with the amount of data that's here at the moment, the majority of people are abandoning either before hitting and hitting this part of the. We're a little bit off, but yeah. So if you want to look at the actual abandon counts, you do that further down spend, you can see the total abandoned count on each field, what proportion that place of abundance, and also be abandoned rate within the field.
So the abandon rate within the field is basically out of everybody that interacted with the field. What percentage of people then ended up abandoning? So as you can see here, the numbers are still quite low. So that's why I'll use another example for a little bit later on just to show how you can draw better conclusions from it.
But if you just look at this, uh, as it is now a course ID is at the moment, the biggest contributor to abandoned.
Dom: And to clarify, the reason that we have low data in the city form, uh, is because on S you will show him one of the learnings at the end of this. Usually there's a lot more data flows in far more quickly, and that's something that a lender is going to show you again, another account that's running this, isn't a city account.
You're about to say, but it's got so much data. It gives you a much better indication of what your forms will actually be collect.
Lene: Yeah. Yeah. So, um, is it easier if I now show that example straight away? So we can, we can look at, look at the same reports from both, or should I do it towards.
Dom: That's up to you.
Lene: I think maybe it might be easier to just show it now. So if we, so now that we're already looking at this report to say as an example, let's look at this one here. Yes. So if we look at this example here, you see, we have a lot more data. So you end up then getting, um, some buttons or. Spending out a lot more in terms of abandoned.
So this is an example from a different industry as well, but it's quite a tight example to look at. So if you see similarly to what we just looked at, you can see the biggest contributor to abandons in this example, form is the step one submit button here. And you can see that that's around half of all abundance, but you can also see that you have some other contributors to abundance.
If you look at abandoned. Right? So for example, This is a multi-step form. So if you look at the step three submitted person here, which is much lower, actual, total abandoned count, but the abandoned rate is still around half of the people that interact here they leave, which means there's also some friction with some fields in, in step three.
So just, just to kind of show how it looks like when you have more data. So let me toggle back to where I was. Um, then the next one here, we have field abundance over time. So this one is normally used. If you make a change to a field and you want to see if that change had an impact on the field directly.
So a changed a field might be that, say that you have identified. Let's see, we identify that the course ID is the biggest contributor to abandon. And you want to change maybe the description of the field, or maybe you want to change the error message that comes within the field. And then you choose that field and you look here.
So at the moment, because there's not much data that looks like this, but if I talk back again to where I was, um, when you have more data, you can kind of see how this moves over time. Then you can see if you've changed, how the impact, uh, in the abandoned, in that specific. So
Dom: then, uh, your, your sulfur Zuko identifies protect potential.
Well, first of all, it's identifies whether the numbers are too high, you need them lower. Like the abandoned rates are too high. Let's bring them down. Or the completion rate is too high. Let's bring it up. So as a result of all of this, you've just said that over time you could, for example, recommend to city, they do three things with their web form.
And if they did all of that, this. Then when you run the stats, you should be able to see the low numbers getting higher and the high numbers getting lower over time. So you can see the difference it's made.
Lene: Um, brilliant. And then another thing you want to, to focus on because, um, quite often, if a field has friction, that means they have to go back to the field and change it. If everything is straightforward with the field or use it probably will not have to return to it. That's why this field returns overview is quite important to look at as well.
So here you can see. Proportionately which feels have, uh, the most amount of returns to it. You can also focus on only abandoned sessions if you want to, or you can, you can do a mix. So you can see here, this is a little bit of a mix between, uh, returns across abandoned and completed sessions, but you can actually see at the moment, the only people that have returned the submit button eventually completed.
So that's a good thing. And then if you want to dig a little bit deeper and to feel returns, that's when you get this graph here. So basically this shows you kind of three different things here. So you have the number of sessions that interacted with each field. So you have here, uh, the total number of sessions that's interacted with the first name field.
So you can see here 37 people interacted with the first name field out of these people. 16 of them ultimately abandoned at some point later in the journey and 21 of these people ultimately. And then you can look at the percentage of sessions that returned to this field. So you can see that 25% of these abundance sessions had the return to the first name field whilst only 4%, almost 5% actually of these completed sessions, 21 sessions they had.
So that's why soup is kind of trying to help you to identify where there might be friction by highlighting this. So where there is a statistical relevant difference between returns of abandoned and completed sessions, it gets highlighted. So the red means that it's abandoned sessions that returns more.
And if it's highlighted in blue over here, then if the completed sessions that gets returned. And then basically here, you just have the average number of returns to the fields out. So the people that return to field on average, how many times do they have to return to the field? So that's also something that's really nice to look at if there is a field that they have to return to a lot of times.
So I'll toggle back to my other example here again, just to show some way where they have a little bit more data to look at. So, if you look at here, for example, let's see average returns to fails. So you can see, for example, let me see if there's one with a low. So if you look at this animal birthday tier, for example, you can see that this one is highlighted in blue, actually, um, compared to the other ones.
So here complete the sessions are proportion of returning more and you can see that completed sessions are returning almost two times loss dependent sessions. Run one and a half times on average. So that's something to look at as well as specific, especially, um, it's good to highlight if abandoned sessions that returning a lot.
So sometimes you might see, uh, if you have a phone number field or something like that, where the use of comped, um, cons get the formatting, right then quite often, abandoned sessions might have. On average for field returns, for example. And then that could cause so much friction at the end of abandoning.
So that's something we would see from experience. Let me.
Dom: So the, uh, the, the stats that you're showing, um, again, you're familiar with your platform. And I imagine the rest of us who are marketers and are thinking, this is a great load of stats, firstly, to get guidance, to work through your platform and to understand where to find the issues and the friction points.
Um, how would a user do that? So two-part question. Firstly, how would you use a, learn your software so now know where to jump, to, to get the beds. And then once you've identified that it is the first name and the date of birth that you've got a suspicion, there's an issue with, how can you help them decide actually how to affect it because we're measuring it, but we then want to improve it.
So one how to use the software B what to do with your recommendation.
Lene: Sure. Okay. So how do you use the software? When we onboard a new user, we have, uh, an in-depth training session together first, where we teach them kind of what to look out for and how to interpret the data. Uh, we also offer monthly bimonthly or quarterly check-ins with you as well to kind of help them look at the data together if they have any problems.
Um, and then kind of when it comes to how to action today. Uh, we're also able to, to help with base and experience kind of what could be causing it. So specifically if we're using an example, like phone number that I used before, uh, quite often it has to do with, with formatting, um, or the error message or the description around it.
Uh, quite often, if it has to do with any kind of personal data, like you're asking for, say an email address and a phone phone number again, maybe the user doesn't really realize why you need it. So it might be that we recommend you to, to explain why this information is needed, for example, and
Dom: the recommendations that you had come up with these, uh, um, actions that I'll use as can immediate.
Uh, undertake themselves by just creating a new version of the web form, create all of that. And then at a certain time, you'll say, okay, version two. Now it goes live. And Zuko immediately starts to see the impact of those changes. So all of your recommendations are actionable inside web form builder by users themselves.
Lene: Yeah. Sometimes the recommendation might also be even just to, to change up the order of the questions a little bit. So there's one, I haven't had time to, to show you guys yet, but if we look at the field fly, for example, so what this can kind of show you. So say if you, for example, have identified that there's an issue with.
The submit button that a lot of people are leaving there. You can look at where they go onto next. So you can look at, okay, they're clicking the submit button. Then they have to return back to say subject of interest ID. Right. And that then kind of indicates that, okay, so they had an error message with this field, uh, what's wrong with this field?
How can we make them not jump this field, but you can also use this to kind of see how people flow through your form. So say you have your first field to get form here. You see, okay. The majority of people are moving on to the last name, which makes sense. Okay. Let's look at last name. Okay. The majority I'm moving on to student email makes sense.
But then at some point, if you find that kind of the path people are taking is spreading a bit, might indicate a little bit of confusion, and then maybe this could also just be, be helped by larger things. Cool. And does that, does that kind of answer the question or did I go a little bit rogue there? I tend to
all of a sudden, okay, cool. So this there's a couple of things I ever post. I haven't shown yet. I realize that we've kind of run over already, but if you have time to stick around while I share the rest, that would be awesome. Cause the rest we have to show now is kind of the. Digging a little bit deeper reports.
So we do also have, um, this report called session Explorer. So say you have identified which fields are causing issues. You've looked at the flow, how people are flowing through your forum. And again, identified how, which fields people are returned active, for example, off the submit. So the people that are making it to the end, and then you might want to go to this one called session Explorer here, which basically then shows you individual users.
That are matching your criteria. So I have already filtered this, um, by sessions that interacted with the submit button. So they made it all the way to the end of this form. And I filtered by abandoned session as well. So then it goes, this, there's not a lot of data here. Now. It only returned, um, to uses that that matches this criteria.
But when you have more data, you'll get more users to look at. So, what this allows you to see is actual real users on how they flow through your form. So here you can see this user here, you got all the metadata on the top. They have around eight field returns, which means there was definitely some friction.
And that's probably the reason why they didn't manage to complete this form. They spent almost 10 minutes to try and complete it as well. And then you can kind of work your way down and see how they move. So you can see this user here moved fine from first name, last name to email. No problem. Uh, residents ID.
You can see them moving through no issues. So if there is a field return, that's highlighted in red. So if they have to return back to field and edit the data that's red and the field we are looking for will be highlighted in yellow. So you can move through here. You can see, and then not having any problems until they get to these fields here.
Now they have to return back to the year of entry and also the subject of interest ID that you have here. And then they continue down the field. They have to return again to. To these fields, uh, continuing, moving down, they tried to submit it. Doesn't work again, have to return back to a subject of interest ID course ID substitute interest ID.
Again, they returned it five times actually before eventually leaving the form. So this, this is really good kind of piece of data to look at if you want to. An actual example, to match your hypothesis and match the kind of overall data that you've seen. So this is really nice to get that super in depth, uh, individual, uh, look,
Dom: that's really great because, um, obviously all Google is going to get you and all our stats is going to get you is the, uh, loading of the form and the completion of the form.
So the session that breaks it down as every single step is, is excellent. I love the granularity of that.
Lene: Brilliant. Um, and then of course, we also do have, um, the segment comparison that I haven't shown yet. So what this does, it allows you to compare. If you have several different forms, you can compare them against each other, or you can also compare the same form with, um, with different filters.
So you can see here, I have already added a comparison. I, you can add in more, if you want somebody to just fail, to take. To see the difference in this particular form from desktop versus mobile users. So you can see that these stats here, this basically been Ciro status from the mobile device. So oldest starts you've had in this form have come from the desk.
Um, but it might be that you can do, for example, novice returning users here, you can compare different kinds of forms to each other. So this is super flexible for you to build any comparison you want to build based on the forms you have in the system. And then of course, you can look at these five a time as well as if you're looking at views.
Of course, now you will have oldest artists from, from one pass. If I look at start to completion right here is of course only going to be one within the staff in it. Um, But, yeah. So this gives you the flexibility to kind of, kind of look at the data and do what you want with it. And this is also exported as a PDF.
So super nice and easy. If you just want to send around a report to the business, for example, um, I did forget to mention that most of the reports are exported as a PDF and some are also exportable as a CSV as well. Um, for, for that.
Dom: Well, thank you ever so much later. I mean, I'm, I'm completely impressed with the package now that we've used it before with you.
Uh, I think it gives our use as, uh, an insight into, uh, forms that was just not possible any other way. I think interpreting the data is best done with you alongside, um, journeying through the software and then understanding it. And then when it comes to actual. Actioning the recommendations again, uh, you can work with any users can work with our team or just directly.
And so I've worked for a minute. I love
Lene: brilliant. Brilliant. I was just going to say, so what we do find is uses normally get very comfortable with, with analyzing the data after. Say say a couple of months of working together or maybe even one session together. It completely depends on, uh, on, on the users.
That's a big mix, but yeah, we're always happy to have regular catch-ups and look through the data together. I think it's, uh, it's really fun to, to identify pain points for users. And definitely when you see conversion rates massively improving.
Dom: Fantastic. Thank you ever so much. So I'm going to pretend to, uh, the deck we've got here and it did run a slightly longer than they thought, but really worthwhile.
I'm really pleased you went through and showed us all of those, um, examples. Now what's interesting about, uh, what we saw with, uh, Citi is there are some takeaways there. Firstly, the formats. Okay. At 40 I'd know, middle forties percent completion rate is not bad. And most people would agree. That's not bad at all, but it's below where it could be.
But the second thing of course, which is a learning that I found out is that the, uh, the form itself linked to from the page, um, actually in city's case, Uh, a link that was used to embed that form actually had a locked version. So if you open up the web form, it opens up version 11. And at the moment we've version of the web form that is current is version 16.
So we'll be following up with Reese and Ryan to just make that tiny little change on their website. And also we'll look at ways of tightening it down. So you don't get so many formulators to begin with and the stats aren't so polluted as for the form performances. Totally with a Lennar, which is just brilliant.
So we've looked at cities form. We've looked at, uh, other forms. We looked at how the system is set up and worked. So this is the point staff where everyone can come off mute and foreign any questions, or if any of these questions is very similar to the one you want, please say,
Lene: Yeah. So Gareth had a question about student CRM. Um, he asked and I think this is, might be quite relevant for something that we're doing at the moment. He asked where the multistep forms are possible in web form builder.
Dom: Okay. Uh, they are in the, I've seen. But it's not released yet in web form builder.
Now, as Zuko does support multi-step forms, the implementation of the code might be a little bit different. Um, but it does that. So you'll be able to see through Lennar's system that it stopped at stage three, you stopped at stage four and the granular inside that, but yes, multi-stage, or multipage forms are on their way.
And if anybody wants a private viewing of that, Uh, please do get in touch with staff and we can show you something that no one else can look at yet.
Cool. Okay. So, um, how much does it cost? It's a good question. So obviously when you've bought students around, you have as many web forms as you like built in our built-in sort of very blunt tracking, uh, to get Zuko on the case. How does it work? How does somebody engage you? And what's the cost over a month or quarter or a year?
Lene: Sure. Um, so if you want to use your go, we do of course have a 1000 free trial for, for new users to test first. Then if the user is super happy with the data that comes through, which most people are, hopefully then they can sign up for either a rolling monthly contract. Or we also have yearly contracts.
If somebody wants to just do the super flexible monthly contract, it basically is no minimum time. You can, you can join and, um, Uh, cancel and rejoined whenever you want. Um, that is basically based on the total number of sessions you attract. So the number of views you have on your form, so the kind of lower level you have up to 10,000 views.
And this, you can, you can use to go on as many forms as you want. So it's not. Um, account per form. You can add as many forms as you want. So it's only limited by the number of views on your forms. So the lowest tier we have, it's up to 10,000 views. That's a hundred pounds per month. Then we have 25,000 views, which is 250 pounds per month.
And up to 50,000 views, which is 500 pounds a month. And then if you want to, to get the one year contract, it's a 20% discount on, on that.
Dom: Thank you. So if any students from a university is thinking about this, um, the question of return on investment, the number of students that come out the bottom of an optimized form, that's been through the Zuko process compared to them, the students that don't, if you don't engage Sukkot and don't spend the money on the stats for 3, 4, 5 months, you need enough time in there.
Uh, I think it's, uh, a very affordable solution for getting it into. Um, so I personally think it's a, uh, it's a no brainer for me and at those prices, I also think it's a no brainer. And with lender support at the side, where then a might want to, um, help you with private consultancy as well at the back, I think it's absolutely critical for cities form.
We will have woken it up and made a big change to it as a result of what Leonard discussed. As well, so yeah, that sets up, um, how much it cost on a yearly contract. Another question there, question two is who sets up the tracking? So a university has logged on spoken to you and they have those Zucca accounts.
How do they set up with tracking?
Lene: Well, they will do it themselves, or, I mean, we can also help. So quite often what I do, if anybody has any issues with getting the tracking set up. So remember how I showed earlier on in the webinar, how you get these, when you create a form, you get these two tracking codes. Um, you basically. Copy them and paste them into your system, uh, what we can do and what we sometimes do.
If anybody has any problems, really to do a screen-share schedule them, say a half an hour meeting, and then that in less than five minutes, it should be done in that meeting if anybody has any problems.
Dom: Okay. Thank you very much. And again, the point of tracking any web form. Yes, you can. You can have multiple web forms inside Zuko and add down metrics inside web form builder inside students.
Sarah. Thank you. Okay. We'll wrap this up in a second. And the next steps is anybody interested in taking their forms to the next level and basically increasing performance, uh, links here that will be shared. This deck will be shared in a touchpoint that goes out after this webinar. So firstly, we've got the website.
Um, over at Zuko, then you've got lenders email to go through and our spine or any questions. And again, we'll also support any questions that come through our customer support at the same time. So yeah. Point three, analyze your forms, increase your conversion rates. I think it's an excellent tool to have,
and thank you very much. And for Allen as well for, uh, partnering with us on. Uh, and for enabling city to run these tests. So really great. Thank you guys. That's been so good. So stuff over to you for a final wrap up.
Lene: That was really useful. Um, Ryan did have to leave earlier, but he's going to watch the rest of the. So that's, that'd be fine. Um, if it's anything that needs to be followed up support wise, then that can come through us. That's no problem at all. Um, when we finish this, the recording will be available and so will the deck, and that'll be sent to people who were here and people who didn't come as well.
Thank you very much.
Dom: Thanks very much everybody. Thanks everybody. Bye-bye. Bye bye now. Bye bye.
