Remove all ums references

Author: sofietoft

13/umbraco-engage/developers/analytics/client-side-events-and-additional-javascript-files/bridging-library-for-google-analytics.md

@@ -1,11 +1,11 @@
 ---
 icon: square-exclamation
-description: Learn how to bridge Google Analytics with the data in uMS.
+description: Learn how to bridge Google Analytics with the data in Umbraco Engage.
 ---
 
 # Bridging Library for Google Analytics
 
-We have included a bridging JavaScript file to "catch" all Google Analytics event calls and send them to Umbraco Engage. If you have a website with Google Analytics events defined you do not have to change the code to send them to uMS. The only thing you need to do is include our JavaScript bridge.
+We have included a bridging JavaScript file to "catch" all Google Analytics event calls and send them to Umbraco Engage. If you have a website with Google Analytics events defined you do not have to change the code to send them to Umbraco Engage. The only thing you need to do is include our JavaScript bridge.
 
 ## Google Analytics 4 (GA4)
 

13/umbraco-engage/developers/analytics/client-side-events-and-additional-javascript-files/bridging-library-for-google-tag-manager.md

@@ -5,7 +5,7 @@ description: Learn how to bridge data between Google Tag Manager and Umbraco Eng
 
 # Bridging Library for Google Tag Manager
 
-When using Google Tag Manager you can collect all events already in uMS. This is set up in the same way as [classic Google Analytics](../../../../../analytics/clientside-events-and-additional-javascript-files/bridging-library-for-google-analytics/).
+When using Google Tag Manager you can collect all events in Umbraco Engage. This is set up in the same way as [classic Google Analytics](../../../../../analytics/clientside-events-and-additional-javascript-files/bridging-library-for-google-analytics/).
 
 To include the file add the following code before the closing `body` tag in your HTML:
 

13/umbraco-engage/developers/introduction/the-umbraco-engage-cookie/README.md

@@ -9,7 +9,7 @@ description: >-
 
 When visiting a website with Umbraco Engage installed you will get a unique cookie. This cookie allows for relating different page visits or sessions to the same visitor. It will also continuously serve the same variant of an A/B test.
 
-By default the uMS cookie has the name `umbracoEngageAnalyticsVisitorId`. You can change the name in the [configuration file](../../settings/configuration-options-2-x/).
+By default the Umbraco Engage cookie has the name `umbracoEngageAnalyticsVisitorId`. You can change the name in the [configuration file](../../settings/configuration-options-2-x/).
 
 The Umbraco Engage cookie:
 

13/umbraco-engage/developers/personalization/implement-your-own-segment-parameters.md

@@ -125,8 +125,12 @@ For more inspiration, you can look at the built-in rule editors of Umbraco Engag
 
 We use the "**data.days**" property of our rule definition in the editor. The editor gets passed in the rule definition as well as a "**config**" object which we should update according to the user input.
 
-```
-<ums-segment-rule-editor name="$ctrl.rule.name" type="$ctrl.rule.type" save="$ctrl.save()">    <select ng-options="value as day for (value, day) in $ctrl.rule.data.days"            ng-model="$ctrl.config.dayOfWeek">        <option value="">- Select -</option>    </select></ums-segment-rule-editor>
+```html
+<ums-segment-rule-editor name="$ctrl.rule.name" type="$ctrl.rule.type" save="$ctrl.save()">
+  <select ng-options="value as day for (value, day) in $ctrl.rule.data.days" ng-model="$ctrl.config.dayOfWeek">
+    <option value="">- Select -</option>
+  </select>
+</ums-segment-rule-editor>
 ```
 
 * `segment-rule-day-of-week-editor.js`

13/umbraco-engage/developers/profiling/external-profile-data.md

@@ -25,7 +25,7 @@ To render this External Profile Tab with a custom component, you have to create
 
 {% code overflow="wrap" %}
 ```javascript
-angular.module("myCustomModule", ["Engage"]);// angular.module("umbraco").requires.push("myCustomModule");// angular.module("myCustomModule").run([ ... ]) // Create a component. We create a component named "myCustomExternalProfileDataComponent" here:angular.module("umbraco").component("myCustomExternalProfileDataComponent", {  bindings: { visitorId: "<" },  template: "<h1>My custom external profile data component! visitorId = {{$ctrl.visitorId}}</h1>",  controller: [function () {    this.$onInit = function () {      // Your logic here    }  }]});// Register your custom external profile data component.// Please note you have to use kebab-case for your component name here// just like how you would use it in an AngularJS template (i.e. myCustomComponent -> my-custom-component)angular.module("umbraco").run(["umsCustomComponents", function (customComponents) {  customComponents.profiles.externalProfileData = "my-custom-external-profile-data-component";}]);
+angular.module("myCustomModule", ["Engage"]);// angular.module("umbraco").requires.push("myCustomModule");// angular.module("myCustomModule").run([ ... ]) // Create a component. We create a component named "myCustomExternalProfileDataComponent" here:angular.module("umbraco").component("myCustomExternalProfileDataComponent", {  bindings: { visitorId: "<" },  template: "<h1>My custom external profile data component! visitorId = {{$ctrl.visitorId}}</h1>",  controller: [function () {    this.$onInit = function () {      // Your logic here    }  }]});// Register your custom external profile data component.// Please note you have to use kebab-case for your component name here// just like how you would use it in an AngularJS template (i.e. myCustomComponent -> my-custom-component)angular.module("umbraco").run(["myCustomComponents", function (customComponents) {  customComponents.profiles.externalProfileData = "my-custom-external-profile-data-component";}]);
 ```
 {% endcode %}
 

13/umbraco-engage/developers/settings/README.md

@@ -8,7 +8,7 @@ description: >-
 
 # Settings
 
-In this section, you can find information about configuring different parts of uMS.
+In this section, you can find information about configuring different parts of Umbraco Engage.
 
 ## **Goals Configuration**
 

13/umbraco-engage/getting-started/for-developers/loadbalancing-and-cm-cd-environments.md

@@ -35,7 +35,7 @@ To learn more, read the [Load Balancing article](https://docs.umbraco.com/umbrac
 
 ## Bot detection (ping)
 
-uMS will perform a ping (POST) to detect if the [visitor is a visitor or a bot](../../../../analytics/types-of-clients/). The `umbraco/engage/pagedata/ping` URL should be accessible from the content delivery and front-end servers. Make sure no firewall or other mechanism is blocking POST requests to `umbraco/engage/pagedata/ping`. If this URL is blocked, all visitors will be treated like a bot and no analytics data is collected.
+Umbraco Engage will perform a ping (POST) to detect if the [visitor is a visitor or a bot](../../../../analytics/types-of-clients/). The `umbraco/engage/pagedata/ping` URL should be accessible from the content delivery and front-end servers. Make sure no firewall or other mechanism is blocking POST requests to `umbraco/engage/pagedata/ping`. If this URL is blocked, all visitors will be treated like a bot and no analytics data is collected.
 
 ## Configuration
 

13/umbraco-engage/getting-started/for-marketers-and-editors/marketing-resources/generic-popup-template.md

@@ -63,7 +63,7 @@ const CookieService = {
 function checkCookie() {if (useCookie) {	CookieService.setCookie(`engage` + popupName + `Shown`,true,cookieExpireDays);
         }};
 
-function sendEvent(eventvalue) {ums("send", "event", "Popup", eventvalue, popupName);
+function sendEvent(eventvalue) {umbEngage("send", "event", "Popup", eventvalue, popupName);
     };
 
 function hideModel() {const message = document.querySelector('.u-alert-message');message.remove();

13/umbraco-engage/getting-started/for-marketers-and-editors/marketing-resources/generic-topbar-template.md

@@ -72,7 +72,7 @@ If you like to use your website's font, you can set the `inheritFont` option to
 
 ## CSS
 
-With the top bar set up, you can change the look to fit your website. Copy and paste this CSS into uMS and your top bar is ready.
+With the top bar set up, you can change the look to fit your website. Copy and paste this CSS into Umbraco Engage and your top bar is ready.
 
 If you would like to change the colors, you can do that in the JavaScript file.
 

13/umbraco-engage/installation/installation.md

@@ -1,23 +1,23 @@
 ---
 description: >-
-  Learn about the different ways available for installing Umbraco uMS on your
+  Learn about the different ways available for installing Umbraco Engage on your
   project.
 ---
 
 # Installation
 
-This article covers two ways to install Umbraco uMS:
+This article covers two ways to install Umbraco Engage:
 
 * [Via NuGet](installation.md#installation-via-nuget), or
 * [Via a terminal](installation.md#installing-using-the-terminal).
 
 {% hint style="info" %}
-Check [the requirements](../getting-started/for-developers/system-requirements.md) before you start installing Umbraco uMS.
+Check [the requirements](../getting-started/for-developers/system-requirements.md) before you start installing Umbraco Engage.
 {% endhint %}
 
 ## Installation via NuGet
 
-Install Umbraco uMS via Nuget in your IDE such as Visual Studio, JetBrains Rider, or VSCode (With [C# DevKit](https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.csdevkit)).
+Install Umbraco Engage via Nuget in your IDE such as Visual Studio, JetBrains Rider, or VSCode (With [C# DevKit](https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.csdevkit)).
 
 The example shown below uses the Nuget Package Manager in Visual Studio.
 
@@ -27,7 +27,7 @@ The example shown below uses the Nuget Package Manager in Visual Studio.
 ![NuGet ](../.gitbook/assets/NuGet-Package-Manager.png)
 
 3. Navigate to the **Browse** tab.
-4. Search for the **Umbraco uMS** package.
+4. Search for the **Umbraco.Engage** package.
 5. Select the package.
 6. Choose which project to install it into.
 7. Install the package.
@@ -36,24 +36,24 @@ The example shown below uses the Nuget Package Manager in Visual Studio.
 
 ## Installing using the terminal
 
-You can install Umbraco uMS using a terminal, like the Package Manager Console in Visual Studio. The steps for doing so are outlined below.
+You can install Umbraco Engage using a terminal, like the Package Manager Console in Visual Studio. The steps for doing so are outlined below.
 
 1. Open the project in Visual Studio.
 2. Find and open the Package Manager Console from the Tools menu.
 3. Type the following into the terminal:
 
 ```console
-PM> install-package Umbraco uMS
+PM> install-package Umbraco.Engage
 ```
 
-Alternatively, Umbraco uMS can be installed via the console on your operating machine.
+Alternatively, Umbraco Engage can be installed via the console on your operating machine.
 
 1. Open a terminal window on your operating system.
 2. Navigate to the folder containing your Umbraco website.
-3. Install the Umbraco uMS Nuget package with the following command:
+3. Install the Umbraco Engage Nuget package with the following command:
 
 ```console
-dotnet add package Umbraco uMS
+dotnet add package Umbraco.Engage
 ```
 
 {% hint style="info" %}
@@ -64,11 +64,11 @@ If you have any trouble, please go to [Troubleshooting installs](../../../instal
 
 ![Engage section in the Umbraco Backoffice.](<../.gitbook/assets/image (4) (1).png>)
 
-When you have installed the Umbraco uMS, build or restart your website, and the **Marketing** section will appear in the backoffice, as shown above.
+When you have installed Umbraco Engage, build or restart your website, and the **Marketing** section will appear in the backoffice, as shown above.
 
 The next step is to [configure a license](../../../installing-umarketingsuite/licensing/).
 
-It is recommended to consider the information detailed in the section below, to get the best out of Umbraco uMS.
+It is recommended to consider the information detailed in the section below, to get the best out of Umbraco Engage.
 
 ### Umbraco Forms
 
@@ -100,7 +100,7 @@ To capture events that happen on the clientside (frontend) of your website, you
 
 ### Cockpit
 
-Cockpit is a tool to help with testing segments and diagnose the data uMarkertingSuite collects. It can be viewed on the frontend of your website, only if you are logged into Umbraco as well.
+Cockpit is a tool to help with testing segments and diagnose the data Umbraco Engage collects. It can be viewed on the frontend of your website, only if you are logged into Umbraco as well.
 
 Install cockpit on your website by adding the following Razor Partial View in your templates in Umbraco before the closing `</body>` tag
 
@@ -112,23 +112,23 @@ Learn more [what Cockpit is and how you can use](../../../installing-umarketings
 
 ### Optional Extras
 
-Here are some optional extras you can do to improve your experience with uMS.
+Here are some optional extras you can do to improve your experience with Umbraco Engage.
 
-* Add a [Google Analytics bridging script](../../../analytics/clientside-events-and-additional-javascript-files/bridging-library-for-google-analytics/) that automatically sends events that you send to Google Analytics, to uMS as well.
+* Add a [Google Analytics bridging script](../../../analytics/clientside-events-and-additional-javascript-files/bridging-library-for-google-analytics/) that automatically sends events that you send to Google Analytics, to Umbraco Engage as well.
 
 ```html
 <script src="~/Assets/uMarketingSuite/Scripts/uMarketingSuite.analytics.ga4-bridge.min.js"></script>
 ```
 
-* Add the [Google Analytics blocker detection script](../../../analytics/clientside-events-and-additional-javascript-files/google-analytics-blocker-detection/). This gives you insights in which page traffic the uMS will track, and Google Analytics will not track.
+* Add the [Google Analytics blocker detection script](../../../analytics/clientside-events-and-additional-javascript-files/google-analytics-blocker-detection/). This gives you insights in which page traffic Umbraco Engage will track, and Google Analytics will not track.
 
 ```html
 <script src="/Assets/uMarketingSuite/Scripts/uMarketingSuite.analytics.blockerdetection.js"></script>
 ```
 
 ### Cookie consent
 
-If you need to influence the default [uMS cookie](../../../the-umarketingsuite-broad-overview/the-umarketingsuite-cookie/) behaviour please go [here](../../../security-privacy/gdpr/). Or go to an example [implementation using Cookiebot](../../../security-privacy/gdpr/how-to-become-gdpr-compliant-using-cookiebot/) which can be used as an example for other cookie consent providers.\\
+If you need to influence the default [The Umbraco Engage cookie](../../../the-umarketingsuite-broad-overview/the-umarketingsuite-cookie/) behaviour please go [here](../../../security-privacy/gdpr/). Or go to an example [implementation using Cookiebot](../../../security-privacy/gdpr/how-to-become-gdpr-compliant-using-cookiebot/) which can be used as an example for other cookie consent providers.\\
 
 {% hint style="warning" %}
 If you [change the default cookie behaviour](../../../the-umarketingsuite-broad-overview/the-umarketingsuite-cookie/module-permissions/) make sure to perform a **client side reload of the initial page after cookie consent**. If this is not done, visitor referrer and/or campaigns will not be tracked.