Many configuration options available to deploy your campaigns and trigger your surveys at the right time!
Thanks to the many available configuration options, you can deploy your campaigns on your website to trigger your surveys at the right time and increase your response rate!
It is even possible to customize the appearance format of your survey (color, text, size, shape...).
Glossary of web deployments
A web deployment is a channel that allows integrating a survey into a website. It can be displayed in various forms: button, bar, pop-under, pop-in and in-page (learn more about creating a web deployment).
An iFrame deployment (Inline Frame) is a URL deployment manually embedded in a website using an HTML "<iframe>" element without interfering with the host page's code. The loading and interactions are managed by the iframe itself. Skeepers does not support technical issues that may arise in this configuration because the integration is not managed by the platform.
A trigger condition is a specific criterion that must be met to trigger an event. In this context, the event corresponds to the survey's display on a website. A condition can be based on a date, platform, specific value, or an event previously configured in the deployment.
A solicitation refers to the display of a survey integrated into a website (pop-in, button, bar or pop-under).
An exit intent is a trigger condition for a web deployment that detects when the visitor moves their mouse toward the browser tab area, which is interpreted as an indication that they are about to leave the page or close the tab.
A domain is a unique address used to identify a website. It is an integral part of a URL and consists of two parts: the domain name and the domain extension - ".com", ".fr", etc. - (learn more about domains).
A URL path refers to the part of the URL located after the domain name that indicates the location of a specific page within a site, based on its hierarchical structure. It excludes the parameters and anchors that follow it.
A deployment tag is a script (JavaScript) that needs to be implanted in a website or a tag manager to display an online survey. When the tag is embedded and activated, it ensures that trigger conditions are met, collects data, and loads the survey on the page (learn more about integrating a deployment tag).
A SPA (Single Page Application) is a type of website where the content of a web page is dynamically updated without a complete reload of the page. Unlike traditional pages (Multi-Page Application or MPA), where a simple reload would trigger the script, a SPA requires more advanced event management to ensure that the survey displays correctly when the conditions are met.
The Console is a tool integrated into web browsers that allows executing commands to test scripts, verify data collection and display errors.
A command is an instruction entered into the Console to interact in real-time with the displayed web page. It allows executing various actions, such as verifying JavaScript code, inspecting page elements, or debugging the script.
CSS (Cascading Style Sheets) is a programming language used on the platform to customize the visual display of a survey or web deployment (color, font, alignment, size, etc.). While HTML handles the structure of a web page, CSS controls its visual aesthetic. However, conflicts can arise when the applied CSS rules contradict or overlap with the website's HTML structure, leading to unexpected behavior in the display of page elements (learn more about advanced CSS customization).
The DOM (Document Object Model) is an interface that structures the HTML content of a web page hierarchically, where each element (tags, text, etc.) is identified. Thanks to this structure, the deployment tag can dynamically manipulate the content of the page in real-time, without reloading the page, in order to directly integrate the survey.
The Content Security Policy (CSP) is a security measure that limits the resources that can be loaded on a web page (scripts, images, styles, etc.). It specifies the allowed content sources (internal and external). If an unauthorized source is detected, the browser automatically blocks its loading (learn more about CSP).
Creating the deployment
- In the side menu, click on "Deployments". Then, you’ll find all your previous Deployments here.
- To create a new one, click the green "Create a new deployment" button at the top right of your page.
- Choose between standard and conversational deployment.
- Select the "Website" deployment type as well as the campaign to deploy.
- Associate it with a campaign.
- Give it a name.
- Finally, click Save.
Triggering your deployment
You can now define the different trigger conditions for your deployment.
The structure of triggers always consists of two parts: " If" and "Then"
Add conditions: "IF"
To add one or more conditions (or sub-conditions) and configure their connections:
Available connections between conditions are:
And: all conditions must be met for the trigger to execute.
Or: if one of the conditions is met, the trigger will execute.
Click "Add a new condition".
The available conditions will appear.
The possible conditions are:
The Attribute condition allows you to define triggering rules for your survey, based on the value of an attribute present in your website's data layer.
You can choose the attribute on which to base the deployment and the triggering condition (“equal to”, “different from”, “does not contain”...).
Deploy to visitors whose birthdate is later than May 15, 2019.
By using the Attribute condition rather than Website variable, you benefit from advanced targeting features for date, time, and numeric formats.
Usage examples:
-
Deploy a survey to customers over 18 years old
-
Trigger a short survey if the cart amount is zero after 10 minutes of browsing, with a promotional offer as an incentive
Two draw modes are available:
-
Visit-based draw: The draw is performed only once for the same visitor session.
-
Page-based draw: The draw is performed each time the visitor views a page.
You can express the draw probability in volume or percentage. A probability expressed as "50%" is equivalent to "1 out of 2".
Deploy to 1 out of every 2 visitors browsing my site.
Deploy 1 out of every 2 page views.
Define a period during or outside of which you want to deploy your campaign.
The period can be defined in two modes:
-
Date mode: Deploy during or outside a period defined by a start and end date.
-
Time mode: Deploy during or outside a timeslot defined by a start and end time.
Two modes are available:
-
"URL" mode: restricts deployment to traffic from a specific third-party page.
Note: the entire URL of the referring page is analyzed, including the protocol, domain, path, and parameters. Anchors are not analyzed. -
"Domain" mode: restricts deployment to traffic from any page of a specific third-party website. In this mode, only the domain name of the referring page is analyzed: http://subdomain.mydomain.extension/path?param
The available comparison operators for this condition allow you to create more complex rules. For example, by using the "contains" operator, you can restrict traffic coming from a specific path of a website.
Deploy to all visitors coming from the skeepers.com site.
Deploy to all visitors coming from the French resource pages of the skeepers.io site.
Restrict deployment to visitors who have spent a minimum amount of time on your website or on the current page.
You can express the time spent in seconds or minutes.
Deploy after 10 seconds spent on a page of my website.
Deploy to visitors who have spent more than one minute on my website.
Limit deployment based on past solicitation of your visitors.
Target visitors who have already been solicited or who have never been solicited by a campaign or deployment in the past number of days.
Deploy to visitors who have never been solicited by the deployment named "test" in the last 30 days.
Deploy to visitors who are browsing a specific page.
Specify the URL path of the page where you want to deploy.
Note that only the path of the URL is analyzed:
http://subdomain.mydomain.extension/path?param
The protocol, domain, parameters, and anchors are ignored. You can use the available comparison operators to define complex rules. For example, by using the “contains” operator, you can target all pages in a subdirectory of your website.
Note
If you use "/" at the end of the URL, but it does not exist in the original URL, then for a deployment using the “contains” operator, Skeepers will not find the correct path, and your survey will not be displayed.
We recommend not using "/" at the end of the URL, except in the specific case where the “equals” operator is used.
For example, in the following case, the Skeepers site
does not use a "/" at the end of the URL path. If I want
to create a deployment on this page, and I enter the
URL as: fr/resources-center/, the survey
will not be displayed.
You can note that there is no "/" at the end of the URL in the screenshot below.
Deploy to visitors currently on the “features” page of my website.
Deploy to visitors browsing any page of my website that is not a French blog page.
Deploy to visitors after a web event on an element of your site.
An event is an action a visitor performs on a specific element on a page of your website (click, focus, or hover). It should not be confused with a browser event, which refers to browser functionality (load, scroll, exit intent, or inactivity).
Select the expected event type and the element(s) on your website where it must occur for the deployment to trigger.
Use CSS 3 selector expressions to designate the elements on your website: CSS 3 Selector
5 events are available:
-
Click: This event is sent when the mouse button is pressed and released on an element.
-
Hover: This event is sent when the mouse is moved over the element.
-
Mouse out: This event is sent when the mouse is moved out of the element.
-
Focus: This event is sent on an element when it receives focus.
-
Focus out: This event is sent on an element when it loses focus.
The focus event is sent to an element when it is selected. This event applies to a limited set of elements, such as form elements.
Display to visitors who hover their mouse over the element on my website with the HTML ID "footer".
Display to visitors after a browser event.
A browser event is an action performed by a visitor or a specific state in their browser window (loading, scrolling, exit intent, or inactivity). It should not be confused with an element event, which corresponds to an action on a specific element of a web page (click, focus, or hover).
4 events are available:
-
Page load: Display when the current page loads.
-
Scroll: Display when the visitor scrolls to the middle of the current page.
-
Exit intent: Display when the visitor moves their mouse from a site element toward the tab bar.
-
Inactivity: Display when the visitor has been inactive for a certain amount of time. You can define inactivity duration in seconds or minutes.
Display to visitors who scroll to the middle of the current page.
Display to visitors who move their mouse outside of my website (exit intent).
Target the deployment based on variables from your website.
Use the variables passed via the Skeepers Javascript tag,
installed on your website, to display only to certain visitors
(learn more:
trigger tag).
Please note: only variables defined in the tag are
analyzed.
Display to visitors whose "id_client" variable equals "premium" and whose "order_amount" variable equals 100.
Once your triggering conditions are set, you can now define the action to apply.
Action configuration: "THEN"
Select the action by clicking on "Add a new action".
The appearance types of your survey will be displayed.
The available actions are:
Opens a window containing the Campaign in your current browser window.
A button on the left side that opens your Campaign when clicked.
A button on the right side that opens your Campaign when clicked.
A bar at the top that includes a button to open your Campaign.
A bar at the bottom that includes a button to open your Campaign.
First opens a popin inviting your visitors to answer your survey at the end of their navigation. When the time comes, visitors who agreed to respond will see a new window open with your Campaign.
A button at the bottom that opens your Campaign when clicked.
This is a new popin format, ideal for engaging visitors before the survey starts. It allows you to create a prompt that fits your graphic charter perfectly (you can customize font colors, buttons, titles, and background image).
Here is an example of a custom popin ready to be deployed:
Once you’ve made your selection, don’t forget to save your scenarios by clicking before navigating away.
Please note:
InPage deployments using the Pop under format are strongly discouraged on mobile and tablet platforms. This format works well on desktop, but is not suitable for other devices.
On mobile and tablet, the respondent needs to close their browsing tab for the survey to be displayed. However, this is rarely done, which can lead to a very low response rate.
Likewise, triggering conditions based on exit intent are not compatible with display on mobile.