Getting started with Contextual's Digital Adoption platform (DAP) for Web apps.¶
This article will go through the basics of the Contextual's DAP and teach you the basics of how to create content and deliver it to your employees or your customers using the Contextual browser extension.
If you haven't already, you will need to download the Contextual browser extension. The extension can be used on either Google Chrome browser (recommended) or Microsoft Edge. Download here
You will also need an account with Contextual. If you don't have one you can create one using the extension or by going here
What this article will cover¶
- Contextual Digital Adoption Platform explained
- The basics of how to create content
- Key features of the tool
Contextual's DAP explained¶
Contextual's DAP has two different modes that are available, Contextual for Teams and Enterprises and Contextual for Product Teams (Contextual classic). The differences between the two modes are explained below.
Contextual for Teams and Enterprises¶
Contextual for Teams has been designed to streamline the process of onboarding and educating your internal Teams on the software they have to use for their work. Teams doesn’t require any integration or code to set up, it sits as an educational layer over any software that staff members use in a browser.
Contextual for Product Teams¶
The main difference between Teams and classic Contextual is that classic Contextual will need to be integrated into your Web app to deliver content. This means that your end-users do not need to download the browser extension to see the content that you create using the Contextual.
The basics of how to create content¶
Creating your first Guide¶
1. Go to the URL where you would like to create a Guide then click on the chrome extension in your browser.¶
The chrome extension is located on the top right corner of your browser.
2. Click on ”New Guide”¶
New Guide button is located bottom right (img below)
3. Choose the use-case you would like¶
For this example, we will go through selecting a contextual tip as the use-case.
4. Choose a template for the design.¶
This step is completely up to personal taste and the utility you require from the tip. i.e If you want an image and or buttons.
For this example we will use a simple tip with no buttons.
5. Place the tip on the screen¶
Once you have selected a design, you will then need to make sure that the extension is in "design mode" (more info lower in doc here), then mouse around your website to place the tip. You should see blue boxes appear around on-screen elements, any element that has a box around it can be selected as the target for the tip.
Please note that if you already have a tip design you want to copy then when in design mode you can click on the apply from others button at the top of the design menu.
6. Edit the tip¶
This part is completely up to you, but one trick here is that if you click on the part of the tip/popup that you want to edit i.e the content, then the correct section on the side menu will open so that you can edit the content.
7. Click on Done¶
Once you have finished designing your content you will need to make sure that you click done to save the design. Done is located bottom right
Once you have created your design you can preview how it will look to your end-user. If you have created more than one step you will be able to also preview how the whole flow will look.
9. Name the Guide and "save and exit"¶
The last step is to go to "step 4 settings", give your Guide a title and then click on "save and exit" (bottom right)
Key features of the tool¶
Below are some of the key features of the digital adoption tool in a bit more detail
Teams mode allows you to share Guides with your Team without any coding required.
How it works¶
Once you have created the Guides you want to share with your Team you will then need to invite them to download the chrome extension. There are two options here:
Invite to edit - When you invite a Team member to edit, Contextual will send this user an email which will prompt them to download the chrome extension (if they don't have it). The person will then get taken to where you created the Guides and will automatically be able to view to Guides that have been enabled. When you invite to edit, this person will also be added to your account where you have created the Guides, they will then be able to create an account with Contextual and open the extension in creator mode and see all the Guides you have created and have the rights to edit and create more Guides.
Invite to view - The difference with an invite to view is that the user will only be able to view the Guides you have created, they will not have access to the account where the Guides were made. This mode is ideal for staff members that you want to educate and onboard.
An end-user can be invited to view more than one app's s if the user already has the extension installed and an invite is sent then the new app will get added to their list and they will be able to view those Guides also
If you do not want to have this mode enabled you can disable it by right-clicking on the chrome extension and choosing disable Teams mode.
This section will go through how the navigate/design toggle works and a couple of tricks on how to use it.
How it works¶
Design - This is the default mode when after you first pick a design, in this mode the tip or pop up you are designing will be visible on the screen. If you are designing a tip then you will be able to mouse around and place the tip.
Navigate - When this option is chosen, it will allow you to navigate to different pages within your site. You can navigate to different pages by clicking on links on the page. Once the new page and the creator load you can either navigate again or click on the Design button to see your design again.
Once you have clicked done on your design for that page then the creator will save the current URL for that step.
Tricks and Tips¶
If you are creating content across multiple pages, Contextual will automatically link the steps across the different URL's. Watch out for dynamic Url's though as Contextual will try to take the user to that exact URL. More on dynamic URLs here
If you want to change which URL some PZ content is on then you will first need to open the step that you want to move (PZ will take you to the page where it is currently saved, then all you need to do is click on Navigate, then go to the new page, click on design, place the tip (if a tip) on a new target element and then click on done to save the URL for that step
This section will go through a couple of the important settings from the side menu.
Overlay is where you will find the design options that control the background dim level and colour, you will also find the feature called coachmarks that will allow you to highlight the element that tips point at. More info here
If the URL you are trying to build content on has some sort of dynamic element, such as an account id or project number i.e yourapp.com/projects/randomprojectd . Then you will need to make sure that you the advanced URL settings. More info here
Changing the order of the steps¶
When you have created a Guide with more than one step and you would like to re-order the steps, all you need to do is drag and drop the steps into the correct spot and then save the changes.
Hotspots and Launchers¶
This is where you get to decide how you want to trigger the Guides that you want to show your users. More info here
Page open - This is the default launcher, this means that when the user opens the url that you have specified for the Guide.
Button This allows you to put tooltips all over a Web app that users can then click on to get help when they need it. You will need to select an element on screen for the button to attach to (similar to a contextual tip)
Click - To make an existing screen element (like a text label or button) clickable. The usage is quite similar to a button launcher, you need to attach it to an on-screen element and when a user clicks on the element the content you have created will be displayed. You will see a red box box around the selected element, this will not be visisble to the end users.
Hover - Similar to a click launcher but when a user mouse overs the selected section it will trigger the Guide to show.
On-demand - Gives you the power to launch the Guide using code inside your app. Gives you the freedom to time it and repeat it however you like.
The audience section is where you can choose what segment of your users you want to see the guide you have created. Below is a few important things to know about the audience section
Operating System is a mandatory filter.
When you ad multiple filters they get applied as an and. For example, if user is a web user and a new user who started using the product less than 14 days ago then they show them this guide (example image below).
You can see the number of possible users who will see the guide by clicking on the refresh button.
Once you have created an Guide and chosen the audience and launcher the last step is to check that the settings are all correct for the Guide.
Below are a couple of the more complex settings explained.
You have two options here
Show until the user completes - This will show the Guide only once to the user.
Repeat forever - This setting will mean that the Guide will keep getting shown forever. This is good when you want a tooltip (button launcher) that is always available.
This allows you to select what domain and subdomain the Guide will be shown on.
If you choose yourapp.com, it will only show on yourapp.com
You can also specify a specific subdomain, such as staging.yourapp.com or dashboard.yourapp.com. This is useful for only showing the Guide to your staging environment for testing.
If you choose *.yourapp.com, it will match all subdomains, for example, prod.yourapp.com and staging.yourapp.com.
If you choose *yourapp.com, it will match all domains contains yourapp.com, for example, hello-yourapp.com, yourapp.com, prod.yourapp.com, and staging.yourapp.com.