diff --git a/user-docs/README.md b/user-docs/README.md index 9766978b..aaa227eb 100644 --- a/user-docs/README.md +++ b/user-docs/README.md @@ -10,10 +10,8 @@ order: 10 Welcome to the Altis User Guides. This documentation is here to help you get the best out of Altis' advanced features and become a power user. -Here’s where you’ll find an assortment of articles on all things Altis. From -creating content with personalisation, to serving up experiences for multiple -audiences. To running A/B tests to understand your visitors. Plus much more. All -the features you’ll need to create, manage and grow your Altis website. +Here’s where you’ll find an assortment of articles on all things Altis. All the features you’ll need to create, manage and grow your +Altis website. (Developers, you probably want the [developer documentation](https://docs.altis-dxp.com/). Although you’re welcome to stick around and explore here too) @@ -43,14 +41,6 @@ article has plenty of links to related topics. - [Editing Images](media/editing-images.md) - [Global Media Library](media/global-media-library.md) -### Content Experimentation - -- [Multivariant Testing](personalising-content/README.md) -- [Experience Blocks](personalising-content/experience-blocks.md) -- [Personalised Content](personalising-content/personalised-content.md) -- [Audiences](personalising-content/audiences.md) -- [Insights](personalising-content/insights.md) - ### Administration - [Configuration](administration/README.md) diff --git a/user-docs/administration/README.md b/user-docs/administration/README.md index 7e9534af..cb80dd0a 100644 --- a/user-docs/administration/README.md +++ b/user-docs/administration/README.md @@ -84,7 +84,6 @@ If there are blocks you never use, you can remove them from the list of blocks. This opens all the available types of blocks: -- Experience blocks - Text - Media - Design diff --git a/user-docs/data-privacy/README.md b/user-docs/data-privacy/README.md index 121c0dbe..dac116e2 100644 --- a/user-docs/data-privacy/README.md +++ b/user-docs/data-privacy/README.md @@ -61,23 +61,8 @@ Click the dropdown to choose whether to **display a cookie consent banner**: ### Choose how long to store cookies -By default cookies are stored for **30 days**. Changing this can impact your [analytics](../personalising-content/insights.md) -and [audiences](../personalising-content/audiences.md). Here’s why. - -Visitors who return to your website **within 30 days** show as repeat visitors. If they return after 30+ days, they count as a new -visitor. This could be an issue if cookies expire on Day 30 and: - -- **Your website greets returning visitors differently**. - A visitor returning on Day 31+ won’t get a “Welcome back” message. Instead they’ll get your “Welcome to our website” message for - new visitors. -- **You’re running A/B tests comparing first-time and returning visitor behavior** - Visitors returning after 30+ days will be counted as new visitors- **You’re tracking impact of PPC ads** - Imagine a visitor clicks your ad and visits your website. They - go away and compare you to other websites. On Day 31 they - return to convert. By then, they’re a new user and you won’t - know they came back because of the ad. - -If you do want to change the number of days, click the white box and add the number: +By default cookies are stored for **30 days**. +If you want to change the number of days, click the white box and add the number: ![Screenshot cookie expiration input box](../assets/privacy-consent-image7.png) diff --git a/user-docs/personalising-content/README.md b/user-docs/personalising-content/README.md deleted file mode 100644 index cd60a4d8..00000000 --- a/user-docs/personalising-content/README.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -title: Content Experimentation -order: 40 ---- - -# Multivariant Testing - -![Screenshot](../assets/altis-header-12.png) - -Multivariant testing allows you to run scheduled A/B tests across content and copy to maximise your audience engagement and -continually refine your personalisation strategy. - -You can test variations of your pages scientifically. Set dimensions beforehand, so you automatically remove any risks of **bias**. -Run tests based on your **hypothesis**. Then wait until Altis notifies you that a test has **won**. - -## How to experiment with A/B tests - -Create a page or post. - -Click the A/B icon to open the experiments sidebar: - -![Screenshot](../assets/multivariant-testing-image12.png) - -You can test: - -- Titles -- Featured images - -### How to A/B test titles & images - -Click the dropdown next to Titles or images: - -![Screenshot](../assets/multivariant-testing-image14.png) - -You can then add the titles or images you want to test. Both involve the same process. So let’s test a standard “how to” title -against something a bit more, well, “marvellous”. - -Title A is the original (or control). It’s generated based on the title already being used: - -![Screenshot](../assets/multivariant-testing-image10.png) - -You can then add the variant as **Title B**. Another box automatically appears if you want to add another variant (**Title C**): - -![Screenshot](../assets/multivariant-testing-image7.png) - -To **remove** a variant, click the **minus icon**. - -#### Choose how many visitors to include - -The **traffic percentage** shows how many website visitors to include in your test. Imagine you get 1,000 visitors per day. - -![Screenshot](../assets/multivariant-testing-image2.png) - -To include all 1,000 visitors, drag to 100%. To include 500 visitors, drag to 50%. - -When you include less than 100%, the remaining percentage just see the original: - -![Screenshot](../assets/multivariant-testing-image10.png) - -#### How long to run a test - -You can set the start and end **dates**. Perhaps for testing seasons (for example winter sales) or promotions (Cyber Monday): - -![Screenshot](../assets/multivariant-testing-image4.png) - -#### How to know when a variant wins - -A test wins when it reaches **statistical significance**. That is, when a variant is outperforming the other/s by at least 5%, and -there’s a 99% certainty that the results aren’t down to chance. - -When this happens, the **Author** and **Admin** get notifications. - -### How to A/B test your content - -Setting up different versions is one thing. You can also test different blocks, and give them a conversion goal. You’ll see the -results, know what’s working, and discover what needs changing. - -Start [creating your content](../content-and-content-blocks/README.md). - -Add an A/B test [block](../content-and-content-blocks/creating-content-with-blocks.md): - -![Screenshot](../assets/multivariant-testing-image16.png) - -Add content to **Variant A** of the block: - -![Screenshot](../assets/multivariant-testing-image3.png) - -Click **Copy** to create **Variant B**: - -![Screenshot](../assets/multivariant-testing-image1.png) - -Use the tab at the top to **switch** between each variant: - -![Screenshot](../assets/multivariant-testing-image5.png) - -When you’re happy with the content for each variant, click the **Settings** icon: - -![Screenshot](../assets/multivariant-testing-image9.png) - -Click **Advanced settings**: - -![Screenshot](../assets/multivariant-testing-image13.png) - -Set the **percentage** of traffic who will view each variant. When you increase the percentage for one variant, you’ll see it -decrease for the other variants. - -This can be useful if you already have a variant that’s performing well. So you might want to send the **majority** of your traffic -there. And show your variant to a smaller percentage instead: - -![Screenshot](../assets/multivariant-testing-image15.png) - -![Screenshot](../assets/multivariant-testing-image6.png) - -You can also reduce the percentage of **traffic included** in the test. Reduce this, and the remaining percentage will see the -Fallback variant. You can also **pause** the test. - -Each variant can have their own conversion goal: - -- **Impressions** (measuring which variant attracts more eyeballs) -- **Click** on any link (useful if you have some calls to action on the page) -- **Submit** a form (when you’re asking for an enquiry, download, or anything involving some sort of transaction) - -![Screenshot](../assets/multivariant-testing-image8.png) - -You can now track the results by checking [Insights](insights.md) in the dashboard: - -![Screenshot](../assets/multivariant-testing-image11.png) - - diff --git a/user-docs/personalising-content/audiences.md b/user-docs/personalising-content/audiences.md deleted file mode 100644 index c32d611e..00000000 --- a/user-docs/personalising-content/audiences.md +++ /dev/null @@ -1,167 +0,0 @@ ---- -order: 30 ---- - -# Audiences - -Want to understand more about your website visitors and give them better **experiences**? Audiences is the place to start. It’s a -way of **grouping** your visitors, based on criteria you set. - -It only takes a **few clicks** to set up an Audience. Naturally, the more Audiences you set up, the more **granular** you can go -with your messaging. - -## How to create an Audience - -Click Audiences in the dashboard: - -![Screenshot](../assets/audiences-image8.png) - -Click Add New: - -![Screenshot](../assets/audiences-image1.png) - -Give your Audience a title. Maybe based on the **Audience type** so you can remember it later. - -For this example, let’s say you run an ecommerce store. You’re running Google PPC ads for your Christmas campaign. You want to -create an Audience for people who’ve clicked your ad: - -![Screenshot](../assets/audiences-image7.png) - -### Audience rules - -Let’s add the rules that **define your Audience**. - -First, choose if the rules should apply to **all** or **any**. - -For the Christmas PPC ad we’ll choose **Match all of the following rules**: - -![Screenshot](../assets/audiences-image14.png) - -### Audience fields - -You’ll find plenty of fields for including (and excluding) people from your Audience. The more fields you use, the more **segmented -** your Audience becomes. - -Click the **Select a field** dropdown: - -![Screenshot](../assets/audiences-image4.png) - -Help yourself to these options: - -#### Campaign-related - -- First UTM Campaign -- First UTM Source -- First UTM Medium -- First UTM Term -- First UTM Content -- UTM Campaign -- UTM Source -- UTM Medium -- UTM Term -- UTM Content -- Referrer -- Current referrer (for tracking visitors referred more than once) -- First referrer (for tracking performance of the initial referrer) - -#### Device-related - -- Browser -- Browser locale -- Browser version -- Operating System -- Operating System version - -#### Location-related - -- Country - -#### Behaviour-related - -- Sessions (when your visitor does more than one action in one visit) -- Page views - -#### Time-related - -- Hour -- Day -- Month -- Year - -### Audience conditions - -Now we can include, exclude, and set conditions. Let’s stick with our Google PPC Christmas ad example: - -First, we’ll choose **UTM Source** (click the dropdown to view all the other options): - -![Screenshot](../assets/audiences-image6.png) - -Next, we’ll choose the **condition**: - -![Screenshot](../assets/audiences-image5.png) - -We’ll add Google as the UTM source, by clicking **Other, please specify**: - -![Screenshot](../assets/audiences-image13.png) - -That’s the first rule done: - -![Screenshot](../assets/audiences-image16.png) - -We can also **make this rule even more specific**. Imagine the ecommerce store runs Google PPC ads all year. Let’s keep our -Christmas ad Audience separate. - -Click **Add a rule**: - -![Screenshot](../assets/audiences-image11.png) - -We’ve already defined the Audience as: - -- People who clicked the ecommerce store’s Christmas PPC ad - -Let’s say the Christmas ad launched in **December**. So we’ll add a rule that this Audience is only people who clicked in December. -We exclude people who clicked ads at other times of the year. - -Choose Month as the field, and then add the number 12 (December = 12th month): - -![Screenshot](../assets/audiences-image10.png) - -The group is ready to go: - -![Screenshot](../assets/audiences-image3.png) - -### Adding multiple audience groups - -Want to add more groups? Click the **Add a group** button: - -![Screenshot](../assets/audiences-image2.png) - -With **two or more groups**, you can also click the dropdown to match **all or any** groups: - -![Screenshot](../assets/audiences-image15.png) - -### Audience size - -Altis also shows you how adding different fields and conditions will impact the **Audience size**. Data is based on the previous -seven days. So if you’re building a new website, it shows 0 until you start getting visitors: - -![Screenshot](../assets/audiences-image12.png) - -As you gather more data, Audiences will become more powerful. Just like your website: - -![Screenshot](../assets/audiences-image17.png) - -### How to activate an Audience - -When you’ve finished configuring, click the toggle to activate (or deactivate) and click Publish. - -You can also save the Audience as a **draft**: - -![Screenshot](../assets/audiences-image9.png) - -You can now use Audiences for: - -- [Analytics](insights.md) - Build up a segmented picture of how different groups act on your website -- [Personalisation](../content-and-content-blocks/experience-blocks.md) - Create experience blocks with content customised for every audience diff --git a/user-docs/personalising-content/experience-blocks.md b/user-docs/personalising-content/experience-blocks.md deleted file mode 100644 index 81abfaf2..00000000 --- a/user-docs/personalising-content/experience-blocks.md +++ /dev/null @@ -1,108 +0,0 @@ ---- -order: 10 ---- - -# Experience Blocks - -With Experience Blocks, you can **create different versions of your content to show to different audiences**. It’s a way of making -your site give more **personalised** and **contextual** experiences. Instead of standard one-size-fits-all messaging. - -For example, you might run an event for CEOs in Spain and the UK. Create an experience block that displays Spanish language to -Spain-based visitors, and displays English to UK-based visitors. For visitors outside of those locations, create a generic -“fallback” block that displays both English and Spanish. - -What’s more, you can **measure the performance** of each variation. Run A/B tests, try different versions of content, and discover -more about your website visitors. - -## How to add an Experience Block - -Click the **+** sign to add a block: - -![Screenshot](../assets/experience-blocks-image13.png) - -Click **Personalized Content** (you may need to type this into the search bar, or click **Browse all**): - -![Screenshot](../assets/experience-blocks-image10.png) - -### Creating a Fallback block in Altis - -First, create your **Fallback block**. This block will be shown to visitors who don't fit into the audiences you specify. Try using -something **generic** that is still informative: - -![Screenshot](../assets/experience-blocks-image1.png) - -Click this block and the **sidebar** opens. Give your block a **title**. Here’s also where you can also add another version of the -block–the **variant**: - -![Screenshot](../assets/experience-blocks-image7.png) - -## How to create a variant experience block - -Click **Settings** to show the block sidebar: - -![Screenshot](../assets/experience-blocks-image8.png) - -Click the Fallback block you’ve created. In the block sidebar, click the **Add a variant** button: - -![Screenshot](../assets/experience-blocks-image7.png) - -Now it’s time to choose which [audience](../personalising-content/audiences.md) is going to see this variant. - -### How to choose an audience for your variant block - -In the **block sidebar**, under **Variant 1** click **Select Audience**: - -![Screenshot](../assets/experience-blocks-image2.png) - -Either scroll down and click on an audience that you’ve already created. Or scroll up and click **Add New**: - -![Screenshot](../assets/experience-blocks-image9.png) - -Review the audience **groups** and **rules**. Check the audience is **active**. - -If you made any changes to the audience, click **Update** then **Select**. Otherwise just click **Select**: - -![Screenshot](../assets/experience-blocks-image6.png) - -For **each variant you create**, a tab will appear above the block. Click each tab to view the content for each block variant: - -![Screenshot](../assets/experience-blocks-image5.png) - -### How to copy or delete variants - -To **save time**, you can **copy** the chosen variant (a new variant tab automatically appears) : - -![Screenshot](../assets/experience-blocks-image4.png) - -To **remove a variant**, just click the variant’s tab and then click the **Trash** icon: - -![Screenshot](../assets/experience-blocks-image3.png) - -## How to create a conversion goal for your Experience Blocks - -First, choose how you’re going to measure the performance of your content blocks. Even if a content block performs badly, at least -you know not to use it again. Just like inventor Thomas Edison is supposed to have said, “**I haven’t failed, I’ve just found 10,000 -ways that won’t work**.” - -Click the block and the variant tab where you want to measure conversions. - -In the **block sidebar**, click the **dropdown** under **Choose a conversion goal**: - -![Screenshot](../assets/experience-blocks-image12.png) - -You’ll see three options: - -- **Impressions** - Choose this when you want to measure how many people **view** the experience block -- **Click on any link** - Choose this when you want to measure how many people **click** any link or an element that’s hyperlinked (you can also use this - for clickable buttons or images) -- **Submit a form** - Choose this when you want to measure how many form **completions** each block gets - -When you’ve made your choice, click **Publish**. Altis then **checks** that your Experience Blocks have valid conversion goals and -fallback content: - -![Screenshot](../assets/experience-blocks-image11.png) - -Altis will now start recording [insights](insights.md) so you can see which variant performs the best. diff --git a/user-docs/personalising-content/insights.md b/user-docs/personalising-content/insights.md deleted file mode 100644 index 0bcf0669..00000000 --- a/user-docs/personalising-content/insights.md +++ /dev/null @@ -1,75 +0,0 @@ ---- -order: 40 ---- - -# Insights - -Insights is where you see the **conversion results** of -your [experience blocks](../content-and-content-blocks/experience-blocks.md). You can either pop in for a quick overview of -progress. Or stick around and drill down for more detail. - -## How to view Insights - -Insights is waiting for you under the **Dashboard** (click Dashboard if Insights isn’t showing): - -![Screenshot](../assets/insights-image3.png) - -This shows a summary of your current Experience blocks. You have **set those up first**, haven’t you? Until that’s done there won’t -be much to see here. - -### Viewing a block summary - -When you arrive in **Insights** you can see a quick performance summary: - -![Screenshot](../assets/insights-image2.png) - -By default this shows: - -- Block name -- Number of views -- Conversion rate -- Author -- Date last modified -- First 20 blocks -- Past 7 days of data (click to view 30 or 90 days’ worth) - - ![Screenshot](../assets/insights-image4.png) - -To **change the default view**, click **Screen Options**: - -![Screenshot](../assets/insights-image5.png) - -### Viewing deeper block insights - -Of course, the summary only gives you, well… a summary of performance. To **dive deeper**, click on a block. You’ll see something -like this: - -![Screenshot](../assets/insights-image1.png) - -These three blocks show: - -- **Block views** - How many times the block has been viewed by unique visitors -- **Conversion rate** - Calculated by number of conversions divided by total unique views -- **Personalisation coverage** - Percentage of visitors who see the personalised blocks - -#### Block variants - -Scroll down and you’ll see a **performance breakdown** of each block variant. - -The example below shows the performance of a block with variants for: - -- French audiences -- Japanese audiences -- Fallback (for audiences that aren’t French or Japanese) - -![Screenshot](../assets/insights-image6.png) - -This gives you answers to questions like: - -- How many visitors viewed each variant? -- How many unique views did we get? -- How does the conversion rate for a variant compare to the fallback? -- What percentage are coming from our specified audiences? diff --git a/user-docs/personalising-content/personalised-content.md b/user-docs/personalising-content/personalised-content.md deleted file mode 100644 index ca784a43..00000000 --- a/user-docs/personalising-content/personalised-content.md +++ /dev/null @@ -1,99 +0,0 @@ ---- -order: 20 ---- - -# Personalised content - -Here’s how to wow your website visitors. Serve up **content that is automatically personalised** based on who they are. * -*Personalise messaging** for first-time visitors, different regions, people clicking specific ads—it’s up to you. - -You just have to define the [audiences](audiences.md). And then create content for each audience. Then your website will know what -to display, to which users, and when. - -## How to add personalised content - -Imagine you are running events in: - -- Paris, France -- Manchester, UK -- New York, US - -You want to show content personalised to those regions. Click -to [add a block](../content-and-content-blocks/creating-content-with-blocks.md) and choose **Personalised Content**: - -![Screenshot](../assets/personalised-content-image9.png) - -The default block that appears is your **Fallback**. - -This is for content for **audiences who aren’t** from your target regions. So you could put something **generic**, such as referring -to “international events”, rather than mentioning specific countries: - -![Screenshot](../assets/personalised-content-image6.png) - -Now it’s time to create **Variant blocks**. These will contain content personalised to your three target regions. - -Click Copy: - -![Screenshot](../assets/personalised-content-image11.png) - -A Variant 1 tab now appears: - -![Screenshot](../assets/personalised-content-image12.png) - -### Choosing the audience - -Let’s say this variant is for [audiences](audiences.md) in Paris, France. - -Click **Select Audience** in the sidebar: - -![Screenshot](../assets/personalised-content-image10.png) - -You can now choose the audience. Either click the audience if it already exists. Or click the Add New button and create an audience -by following the process explained in the [Audiences article](audiences.md): - -![Screenshot](../assets/personalised-content-image2.png) - -The personalised block now displays the Audience name. Add the content for the France audience: - -![Screenshot](../assets/personalised-content-image4.png) - -Now copy the Variant again. Repeat the process, this time choosing an audience in the UK. - -Then repeat the process for New York, choosing an audience based in the US. - -Prefer to create a **personalised variant from scratch**? Just click the **+** next to **Fallback**: - -![Screenshot](../assets/personalised-content-image7.png) - -### Choosing a conversion goal - -You can also attach a conversion goal to each personalised content variant. You can then track each variant’s performance. The -results can be found in [Insights](insights.md). - -After defining your audience, click the **dropdown** under **Choose a conversion goal**: - -![Screenshot](../assets/personalised-content-image1.png) - -Click to decide how to **measure** the variant’s **performance**: - -- **Impressions** -- Click on any **link** -- Submit a **form** - -Altis will let you know if the content doesn’t have a link or form: - -![Screenshot](../assets/personalised-content-image5.png) - -### Previewing personalised content - -Depending on your [role and permissions](../collaboration-and-users/roles-and-permissions.md), you can preview the content for each -audience. Choose which variant to preview and then click **Preview**: - -![Screenshot](../assets/personalised-content-image8.png) - -While viewing the preview, hover over **Audience Preview**. You can now click to preview the page for your audiences: - -![Screenshot](../assets/personalised-content-image3.png) - -When you’re happy with how everything looks, click **Publish**. Your website is now **automatically** serving up personalised web -experiences.