Skip to content

Commit 6df0151

Browse files
committed
Fixed vale errors and added missing descriptions
1 parent b255d4b commit 6df0151

File tree

13 files changed

+57
-71
lines changed

13 files changed

+57
-71
lines changed

13/umbraco-engage/developers/analytics/extending-analytics/sending-data-to-the-gtm-datalayer.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: >-
44
Engage to the Google Tag Manager (GTM) data layer in Razor templates.
55
---
66

7-
# Sending data to the GTM Datalayer
7+
# Sending data to the Google Tag Manager (GTM) Datalayer
88

99
Umbraco Engage provides a partial view that pushes variables related to A/B testing and personalization to the Google Tag Manager (GTM) data layer.
1010

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

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -77,15 +77,17 @@ public class DayOfWeekSegmentRuleFactory : ISegmentRuleFactory
7777
}
7878
```
7979

80-
We are using the class `DayOfWeekSegmentRuleConfig` as a representation of the configuration of the rule, which is not strictly necessary but makes it easier. The configuration is stored as a string in the database but in code, we like to have IntelliSense so we parse the stored configuration to this class:
80+
We are using the class `DayOfWeekSegmentRuleConfig` as a representation of the configuration of the rule, which is not strictly necessary but makes it easier. The configuration is stored as a string in the database. or IntelliSense support in code, the stored configuration is parsed into this class:
8181

8282
{% code overflow="wrap" %}
83+
8384
```csharp
8485
public class DayOfWeekSegmentRuleConfig
8586
{
8687
public DayOfWeek DayOfWeek { get; set; }
8788
}
8889
```
90+
8991
{% endcode %}
9092

9193
The segment rule factory needs to be registered so Umbraco Engage can use it.\
@@ -247,7 +249,7 @@ We want to display the picked day to the user:
247249
</span>
248250
```
249251

250-
We store the chosen day of the week as an integer 0-6 ($ctrl.config.dayOfWeek) but in the display component, we want to show the actual day (e.g. `Monday`). Our rule definition defines the mapping in its `data.days` property so we convert it using that and display the name of the day.
252+
The chosen day of the week is stored as an integer (0-6) in `$ctrl.config.dayOfWeek`, but in the display component shows the actual day (for example. `Monday`). Our rule definition defines the mapping in its `data.days` property so we convert it using that and display the name of the day.
251253

252254
* `segment-rule-day-of-week-display.js`
253255

13/umbraco-engage/developers/settings/custom-goals-scoring.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ Creating the goal is similar to creating a page view or page event goal. The **g
1818

1919
![goal id](../../.gitbook/assets/engage-custom-goal-ID.png)
2020

21-
## Trigger goal in C\#
21+
## Trigger goal in C#
2222

2323
To trigger the goal, execute C# code during the visitor's pageview. Inject `Umbraco.Engage.Business.Analytics.Goals.IGoalService`, which has a `TriggerGoal(long goalId, int value)` method. An implementation looks like:
2424

@@ -45,7 +45,7 @@ The method automatically determines the current page view, linking the goal to a
4545

4646
To trigger a goal outside of an HTTP request, use the overload of **TriggerGoal** that takes the GUID of the pageview.
4747

48-
Retrieve this pageview GUID during the original request using the **Umbraco.Engage.Business.Analytics.Common.IPageviewGuidManager**. You will need to store this pageview GUID for later use when invoking:
48+
Retrieve the pageview GUID in the original request using **Umbraco.Engage.Business.Analytics.Common.IPageviewGuidManager**. You will need to store this pageview GUID for later use when invoking:
4949

5050
```cs
5151
_goalService.TriggerGoal(pageviewGuid, goalId, value);

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ Get insights on sizing your infrastructure to meet your project's demands.
1616

1717
Discover best practices for setting up load balancing and managing continuous integration and deployment environments.
1818

19-
## [Content Delivery Network Recommendations](content-delivery-network-recommendations.md)
19+
## [Content Delivery Network (CDN) Recommendations](content-delivery-network-recommendations.md)
2020

2121
Explore recommended CDN options to improve content delivery speeds.
2222

13/umbraco-engage/getting-started/for-developers/infrastructure-sizing.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ The following presents recommendations based on the environment and the number o
1111
## Non-cloud
1212

1313
* **100.000 page views per month or less:** Database: CPU 2, 4-8 GB RAM, 50GB disk
14-
* **500.000 page views per month or less:** Database: CPU 4, 8-16 GB RAM, 100GB SSD disk
14+
* **500.000 page views per month or less:** Database: CPU 4, 8-16 GB RAM, 100GB Solid State Drive (SSD) disk
1515
* **1.000.000 page views per month or less:** Database: CPU 8, 16-32 GB RAM, 250GB SSD disk
1616
* **1.000.000 page views per month or more:** Please [contact our Expert Services](mailto:[email protected]) team to discuss the infrastructure requirements.
1717

13/umbraco-engage/getting-started/for-marketers-and-editors/cockpit.md

Lines changed: 6 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -11,25 +11,17 @@ The cockpit lets you check out all the stored data when browsing the website. It
1111

1212
You should see the Umbraco Engage Cockpit on the left or right side of the screen:
1313

14-
<div align="center">
15-
16-
<figure><img src="../../.gitbook/assets/engage-cockpit-3.png" alt="Cockpit"><figcaption><p>Cockpit</p></figcaption></figure>
17-
18-
</div>
14+
![Cockpit](../../.gitbook/assets/engage-cockpit-3.png)
1915

2016
Click **Open** to see all the features of the Cockpit:
2117

22-
<div align="center">
23-
24-
<figure><img src="../../.gitbook/assets/engage-cockpit-overview.png" alt="Cockpit features"><figcaption><p>Cockpit features</p></figcaption></figure>
25-
26-
</div>
18+
![Cockpit features](../../.gitbook/assets/engage-cockpit-overview.png)
2719

2820
## Access to the cockpit
2921

3022
When the Umbraco Engage code has been added to the page you can see it when you are logged in to Umbraco. Visitors to your website do not have access to the Cockpit.
3123

32-
If you do not see the Cockpit while the Umbraco back-office runs on a different domain please contact the technical team and refer to the [load balancing / CM / CD environments](../for-developers/loadbalancing-and-cm-cd-environments.md) section.
24+
If the Cockpit is missing while Umbraco backoffice runs on a different domain, contact the technical team. You can also refer to the [Load Balancing and CM/CD Environments](../for-developers/loadbalancing-and-cm-cd-environments.md) article.
3325

3426
### Data reporting client-side
3527

@@ -43,11 +35,7 @@ The following information is tracked:
4335
* All [fired events](../../developers/analytics/client-side-events-and-additional-javascript-files/create-your-own-events.md) are tracked.
4436
* Every out-click to other domains, a pdf file or excel file is measured by default.
4537

46-
<div align="left">
47-
48-
<figure><img src="../../.gitbook/assets/engage-cockpit-analytics.png" alt="Cockpit Analytics."><figcaption><p>Cockpit Analytics.</p></figcaption></figure>
49-
50-
</div>
38+
![Cockpit Analytics](../../.gitbook/assets/engage-cockpit-analytics.png)
5139

5240
### Data reporting server-side
5341

@@ -61,18 +49,10 @@ In this section you can see all the data that is captured on the server side:
6149

6250
Also, you have the option to delete your Umbraco Engage cookie
6351

64-
<div align="left">
65-
66-
<figure><img src="../../.gitbook/assets/engage-cockpit-analytics-2.png" alt="Delete Umbraco Engage cookies."><figcaption><p>Delete Umbraco Engage cookies.</p></figcaption></figure>
67-
68-
</div>
52+
![Delete Umbraco Engage cookies](../../.gitbook/assets/engage-cockpit-analytics-2.png)
6953

7054
### Segments
7155

7256
In the segments section, you can see which segments are configured and which are applied to the current visitor.
7357

74-
<div align="left">
75-
76-
<figure><img src="../../.gitbook/assets/engage-cockpit-personalization.png" alt="Segments"><figcaption><p>Segments</p></figcaption></figure>
77-
78-
</div>
58+
![Segments](../../.gitbook/assets/engage-cockpit-personalization.png)

13/umbraco-engage/installation/licensing.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ There are a few differences as to what the licenses cover:
4444
* Each individual subdomain has to be specified as part of the license (e.g. `subdomain.mysite.com`), wildcard subdomains are not allowed.
4545

4646
{% hint style="info" %}
47-
If you have multiple backoffice domains pointing at the same installation, you have the option to purchase and [add **additional domains**](the-licensing-model.md#add-additional-domains) to your license.
47+
If multiple backoffice domains share the same installation, you have purchase and add [**additional domains**](the-licensing-model.md#add-additional-domains) to your license.
4848

4949
This is an add-on domain for existing licenses. Refunds will not be given for this product.
5050
{% endhint %}

13/umbraco-engage/marketers-and-editors/ab-testing/what-is-ab-testing.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -2,26 +2,26 @@
22

33
It goes too far to give a total overview of what A/B testing is. There are some great resource out there that can inspire you and can go in real depth what A/B testing is.
44

5-
For now we will stick with this explaination: A/B testing is a methodical way of testing (and hopefully improving) your website. By serving two or more versions of a webpage, contentblock or website to different visitors results can be gathered which version is performing better for a specific conversion goal.
5+
For now we will stick with this explaination: A/B testing is a methodical way of testing (and hopefully improving) your website. By serving multiple versions of a webpage, content block, or website to different visitors, gather data on which version performs better for a specific goal.
66

77
## Why should you A/B test your website?
88

9-
Your website is always underperforming its potential. Your website will never have a conversion rate of 100% (all visitors do exactly what you want them to do) and probably not even near that conversion rate. By testing specific parts of your website you can experiment and hopefully increase your conversion rate. The internet gives you the ability to test with different variants of your website and see what happens.
9+
Your website is always underperforming its potential. Your website will never have a conversion rate of 100%. All visitors do exactly what you want them to do and probably not even near that conversion rate. By testing specific parts of your website you can experiment and hopefully increase your conversion rate. The internet gives you the ability to test with different variants of your website and see what happens.
1010

1111
## A/B Testing in Umbraco
1212

13-
There are already a lot of great A/B testing tooling out there (Google Experiments, Optimizely, Visual Website Optimizer). They do a really great job on A/B testing but they all lack a key feature that Umbraco Engage has; Umbraco Engage is fully integrated within Umbraco. This allows you to integrate A/B testing in your daily workflow instead of an add-on on top of your website. This means:
13+
There are already a lot of great A/B testing tooling out there (Google Experiments, Optimizely, Visual Website Optimizer). They do a really great job on A/B testing but they lack a key feature that Umbraco Engage offers: full integration within Umbraco. This allows you to integrate A/B testing in your daily workflow instead of an add-on on top of your website. This means:
1414

15-
* You can A/B test your content in exactly the same and user-friendly way that Umbraco does. This will enable you and your editors to start A/B testing really easy.
16-
* The A/B test is rendered automatically without any additional line of code. This means that you don't have to reserve time to "implement A/B testing". It is just there and you can start immediately start testing. Also that means there is no content flickering like in many other tools (just for fun... Google for "[A/B Testing flickering](https://www.google.com/search?q=ab+testing+flickering)"...)
17-
* You can use all the resources that Umbraco gives you. You can reuse images of the media library, you can pick contentblock as you are used, and you do not have to worry about changing url's while doing a test.
15+
* You can A/B test your content in the same user-friendly way as Umbraco does, allowing you and your editors to start A/B testing.
16+
* The A/B test is rendered automatically without any additional line of code. This means that you don't have to reserve time to "implement A/B testing". It is there and you can start testing immediately. Also that means there is no content flickering like in many other tools.
17+
* You can use all the resources that Umbraco gives you. You can reuse images of the media library, you can pick contentblock as you are used, and you do not have to worry about changing URL's while doing a test.
1818
* Within Umbraco Engage you will see that A/B tests are running, so your fellow editors are aware of this and will not ruin your experiments
1919
* Because we use first-party analytics and cookies you will track data across all your visitors and not only on a subset of customers which do not have any ad- and cookie block tooling
2020
* Our A/B test is context aware and will make sure that the A/B test is render everywhere correctly. For example; if you are testing a catchy product title it will automatically not render only that new title on the page itself, but also on your overview, your homepage, your shopping cart or at any other place you're using the title. This is impossible with any other tool!
2121

2222
## Some great resources
2323

24-
There are a lot of books out there that do a great job explaining the importance of A/B testing and why you should start testing your website today. A short list of the books that inspired the Umbraco Engage team:
24+
Many books explain the importance of A/B testing and why you should start testing your website today. A short list of the books that inspired the Umbraco Engage team:
2525

2626
* Dan Siroker and Pete Koomen. _A/B Testing. The most powerful way to turn clicks into customers_. Hoboken, New Jersey: John Wiley & Sons, Inc., 2013. [Print](https://www.amazon.com/Testing-Most-Powerful-Clicks-Customers/dp/1118792416)
2727
* Chris Goward. _You should test that!_ Indianapolis, Indiana: John Wiley & Sons, Inc., 2013. [Print](https://www.amazon.com/You-Should-Test-That-Optimization/dp/1118301307)

13/umbraco-engage/marketers-and-editors/analytics/campaigns.md

Lines changed: 12 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -10,27 +10,29 @@ In the **Campaigns** tab of the Umbraco Engage, you can view all analytics data
1010

1111
You can add five different parameters to your URLs:
1212

13-
* **utm\_source**: Identify the advertiser, site, publication that is sending traffic to your property. For example: google, newsletter4, billboard.
14-
* **utm\_medium**: The advertising or marketing medium. For example: cpc, banner, email newsletter.
15-
* **utm\_campaign**: The individual campaign name, slogan, promo code for a product.
16-
* **utm\_term**: Identify paid search keywords. If you are manually tagging paid keyword campaigns, you should also use _utm\_term_ to specify the keyword.
17-
* **utm\_content**: Used to differentiate similar content or links within the same ad. For example: if you have two call-to-action links within the same email message, you can use _utm\_content_ and set different values for each so you can tell which version is more effective.
13+
* **utm_source**: Identify the advertiser, site, publication that is sending traffic to your property. For example: google, newsletter4, billboard.
14+
* **utm_medium**: The advertising or marketing medium. For example: cpc, banner, email newsletter.
15+
* **utm_campaign**: The individual campaign name, slogan, promo code for a product.
16+
* **utm_term**: Identify paid search keywords. If you are manually tagging paid keyword campaigns, you should also use _utm_term_ to specify the keyword.
17+
* **utm_content**: Used to differentiate similar content or links within the same ad. For example: if you have two call-to-action links within the same email message, you can use _utm_content_ and set different values for each so you can tell which version is more effective.
1818

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

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

23-
* **utm\_source** = newsletter-july-2024 to identify that this visitor came from this specific newsletter
24-
* **utm\_medium** = newsletter to show that the medium was a newsletter
25-
* **utm\_campaign** = more\_signups because that newsletter was part of a larger campaign
26-
* **utm\_content** = bottom\_button to identify a specific link in the newsletter
23+
* **utm_source** = newsletter-july-2024 to identify that this visitor came from this specific newsletter
24+
* **utm_medium** = newsletter to show that the medium was a newsletter
25+
* **utm_campaign** = more_signups because that newsletter was part of a larger campaign
26+
* **utm_content** = bottom_button to identify a specific link in the newsletter
2727

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

3030
{% code overflow="wrap" %}
31+
3132
```
3233
https://www.umbraco.com/pricing/?utm_source=newsletter-july-2024&utm_medium=newsletter&utm_campaign=more_signups&utm_content=bottom_button
3334
```
35+
3436
{% endcode %}
3537

3638
## Campaign Report

13/umbraco-engage/marketers-and-editors/analytics/google-analytics-vs-umbraco-engage.md

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

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

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

0 commit comments

Comments
 (0)