Site visits

Understanding visitor engagement with your site's links

Ashmita Taneja avatar
Written by Ashmita Taneja
Updated over a week ago

Zoomforth provides you with a detailed view into how individual visitors are engaging with your site—what they're clicking on and how much time they're spending on specific parts of the site.

Site visits are found in the Analytics tabs found from the Link Details or Site Details menus. The latter presents an aggregate of all the analytics found from the different links or URLs created for the same site. A site can be given more than one address.

To understand how Zoomforth tracks visitor engagement with your sites, watch this video or continue reading the article below:

To get an insight about how a visitor consumed the site, click an entry in the Visits section, or click View Details, hover over a visit or visitor entry in the Visitor table, and click Details.

Depending on the site settings, some information during a visit session may be provided by the visitor, such as name and email, without server verification. Some may be masked, hidden, or changed, such as when a visitor uses VPN so the location captured in the analytics may not be true or accurate.

In the screen capture above, a visitor or visit is named as Duke, associated with an email in Budapest, Hungary.

The left table shows more statistics about the visit including the date and time, duration, device used, etc. The right table shows the list of interactions and content used.

How to use this information

Using the activity feed, you can understand how visitors are using your sites—where they're scrolling to, where they're dropping off, and what they appear to be most interested in.

You might use this information to make business decisions—e.g., contact this individual again; send them sales content focusing on feature X rather than feature Y.

You might use this information to improve your content—e.g., improve the flow of your site, or better direct visitors to important information they might be missing.

Did this answer your question?