.svg){kind=small}
If you can’t find the answer to your question here you can get more details from our product guide section or contact us on support@zuko.io
There are two pieces of code that you will have to install on your site - one triggers on form load and the other on successful form completion. You can do this via a tag manager or through installing the code directly to the site.
If you look at the “Live” tab in your Zuko account you’ll be able to see whether Zuko is picking up your form view and completion events. You can also use the network tab of your browser to check whether specific Zuko events are firing.
The Zuko javascript is 4.7 kb in size (12.7 kb uncompressed) in size which means there is minimal impact on page loads. You can view more technical information about Zuko here.
Zuko has been designed to track all types of forms so tracking multi-step forms is pretty easy. You can read the guide to setting up multi-step forms here.
Yes, Zuko has an IP blocking function if you want to exclude certain visitors (testers, for instance). You can find this under the “IP Filters” tab in the “Organisations” section of your account.
You can find our technical documentation here. This provides an overview of the basics of installing Zuko plus the more advanced features that are available.
The Zuko pricing model is based on the number of form sessions tracked per month. You can view the different packages available on our pricing page.
A form session is an individual visitor visiting your form. That visitor will then be tracked until they either complete the form or have thirty minutes of inactivity. At that point the form session will be closed off and the data pushed into the Zuko dashboard. If the visitor subsequently returns to the form after this period, a new form session will be created.
The standard model is a rolling monthly subscription that can be cancelled or upgraded at any time from within your Zuko account. This is designed to be super-flexible; you can change your package quickly depending on your needs.
Yes, if you pay for a full year there is a 20% discount over the monthly price.
If you run out of sessions for one month your Zuko data will stop tracking but will, of course, re-start again the next month. If you see that you are going to run out of sessions (we’ll email you if you are getting close to the limit), you can easily upgrade to a larger allowance in the Organisations section of your Zuko account.
The Enterprise Package is for companies that want to track more than 50,000 form sessions per month. When purchasing a Zuko Enterprise Package the unit price per session tracked comes down substantially in return for a longer term licence (usually one year). As Zuko’s Enterprise plans are built to suit your needs we price them individually depending on your volumes and commitments. Contact Zuko’s sales team for more details.
You can track as many forms as you want at no additional cost. They will all fall under the Zuko session package that you have purchased.
No, you can add other users to your account for free from within your dashboard.
Yes, you can sign up here for a free trial that allows you to track 1,000 form sessions. You can access all of Zuko’s functionality, there is no commitment and we won’t ask you for a credit card.
An abandoned session is counted after a visitor does not successfully complete the form and is inactive for 30 minutes.
A field return means that the visitor interacted with the field, then went back to it to change their input. For example, if they were prompted by an error message.
Field abandonment shows which was the last field or button the visitor interacted with before abandoning your form.
Abandonment rate is calculated by:
Number of visitors who abandoned on the field / Total number of visitors who interacted on the field.
For example; 100 visitors abandoned on the field, 1,000 visitors interacted with the field. The abandonment rate is 10% (100 / 1,000).
Each report in Zuko has in-depth tooltips to help you understand what it means and how to best use them. If you have any other questions, you also have the support of your account manager to help you analyse your data. Click here for advice on getting your first insights.
Data is kept within the Zuko dashboard for one year.
Yes, Zuko’s Segment Comparison Report has been designed with this in mind.
Zuko report data can be exported in CSV format and the Zuko reports can be downloaded as a shareable pdf. Zuko also has an API which allows you to pull the data out so that you can push it into your own reporting systems. For more details on accessing the API please contact Zuko’s support team.
Yes, Zuko’s customer success team will be on hand to help you get started and to ensure that you get the most out of Zuko’s data and insights. They’ll be in touch once you have signed up or you can contact them by emailing support@zuko.io.
Zuko have a consultancy team dedicated to optimizing the performance of web forms and checkouts. They can take a look and provide detailed design advice for your form.
Zuko’s form optimization consultancy offering is available for customers who want an in-depth report into their form and how to improve it. In a nutshell, Zuko’s customer success team will point you in the right direction; our consultancy team will do the analysis for you. The customer success support is part of the Zuko software license; there would be an additional charge for a full blown consultancy project.
Yes. Zuko has been built with GDPR compliance in mind. Zuko does not track any information that the end user inputs into your form, only their behaviour (clicks + keypresses). For more details, please read the GDPR & Privacy section of Zuko’s Terms & Conditions.
Zuko uses first party cookies in order to deliver tracking. We do not use third party cookies nor collect personally identifiable information from end users. For more information please read our Cookies Statement.
Custom attributes are essentially filters: groups of visitors that can be individually analysed within Zuko. For example, visitors who have selected a particular product or who are from a particular geography. The custom attributes feature has been designed to be very flexible - if you are already tracking any attribute of a visitor group you should be able to push it into Zuko. For more details read our guide to using custom attributes.
Custom events are individual occurrences within your form that can be pushed into Zuko’s dashboard (in a similar way to Google Analytics). By far the most common use case for custom events is to track which error messages have been displayed in your form and how many times they were triggered, although you can technically push any form event in if you desire. Our guide to using custom events can be found here.
Think of custom attributes as essentially an audience group with a particular attribute that you can filter Zuko data on. Custom events are single occurrences that can track in much the same way as Google Analytics does.
Zuko has a specific code tag that can be added to your site which lets you track the source of traffic to your site / form and push it into the dashboard as a custom attribute. This is based on Googles "Medium" dimension. The guide to add this tag can be read here.
Zuko has been set up to track all standard form elements. If you are using a non-standard element in your form (for example a ‘div’ or ‘span’ element), you are still able to track it. Zuko has a feature that lets you treat these as standard elements so they can be tracked as normal.
Zuko has direct integrations with Google Optimize, Convert and Optimizely which enable test variants to be pushed into the dashboard as custom attributes. However, we are also able to take the same data from pretty much all the experimentation platforms. If you contact our team on support@zuko.io we’d be happy to help you do this.
