Skip to content

Commit 712a18e

Browse files
authored
Merge pull request #6651 from umbraco/image-description
Added missing image alt text...
2 parents a05fca0 + 4685e01 commit 712a18e

File tree

23 files changed

+140
-123
lines changed

23 files changed

+140
-123
lines changed

13/umbraco-engage/developers/analytics/forms.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ https://**yoursite.com**/umbraco/#Engage/profiles/profiles/insights?id=**[[visit
3636

3737
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.
3838

39-
![](../../.gitbook/assets/engage-analytics-forms-visitor-id2.png)
39+
![Visitor Form Submissions - Design view](../../.gitbook/assets/engage-analytics-forms-visitor-id2.png)
4040

4141
## Disable Umbraco Forms tracking
4242

13/umbraco-engage/developers/headless/using-the-marketing-api.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -93,7 +93,7 @@ Optionally, provide an External-Visitor-Id header in order to automatically upda
9393

9494
These requests let you verify if a content page, by ID or Path, has a **JavaScript** or **CSS** variant available for page injection.
9595

96-
![](../../.gitbook/assets/engage-headless-segment-css.png)
96+
![Add custom code for variant](../../.gitbook/assets/engage-headless-segment-css.png)
9797

9898
### Segmentation - Content
9999

13/umbraco-engage/developers/personalization/segment-information.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,6 +35,7 @@ The `PageView` lies at the heart of Umbraco Engage Analytics feature and exposes
3535
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:
3636

3737
{% code overflow="wrap" %}
38+
3839
```csharp
3940
public ActionResult HomeTemplate()
4041
{
@@ -49,23 +50,26 @@ public ActionResult HomeTemplate()
4950
...
5051
}
5152
```
53+
5254
{% endcode %}
5355

5456
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**".
5557

5658
The personalization used by the Umbraco Engage to modify the appearance of a page is called **Applied Personalization**.
5759

58-
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).
60+
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).
5961

6062
To inspect the resolved Applied Personalization, we can use the property `AppliedPersonalization` on the state's **PageView**:
6163

6264
{% code overflow="wrap" %}
65+
6366
```csharp
6467
if (analyticsState.Pageview.AppliedPersonalization != null && analyticsState.Pageview.AppliedPersonalization.Name == "MyAppliedPersonalization")
6568
{
6669
...
6770
}
6871
```
72+
6973
{% endcode %}
7074

7175
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.

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -85,9 +85,9 @@ The default configuration will look like this:
8585
```
8686
{% endcode %}
8787

88-
All these settings are also visualized in Umbraco Engage. This overview can be found in the section 'Engage' -> Settings -> Configuration.
88+
All these settings are also visualized in Umbraco Engage. This overview can be found in the section **Engage** -> **Settings** -> **Configuration**.
8989

90-
![](../../.gitbook/assets/engage-settings-configuration.png)
90+
![Settings Configuration Overview](../../.gitbook/assets/engage-settings-configuration.png)
9191

9292
{% hint style="warning" %}
9393
You cannot change any of the settings in the backoffice. To use the new settings the website must be restarted.

13/umbraco-engage/getting-started/for-developers/cockpit.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -14,18 +14,18 @@ To add the cockpit to your website:
1414

1515
1. Render the HTML partial provided by Umbraco Engage.
1616
2. The partial view is located at `/Views/Partials/Umbraco.Engage/Cockpit.cshtml`.
17-
3. Insert the following code before the closing `</body>` tag:
17+
3. Insert the following code before the closing `</body>` tag:
1818

1919
```cs
2020
@Html.Partial("Umbraco.Engage/Cockpit")
2121
```
2222

2323
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.
2424

25-
![](../../.gitbook/assets/engage-cockpit.png)
25+
![Umbraco Engage Cockpit](../../.gitbook/assets/engage-cockpit.png)
2626

2727
Clicking the Open button provides detailed information:
2828

29-
![](../../.gitbook/assets/engage-cockpit-2.png)
29+
![Umbraco Engage Cockpit - Detailed information](../../.gitbook/assets/engage-cockpit-2.png)
3030

31-
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.
31+
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.

13/umbraco-engage/installation/troubleshooting-installs.md

Lines changed: 21 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -6,75 +6,75 @@ description: Use the checklist in this article to verify your Umbraco Engage ins
66

77
## The Umbraco Engage Checklist
88

9-
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
9+
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.
1010

11-
### 1. The Marketing section
11+
### 1. The Engage section
1212

13-
After logging in to Umbraco you can see the Marketing section next to the other main sections in the Umbraco backoffice.
13+
After logging in to Umbraco, you can see the Engage section next to the other main sections in the Umbraco backoffice.
1414

15-
If you cannot see this, please check if your Umbraco user or user group has access to the Marketing section.
15+
If you cannot see this, please check if your Umbraco user or user group has access to the Engage section.
1616

17-
![](../.gitbook/assets/engage-engage-section.png)
17+
![Engage section in the Backoffice](../.gitbook/assets/engage-engage-section.png)
1818

19-
### 2. Marketing Content Apps
19+
### 2. Engage Content Apps
2020

21-
When editing a page within Umbraco you should be able to see the following Content App on the top right of the page:
21+
When editing a page within Umbraco, you should be able to see the following Content App on the top right of the page:
2222

23-
![](../.gitbook/assets/engage-content-apps.png)
23+
![Content Apps on content page](../.gitbook/assets/engage-content-apps.png)
2424

25-
If you cannot see this, please check if your Umbraco user or user group has access to the Marketing section.
25+
If you cannot see this, please check if your Umbraco user or user group has access to the Engage section.
2626

2727
### 3. Cockpit
2828

2929
Is the **Umbraco Engage Cockpit tool** visible on the front end of your site **after logging into Umbraco**?
3030

31-
No? Ensure you added the [Cockpit Partial view](../getting-started/for-developers/cockpit.md) in your main template.
31+
No? Ensure you have added the [Cockpit Partial view](../getting-started/for-developers/cockpit.md) in your main template.
3232

33-
![](../.gitbook/assets/engage-cockpit-1.png)
33+
![Umbraco Engage Cockpit tool](../.gitbook/assets/engage-cockpit-1.png)
3434

35-
### 4. Cockpit Client Side Data
35+
### 4. Cockpit Client-Side Data
3636

3737
Can you see client-side data such as **scroll depth** & **total time** on pages in analytics or the cockpit?
3838

3939
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.
4040

41-
<figure><img src="../.gitbook/assets/engage-cockpit-2.png" alt=""><figcaption></figcaption></figure>
41+
![Cockpit Client-Side Data](../.gitbook/assets/engage-cockpit-2.png)
4242

4343
### 5. Umbraco Forms
4444

4545
Go to a form and add a new question. Do you see this option?
4646

47-
![](../.gitbook/assets/engage-analytics-form-field.png)
47+
![Analytics Visitor ID field in Forms](../.gitbook/assets/engage-analytics-form-field.png)
4848

49-
Go to Marketing -> Settings -> Create a new goal. Do you see the following option called **Umbraco Forms Submission**?
49+
Go to Engage -> Settings -> Create a new goal. Do you see the following option called **Umbraco Forms Submission**?
5050

51-
![](../.gitbook/assets/engage-forms-goal-type.png)
51+
![Umbraco Forms Submission optiom in Goal dropdown](../.gitbook/assets/engage-forms-goal-type.png)
5252

5353
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).
5454

5555
### 6. Analytics
5656

57-
Edit a page and go to the Content App marked **Analytics** or **Marketing** -> **Analytics** from the top navigation.
57+
Edit a page and go to the Content App marked **Analytics** or **Engage** -> **Analytics** from the top navigation.
5858

5959
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.
6060

6161
### 7. Locations for Analytics
6262

63-
Do you only see \<unknown> in the Location tab of Analytics?
63+
Do you only see <unknown> in the Location tab of Analytics?
6464

6565
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).
6666

6767
Once set up, you will see analytics for countries like this below:
6868

69-
![](../.gitbook/assets/engage-analytics-error-fixed.png)
69+
![Countries Analytics Data](../.gitbook/assets/engage-analytics-error-fixed.png)
7070

7171
### 8. Setup IP Filters
7272

7373
Confirm that the IP of your company/office building has been set to be excluded from Umbraco Engage. This is done to ensure it is excluded from tracking and reporting, along with anyone else who is a content editor of the website.
7474

7575
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**.
7676

77-
![](../.gitbook/assets/engage-settings-ip-filter.png)
77+
![Setup IP Filters](../.gitbook/assets/engage-settings-ip-filter.png)
7878

7979
### 9. Reload after Cookie consent
8080

@@ -88,7 +88,7 @@ If you have performed all the steps and do not see Analytics data within Umbraco
8888
* Refresh the page while the developer tools are open.
8989
* Look for a POST request being made to `umbraco/engage/pagedata/ping` in the Network Tab of requests
9090

91-
<figure><img src="../.gitbook/assets/engage-troubleshoot-missing-data.png" alt=""><figcaption></figcaption></figure>
91+
![Network tab of your browser](../.gitbook/assets/engage-troubleshoot-missing-data.png)
9292

9393
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:
9494

13/umbraco-engage/marketers-and-editors/ab-testing/monitor-the-ab-test.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ description: >-
88

99
# Monitor the A/B Test
1010

11-
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.
11+
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.
1212

1313
If you go to the overview you can see all running tests. The overview includes the following information:
1414

13/umbraco-engage/marketers-and-editors/ab-testing/setting-up-the-ab-test.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ Setting up an A/B test in Umbraco Engage requires no code or need for any extern
1313
Starting A/B tests can be done in two ways:
1414

1515
* Initiate a Single Page, Multiple Page, or Document Type test via the Content App on the specific page,
16-
* Initiate Multipage and Document Type tests via the Marketing section.
16+
* Initiate Multipage and Document Type tests via the Engage section.
1717

1818
## Set up the test
1919

13/umbraco-engage/marketers-and-editors/ab-testing/types-of-ab-tests/document-type-test.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -9,15 +9,15 @@ description: >-
99

1010
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.
1111

12-
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.
12+
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.
1313

14-
![](../../../.gitbook/assets/engage-ab-test-document-type-test.png)
14+
![Setup Test](../../../.gitbook/assets/engage-ab-test-document-type-test.png)
1515

1616
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.
1717

1818
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:
1919

20-
![](../../../.gitbook/assets/engage-ab-test-documettype-javascript.png)
20+
![Edit variant using CSS or JavaScript](../../../.gitbook/assets/engage-ab-test-documettype-javascript.png)
2121

2222
In this example, some JavaScript changes the page's background color.
2323

13/umbraco-engage/marketers-and-editors/ab-testing/types-of-ab-tests/multiple-pages-test.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -9,15 +9,15 @@ description: >-
99

1010
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.
1111

12-
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.
12+
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.
1313

14-
![](../../../.gitbook/assets/engage-ab-test-mutliple-pages.png)
14+
![Setup Test](../../../.gitbook/assets/engage-ab-test-mutliple-pages.png)
1515

1616
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.
1717

1818
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:
1919

20-
![](../../../.gitbook/assets/engage-ab-test-documettype-javascript.png)
20+
![Edit variant using CSS or JavaScript](../../../.gitbook/assets/engage-ab-test-documettype-javascript.png)
2121

2222
In this example, some JavaScript is added to change the page's background color.
2323

0 commit comments

Comments
 (0)