Key Concepts

Table of contents

1. Introduction
2. How Zuko works
3. Key terms
   1. Visitor
   2. Session
   3. Slug
   4. Domain
   5. Forms
   6. Fields
   7. Events
   8. Attributes
      1. Default Attributes
         1. browserFamily
         2. Operating System
         3. deviceType
         4. Visitor Type
         5. autofillTriggered
         6. trafficMedium
      2. Custom Attributes
   9. Custom Events
   10. Field Returns
   11. Flurries

Introduction

Zuko is a SaaS platform designed to help you understand how your website visitors are interacting with your online forms, surveys and checkouts.

How Zuko works

Zuko works by tracking your site visitors when they:

• View your form
• Interact with your form’s fields
• Successfully complete your form

Zuko tracks these events by adding a tracking JavaScript to your web page. Zuko does not track your visitor’s data that they enter into your form, but simply that they are entering data and how they are interacting with the form.

From the data that we collect, we calculate the metrics that enable you to discover the issues that your visitors encounter whilst interacting with your forms. This data is made available through the Zuko app.

Key terms

Visitor

A visitor is someone who interacts with your form and is given a unique ID. Their unique ID is persisted across all forms on the same domain.

Session

A session represents a period of activity from when a visitor first views your form, then interacts with it, to when they either complete the form or stop interacting with the form. If a visitor is inactive for more than 30 minutes, the session will expire and Zuko will class this session as abandoned. Subsequent events from this visitor after 30 minutes of inactivity will create a new session.

Slug

A slug is a unique identifier for your form on your domain. When events are sent to the Zuko platform, they include the slug and domain from where the event originates. When combined, slug and domain form a unique identifier for a form on the Zuko platform.

Domain

The domain that Zuko uses is the domain that your site is on, ignoring subdomains.

Here are some examples of URLs and the domain that will be used by Zuko:

Forms

Any standard HTML element can be tracked as a form in Zuko.

Fields

Zuko tracks interactions on these types of HTML elements:

• <input>
  • type="button"
  • type="checkbox"
  • type="date"
  • type="datetime-local"
  • type="email"
  • type="month"
  • type="number"
  • type="password"
  • type="radio"
  • type="range"
  • type="reset"
  • type="search"
  • type="submit"
  • type="tel"
  • type="text"
  • type="time"
  • type="url"
  • type="week"
  • Note: type="hidden" is not a supported attribute for an <input> element as visitors are unable to interact with these fields.
• <textarea>
  • Note: type is not a supported attribute for a <textarea> element.
• <select>
  • Note: type is not a supported attribute for a <select> element.
• <button>
  • type="button"
  • type="reset"
  • type="submit"

Along with a field’s tagName, Zuko records three optional HTML attributes for each field: type, name and id.

It is important that your fields can be identified by a combination of the field’s tagName and these three HTML attributes. Your account manager will then help to label your fields to easily view them in the Zuko app.

Events

Zuko tracks the following standard event types on your fields:

• change
• click
• input

Attributes

Zuko allows you to assign attributes to a visitor’s session. You can then compare segments of visitors, and explore certain behaviours and outcomes across segments.

Default Attributes

By default, Zuko will automatically detect and track a series of attributes for you.

browserFamily

The browser that the visitor used to interact with the form

Operating System

The type of operating system that the visitor used to interact with the form

deviceType

The device type that the visitor used to interact with the form

Visitor Type

Determines if the visitor is new to the form, or is returning to the form

autofillTriggered

Identifies if the visitor used autofill on your form

trafficMedium

Once you setup traffic medium tracking, Zuko will automatically detect and track this attribute for you.

This attributes describes the medium that the visitor came through to reach your website

Custom Attributes

You also have the ability to push any information you collect about your visitors into the platform. An attribute is a piece of information about a visitor. Custom attributes are intended to segment your form’s sessions, they are not intended to be used for identifiers.

Examples of custom attributes are:

• visitorSource e.g. email, market_campaign
• existingCustomer e.g. true, false
• campaignRef e.g. testA, testB

Custom Events

Visitors will encounter specific types of events when interacting with your form. For example, they may encounter field errors or see promotional messages.

Zuko can track these custom events as and when they occur throughout a visitor’s session. Even if they occur multiple times for the same event type, you can send as many custom events as you need.

Custom events are sent simply as a short string to describe the event type.

Examples of custom events are:

• Email field: email invalid
• Promotion: 20% discount code
• Error_email-field-is-invalid

By default, Zuko will automatically track this custom event:

• Autofill triggered Identifies the first time the visitor used autofill on your form

Field Returns

During a session, visitor will interact with a field – for example the email field – then proceed on to the password field, then attempt to submit the form.

At this point, validation on the form may stop the form from being submitted if the email is not valid. The visitor would then return to the email field to correct their mistake before attempting to submit the form again.

This is classed as a field return. Any number of field returns my occur within a session.

Flurries

The term flurry covers the time between a visitor starting and stopping interacting with a particular field in your form, before progressing on to another field in the form. During this time, we receive a group of related events for this field and we refer to this as a flurry of events.