Engage tracks only real visitors, filtering out bot traffic. The data for bots is not stored in Umbraco Engage and is excluded from the Analytics section.

From a Search Engine Optimization (SEO) perspective, bots and crawlers always see the default content, with no personalization or participation in A/B tests.

The tracking of a visitor is done via the following steps:

• DeviceDetector.NET will assess if the visitor is a bot or a 'real' visitor` using the device ID of the browser.

• If it is a 'real' visitor the page will send a special ping request to Umbraco Engage to record the visit. If this ping is not received the requests of this visitor will not be tracked.

Umbraco Engage helps you with some additional scripts and views.

Find more information about the scripts in the Analytics section for Developers.

In the Analytics section, Umbraco Engage displays all the collected data. This data is gathered through both server-side and client-side tracking.

In this section, you will find:

• Which data is collected

• How different clients visiting your website are classified

• How you can extend the data collection with your own custom data

The Analytics section is accessible from the Engage section and as a content app on each node.

In the Campaigns tab of the Umbraco Engage, you can view all analytics data related to your campaigns. These campaigns are tracked automatically using Urchin Tracking Module (UTM) parameters, which you may already be using to monitor your marketing efforts.

You can add five different parameters to your URLs:

• utm_source: Identify the advertiser, site, publication that is sending traffic to your property. For example: google, newsletter4, billboard.

• utm_medium: The advertising or marketing medium. For example: cpc, banner, email newsletter.

• utm_campaign: The individual campaign name, slogan, promo code for a product.

• utm_term: Identify paid search keywords. If you are manually tagging paid keyword campaigns, you should also use utm_term to specify the keyword.

• utm_content: Used to differentiate similar content or links within the same ad. For example: if you have two call-to-action links within the same email message, you can use utm_content and set different values for each so you can tell which version is more effective.

Each parameter must be paired with a value that you assign. Each parameter-value pair then contains campaign-related information.

For example, if you want to link from a newsletter to the pricing page of umbraco.com, you can use the following parameters:

• utm_source: Newsletter-july-2024 to identify that this visitor came from this specific newsletter

• utm_medium: Newsletter to show that the medium was a newsletter

• utm_campaign: More_signups because that newsletter was part of a larger campaign

• utm_content: Bottom_button to identify a specific link in the newsletter

If you want to use these parameters, you will need to set up the URL like:

https://www.umbraco.com/pricing/?utm_source=newsletter-july-2024&utm_medium=newsletter&utm_campaign=more_signups&utm_content=bottom_button

Campaign Report

The report shows all campaigns set up with the utm_campaign parameter.

You can see:

• How many visitors came to the website via the campaign URL?

• How many sessions were created?

• How often was a goal triggered by visitors from this campaign?

You can also drill down to view the source and medium for each campaign.

If you install Umbraco Engage we will automatically collect a lot of data for you.

Serverside the following data is tracked:

• The URL of the visited page (/foobar/)

• The query string of the visited page (?filtering=on&parameter1=2)

• The variant of the page that we serve. This could be a personalized version of the page or one of the A/B-test variants.

• The time that the page was visited (31 august 2021, 16:04:22)

• Where the visitor came from before this visit (the so-called referrer). This could be an internal webpage (/my-contentpage/) or an external URL (www.umbraco.com/products/engage/)

• The browser being used (Firefox), the Operating System used (Windows), and the type of device being used (Desktop). These data points are based on the user-agent string that any browser is sending.

• The IP address (213.62.44.123) or anonymized IP address (213.62.44.0), depending on your configuration.

With the data collected, the Analytics reports in Umbraco Engage can be visualized. It also allows us to calculate other metrics, such as conversion rates, bounce rates, and landing & exit pages.

If you as well, you can also capture behavioural data of your visitors.

The localization information is displayed under the Location tab in the Analytics section of the Umbraco Engage dashboard:

The graph contains all sessions started within the given time, similar to the "New and returning visitors" tab. This information is not location-bound and the graph is always displayed, even if no localization information is available.

Underneath the graph, is the table containing session and pageview information based on country.

If the pageviews contain location information, the table with countries is displayed:

From the country, you can drill down to a city. This will filter the displayed data to display session and pageview information for the selected country. Even though Umbraco Engage does support the storage for county and province, currently the UI only supports displaying data by country and city.

To track Umbraco Forms submissions, you need to install with a valid license. You also need to install the Umbraco Engage .

Summary

Umbraco Engage measures interactions with Umbraco Forms on your website automatically if you include the . No additional configuration is needed. The data is visualized in the backoffice in Engage > Analytics > Forms.

The following are measured:

• The time a visitor started filling in the form.

• The time a visitor finished filling in the form (like when it was submitted).

• If the visitor has seen the form, and whether it was in their viewport.

• If the form was submitted successfully.

  • This is based on client-side validation only. If client-side validation passes it is seen as a successful submit.

• If the form raised any client-side errors, and how many were raised?

• Focus/unfocus events of each field and whether the field was empty or contained data at that time.

The Report

The Forms tab in the Analytics section holds all data gathered about your forms.

In this overview, you can see the following:

• How many times a form is shown.

• How many times a visitor started filling in the form.

• The number of times a form was submitted (filled in and hitting the "submit" button).

• How often a form was abandoned before it was submitted.

• How many errors were triggered in the form.

Select a form to drill down to this specific form and see more details for the specific form fields.

For each field you see:

• How many times did the field receive focus.

• How often was this field the last field before a visitor abandoned the form.

• How often an error was triggered on the specific field.

This data gives you insights on how to optimize your forms to create a better conversion rate.

Finally, drill down to a specific field to see which type of error was triggered, be it a validation error or a mandatory error.

Tracking a visitor Form submissions

It is possible to track a specific visitor to your website and see if they have made any form submissions. To do so, follow these steps:

1. Edit the Umbraco Form you wish to track visitors for and go to the Design view.

2. Add a new field to your form called Analytics - VisitorId.

3. Give the new form field a name such as Visitor ID.

4. Specify a URL in the settings of the field type called Template:

The URL above is a link to your website, including a visitor ID. By using a URL like this you can click directly through to view the visitor profile from Forms workflows. This includes emails, Slack messages as well as exported Excel data.

Disable Umbraco Forms tracking

By adding the umbraco-engage-no-tracking attribute you can disable Umbraco Forms tracking on the form or field level. The attribute needs to be added to either the form tag or to a field tag (like input, select, or textarea).

In the Analytics - Referrers tab, you can view all visits to your site that originated from external sources.

To see the specific path a visitor took, click on the domain, and it will display all exact referral paths.

You can see a difference in statistics (Pageviews, Visitors, etc.) between Google Analytics and Umbraco Engage.

Umbraco Engage will collect pageviews unless Google Analytics (GA)/Google Tag Manager (GTM) is blocked or GA/GTM cookies are not accepted. So approx. 10% - 25% more pageviews in Umbraco Engage compared to GA should be considered as normal depending on the audience with the current available information.

Umbraco Engage gathers video statistics for the following types of videos:

• HTML5 videos (videos provided via the <video> element)

• Embedded YouTube videos

• Embedded Vimeo videos

The Data

For the videos, the following information is gathered:

• Video URL

• Video name

  • For YouTube and Vimeo the name can be retrieved.

  • For HTML5 we record the file name.

• Total Time Watched (seconds)

• Total Percentage Watched

• In Viewport

  • True if the video was in the user's viewport.

• Watched

  • True if the video played for at least 1 second.

Apart from the metadata above we also track actions performed on the video player. These actions are:

The Report

By collecting this data, you can visualize different reports about the videos. You will find these reports in the Videos tab of the Analytics section.

Here you find all the videos that are displayed on the website. For each video you can see the following:

• How often was the video played?

• The total playtime of the video.

• The average video playtime of the video.

From here you can also drill down on a specific video to see more details about that video. You can do that by clicking on the video itself.

You see how often the video was started and paused, how often it was resumed, and how often visitors sought within the video.

The Scroll Heatmap shows you how your visitors consume your content.

The feature gives a visual representation of the average scroll depth of your visitors on a specific page. This feature is only available within the Analytics Content App on an Umbraco page.

An advantage is that you do not need to integrate any 3rd-party tools. This will prevent additional load times and possible issues with data ownership.

The heatmap only collects data if the client-side script is installed on your website.

In the Devices report within Analytics, you can view the ratio of visitors using different devices. It shows how many visitors access your website via desktop, tablet, and mobile.