Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ If you go to the overview you can see all running tests. The overview includes t
* How many visitors are included in the test?
* For how long should the test run to produce relevant results?

<figure><img src="../../.gitbook/assets/engage-ab-test-monitor.png" alt="Monitoring the A/B tests."><figcaption><p>Monitoring the A/B tests.</p></figcaption></figure>
![Monitoring the A/B tests.](../../.gitbook/assets/engage-ab-test-monitor-v16.png)

You can see all test variants when you access the details on a test. You can preview the variants, or disable them. If for example, the conversion rate has decreased in a variant, it could be smart to disable that variant.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -6,30 +6,20 @@ description: >-

# Previewing an A/B Test

There are different ways to preview your A/B Test variants. In this article, we will discuss all options.
There are different ways to preview your A/B Test variants.

## During the setup of your new A/B Test

When setting up a new A/B Test there are three options to preview your A/B Test variant. First of all, you open the preview of your variant by clicking on the **preview** button in the overview of variants:

![Open the preview of your variant by clicking on the preview button in the overview of variants when setting up the test.](../../.gitbook/assets/engage-ab-preview-1.png)

When editing a specific variant on a single page you can also preview the page. In the top bar, there is a **Save & Preview** button available:

![When editing a specific variant on a single page you can also preview the page.](../../.gitbook/assets/engage-ab-preview-2.png)

You can also click on **Edit variant** which will open a pop-up where you can add some CSS and JavaScript. Also from here, you can open up the preview by clicking on **Save & preview**:

![You can also preview the variant from the Edit Variant dialog.](../../.gitbook/assets/engage-ab-preview-3.png)

There are plenty of options to open up the preview.
![Open the preview of your variant by clicking on the preview button in the overview of variants when setting up the test.](../../.gitbook/assets/engage-ab-preview-v16-1.png)

With all variants set up, you can get an overview before the A/B Test. In that screen, you also have the option to preview all variants:

![Before launching a test, you can preview the variants to ensure everything looks as it should.](../../.gitbook/assets/engage-ab-preview-4.png)
![Before launching a test, you can preview the variants to ensure everything looks as it should.](../../.gitbook/assets/engage-ab-preview-v16-3.png)

## During a running test

You can preview all the A/B test variants while a test is running. Go to the specific test, and you will have an overview of the current results. You can also preview each variant by clicking the "preview"-button.

![You can also preview your variants while the test is running.](../../.gitbook/assets/engage-ab-preview-5.png)
![You can also preview your variants while the test is running.](../../.gitbook/assets/engage-ab-preview-v16-2.png)
Original file line number Diff line number Diff line change
Expand Up @@ -18,32 +18,32 @@ Starting A/B tests can be done in two ways:

Open the Umbraco content tree and select the A/B tests Content App on the page.

![You can find the A/B Tests Content App on each of the content items in the Content section.](../../.gitbook/assets/engage-a-b-test-content-app.png)
![You can find the A/B Tests Content App on each of the content items in the Content section.](../../.gitbook/assets/engage-a-b-test-content-app-v16.png)

Make sure that you have access to the Content App. [These permissions can be specified](../settings/permissions.md) per Document Types or User Groups.

When you open the Content App you will have an overview of all the A/B tests that are running or finished. You also have the option to start a new test.
When you open the Content App you will have an overview of all the A/B tests that are running or finished. You also have the option to **Create a new test**.

![Use the A/B Tests Content App to get an overview of running tests and start new ones.](../../.gitbook/assets/engage-a-b-test-content-app-overview.png)
![Use the A/B Tests Content App to get an overview of running tests and create new ones.](../../.gitbook/assets/engage-a-b-test-content-app-overview-v16.png)

## Configure the A/B test

When you start a new test you will have to specify the following:

* The name of the test.
* The title of the test.
* Which testing project it should be part of.
* Write a description/hypothesis.

After that, you have to specify the type of test and set up the specific test. It is also possible to preview your variant from here.
After that, you need to specify which goal you want to measure, as it is all about optimizing for this goal. Set the audience that you want to include in the test.

As a final step, you need to specify which goal you want to measure, as it is all about optimizing for this goal. Set the audience that you want to include in the test.
As a final step, you have to specify the type of test and set up the specific test. It is also possible to preview your variant from here.

![An overview of all the configuration options available when setting up an A/B test.](../../.gitbook/assets/engage-a-b-test-test-setup.png)
![An overview of all the configuration options available when setting up an A/B test.](../../.gitbook/assets/engage-a-b-test-test-setup-v16.png)

## Launching the A/B test

Once you have set everything up the test is ready to go. You can preview the final variants and check if everything set up correct.

If that is the case you can start the test immediately, or schedule it for later.

![Launch the test right away, or schedule it to start at a later point.](../../.gitbook/assets/engage-ab-test-launch.png)
![Launch the test right away, or schedule it to start at a later point.](../../.gitbook/assets/engage-ab-test-launch-v16.png)
Original file line number Diff line number Diff line change
Expand Up @@ -9,18 +9,18 @@ icon: square-exclamation

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 **Content 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 the **Test setup** section.

![Setup Test](../../../.gitbook/assets/engage-ab-test-document-type-test.png)
![Setup Test](../../../.gitbook/assets/engage-ab-test-content-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:

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

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

You can save and preview whether your code works by clicking **Save & preview**.
You can check if your code works by clicking **Preview**.

After creating all variants, start your A/B testing as written in the [Setting up the A/B test](../setting-up-the-ab-test.md) article.
Original file line number Diff line number Diff line change
Expand Up @@ -7,20 +7,20 @@ icon: square-exclamation

# Multiple Pages Test

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 Multiple Pages test allows you to run A/B tests 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 [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 **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 the **Test setup** section.

![Setup Test](../../../.gitbook/assets/engage-ab-test-mutliple-pages.png)
![Setup Test](../../../.gitbook/assets/engage-ab-test-mutliple-pages-v16.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:

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

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

You can save and preview whether your code works by clicking **Save & preview**.
You can check if your code works by clicking **Preview**.

After you have created all variants start your A/B testing as described in the [Setting up the A/B test](../setting-up-the-ab-test.md) article.
Original file line number Diff line number Diff line change
Expand Up @@ -18,41 +18,37 @@ The first variant is always the original content and the published page. Variant

The variant can be given a name and if you click on **Edit** you will open up the split view editor:

<figure><img src="../../../.gitbook/assets/image (6).png" alt="Split view editing"><figcaption><p>Split view editing</p></figcaption></figure>
![Split view editing](../../../.gitbook/assets/Split-view-editing.png)

On the left side, the original content is shown (Original) and the variant is shown on the right. In this side-by-side editing mode, you can edit the content for your variant.

### Setting up the Document Type for split-view editing

Some properties are inactive (_visually indicated because they are greyed out_). Which properties you can edit is specified in [the setup of the properties of your Document Type](https://docs.umbraco.com/umbraco-cms/fundamentals/data/defining-content).

Specifying when segmentation is allowed can be done per property using the **Allow segmentation** value.
Specifying when segmentation is allowed can be done per property using the **Shared across segments** value.

<figure><img src="../../../.gitbook/assets/image (7).png" alt="Property settings"><figcaption><p>Property settings</p></figcaption></figure>
![Property settings](../../../.gitbook/assets/property-settings.png)

In the overview of the Document Type, you will see if properties can be segmented as they will have the **Vary by segments** label:
In the overview of the Document Type, you will see if properties can be segmented as they will have the **Shared across segments** label:

<figure><img src="../../../.gitbook/assets/image (8).png" alt="Vary by segment label"><figcaption><p>Vary by segment label</p></figcaption></figure>
![Shared across segments](../../../.gitbook/assets/Shared-across-segments.png)

### Add CSS or JavaScript

Sometimes you cannot adjust a specific property because it was not configured when Umbraco was set up. In those cases, you can use the CSS/JavaScript field to add a code-snippet to make these adjustments. The best way is to do it via property editing in the split view edit mode. You do not have to write any CSS or JavaScript code.

To do this click **CSS/JavaScript** in the A/B Testing editor bar:

<figure><img src="../../../.gitbook/assets/image (10).png" alt="Add CSS/JavaScript tab"><figcaption><p>Add CSS/JavaScript tab</p></figcaption></figure>

This will give the editor a popup where CSS and JavaScript can be entered:
To do this, go to **A/B Tests** Content App. Click **Edit** on the variant. This will give the editor a popup where CSS and JavaScript can be entered:

<figure><img src="../../../.gitbook/assets/image (9).png" alt="CSS/JavaScript popup"><figcaption><p>CSS/JavaScript popup</p></figcaption></figure>

These lines of code will automatically be inserted at the bottom of the page.
![CSS/JavaScript popup](../../../.gitbook/assets/single=page-ab-test-edit-variant.png)

Use the **Save & preview** button to make sure all works as expected. This can also be done via the "Save & preview" option in the editor bar.
These lines of code will automatically be inserted at the bottom of the page.

Once the variant is set up, finish the A/B Test via the **Back to A/B test** button in the editor bar.
You can check if your code works by clicking **Preview**.

<figure><img src="../../../.gitbook/assets/image (11).png" alt="Finish setting up A/B test"><figcaption><p>Finish setting up A/B test</p></figcaption></figure>
Once the variant is set up, click **Save** to finish the A/B Test.

Finish the steps in the [Settings up the A/B test](../setting-up-the-ab-test.md) article to verify and start your A/B Test.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ Split URL testing in Umbraco Engage allows you to compare different versions of

To set up a Split URL test, you must create multiple versions of a page. Each version can have different designs, text, or buttons based on the options setup in Umbraco.

You can start a Split URL test from the [Engage section](../../introduction/the-umbraco-engage-section.md) or within the [Content App](../../introduction/content-apps.md). The type is selected in step 2 of the setup.
You can start a Split URL test from the [Engage section](../../introduction/the-umbraco-engage-section.md) or within the [Content App](../../introduction/content-apps.md). The type is selected in the **Test setup** section.

![Split URL Test](../../../.gitbook/assets/split-url-test.png)

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,6 @@ The feature gives a visual representation of the average scroll depth of your vi

An advantage is that you do not need to integrate any 3rd-party tools. This will prevent additional load times and possible issues with data ownership.

![View a scroll heatmap on each published content item in the Content section.](../../.gitbook/assets/engage-analytics-scroll-heatmap-2.png)
![View a scroll heatmap on each published content item in the Content section.](../../.gitbook/assets/engage-analytics-scroll-heatmap-v16.png)

The heatmap only collects data if [the client-side script](../../developers/analytics/client-side-events-and-additional-javascript-files/) is installed on your website.
Original file line number Diff line number Diff line change
Expand Up @@ -36,6 +36,6 @@ It also allows you to set up personalized variants for each node.

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

![Document Type Permissions in the Settings section](../../.gitbook/assets/engage-content-apps-permissions1.png)
![Document Type Permissions in the Settings section](../../.gitbook/assets/engage-content-apps-doc-type-permissions.png)

![User group Permissions in the Settings section](../../.gitbook/assets/engage-content-apps-permissions2.png)
![User group Permissions in the Settings section](../../.gitbook/assets/engage-content-apps-user-group-permissions.png)
Original file line number Diff line number Diff line change
Expand Up @@ -14,11 +14,11 @@ Most parameters within Umbraco Engage are explicit and true or false.

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.

This article teaches you how to set up[ the customer journey](setting-up-the-customer-journey.md) or [personas](setting-up-personas.md). As soon as you have set these up you can use the segment parameters for the customer journey and the personas.
This article teaches you how to set up [the customer journey](setting-up-the-customer-journey.md) or [personas](setting-up-personas.md). As soon as you have set these up you can use the segment parameters for the customer journey and the personas.

In the [segment builder](../creating-a-segment.md), you can use these implicit parameters the same way you would apply any other segment parameter.

![Using implicit parameters in the segment builder](../../../.gitbook/assets/engage-personalization-implicit.png)
![Using implicit parameters in the segment builder](../../../.gitbook/assets/engage-personalization-implicit-v16.png)

By clicking personas you will see an overview of all the personas that you have set up within your installation.

Expand Down
Loading