diff --git a/13/umbraco-engage/developers/analytics/forms.md b/13/umbraco-engage/developers/analytics/forms.md index 9189828eda2..df21d27579c 100644 --- a/13/umbraco-engage/developers/analytics/forms.md +++ b/13/umbraco-engage/developers/analytics/forms.md @@ -36,7 +36,7 @@ https://**yoursite.com**/umbraco/#Engage/profiles/profiles/insights?id=**[[visit 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. -![](../../.gitbook/assets/engage-analytics-forms-visitor-id2.png) +![Visitor Form Submissions - Design view](../../.gitbook/assets/engage-analytics-forms-visitor-id2.png) ## Disable Umbraco Forms tracking diff --git a/13/umbraco-engage/developers/headless/using-the-marketing-api.md b/13/umbraco-engage/developers/headless/using-the-marketing-api.md index 029732d9d96..bb4c98d2e4a 100644 --- a/13/umbraco-engage/developers/headless/using-the-marketing-api.md +++ b/13/umbraco-engage/developers/headless/using-the-marketing-api.md @@ -93,7 +93,7 @@ Optionally, provide an External-Visitor-Id header in order to automatically upda These requests let you verify if a content page, by ID or Path, has a **JavaScript** or **CSS** variant available for page injection. -![](../../.gitbook/assets/engage-headless-segment-css.png) +![Add custom code for variant](../../.gitbook/assets/engage-headless-segment-css.png) ### Segmentation - Content diff --git a/13/umbraco-engage/developers/personalization/segment-information.md b/13/umbraco-engage/developers/personalization/segment-information.md index ef60278f07f..0da392d62c1 100644 --- a/13/umbraco-engage/developers/personalization/segment-information.md +++ b/13/umbraco-engage/developers/personalization/segment-information.md @@ -35,6 +35,7 @@ The `PageView` lies at the heart of Umbraco Engage Analytics feature and exposes Consider the following example (continued from above) where the content of content type "`Home`" was requested. We will now tell Umbraco to execute this custom code whenever the template `HomeTemplate` is requested: {% code overflow="wrap" %} + ```csharp public ActionResult HomeTemplate() { @@ -49,23 +50,26 @@ public ActionResult HomeTemplate() ... } ``` + {% endcode %} We can for example check if the current visitor falls into a segment called "**MySegment**". Keep in mind that a visitor can fall into any number of segments (zero, one, or all). A segment alone don't anything and can be regarded as purely informational, or as a "**Flag**" or "**Label**". The personalization used by the Umbraco Engage to modify the appearance of a page is called **Applied Personalization**. -A page request can have only **one** active Applied Personalization. Based on the current segments (and their sort order), Umbraco Engage picks the first applicable Applied Personalization. This could be a multi-doctype or multi-page personalization (Marketing section) or single-page personalization (content). +A page request can have only **one** active Applied Personalization. Based on the current segments (and their sort order), Umbraco Engage picks the first applicable Applied Personalization. This could be a multi-doctype or multi-page personalization (Engage section) or single-page personalization (content). To inspect the resolved Applied Personalization, we can use the property `AppliedPersonalization` on the state's **PageView**: {% code overflow="wrap" %} + ```csharp if (analyticsState.Pageview.AppliedPersonalization != null && analyticsState.Pageview.AppliedPersonalization.Name == "MyAppliedPersonalization") { ... } ``` + {% endcode %} Be aware that no personalization may have been resolved for the current request. Make sure to do a **null check** before reading the `AppliedPersonalization` property. The property `SegmentId` will tell you which active segment was responsible for triggering the Applied Personalization. diff --git a/13/umbraco-engage/developers/settings/configuration.md b/13/umbraco-engage/developers/settings/configuration.md index e1d1d0ce397..103de255a12 100644 --- a/13/umbraco-engage/developers/settings/configuration.md +++ b/13/umbraco-engage/developers/settings/configuration.md @@ -85,9 +85,9 @@ The default configuration will look like this: ``` {% endcode %} -All these settings are also visualized in Umbraco Engage. This overview can be found in the section 'Engage' -> Settings -> Configuration. +All these settings are also visualized in Umbraco Engage. This overview can be found in the section **Engage** -> **Settings** -> **Configuration**. -![](../../.gitbook/assets/engage-settings-configuration.png) +![Settings Configuration Overview](../../.gitbook/assets/engage-settings-configuration.png) {% hint style="warning" %} You cannot change any of the settings in the backoffice. To use the new settings the website must be restarted. diff --git a/13/umbraco-engage/getting-started/for-developers/cockpit.md b/13/umbraco-engage/getting-started/for-developers/cockpit.md index b88587f9842..c1dba3fdba8 100644 --- a/13/umbraco-engage/getting-started/for-developers/cockpit.md +++ b/13/umbraco-engage/getting-started/for-developers/cockpit.md @@ -14,7 +14,7 @@ To add the cockpit to your website: 1. Render the HTML partial provided by Umbraco Engage. 2. The partial view is located at `/Views/Partials/Umbraco.Engage/Cockpit.cshtml`. -3. Insert the following code before the closing `` tag: +3. Insert the following code before the closing `` tag: ```cs @Html.Partial("Umbraco.Engage/Cockpit") @@ -22,10 +22,10 @@ To add the cockpit to your website: Once the code is added, reload the page to see the Umbraco Engage Cockpit on the left or right side of the screen. The cockpit will only be rendered if the user is logged into Umbraco. -![](../../.gitbook/assets/engage-cockpit.png) +![Umbraco Engage Cockpit](../../.gitbook/assets/engage-cockpit.png) Clicking the Open button provides detailed information: -![](../../.gitbook/assets/engage-cockpit-2.png) +![Umbraco Engage Cockpit - Detailed information](../../.gitbook/assets/engage-cockpit-2.png) -If you do not see the Cockpit while the Umbraco backoffice runs on a different domain please refer to the [load balancing / CM / CD environments](loadbalancing-and-cm-cd-environments.md) section. +If the Cockpit is missing and the Umbraco backoffice runs on a different domain, see the [Load Balancing and CM/CD Environments](loadbalancing-and-cm-cd-environments.md) article. diff --git a/13/umbraco-engage/installation/troubleshooting-installs.md b/13/umbraco-engage/installation/troubleshooting-installs.md index a5680cbbfd5..3fec6a2f321 100644 --- a/13/umbraco-engage/installation/troubleshooting-installs.md +++ b/13/umbraco-engage/installation/troubleshooting-installs.md @@ -6,67 +6,67 @@ description: Use the checklist in this article to verify your Umbraco Engage ins ## The Umbraco Engage Checklist -If you have problems with Umbraco Engage setup or configuration, this checklist is for you. Verify you installed the Nuget package **Umbraco.Engage** into your Umbraco website +If you have problems with Umbraco Engage setup or configuration, this checklist is for you. Verify you installed the Nuget package **Umbraco.Engage** into your Umbraco website. -### 1. The Marketing section +### 1. The Engage section -After logging in to Umbraco you can see the Marketing section next to the other main sections in the Umbraco backoffice. +After logging in to Umbraco, you can see the Engage section next to the other main sections in the Umbraco backoffice. -If you cannot see this, please check if your Umbraco user or user group has access to the Marketing section. +If you cannot see this, please check if your Umbraco user or user group has access to the Engage section. -![](../.gitbook/assets/engage-engage-section.png) +![Engage section in the Backoffice](../.gitbook/assets/engage-engage-section.png) -### 2. Marketing Content Apps +### 2. Engage Content Apps -When editing a page within Umbraco you should be able to see the following Content App on the top right of the page: +When editing a page within Umbraco, you should be able to see the following Content App on the top right of the page: -![](../.gitbook/assets/engage-content-apps.png) +![Content Apps on content page](../.gitbook/assets/engage-content-apps.png) -If you cannot see this, please check if your Umbraco user or user group has access to the Marketing section. +If you cannot see this, please check if your Umbraco user or user group has access to the Engage section. ### 3. Cockpit Is the **Umbraco Engage Cockpit tool** visible on the front end of your site **after logging into Umbraco**? -No? Ensure you added the [Cockpit Partial view](../getting-started/for-developers/cockpit.md) in your main template. +No? Ensure you have added the [Cockpit Partial view](../getting-started/for-developers/cockpit.md) in your main template. -![](../.gitbook/assets/engage-cockpit-1.png) +![Umbraco Engage Cockpit tool](../.gitbook/assets/engage-cockpit-1.png) -### 4. Cockpit Client Side Data +### 4. Cockpit Client-Side Data Can you see client-side data such as **scroll depth** & **total time** on pages in analytics or the cockpit? No? Ensure you have [added the client-side tracking script](../developers/analytics/client-side-events-and-additional-javascript-files/additional-measurements-with-the-analytics-scripts.md) in your main template. -
+![Cockpit Client-Side Data](../.gitbook/assets/engage-cockpit-2.png) ### 5. Umbraco Forms Go to a form and add a new question. Do you see this option? -![](../.gitbook/assets/engage-analytics-form-field.png) +![Analytics Visitor ID field in Forms](../.gitbook/assets/engage-analytics-form-field.png) -Go to Marketing -> Settings -> Create a new goal. Do you see the following option called **Umbraco Forms Submission**? +Go to Engage -> Settings -> Create a new goal. Do you see the following option called **Umbraco Forms Submission**? -![](../.gitbook/assets/engage-forms-goal-type.png) +![Umbraco Forms Submission optiom in Goal dropdown](../.gitbook/assets/engage-forms-goal-type.png) If you see both options, this has been configured correctly. If not, ensure that your development team has installed the additional Umbraco Engage [UmbracoForms NuGet package](https://www.nuget.org/packages/Umbraco.Engage.Forms). ### 6. Analytics -Edit a page and go to the Content App marked **Analytics** or **Marketing** -> **Analytics** from the top navigation. +Edit a page and go to the Content App marked **Analytics** or **Engage** -> **Analytics** from the top navigation. Are you able to see analytical data? If not then you **need to wait 24 hours for today's analytics** to be collected and reported. ### 7. Locations for Analytics -Do you only see \ in the Location tab of Analytics? +Do you only see in the Location tab of Analytics? This means that additional configuration is required. Get in touch with a developer, as they need to [work to set up and track visitor locations by country and city](../developers/analytics/extending-analytics/getting-the-correct-ip-address.md). Once set up, you will see analytics for countries like this below: -![](../.gitbook/assets/engage-analytics-error-fixed.png) +![Countries Analytics Data](../.gitbook/assets/engage-analytics-error-fixed.png) ### 8. Setup IP Filters @@ -74,7 +74,7 @@ Confirm that the IP of your company/office building has been set to be excluded You can check your IP by [Googling for What is My IP](https://www.google.com/search?q=what+is+my+IP). Ensure it is in the list of IPs by navigating to **Engage** -> **Settings** -> **IP Filters**. -![](../.gitbook/assets/engage-settings-ip-filter.png) +![Setup IP Filters](../.gitbook/assets/engage-settings-ip-filter.png) ### 9. Reload after Cookie consent @@ -88,7 +88,7 @@ If you have performed all the steps and do not see Analytics data within Umbraco * Refresh the page while the developer tools are open. * Look for a POST request being made to `umbraco/engage/pagedata/ping` in the Network Tab of requests -
+![Network tab of your browser](../.gitbook/assets/engage-troubleshoot-missing-data.png) Only '**real**' visitors will be tracked and any information we determine to be from a bot is discarded. The following steps are taken to report a page view: diff --git a/13/umbraco-engage/marketers-and-editors/ab-testing/monitor-the-ab-test.md b/13/umbraco-engage/marketers-and-editors/ab-testing/monitor-the-ab-test.md index e97a9af242a..6b7d3d1051c 100644 --- a/13/umbraco-engage/marketers-and-editors/ab-testing/monitor-the-ab-test.md +++ b/13/umbraco-engage/marketers-and-editors/ab-testing/monitor-the-ab-test.md @@ -8,7 +8,7 @@ description: >- # Monitor the A/B Test -When the A/B test is running it is advised to check the progress regularly. This can be done on the specific page or via the Marketing Section. +When the A/B test is running it is advised to check the progress regularly. This can be done on the specific page or via the Engage Section. If you go to the overview you can see all running tests. The overview includes the following information: diff --git a/13/umbraco-engage/marketers-and-editors/ab-testing/setting-up-the-ab-test.md b/13/umbraco-engage/marketers-and-editors/ab-testing/setting-up-the-ab-test.md index 4639e0f08b3..87b5540155f 100644 --- a/13/umbraco-engage/marketers-and-editors/ab-testing/setting-up-the-ab-test.md +++ b/13/umbraco-engage/marketers-and-editors/ab-testing/setting-up-the-ab-test.md @@ -13,7 +13,7 @@ Setting up an A/B test in Umbraco Engage requires no code or need for any extern Starting A/B tests can be done in two ways: * Initiate a Single Page, Multiple Page, or Document Type test via the Content App on the specific page, -* Initiate Multipage and Document Type tests via the Marketing section. +* Initiate Multipage and Document Type tests via the Engage section. ## Set up the test diff --git a/13/umbraco-engage/marketers-and-editors/ab-testing/types-of-ab-tests/document-type-test.md b/13/umbraco-engage/marketers-and-editors/ab-testing/types-of-ab-tests/document-type-test.md index 729cff643b7..200f62d144c 100644 --- a/13/umbraco-engage/marketers-and-editors/ab-testing/types-of-ab-tests/document-type-test.md +++ b/13/umbraco-engage/marketers-and-editors/ab-testing/types-of-ab-tests/document-type-test.md @@ -9,15 +9,15 @@ description: >- Test all pages using a specific Document Type with this test. Select the Document Type(s) you want to test and Umbraco Engage makes sure the correct CSS and JavaScript is inserted to the correct pages. -The test type "**Document Type**" can be started in the Engage [section](../../introduction/the-umbraco-engage-section.md) and in the [Content App](../../introduction/content-apps.md). The type is selected in step 2 of the setup. +The test type **Document Type** can be started in the [Engage section](../../introduction/the-umbraco-engage-section.md) and in the [Content App](../../introduction/content-apps.md). The type is selected in step 2 of the setup. -![](../../../.gitbook/assets/engage-ab-test-document-type-test.png) +![Setup Test](../../../.gitbook/assets/engage-ab-test-document-type-test.png) The test allows you to select one or more Document Types within Umbraco. On all pages using the selected Document Type(s) the A/B Test will render the additional CSS and JavaScript you will enter. The CSS and JavaScript must not create any side effects on these pages. This is a manual task. Once you have selected the pages you want to test, you can specify one or more variants. For each variant, it is possible to click the Edit button. This will bring up a popup that allows you to write JavaScript or CSS: -![](../../../.gitbook/assets/engage-ab-test-documettype-javascript.png) +![Edit variant using CSS or JavaScript](../../../.gitbook/assets/engage-ab-test-documettype-javascript.png) In this example, some JavaScript changes the page's background color. diff --git a/13/umbraco-engage/marketers-and-editors/ab-testing/types-of-ab-tests/multiple-pages-test.md b/13/umbraco-engage/marketers-and-editors/ab-testing/types-of-ab-tests/multiple-pages-test.md index 3882aafdcfe..250ed646429 100644 --- a/13/umbraco-engage/marketers-and-editors/ab-testing/types-of-ab-tests/multiple-pages-test.md +++ b/13/umbraco-engage/marketers-and-editors/ab-testing/types-of-ab-tests/multiple-pages-test.md @@ -9,15 +9,15 @@ description: >- The Multiple Pages test allows you to across multiple pages at once. In Umbraco, you can select the pages you want to test. For all these pages you can specify which type of CSS or JavaScript will be added to the specific variant. The multiple pages test requires you to write (or copy in) some CSS and JavaScript code. -The test type **Multiple pages** can be started in the [Marketing section](../../introduction/the-umbraco-engage-section.md) and in the [Content App](../../introduction/content-apps.md). The type is selected in step 2 of the setup. +The test type **Multiple pages** can be started in the [Engage section](../../introduction/the-umbraco-engage-section.md) and in the [Content App](../../introduction/content-apps.md). The type is selected in step 2 of the setup. -![](../../../.gitbook/assets/engage-ab-test-mutliple-pages.png) +![Setup Test](../../../.gitbook/assets/engage-ab-test-mutliple-pages.png) The test allows you to select one or more pages within Umbraco. On all these pages the A/B Test will render the additional CSS and JavaScript you enter. The CSS and JavaScript must not create any side effects on these pages. This is a manual job that cannot be automated with Umbraco Engage. Once you have selected the pages you want to test, you can specify one or more variants. For each variant, it is possible to click the Edit button. This will bring up a popup that allows you to write JavaScript or CSS: -![](../../../.gitbook/assets/engage-ab-test-documettype-javascript.png) +![Edit variant using CSS or JavaScript](../../../.gitbook/assets/engage-ab-test-documettype-javascript.png) In this example, some JavaScript is added to change the page's background color. diff --git a/13/umbraco-engage/marketers-and-editors/analytics/device-type.md b/13/umbraco-engage/marketers-and-editors/analytics/device-type.md index 0d6a386b1a5..7486bc1e893 100644 --- a/13/umbraco-engage/marketers-and-editors/analytics/device-type.md +++ b/13/umbraco-engage/marketers-and-editors/analytics/device-type.md @@ -8,4 +8,4 @@ description: >- 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. -![](../../.gitbook/assets/engage-analytics-device-type.png) +![Device Type report in Analytics](../../.gitbook/assets/engage-analytics-device-type.png) diff --git a/13/umbraco-engage/marketers-and-editors/analytics/forms.md b/13/umbraco-engage/marketers-and-editors/analytics/forms.md index c08a75328ee..88480af3cd3 100644 --- a/13/umbraco-engage/marketers-and-editors/analytics/forms.md +++ b/13/umbraco-engage/marketers-and-editors/analytics/forms.md @@ -5,8 +5,7 @@ description: Learn how data from Umbraco Forms is tracked with Umbraco Engage. # Forms -To track Umbraco Forms submissions, you need to install [Umbraco Forms](https://umbraco.com/products/add-ons/forms/) with a valid license.\ -You also need to install the Umbraco Engage[ Forms Addon package from Nuget](https://www.nuget.org/packages/Umbraco.Engage.Forms). +To track Umbraco Forms submissions, you need to install [Umbraco Forms](https://umbraco.com/products/add-ons/forms/) with a valid license. You also need to install the Umbraco Engage [Forms Add-on package from Nuget](https://www.nuget.org/packages/Umbraco.Engage.Forms). ## Summary @@ -22,13 +21,13 @@ The following are measured: * 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 Report -The "Forms" tab in the Analytics section holds all data gathered about your forms. +The **Forms** tab in the **Analytics** section holds all data gathered about your forms. -![](../../.gitbook/assets/engage-analytics-forms.png) +![Forms tab in the Analytics section](../../.gitbook/assets/engage-analytics-forms.png) -In this overview you can see the following: +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. @@ -44,18 +43,18 @@ For each field you see: * How often was this field the last field before a visitor abandoned the form. * How often an error was triggered on the specific field. -![](../../.gitbook/assets/engage-analytics-form-details.png) +![Form Details](../../.gitbook/assets/engage-analytics-form-details.png) This data gives you insights on how to optimize your forms to create a better conversion rate. -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. +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**\`. +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**: @@ -65,7 +64,7 @@ https://**yoursite.com**/umbraco/#Engage/profiles/profiles/insights?id=**[[visit 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. -![](../../.gitbook/assets/engage-analytics-forms-visitor-id2.png) +![Adding Analytics - VisitorId field to Form](../../.gitbook/assets/engage-analytics-forms-visitor-id2.png) ## Disable Umbraco Forms tracking diff --git a/13/umbraco-engage/marketers-and-editors/analytics/referral-traffic.md b/13/umbraco-engage/marketers-and-editors/analytics/referral-traffic.md index fcf018c42e5..573c7ea4b3b 100644 --- a/13/umbraco-engage/marketers-and-editors/analytics/referral-traffic.md +++ b/13/umbraco-engage/marketers-and-editors/analytics/referral-traffic.md @@ -8,8 +8,8 @@ description: >- In the **Analytics - Referrers** tab, you can view all visits to your site that originated from external sources. -![Referral Traffic](../../.gitbook/assets/Referral-traffic.png) +![Referral Traffic tab in Analytics section](../../.gitbook/assets/Referral-traffic.png) To see the specific path a visitor took, click on the domain, and it will display all exact referral paths. -![](../../.gitbook/assets/Referral-Traffic-Path.png) +![Domain view displaying visitor referral paths](../../.gitbook/assets/Referral-Traffic-Path.png) diff --git a/13/umbraco-engage/marketers-and-editors/analytics/videos.md b/13/umbraco-engage/marketers-and-editors/analytics/videos.md index d8ea7afab5d..c99f89d5f90 100644 --- a/13/umbraco-engage/marketers-and-editors/analytics/videos.md +++ b/13/umbraco-engage/marketers-and-editors/analytics/videos.md @@ -13,7 +13,7 @@ Umbraco Engage gathers video statistics for the following types of videos: {% hint style="info" %} Make sure the embed URL contains `?enablejsapi=1` as part of the full URL to enable tracking. The `src` property of the iframe should be something like: `https://www.youtube.com/embed/<CODE>?enablejsapi=1`. -The [https://www.youtube.com/iframe\_api](https://www.youtube.com/iframe\_api) is loaded for this purpose. +The [https://www.youtube.com/iframe_api](https://www.youtube.com/iframe_api) is loaded for this purpose. {% endhint %} * Embedded Vimeo videos @@ -22,7 +22,7 @@ The [https://www.youtube.com/iframe\_api](https://www.youtube.com/iframe\_api) i The [https://player.vimeo.com/api/player.js](https://player.vimeo.com/api/player.js) is loaded for this purpose. {% endhint %} -## The data +## The Data For the videos, the following information is gathered: @@ -39,13 +39,20 @@ For the videos, the following information is gathered: Apart from the metadata above we also track actions performed on the video player. These actions are: -
ActionDescription
AutoplayIf the video was started automatically.
PlayWhen the video starts playing.
PauseWhen the video is paused.
ResumeWhen the video is resumed from a Paused state.
EndedWhen the video is ended.
SeekWhen a seek operation is performed.
+| Action | Description | +|----------|------------------------------------------------| +| Autoplay | If the video was started automatically. | +| Play | When the video starts playing. | +| Pause | When the video is paused. | +| Resume | When the video is resumed from a Paused state. | +| Ended | When the video is ended. | +| Seek | When a seek operation is performed. | -## The report +## The Report -By collecting this data you can visualize different reports about the videos. You will find these reports in the Analytics subsection and the tab Videos. +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. -![](../../.gitbook/assets/engage-analytics-videos.png) +![Reports in the Videos tab of the Analytics section](../../.gitbook/assets/engage-analytics-videos.png) Here you find all the videos that are displayed on the website. For each video you can see the following: @@ -55,6 +62,6 @@ Here you find all the videos that are displayed on the website. For each video y 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. -![](../../.gitbook/assets/enage-analytics-video-details.png) +![View detailed analytics for a specific video](../../.gitbook/assets/enage-analytics-video-details.png) You see how often the video was started and paused, how often it was resumed, and how often visitors sought within the video. diff --git a/13/umbraco-engage/marketers-and-editors/introduction/content-apps.md b/13/umbraco-engage/marketers-and-editors/introduction/content-apps.md index dfef6c4afb1..adb0130cc6b 100644 --- a/13/umbraco-engage/marketers-and-editors/introduction/content-apps.md +++ b/13/umbraco-engage/marketers-and-editors/introduction/content-apps.md @@ -6,34 +6,36 @@ description: >- # Content Apps -In the content section of Umbraco you'll see all Umbraco nodes and most of them will relate to a specific page in your website. If you have installed the Umbraco Engage each Umbraco node will have three extra Content Apps. +In the Content section of Umbraco, you will see all Umbraco nodes and most of them will relate to a specific page in your website. If you have installed the Umbraco Engage each Umbraco node will have three extra Content Apps. -![](../../.gitbook/assets/engage-content-apps-2.png) +![Umbraco nodes with additional content apps from Umbraco Engage](../../.gitbook/assets/engage-content-apps-2.png) ## Analytics If you navigate to a node you will see the Analytics content app. If you open the Content App the Analytics data of this specific node is loaded. -![](../../.gitbook/assets/engage-content-apps-analytics.png) +![Viewing the Analytics content app for a specific node](../../.gitbook/assets/engage-content-apps-analytics.png) ## A/B Testing -The A/B testing content app will allow you to test your Umbraco node within the splitview functionality. Every document type can be A/B tested: +The A/B testing content app will allow you to test your Umbraco node within the splitview functionality. Every Document Type can be A/B tested: -![](../../.gitbook/assets/engage-content-apps-ab-tests.png) +![Using the A/B testing content app to test splitview functionality](../../.gitbook/assets/engage-content-apps-ab-tests.png) ## Personalization -The personalization content app allows you to score this specific page on the customer journey & persona (if you want to implicit score your content). It also allows you to setup personalized variants of each node. +The Personalization content app allows you to score a specific page based on the customer journey and persona (for implicit content scoring). -![](../../.gitbook/assets/engage-content-apps-personalization-1.png) +![Personalization content app for scoring a page](../../.gitbook/assets/engage-content-apps-personalization-2.png) -![](../../.gitbook/assets/engage-content-apps-personalization-2.png) +It also allows you to setup personalized variants of each node. + +![Setting up personalized variants for each Umbraco node](../../.gitbook/assets/engage-content-apps-personalization-1.png) ## Managing the access to content apps -In the settings of the Engage-section you can manage on which document types these content apps are displayed, and which Umbraco user groups have access to these content apps. They can be easily managed per document type and per user group +In the **Engage** -> **Settings** section, you can manage which Document Types the content apps are displayed, and which Umbraco user groups can access them. They can be managed per Document Type and per user group -![](../../.gitbook/assets/engage-content-apps-permissions1.png) +![Document Type Permissions in the Settings section](../../.gitbook/assets/engage-content-apps-permissions1.png) -![](../../.gitbook/assets/engage-content-apps-permissions2.png) +![User group Permissions in the Settings section](../../.gitbook/assets/engage-content-apps-permissions2.png) diff --git a/13/umbraco-engage/marketers-and-editors/introduction/the-umbraco-engage-section.md b/13/umbraco-engage/marketers-and-editors/introduction/the-umbraco-engage-section.md index 4a122712da4..9677b06fb6c 100644 --- a/13/umbraco-engage/marketers-and-editors/introduction/the-umbraco-engage-section.md +++ b/13/umbraco-engage/marketers-and-editors/introduction/the-umbraco-engage-section.md @@ -8,22 +8,22 @@ description: >- When you install Umbraco Engage, a new section called **Engage** is automatically enabled in the Umbraco backoffice. -![](../../.gitbook/assets/engage-engage-section-2.png) +![Engage section in Umbraco backoffice](../../.gitbook/assets/engage-engage-section-2.png) If you do not see the Engage section, it is likely that you have not been granted access to it. You can set up access in the **Users** section of Umbraco. If the Engage or Users section is not visible, ask your administrator for assistance. ## The Engage Section -In the Engage section, you will find several subsections, each providing insights into a specific feature of Umbraco Engage. +In the Engage section, you will find subsections, each providing insights into a specific feature of Umbraco Engage. Currently, the available sections are: -* [Analytics](../analytics/): The most important feature of Umbraco Engage is where all data is collected. +* [Analytics](../analytics/): The most important feature of Umbraco Engage where all data is collected. * [A/B Testing](../ab-testing/): Set up new projects and start A/B testing directly. * [Personalization](../personalization/): Implement your marketing strategy and set up your personalizations. * [Profiling](../profiling/): See how visitors engage with your site. * [Reporting](../reporting.md): See how your optimizations contribute to your goals. -* [Settings](../settings/): View and configure various global settings used throughout Umbraco Engage. +* [Settings](../settings/): View and configure global settings used throughout Umbraco Engage. ## The Dashboard diff --git a/13/umbraco-engage/marketers-and-editors/personalization/cockpit-insights.md b/13/umbraco-engage/marketers-and-editors/personalization/cockpit-insights.md index f54a553de9a..ed6b1ccc574 100644 --- a/13/umbraco-engage/marketers-and-editors/personalization/cockpit-insights.md +++ b/13/umbraco-engage/marketers-and-editors/personalization/cockpit-insights.md @@ -8,11 +8,11 @@ description: >- Umbraco Engage includes a cockpit feature to help verify the tracking of analytics and understand personalization behavior. The cockpit adds a button to the front end, giving real-time insights: -![](../../.gitbook/assets/engage-cockpit.png) +![Umbraco Engage cockpit feature](../../.gitbook/assets/engage-cockpit.png) -Clicking the button provides detailed information: +Clicking the Open button provides detailed information: -![](../../.gitbook/assets/engage-cockpit-2.png) +![Detailed information displayed after clicking the Open button](../../.gitbook/assets/engage-cockpit-2.png) ## Adding the Cockpit to Your Website @@ -20,7 +20,7 @@ To add the cockpit to your website: 1. Render the HTML partial provided by Umbraco Engage. 2. The partial view is located at `/Views/Partials/uMarketings/Cockpit.cshtml`. -3. Insert the following code before the closing `` tag: +3. Insert the following code before the closing `` tag: ```cs @Html.Partial("uMarketingSuite/Cockpit") diff --git a/13/umbraco-engage/marketers-and-editors/personalization/implicit-and-explicit-personalization/README.md b/13/umbraco-engage/marketers-and-editors/personalization/implicit-and-explicit-personalization/README.md index d8492aefcc6..976f5067c9d 100644 --- a/13/umbraco-engage/marketers-and-editors/personalization/implicit-and-explicit-personalization/README.md +++ b/13/umbraco-engage/marketers-and-editors/personalization/implicit-and-explicit-personalization/README.md @@ -4,13 +4,13 @@ description: Umbraco Engage uses both the concept of implicit and explicit perso # Implicit and Explicit Personalization -## Explicit personalization +## Explicit Personalization This is the "**easiest**" concept to grasp. For every explicit parameter Umbraco Engage is true or false. For example, the browser parameter is an example of an explicit parameter. Suppose the visitor is using a Chrome browser, or not. There cannot be much debate about this and the parameter returns "`true`" or "`false`". Most parameters within Umbraco Engage are explicit and true or false. -## Implicit personalization +## Implicit Personalization The unique part of Umbraco Engage is that it also uses implicit personalization. Based on the behavior of a specific visitor Umbraco Engage can assume that a visitor is a specific persona or customer journey phase. @@ -18,13 +18,13 @@ This article teaches you how to set up[ the customer journey](setting-up-the-cus In the [segment builder](../creating-a-segment.md), you can use these implicit parameters the same way you would apply any other segment parameter. -![](../../../.gitbook/assets/engage-personalization-implicit.png) +![Using implicit parameters in the segment builder](../../../.gitbook/assets/engage-personalization-implicit.png) By clicking personas you will see an overview of all the personas that you have set up within your installation. -In our case we see the persona groups "**Profiles**" and "**Companies**" and the personas "**Data & Privacy Officer**", "**Developer**", "**Marketer**", "**Agency**", "**Company**" and "**Umbraco HQ**". If we want to create a segment for all personas that are "**Data & Privacy officer**" add that persona as a parameter to the segment. +In our case, we see the persona groups **Profiles** and **Companies** and the personas **Data & Privacy Officer**, **Developer**, **Marketer**, **Agency**, **Company** and **Umbraco HQ**. If we want to create a segment for all personas that are **Data & Privacy officer** add that persona as a parameter to the segment. -![](../../../.gitbook/assets/engage-personalization-persona-segment.png) +![Creating a segment for the 'Data & Privacy Officer' persona in Umbraco Engage.](../../../.gitbook/assets/engage-personalization-persona-segment.png) From now on you can use this segment to personalize the experience of your visitors. diff --git a/13/umbraco-engage/marketers-and-editors/personalization/implicit-and-explicit-personalization/implicit-personalization-scoring-explained.md b/13/umbraco-engage/marketers-and-editors/personalization/implicit-and-explicit-personalization/implicit-personalization-scoring-explained.md index 376f1f4c1c7..997ed995263 100644 --- a/13/umbraco-engage/marketers-and-editors/personalization/implicit-and-explicit-personalization/implicit-personalization-scoring-explained.md +++ b/13/umbraco-engage/marketers-and-editors/personalization/implicit-and-explicit-personalization/implicit-personalization-scoring-explained.md @@ -15,31 +15,30 @@ Implicit personalization is based on gaining confidence that a visitor shows beh There are four ways to score the behavior of your visitors: 1. [Score the content that a visitor is viewing](content-scoring.md). This can be done per node. -2. [Score from which (external) website or (external) webpage a visitor was\ - coming](referral-scoring.md) +2. [Score from which (external) website or (external) webpage a visitor was coming](referral-scoring.md). 3. [Score the campaigns](campaign-scoring.md) that a visitor is part of. 4. [Implement your own scoring](../../../developers/personalization/custom-scoring.md). In this way, the sky is the limit, because you can hook into any external data source you have or behavior that you want to score. -## Collecting points +## Collecting Points -The points of all these different sources are added and this reaches a certain amount of points per persona. As soon as one of the personas or customer journey steps reaches the threshold that is set up, the algorithm assumes that you are this persona or in that specific journey step. +The points of all these different sources are added and this reaches a certain amount of points per persona. Once a persona or journey step reaches the set threshold, the algorithm assigns you to that persona or step. -In the example, the visitor collected 40 points for the "**Data & Privacy officer**", 30 points for the "**Marketer**", and 0 points for the developer persona: +In the example, the visitor collected 40 points for the **Data & Privacy officer**, 30 points for the **Marketer**, and 0 points for the developer persona: -![](../../../.gitbook/assets/engage-persona-scoring.png) +![Persona scoring example showing points for Data & Privacy Officer](../../../.gitbook/assets/engage-persona-scoring.png) -The threshold in this specific case was set to 25 points. As soon as the "**Data & Privacy officer**" reached 25 points Umbraco Engage assumed that this visitor was a "**Data & Privacy officer**". +The threshold in this specific case was set to 25 points. As soon as the **Data & Privacy officer** reached 25 points Umbraco Engage assumed that this visitor was a **Data & Privacy officer**. -In this example the "**Think**" customer journey step is assumed based on the collected amount of points: +In this example the **Think** customer journey step is assumed based on the collected amount of points: -![](../../../.gitbook/assets/engage-journey-scoring.png) +![Customer journey step 'Think' assumed based on the collected points.](../../../.gitbook/assets/engage-journey-scoring.png) -## Tweaking the scoring +## Tweaking the Scoring The threshold value and the expected difference between two personas or journey steps can be set in the [customer journey group](setting-up-the-customer-journey.md) and [persona group](setting-up-personas.md). Setting up a deviation of at least 35 points between two personas the cockpit will show a different visualization in the previous example: -![](../../../.gitbook/assets/engage-persona-scoring-with-minimal-deviation.png) +![Persona scoring showing minimal deviation and the algorithm waiting for the threshold to be reached](../../../.gitbook/assets/engage-persona-scoring-with-minimal-deviation.png) -You can see that the "**Data and privacy officer**" still has 40 points and the marketer 30 points. Both have also reached the threshold of 25 points, but there is not a minimal deviation of 35 points. Umbraco Engage algorithm now does not assume a persona yet, but will wait until the deviation is big enough (according to the settings) and the "**Data & privacy officer**" reaches 65 points **(30 points of the marketer + a minimal deviation of 35 points)**. +You can see that the "**Data and privacy officer**" still has 40 points and the marketer 30 points. Both have also reached the threshold of 25 points, but there is not a minimal deviation of 35 points. The Umbraco Engage algorithm waits for the deviation to reach the set threshold before assuming a persona. For example: the **Data & privacy officer** reaches 65 points (30 points of the marketer + a minimal deviation of 35 points). diff --git a/13/umbraco-engage/marketers-and-editors/personalization/setting-up-personalization.md b/13/umbraco-engage/marketers-and-editors/personalization/setting-up-personalization.md index c2560871719..3384a644822 100644 --- a/13/umbraco-engage/marketers-and-editors/personalization/setting-up-personalization.md +++ b/13/umbraco-engage/marketers-and-editors/personalization/setting-up-personalization.md @@ -5,9 +5,9 @@ description: In this article we are going to set up some personalization for our # Setting up Personalization {% hint style="info" %} -Please make sure you have set up[ your first segment](creating-a-segment.md). A segment is a group of visitors for which you want to personalize the website experience. +Ensure you have set up [your first segment](creating-a-segment.md), which is a group of visitors you want to target for personalized website experiences. -Once that is done we can go to the next step and personalize the experience. +Once that is done, you can move on to the next step and personalize the experience. {% endhint %} ## Applying personalization @@ -19,47 +19,53 @@ You can apply personalization in two ways: ### Personalizing a specific page -To personalize a specific page you can go the any node within Umbraco. When you open the node you'll find all Umbraco Engage content apps on that specific node. To personalize the page you can go to the "**Personalization**" content app: +To personalize a specific page: -![](../../.gitbook/assets/engage-personalization-content-app.png) +1. Go to any content node within Umbraco. +2. Open the node. You will find all Umbraco Engage content apps on that specific node. +3. Go to the "**Personalization**" content app: -By clicking on the content app you go to an overview of all applied personalizations for this specific page. You can create your first personalization by clicking "**Add personalized variant**": +![Accessing the 'Personalization' content app for a specific node in Umbraco](../../.gitbook/assets/engage-personalization-content-app.png) -![](../../.gitbook/assets/engage-personalization-add-personalized-variant.png) +4. Clicking the content app takes you to an overview of all applied personalizations for the page. +5. Click **Add personalized variant**: -In the popup you can specify the segment for which you want to personalize the experience. It also advised to create a descriptive name for the personalization and a short description: +![Overview of applied personalizations with the option to add a personalized variant](../../.gitbook/assets/engage-personalization-add-personalized-variant.png) -![](../../.gitbook/assets/engage-personalization-add-new-variant.png) +6. Select the segment from the dropdown for which you want to personalize the experience in the popup. +7. Provide a descriptive name for the personalization and a short description: -When you've selected the correct segment you can click on "**Add variant**". This opens up the split-view editor on the left side of the original page. On the right side, there is the option to create a personalized variant. +![Popup for defining the segment](../../.gitbook/assets/engage-personalization-add-new-variant.png) -![](../../.gitbook/assets/engage-personalization-splitview-text.png) +8. Click **Add variant**. +9. A split-view editor opens up, where you can create a personalized variant on the right side of the original page. -Depending on your segmentation setup of the document types you can edit the specific properties of your Document Type. Please read the section "[Setting up the Document Type for splitview editing](../ab-testing/types-of-ab-tests/single-page-ab-test.md)" to set this up correctly. +![Split-view editor with options to create a personalized variant for the selected segment](../../.gitbook/assets/engage-personalization-splitview-text.png) -You can for example specify a different title for this variant: +10. Edit specific properties of your Document Type depending on your segmentation setup. To set this up correctly, see the [Setting up the Document Type for splitview editing](../ab-testing/types-of-ab-tests/single-page-ab-test.md) article. -![](../../.gitbook/assets/engage-my-first-personalization.png) +For example, you can specify a different title for this variant: -You can save and preview your applied personalization by clicking "**Save & Preview**". +![Editing a personalized variant with a different title in the splitview editor](../../.gitbook/assets/engage-my-first-personalization.png) -You will see an extra querystring parameter in the URL when previewing the personalization:\ -`https:///?engagePreviewAppliedPersonalization=` +11. Click **Save & Preview** to save and preview your applied personalization. -This is only the case when previewing your personalization. As soon as you publish the page regular visitors will only see one URL an depending on the segment they will see different content. +While previewing the personalization, you will see an extra querystring in the URL: `https:///?engagePreviewAppliedPersonalization=` -If we now publish the website and go to the URL we will see different pages. The visitors who are part of the segment will see the personalized variant. All other visitors will see the default content. +This is only visiblee when previewing your personalization. Once published, visitors will see a single URL, and depending on their segment, they will view different content. -we have now set up our first personalization. +After publishing the website, visitors in the segment will see the personalized variant, while others will see the default content. + +Congratulations, you've successfully set up your first personalization. ## Applying personalization to multiple pages or per Document Type -You can also apply personalization to multiple pages at once. This can only be setup via the Marketing section in Umbraco. Within that section you can go to the subsection "**Personalization**" and click on "**Apply new personalization**": +You can also apply personalization to multiple pages at once. This can only be setup via the Engage section in Umbraco. Within that section you can go to the subsection **Personalization** and click on **Apply new personalization**: -![](../../.gitbook/assets/engage-personalization-new-personalization.png) +![Accessing the Personalization section in Engage](../../.gitbook/assets/engage-personalization-new-personalization.png) -Here you can specify to which pages or document types you want to apply the personalization. Also you need to specify for which segment this is triggered. +Here, you can specify to which pages or Document Types you want to apply the personalization. Also you need to specify for which segment this is triggered. -![](../../.gitbook/assets/engage-apply-personalization-to-multiple-pages.png) +![Setting up Personalization](../../.gitbook/assets/engage-apply-personalization-to-multiple-pages.png) With multiple pages and Document Types you can either add in some additional `CSS` or `JavaScript` code or personalize the experience via code. You can add CSS `JavaScript` via the button "**Include CSS/JavaScript**". The `CSS` and `JavaScript` will automatically be added to the pages where the segment applies. diff --git a/13/umbraco-engage/marketers-and-editors/profiling/README.md b/13/umbraco-engage/marketers-and-editors/profiling/README.md index 108f80274f2..9871803d4d1 100644 --- a/13/umbraco-engage/marketers-and-editors/profiling/README.md +++ b/13/umbraco-engage/marketers-and-editors/profiling/README.md @@ -45,9 +45,9 @@ Finally, you can see a blue or a grey icon at the beginning of the row. A grey i ### Filtering the Results -It is possible to filter the overview of profiles by clicking the filter button at the top of the profiles overview. +It is possible to filter the overview of profiles by clicking the **Filter** button at the top of the profiles overview. -![](../../.gitbook/assets/filtering-results.png) +![Filtering the profiles overview using the filter button](../../.gitbook/assets/filtering-results.png) You can filter by: diff --git a/13/umbraco-engage/marketers-and-editors/settings/README.md b/13/umbraco-engage/marketers-and-editors/settings/README.md index 75d464ae8d4..d21fe0b74a4 100644 --- a/13/umbraco-engage/marketers-and-editors/settings/README.md +++ b/13/umbraco-engage/marketers-and-editors/settings/README.md @@ -23,4 +23,4 @@ Get an overview of all configured settings of Umbraco Engage. ## [Permissions](permissions.md) -Explore how to control which Umbraco user groups have access to the Marketing section settings and manage where content apps are displayed. +Explore how to control which Umbraco user groups have access to the Engage section settings and manage where content apps are displayed. diff --git a/13/umbraco-engage/marketers-and-editors/settings/permissions.md b/13/umbraco-engage/marketers-and-editors/settings/permissions.md index bf841d47734..eb5e1486fe2 100644 --- a/13/umbraco-engage/marketers-and-editors/settings/permissions.md +++ b/13/umbraco-engage/marketers-and-editors/settings/permissions.md @@ -5,8 +5,8 @@ description: Manage content apps and access on Document Types. # Permissions -You can manage which document types the content apps are shown, and which Umbraco user groups have access to in the Marketing section settings. They can be managed per Document Type and user group +In the **Engage** -> **Settings** section, you can manage which Document Types the content apps are shown and which Umbraco user groups have access to them. This can be configured per Document Type and user group. -![](../../.gitbook/assets/engage-content-apps-permissions1.png) +![Document Type Permissions in Settings section](../../.gitbook/assets/engage-content-apps-permissions1.png) -![](../../.gitbook/assets/engage-content-apps-permissions2.png) +![User group Permissions in Settings section](../../.gitbook/assets/engage-content-apps-permissions2.png)