umbraco · sofietoft · Oct 2, 2024 · Oct 2, 2024 · Oct 2, 2024
diff --git a/13/umbraco-ums/developers/ab-testing/README.md b/13/umbraco-ums/developers/ab-testing/README.md
@@ -2,6 +2,7 @@
 description: >-
   uMS offers multiple ways for performaing A/B tests on your website. Learn more
   about each option and how to configure them in this section.
+icon: square-exclamation
 ---
 
 # A/B Testing

diff --git a/13/umbraco-ums/developers/ab-testing/ab-test-distribution-algorithm.md b/13/umbraco-ums/developers/ab-testing/ab-test-distribution-algorithm.md
@@ -2,6 +2,7 @@
 description: >-
   uMS distributes visitors randomly across the different variants of your A/B
   tests.
+icon: square-exclamation
 ---
 
 # A/B Test Distribution Algorithm

diff --git a/13/umbraco-ums/developers/ab-testing/finish-an-ab-test.md b/13/umbraco-ums/developers/ab-testing/finish-an-ab-test.md
@@ -2,6 +2,7 @@
 description: >-
   When the A/B test has enough data for a statistically complete picture, uMS
   will notify you. You can also end the test at any time.
+icon: square-exclamation
 ---
 
 # Finish an A/B Test

diff --git a/13/umbraco-ums/developers/ab-testing/front-end-rendering.md b/13/umbraco-ums/developers/ab-testing/front-end-rendering.md
@@ -2,6 +2,7 @@
 description: >-
   uMS takes care of applying the correct styles to the pages part of your A/B
   tests.
+icon: square-exclamation
 ---
 
 # Front end Rendering

diff --git a/13/umbraco-ums/developers/ab-testing/monitor-the-ab-test.md b/13/umbraco-ums/developers/ab-testing/monitor-the-ab-test.md
@@ -2,6 +2,7 @@
 description: >-
   uMS provides the ability to continuously monitor the A/B tests you are running
   on your website. It is recommended to disable tests that perform poorly.
+icon: square-exclamation
 ---
 
 # Monitor the A/B Test

diff --git a/13/umbraco-ums/developers/ab-testing/previewing-an-ab-test.md b/13/umbraco-ums/developers/ab-testing/previewing-an-ab-test.md
@@ -2,6 +2,7 @@
 description: >-
   When running A/B tests using uMS it recommended to preview the test before
   running it. Learn how this is done.
+icon: square-exclamation
 ---
 
 # Previewing an A/B Test

diff --git a/13/umbraco-ums/developers/ab-testing/setting-up-the-ab-test.md b/13/umbraco-ums/developers/ab-testing/setting-up-the-ab-test.md
@@ -2,6 +2,7 @@
 description: >-
   To set up an A/B test in uMS you need to go through a series of steps. Learn
   more about the required configuration is required for initating a test.
+icon: square-exclamation
 ---
 
 # Setting up the A/B Test

diff --git a/13/umbraco-ums/developers/ab-testing/types-of-ab-tests/README.md b/13/umbraco-ums/developers/ab-testing/types-of-ab-tests/README.md
@@ -1,5 +1,6 @@
 ---
 description: Get an overview of the available types of A/B tests you can run with uMS.
+icon: square-exclamation
 ---
 
 # Types of A/B Tests

diff --git a/13/umbraco-ums/developers/ab-testing/types-of-ab-tests/document-type-test.md b/13/umbraco-ums/developers/ab-testing/types-of-ab-tests/document-type-test.md
@@ -2,6 +2,7 @@
 description: >-
   uMS enables running A/B tests on pages using a specified Document Type. This
   article covers how and when to use this type of test.
+icon: square-exclamation
 ---
 
 # Document Type Test

diff --git a/13/umbraco-ums/developers/ab-testing/types-of-ab-tests/multiple-pages-test.md b/13/umbraco-ums/developers/ab-testing/types-of-ab-tests/multiple-pages-test.md
@@ -2,6 +2,7 @@
 description: >-
   uMS provides the option to run A/B tests across multiple pages. This article
   covers how and when to use this type of test.
+icon: square-exclamation
 ---
 
 # Multiple Pages Test

diff --git a/13/umbraco-ums/developers/ab-testing/types-of-ab-tests/single-page-ab-test.md b/13/umbraco-ums/developers/ab-testing/types-of-ab-tests/single-page-ab-test.md
@@ -2,6 +2,7 @@
 description: >-
   uMS provides the option to set up A/B testing on individual pages. This
   article covers how and when to use this type of test.
+icon: square-exclamation
 ---
 
 # Single-page A/B Test

diff --git a/13/umbraco-ums/developers/ab-testing/types-of-ab-tests/split-url-test.md b/13/umbraco-ums/developers/ab-testing/types-of-ab-tests/split-url-test.md
@@ -1 +1,5 @@
+---
+icon: square-exclamation
+---
+
 # Split URL test
diff --git a/...velopers/analytics/client-side-events-and-additional-javascript-files/README.md b/...velopers/analytics/client-side-events-and-additional-javascript-files/README.md
@@ -2,6 +2,7 @@
 description: >-
   Learn about what scripts can be used to connect with other data-gathering
   tools.
+icon: square-exclamation
 ---
 
 # Client-side Events

diff --git a/...events-and-additional-javascript-files/bridging-library-for-google-analytics.md b/...events-and-additional-javascript-files/bridging-library-for-google-analytics.md
@@ -1,5 +1,6 @@
 ---
 description: Learn how to bridge Google Analytics with the data in uMS.
+icon: square-exclamation
 ---
 
 # Bridging library for Google Analytics

diff --git a/...ents-and-additional-javascript-files/bridging-library-for-google-tag-manager.md b/...ents-and-additional-javascript-files/bridging-library-for-google-tag-manager.md
@@ -1,5 +1,6 @@
 ---
 description: Learn how to bridge data between Google Tag Manager and uMS.
+icon: square-exclamation
 ---
 
 # Bridging library for Google Tag Manager

diff --git a/...cs/client-side-events-and-additional-javascript-files/create-your-own-events.md b/...cs/client-side-events-and-additional-javascript-files/create-your-own-events.md
@@ -1,5 +1,6 @@
 ---
 description: Learn how to create and add custom events to uMS.
+icon: square-exclamation
 ---
 
 # Create your own events

diff --git a/...de-events-and-additional-javascript-files/google-analytics-blocker-detection.md b/...de-events-and-additional-javascript-files/google-analytics-blocker-detection.md
@@ -1,5 +1,6 @@
 ---
 description: Learn how uMS handles visitors who use blocker detection.
+icon: square-exclamation
 ---
 
 # Google Analytics blocker detection

diff --git a/13/umbraco-ums/developers/analytics/forms.md b/13/umbraco-ums/developers/analytics/forms.md
@@ -1,64 +1,71 @@
-# Forms
+---
+description: Learn how data from Umbraco Forms is tracked with uMS.
+icon: square-exclamation
+---
 
-### Installing uMarketingSuite Forms Addon
+# Forms
 
-Tracking Umbraco Forms submissions, you need to ensure you have [Umbraco Forms](https://umbraco.com/products/add-ons/forms/) installed with a valid license from Umbraco HQ along with installing the [uMarketingSuite Forms Addon package from Nuget](https://www.nuget.org/packages/uMarketingSuite.UmbracoForms).
+To track Umbraco Forms submissions, you need to install [Umbraco Forms](https://umbraco.com/products/add-ons/forms/) with a valid license from Umbraco HQ. You also need to install the [uMS Forms Addon package from Nuget](https://www.nuget.org/packages/uMarketingSuite.UmbracoForms).
 
-### Summary
+## Summary
 
-uMarketingSuite measures interactions with Umbraco Forms on your website automatically if you include the [uMarketingSuite analytics JavaScript file](/analytics/clientside-events-and-additional-javascript-files/). No additional configuration is needed. The data is visualized in the backoffice in **Marketing** &gt; **Analytics** &gt; **Forms**.
+uMS measures interactions with Umbraco Forms on your website automatically if you include the [uMarketingSuite analytics JavaScript file](../../../../analytics/clientside-events-and-additional-javascript-files/). No additional configuration is needed. The data is visualized in the backoffice in **Marketing > Analytics > Forms**.
 
-We measure the following:
+The following is measured:
 
-- The time a visitor started filling the form
-- The time a visitor finished filling the form (i.e. when it was submitted)
-- If the visitor has seen the form, i.e. whether it was in their viewport
-- If the form was submitted successfully
-    - Note 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.
-- Focus/unfocus events of each field and whether the field was empty or contained data at that time.
+* 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 was raised.
+* Focus/unfocus events of each field and whether the field was empty or contained data at that time.
 
 ## The report
 
-In you Analytics section you will see a tab "Forms" where all data about your forms is gathered.
+The "Forms" tab in the Analytics section holds all data gathered about your forms.
 
 ![]()
 
-In this overview you can see:
+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.
 
-- How many times a form has been shown
-- How many times a visitor started filling in the form
-- The number of times a form was submitted (so filled in and hitting the "submit" button)
-- How often a form was abandoned without submitting the form
-- 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.
 
-By clicking on the form you can drill down to this specific form and you see more details of the specific form fields. For each field you see:
+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
+* 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 great insights on how to optimize your forms to create a better conversion rate.
+This data gives you insights on how to optimize your forms to create a better conversion rate.
 
-Finally you can drilldown to a specific field to see which type of error was triggered; a validation error or a mandatory error.
+Finally, you can 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
 
-Using uMarketingSuite Forms addon it is possible to track a specific visitor to your website and see if they have made any form submissions. In order to do so, follow these simple steps:
+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:
 
-- Edit an Umbraco Form you wish to track visitors for and go to the design view
-- Add a new field to your form called '**Analytics - VisitorId**`
-- Give the new form field a name such as **Visitor ID**
-- In the settings of the field type called **Template** specify a URL such as this
+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**:
 
-https://**yoursite.com**/umbraco/#uMarketingSuite/profiles/profiles/insights?id=**[[visitor.id]]**
+```console
+https://**yoursite.com**/umbraco/#uMarketingSuite/profiles/profiles/insights?id=**[[visitor.id]]**`
+```
 
-By setting this value to the URL of your website to a deep link to the uMarketingSuite profiles with the visitor ID, you will be able to click through directly to view the visitor profile from Forms workflows such as emails, slack messages etc and exported excel data
+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
+## Disable Umbraco Forms tracking
 
-You can disable Umbraco Forms tracking either on form level or on field level by adding the attribute "**umarketingsuite-no-tracking**" to either the form tag or to a field tag (i.e. input / select / textarea).
+By adding the `umarketingsuite-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).
diff --git a/13/umbraco-ums/developers/analytics/location.md b/13/umbraco-ums/developers/analytics/location.md
@@ -1,17 +1,26 @@
+---
+description: Learn about what localization data is tracked and how you can view it.
+icon: square-exclamation
+---
+
 # Location
 
-The localization information is displayed under the tab Location in the Analytics section of the uMarketingSuite dashboard:
+The localization information is displayed under the Location tab in the Analytics section of the uMS dashboard:
 
 ![Location tab, located under the Analytics section]()
 
-The graph contains all sessions that were started for the given time period, similar to the tab "**New and returning visitors**". As this information is not location bound this graph is always displayed, even if no localization information is present.
-
-Underneath the graph you may find the table containing session and pageview information per country. If you have not implemented the [LocationExtractor](/analytics/extending-analytics/implement-an-ip-to-location-provider/) service, or if the pageviews for the given date range do not contain location information, the following error is displayed instead of the table:
+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.
 
-![Location table - missing data error]()
+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:
 
 ![Location table with data]()
 
-From country, you can drilldown to city. This will then filter the displayed graph and table data to only display session and pageview information for the selected country. Even though the uMarketingSuite does support the storage for county and province as well, currently the UI only supports displaying data by country and city.
+There might be cases where you will see the following error displayed in the table:
+
+![Location table - missing data error]()
+
+This will occur when the [LocationExtractor](../../../../analytics/extending-analytics/implement-an-ip-to-location-provider/) service is not implemented, or if the pageviews for the given date range do not contain location information.
+
+From the country, you can drill down to a city. This will then filter the displayed data to display session and pageview information for the selected country. Even though uMS does support the storage for county and province, currently the UI only supports displaying data by country and city.
diff --git a/13/umbraco-ums/developers/analytics/scroll-heatmap.md b/13/umbraco-ums/developers/analytics/scroll-heatmap.md
@@ -1,11 +1,18 @@
-# Scroll heatmap
+---
+description: >-
+  Learn how you can use the Scroll Heatmap in uMS to gather data on the
+  behaviour of your visitors.
+icon: square-exclamation
+---
 
-Curious how visitors consume you content?
+# Scroll Heatmap
 
-In the Heatmap feature the uMarketingSuite gives a visual representation of the average scroll depth from your visitors on a specific page. This feature is only (!) available within the Analytics Content App on a specific Umbraco page.
+The Scroll Heatmap shows you how your visitors consume your content.
 
-An advantage is that you do not need to integrate any 3rd party tools which will prevent additional load times and possible data ownership issues.
+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.
 
 ![]()
 
-Please note that the heatmap is only collecting data if you've installed [the clientside script](/analytics/clientside-events-and-additional-javascript-files/) on your website!
+The heatmap only collects data if [the client-side script](../../../../analytics/clientside-events-and-additional-javascript-files/) is installed on your website.
diff --git a/13/umbraco-ums/developers/analytics/types-of-clients.md b/13/umbraco-ums/developers/analytics/types-of-clients.md
@@ -1,23 +1,28 @@
-# Types of clients
+---
+description: Learn more about how uMS distinguishes between bots and real visitors.
+icon: square-exclamation
+---
 
-### Version 1.21 and newer
+# Types Of Clients
 
-In versions 1.21 and newer of uMarketingSuite we only track '**real**' visitors and discard any visit we determine to be from a bot. The data for bot visits is no longer stored in uMarketingSuite and thus can not be viewed in the analytics section with the bot tab for reporting.
+## Version 1.21 and newer
 
-The tracking of a visitor is done with the following steps:
+In versions 1.21 and newer of uMS, we only track '**real**' visitors and discard any visit we determine to be from a bot. The data for bots is no longer stored in uMS and cannot be viewed in the Analytics section.
 
-- DeviceDetector.NET will assess if the visitor is a bot or a 'real' visitor
-- If it's a 'real' visitor then the page will send a POST request to **umbraco/umarketingsuite/pagedata/ping** record a visit
-- If they are deemed a bot, they won't make this request
+The tracking of a visitor is done via the following steps:
 
-### Prior to version 1.21
+* DeviceDetector.NET will assess if the visitor is a bot or a 'real' visitor\`.
+* If it is a 'real' visitor the page will send a POST request to `umbraco/umarketingsuite/pagedata/ping` recording a visit.
+* The page will not add a POST request if the visitor is deemed a bot.
 
-In versions older than 1.21 The uMarketingSuite automatically classified every visitor of the websites in two groups: **Bots** and "**Real**" visitors.
+## Before version 1.21
 
-This is done by using [DeviceDetector.NET](https://github.com/totpero/DeviceDetector.NET)
+In versions older than 1.21 uMS automatically classified every visitor of the websites into two groups: **Bots** and "**Real**" visitors.
 
-With the uMarketingSuite we do **not** filter any traffic from your website. We only classify them. This classification is used in our Analytics reports. We do not show any bot-traffic within Analytics, only real visitors.
+This is done by using [DeviceDetector.NET](https://github.com/totpero/DeviceDetector.NET).
 
-The obvious exception is of course the bots-tab in Analytics 😉!
+No traffic is filtered from your website. Instead, the traffic is classified. This classification is used in the Analytics reports. No bot traffic is shown within Analytics, only real visitors.
 
-![]
+You can find bot traffic under the Bots-tab in the Analytics section.
+
+!\[]