AB Tasty FAQs
AB Tasty's Frequently Asked Questions page is a central hub where its customers can always go to with their most common questions. These are the 151 most popular questions AB Tasty receives.
Frequently Asked Questions About AB Tasty
AB Tasty offers a very simple and detailed report interface, but you may prefer to read your test results directly in the web analytics tool you are used to, and where you have already defined your objectives.
For this, just link your test to... Google Analytics, AT Internet or SyteCatalyst. Go to the editor, at the 3rd party integration step, and select your tool.
Then all you have left to do is choose a variable that will categorize and segment the data in your tool (customized variable for Google Analytics, Wave for AT Internet).
When you start the test, the data will automatically be entered into your reports. In the case of Google Analytics, you will have to go into the report "Audience > Custom > Custom Variables" and select custome variable that you chose previously.
Your tests linked to Google Analytics will appear in the main table. Select one of them to see the detail of results by variation. You can configure this report as you wish to emphasize the key indicators.
Note: if you are exclusively using your web analytics tool to track your test results, you will have to calculate an indicator yourself to measure the statistical reliability of the differences between your variations.
View ArticleIn this example, we will go through the steps involved in creating a widget to indicate the number times a blog post was viewed:
Social Proof widget
This modal features the following elements:
a personalized message;
a personalized background color;
a personalized border.
Accessing the Social Proof widget
Open the variation editor on the desired website.
Click Widgets in the toolbar on the right-hand side.
Enter Social Proof in the search field.
Click the Social Proof card:The configuration form is displayed along with a modal featuring a message.
You can now start configuring your modal. The Layout tab is displayed by default.
Layout tab
In the Layout tab, go to the Sticky to the page, category and click Left:the modal is displayed to the left of the page.
Click the Content tab.
Content tab
In the Type of content to display category, select Number of views.
Select In the last 24 hours.
Click in the Message field:a formatting toolbar appears.
Enter This post was viewed !views! times in the last !period! hours
Click the Style tab.
Style tab
Text
In the Text alignment category, click Center.
Border and background
Set the Border Thickness to 0 px.
Set the Border Radius to 10 px.
Click Border color and select a color from the palette or enter its hexadecimal value in the Hex field.
Click Background color and select a color from the palette or enter its hexadecimal value in the Hex field.
Set the Overlay opacity to 0 %.
Margins and spacing
Set all Margins to 0 px.
Set the Padding to 0 px.
Shadow
Enable the Drop shadow.
Set the Shadow opacity to 40 %.
Click the Conditions tab.
Conditions tab
In Dynamic content, leave the Always value.
In the drop-down list, set the Dismiss content option to Never hide it.
Click Save.
Related articles
View ArticleThe Social Proof widget enables you to display a message for your visitors, specifying the number of views or purchases for a specific product or page within a preset time period.
Example: creating a Social Proof widget
Social Proof is a social psychology principle that describes the fact that individuals are highly influenced by the behaviors and opinions of others.
Social Proof is part of the Nudge theory, which stipulates that indirect suggestions are likely to influence the decisions and behaviors of individuals more efficiently than legislation is.
The Social Proof widget enables people who visit your website to know exactly how many people have seen or purchased an article, thereby impacting their behavior.
In the case of a newspaper article, the more views it has, the more people will be tempted to read it because it has already sparked the interest of others.
In the case of a commercial product, a large number of views may convince people that the product is popular and therefore make them want to purchase it.
A large number of purchases is likely to accelerate the purchase decision of hesitant users, who fear the item will soon be out of stock. They will also view the large number of purchases as proof of the articles high quality.
A low number of views or purchases, on the other hand, is likely to put the visitor off buying.
That is why it makes more sense to use this widget on product pages and articles that are trending, to increase the snowball effect. The message you will configure is also very important, since it can impact the visitors behavior even more.
The Social Proof widget belongs to the Dynamic content category, which is a chargeable option. To benefit from this widget, please contact your KAM.
Accessing the widget
Open the variation editor on the desired website.
Click Widgets in the toolbar on the right-hand side.
Browse to the Dynamic contentsection or filter on the widgets name.
Click the widgets card:The configuration form is displayed and the animation starts.
Configuring the widget
During this configuration step, changes are displayed in real-time.Once your changes have been applied:
Click Save to save your changes,
If necessary, you can click History in the toolbar to edit and make changes to your configuration.
List of options of the Social Proof widget
The first time you access the widget, red dots are displayed on the tabs to indicate that new options are available.
Layout tab
Options
Use
Sticky to the page
Left
Place the widget to the left of the page
Right
Place the widget to the right of the page
Bottom
Place the widget at the bottom of the page
Top
Place the widget at the top of the page
Sticky to an element
Select an element
Select the page element the widget will be stuck to
Below
Place the widget below the selected element
Before
Place the widget before the selected element
To the left
Place the widget to the left of the selected element
To the right
Place the widget to the right of the selected element
Content tab
Options
Use
Type of content to display
Number
Select the Type of content to display.
Number of purchases
Number of views
Within
Select the time span to be displayed.
In the last 3 hours
In the last 12 hours
In the last 24 hours
In the last 3 days
In the last 7 days
Message personalization
Text
Make changes to the message text.Click in the field to display the toolbar and format the text.
Toolbar
Format the text message
Font color
Bold or italic
Paragraph format
Numbered list or bullet list
Enter text and content in HTML format
Add a hypertext link
Insert an image
Display the number of purchases
The number of product views is collected automatically thanks to AB Tastys data collection system (Universal Collect).
To recover the number of purchases however, AB Tasty needs to collect information about the product, which is stored in your websites datalayer. The transaction tag has to be implemented on your website.
To do this:
Copy the following code below.> If the transaction tag is already implemented :
if (productPageCondition) { // set your product page conditions const productKeyInterval = setInterval(function () { if (datalayerConditions) { // set your product page datalayer conditions clearInterval(productKeyInterval); window.ABTastyProductKey = yourItemCodeSKU; // set your product item code (SKU), it must be the same as the "item" ic value below! } }, 1000);}if (checkoutPageCondition) { // set your checkout page conditions const sendItemInterval = setInterval(function () { if (datalayerConditions) { // set your checkout page datalayer conditions clearInterval(sendItemInterval); for (let i = 0; i < productsInsideTheTransaction.length; i++) { // set the datalayer array of products inside the the transaction window.abtasty.send("item", { tid: datalayer.transactionID, // value example: "OD564" in: datalayer.productsInsideTheTransaction[i].itemName, // value example: "Shoe" ip: datalayer.productsInsideTheTransaction[i].itemPrice, // value example: 3.5 iq: datalayer.productsInsideTheTransaction[i].itemQuantity, // value example: 4 ic: datalayer.productsInsideTheTransaction[i].itemCodeSKU, // value example: "SKU47" iv: datalayer.productsInsideTheTransaction[i].itemCategory // value example: "Blue" }); } } }, 1000);}
> If the transaction tag is not implemented yet :
if (productPageCondition) { // set your product page conditions const productKeyInterval = setInterval(function () { if (datalayerConditions) { // set your product page datalayer conditions clearInterval(productKeyInterval); window.ABTastyProductKey = yourItemCodeSKU; // set your product item code (SKU), it must be the same as the "item" ic value below! } }, 1000);}if (checkoutPageCondition) { // set your checkout page conditions const sendItemInterval = setInterval(function () { if (datalayerConditions) { // set your checkout page datalayer conditions clearInterval(sendItemInterval); window.abtasty.send("transaction", { tid: datalayer.transactionID, // value example: "OD564" ta: datalayer.transactionAffiliation, // value example: "Member" tr: datalayer.transactionRevenue, // value example: 15.47 ts: datalayer.transactionShipping, // value example: 3.5 tt: datalayer.transactionTax, // value example: 2.60 tc: datalayer.transactionCurrency, // value example: "EUR" tcc: datalayer.transactionCouponCode, // value example: "Coupon" pm: datalayer.transactionPaymentMethod, // value example: "Paypal" sm: datalayer.transactionShippingMethod, // value example: "Fedex" icn: datalayer.numberOfItems // value example: 12 }); for (let i = 0; i < productsInsideTheTransaction.length; i++) { // set the datalayer array of products inside the the transaction window.abtasty.send("item", { tid: datalayer.transactionID, // value example: "OD564" in: datalayer.productsInsideTheTransaction[i].itemName, // value example: "Shoe" ip: datalayer.productsInsideTheTransaction[i].itemPrice, // value example: 3.5 iq: datalayer.productsInsideTheTransaction[i].itemQuantity, // value example: 4 ic: datalayer.productsInsideTheTransaction[i].itemCodeSKU, // value example: "SKU47" iv: datalayer.productsInsideTheTransaction[i].itemCategory // value example: "Blue" }); } } }, 1000);}
From the dashboard, click Settings.
Click Global code.
Paste the code in the dedicated field and adapt it to suit your conditions and your datalayer.
A datalayer is necessary to display the number of purchases. Without one, the information or values may not be recovered.
Style tab
Options
Use
Text alignment
Left
Align the text to the left
Center
Center the text
Right
Align the text to the right
Border
Border thickness
Add a border to the modal and configure its thickness in pixels
Border radius
Configure the border radius of the modal in pixels
Border color
Add a border to the modal and configure its color: use the palette to configure the hexadecimal value and opacity
Background
Background color
Select a background color for the modal
Overlay opacity
Darken or lighten the visual used for the modal background
Margin
Margin top px
Define the space of the margin applied above the element
Margin bottom px
Define the space of the margin applied below the element
Margin left px
Define the space of the margin applied to the left of the element
Margin right px
Define the space of the margin applied to the right of the element
Padding
Padding
Define the space between the border and the text, on all four sides
Shadow
Drop shadow
Add a shadow around the widget
Shadow opacity
Configure the size of the drop shadow
Conditions tab
Options
Use
Recurrence
Enter the minimum number of page views or product purchases required for the widget to be displayed. Always means you want to display the widget even if there are no conversions.
Hide content
Choose when content should be faded out.
Never
Hide content after 5 seconds
Hide content after 6 seconds
Hide content after 7 seconds
Hide content after 8 seconds
Hide content after 9 seconds
Hide content after 10 seconds
Related articles
View ArticleThe Christmas Hat widget enables you to place a Christmas hat on an element of the web page.
Select parent or Select children
Accessing the widget
Open the variation editor on the desired website,
Click Widgets in the toolbar on the right-hand side,
Browse to the Specialsection or filter on the widgets name,
Click the widgets card,The configuration form is displayed.
Configuring the widget
During this configuration step, changes are displayed in real-time.
Once your changes have been applied:
Click Save to save your changes,
If necessary, you can click History in the toolbar to edit and make changes to your configuration.
Content tab
Click Select element,
In the web page, select the element that will host the hat,A contextual menu is displayed.
Click Select this element,(if necessary, use the option to select the right element),The code that matches the selected element is displayed in the configuration form and the animation starts.
Style tab
Select the Position option to hang the hat on the left or the right-hand side of the element,
Use the + and - button to make the hat larger or smaller
Use the + and - buttons to move the hat vertically or horizontally in relation to the host element.
Click Save to save your changes,
If necessary, you can click History in the toolbar to edit and make changes to your configuration.
View ArticleThe Countdown widget enables you to display a countdown of the remaining days, hours, minutes and seconds until the date and time you will have configured.
Select parent or Select children
Accessing the widget
Open the variation editor on the desired website,
Click Widgets in the toolbar on the right-hand side,
Browse to the Promotional Contentsection or filter on the widgets name,
Click the widgets card,The configuration form is displayed and the animation starts.
Configuring the widget
During this configuration step, changes are displayed in real-time.
Once your changes have been applied:
Click Save to save your changes,
If necessary, you can click History in the toolbar to edit and make changes to your configuration.
Content tab
Click Select element,
In the web page, select the element that will host the countdown,A contextual menu is displayed.
Click Select this element,(if necessary, use the option to select the right element),The code that matches the selected element is displayed in the configuration form and the animation starts.
Click in the end date field and use the calendar to select the date on which the countdown will end.
Apply the same process for the end time,
Click Save to save your changes,
If necessary, you can click History in the toolbar to edit and make changes to your configuration.
View ArticleThe Session recording functionality enables you to save your visitors actions on your website in video format. This helps you understand their behavior on your website and identify users sticking points and browsing issues based on real-life situations.
The Session recording functionality is compliant with your users data confidentiality and also enables you to select the HTML elements you want to blur out on the page in the case of a recording.
Applying tags to your videos
This functionality is subject to licensing and depends on your traffic volume. To benefit from it, please contact your sales manager.
To record and view your visitors sessions, apply the following steps:
Implementing the generic tag on the pages of your website.
Creating a recording.
Starting the recording.
Accessing the videos.
Viewing your visitors sessions.
Prerequisites to using session recording
In order for session recording to work, you need to implement the tag on all the pages of your website.
For more information, please refer to the How do I install AB Tasty on my site? article
Once the option is enabled, you will be allocated a daily quota of videos depending on your contract.
Confidentiality of user data
We do not actually film the visitors session: Session recording reenacts the mouse movements of visitors who browse your website.
Moreover, completion of confidential fields is blurred out by default.
You can also specify additional elements to be hidden. This guarantees that theywon'tbe recorded.
For more information, refer to Hiding elements during recording.
Creating a recording
When creating a recording, specify the URL of the page(s) for which you want to record visitor behavior. Each recording includes several videos featuring the users various visits to the pages of your website.
Log in to AB Tasty at: https://app.abtasty.com/login.
Go to the dashboard and click Insights > Session recording.
If this is your first time using Session recording, thedefault Recording name field will beblank. You need to fill it in to configure your firstrecording.
Enter the label you want to assign to this recording in the Recording name field.
Click Add.
Specify the pages for which you want to apply session recording:Insert the URL of the website and, where applicable, specify the shared structure of the various URLs using the Corresponds exactly, URL ignoring parameters, Contains and Regular expression operators (see Defining target pages )
Click Save.
To create additional recordings, click Add a new recording and repeat steps 3 to 6.
You are now ready to create videos of your pages.
For more information, refer to Starting a recording.
You can create as many videos as your quota allows.
If you want to hide certain elements to make sure theydon'tappear on the video, you can do so manually; even though visitor confidentiality is protected by default.
For more information, refer to Hiding elements during recording.
Hiding elements during recording
Before you start recording visits to your website, you can blur specific information by adding the(data attribute)
data-ab_disable_record
data attribute to a given HTML element.
There are three ways of doing this:
In the source code of your website,
Via the WYSIWYG editor,
In the global code of your account.
Modifying the source code
Access the source code of your websites pages.
Add the
data-ab_disable_record=true
attribute to each element you want to blur.
For example, on an online banking website, when your clients are logged in, their name and their balance appear at the top of the page. The code is similar to the following example:
To blur the clients name and balance in the video, add the attribute to each HTML element. The code will be similar to the following example:
Using the variation editor
You can use the variation editor to create a personalization and add the
data-ab_disable_record
attribute to the elements you want to hide.
To do this, apply the following steps:
Go to the personalization dashboard.
Click Create >Personalization.
On the Main information page, specify your websites URL.
Click Save: Your website is displayed and the variation editor opens.
Select the element of the web page you want to hide.
In the menu which appears, click Edit > Edit attributes.
In the Attribute name field, enter
data-ab_disable_record
In the Attribute value field, enter true.
Click Save.
Go to the 2 - Targeting step of your personalization.
Configure all the pages that feature the element you want to hide, then click Save this step.
Start your personalization.
Configuring the global code
You can add the attribute via the Global code functionality of your account.
To do this,
Click, then click Settings>Global Code.
Define the targeted pages for which elements need to be hidden.
Add the attribute in JavaScript or jQuery.Example of code designed to hide h1 and h2 title elements:
Click Save.
Start a recording
As soon as you click Start recording, all user visits to your website are recorded. The duration of each video coincides with the amount of time the visitor spent on the website.
Deleting a recording
To delete a session recording and all the videos it contains, click Delete recording and confirm deletion.
Accessing the videos
For more information, refer to Viewing a session recording.
Related articles
Viewing a session recording
Using the session recording dashboard
View ArticleThe Olark chat widget enables you to display the Olark chat window ( https://www.olark.com/ ) on your website in order to encourage conversations with people who visit your website and to collect their feedback.
An Olark account and ID are required in order to use this widget. These will not be provided by AB Tasty.
Accessing the widget
Open the variation editor on the desired website,
Click Widgets in the toolbar on the right-hand side,
Browse to the Integrationssection or filter on the widgets name,
Click the widgets card,The configuration form is displayed.
Configuring the widget
Once your changes have been applied:
Click Save to save your changes,
If necessary, you can click History in the toolbar to edit and make changes to your configuration.
Content tab
Enter your Olark ID in the relevant field.The chat widget is displayed in your test variation or your personalization.
View ArticleThe Zendesk chat widget enables you to display the Olark chat window ( https://www.zendesk.com/chat/ ) on your website in order to encourage conversations with people who visit your website and to collect their feedback.
A Zendesk chat account and ID are required in order to use this widget. These will not be provided by AB Tasty.
Accessing the widget
Open the variation editor on the desired website,
Click Widgets in the toolbar on the right-hand side,
Browse to the Integrationssection or filter on the widgets name,
Click the widgets card,The configuration form is displayed.
Configuring the widget
Once your changes have been applied:
Click Save to save your changes,
If necessary, you can click History in the toolbar to edit and make changes to your configuration.
Content tab
Enter your Zendesk chat account number in the relevant field.The chat widget is displayed in your test variation or your personalization.
View ArticleIn this example, we will detail the steps required to create the following NPS:
NPS (Net Promoter Score) widget
This widget features the following elements:
an NPS question,
a rating scale from 0 to 10,
an open-ended question,
a send button,
a thank you message.
Accessing the NPS widget
Open the variation editor on the desired website,
Click Nudge in the toolbar on the right-hand side,
Enter NPS in the search field,
Click the NPS card:the configuration form is displayed.
You can now start configuring your widget. The Layout tab is displayed by default.
Layout tab
In the Layout tab, click Modal.
Choose to place the content Above.
Click the Content tab.
Content tab
In the Question field, keep the default text displayed on the widget, above the rating scale: How likely are you to recommend us to a friend or family member?
Check the Ask an open-ended question box.
Enter your question: Do you have any suggestions for improvements?
Keep the default text of the button you want to display: Send.
Check the Display a thank you message box.
Enter the message to be displayed once the visitors have given a rating: Thank you for your feedback!
Check the Display a key box.
Keep the key values for the lowest rating: Very low and for the highest rating: Very high.
Click the Style tab.
.
Style tab
Notes
In the Notes step, select Clear appearance.
In the Border category, set the border thickness to 0px, the border radius to 20px and leave the color as is (#1079ff).
In the Background category, leave the background color as is (#ffffff) and the overlay color as is (#000000), keep the overlay opacity at 50%.
In the Container category, leave the color as is (#1079ff), set the question/reply spacing to 40px, the horizontal and vertical padding to 40px, the horizontal and vertical margins to 0px.
In the Button style category, leave the Button spacing set to 5px, select the dark contrast and the rounded button shape with an 8px border, leave the background color and the button border color as is (#1079ff) and the button font color as is (#ffffff); set the border thickness to 0px.
Open-ended question
For the Open-ended question step, in the Field style category, set the border thickness to 1px and set the button spacing to 30px.
In the Send button style category, set the button background color to #1079ff and the button font color to #ffffff.
Click the Conditions tab.
Conditions tab
In the Recurrence category, set the Display recurrence to Every session.
Set the Recurrence after closing to Every session.
Set the Recurrence after validation to Every session.
In the Trigger category, choose Page load.
Check the Hide automatically after validation box after 1 second.
Click Save.
Related articles
View ArticleThe NPS widget enables you to display a satisfaction survey in order to collect recommendations from visitors. The NPS, or Net Promoter Score, is an international customer satisfaction measuring tool based on a single question.
This functionality enables you to carry out a satisfaction survey via a form displayed on one or more pages or your website. This way, visitors can rate and comment on their experience as users, as well as recommend the website to other visitors.
Among other things, the NPS widget enables you to identify promoters and detractors on your website, to collect feedback and to measure the impact or your changes.
The NPS widget then lets you:
track the evolution potential of customer loyalty,
find out how you are performing compared to other players in your field,
improve the user experience.
Example: creating an NPS widget
Accessing the widget
Open the variation editor on the desired website,
Click Nudge in the toolbar on the right-hand side,
Browse to the Dynamic content section or filter on the widgets name,
Click Add,The configuration form is displayed.
Configuring the widget
During this configuration step, changes are displayed in real-time.
Once your changes have been applied:
Click Save to save your changes,
If necessary, you can click History in the toolbar to edit and make changes to your configuration.
List of options of the NPS widget
The first time you access the widget, red dots are displayed on the tabs to indicate that new options are available.
Layout tab
Options
Use
Banner
At the bottom
Place the banner at the top of the web page
At the top
Place the banner at the bottom of the web page
Modal
/
Display a modal in the center of the web page
Free placement
Before
Fix the widget before a specific element of the web page
After
Fix the after before a specific element of the web page
At the start
Place the widget in the HTML code, at the start of the element definition
At the end
Place the widget in the HTML code, at the end of the element definition
Text position
Above
Display the question above the rating scale
To the left
Display the question to the left of the rating scale
Content tab
Options
Use
Question
Enter the title of the NPS question
Ask an open-ended question
[Optional] Add an open-ended question after the NPS question
Button text
[Optional] Add a button to send the answer to the open-ended question
Display a thank you message
[Optional] Add a thank you message after the answer to the NPS
Display key
[Optional] Add a key next to the lowest rating and the highest rating
Style tab
Options
Use
Section to be personalized
Select the section of the survey you want to apply the Style tab options to. Either:
Notes
Open-ended question
Thank yous
Type of personalization
Choose the way you want to customize your widget
Theme: customize an existing theme
Custom CSS: add your own CSS code directly in the campaign editor (step 2)
Appearance
Choose the appearance you want to apply to the survey. Either:
Light
Dark
Border
Border thickness
Configure the thickness of the modal border (in pixels)
Border radius
Configure the border radius of the modal (in pixels)
Border color
Configure the color of the modals border: use the palette to configure the hexadecimal value and opacity
Background
Background color
Select a background color for the modal
Overlay opacity
Darken or lighten the visual used for the modal background
Container
Text color
Select the text color of the NPS question
Question/reply spacing
Configure the distance between the NPS question and the rating scale (in pixels)
Padding
Configure the horizontal and vertical inner margin (in pixels)
Margins
Configure the horizontal and vertical margins (in pixels)
Drop shadow
Define a drop shadow
Shadow opacity
Configure the opacity of the drop shadow (in pixels)
Button style
Button spacing
Configure the distance between the buttons and the rating scale (in pixels)
Button contrast
Configure button contrast: dark background and light font or light background and dark font
Button shape
Configure button shape:
Square
Rounded
Round
Button background color
Configure the button background color using the palette
Button text color
Configure the button font color using the palette
Button border color
Configure the button border color using the palette
Button border thickness
Configure the button border thickness
Field style
Comment field background color
Configure the background color of the comment field using the palette
Comment field border color
Configure the border color of the comment field using the palette
Comment field border thickness
Configure the comment field border thickness (in pixels)
Comment field border radius
Configure the comment field border radius (in pixels)
Comment field text color
Configure the font color of the comment field using the palette
Spacing between the field and the send button
Configure the spacing between the comment field and the send button (in pixels)
Send button style
Send button background color
Configure the background color of the send button using the palette
Send button border color
Configure the border color of the send button using the palette
Send button border thickness
Configure the send button border thickness (in pixels)
Send button border radius
Configure the send button border radius (in pixels)
Send button text color
Configure the font color of the send button using the palette
Custom CSS
You may also customize your NPS with your own CSS code thanks to the custom CSS function. This is an advanced mode that only displays the widgets DOM (Document Object Model) structure if you do not wish to use the style offered by AB Tasty.
To add your own CSS code, click Add CSS in the variation menu, then enter your CSS code according to the previously defined widget categories.
Conditions tab
Options
Use
Display recurrence
Configure the widgets display frequency until user carries out an action on it:
All the time
Every session
Every day
Every week
Every month
Once per visitor (no recurrence)
Recurrence after closing
Configure the widgets redisplay frequency if the user closes the widget without carrying out an action on it
Recurrence after approval
Configure the widgets redisplay frequency if the user has carried out an action on the NPS
Triggers on
Page load
Displays the widget when the page is loaded
Click
Displays the widget when the user clicks an element of the web page
Exit intent
Displays the widget when the user moves their cursor towards the cross to close the active tab
End of interval
Displays the widget after a given time interval
Reengage (following inactivity)
Displays the widget when the user reengages on the website after a certain period of inactivity.
Related articles
View ArticleConfiguring targeting for a campaign involves specifying the URL of the page(s) to be modified on the one hand, and the visitors who will see the changes, i.e. your campaign audience, on the other hand.
Targeting definition is step 4 of the test campaign configuration process and step 2 of the personalization campaign configuration process (for more information, refer to the post on Defining campaign targeting ). At this stage, you must configure the target page(s) on which the changes made via the variation editor will be visible to your visitors.
To define your audience, you can either configure campaign targeting for all visitors, customize your audience or use an existing audience by selecting it from a drop-down list.
Once targeting is complete, you can run the QA process for your campaign via the targeting configuration page. Simply enable the QA mode option.
Managing targeting criteria
The options detailed in this article are only available from version 2.4 upwards of the framework. For more information, please contact your CSM.
Displaying the targeting configuration screen
Test campaigns
From the dashboard, click, then 4 Targeting.
From the variation editor, display the left-hand pane of the campaign and click 4 Targeting.
Personalization campaigns
From the dashboard, click, then 2 Targeting.
From the variation editor, display the left-hand pane of the campaign and click 2 Targeting.
Targeting all visitors
The first time you access the targeting section of your campaign, the All visitors option is selected by default in the audience drop-down list.
This means no targeting criteria are defined and all the users who visit the target pages will be targeted.
Creating a custom audience
To create a specific audience, you need to select the targeting criteria to be applied to visitors.
To create a custom audience, apply the following steps:
Select Custom audience from the drop-down list.
Click Add a criterion.
Place the cursor on the criterion you want to use.
Click Add.
Select the values that are specific to the chosen targeting criterion.
At this point, you can either save this audience to reuse it for other campaigns or simply save the targeting step of your campaign: in this case, the audience will be unique and linked to this campaign only.
Managing targeting criteria
When you create a custom audience or change a previously saved audience, you will need to select targeting criteria.
For more information, refer to Managing targeting criteria.
Saving a unique audience
To save the audience configured for a given campaign, apply the following steps:
Click Save step. A confirmation message is displayed.
Move on to the next campaign configuration steps: traffic allocation and third-party tool integration, if applicable.
Saving a custom audience
Once you have finalized the creation of a custom audience, you can save it in order for it to be reused to target the same audience in another campaign.
To do this, apply the following steps:
Create your custom audience.
Click Save audience.
Enter the label you want to assign to this audience in the Audience name field.
If necessary, enter a description.
Click Save. This audience is applied to your campaign in progress by default.
Click Save step. A confirmation message is displayed.
Move on to the next campaign configuration steps: traffic allocation and third-party tool integration, if applicable.
The audience you have just saved is now available when you select the Saved audiences option using the drop-down list.
Selecting a saved audience
You can apply a previously saved audience to your current campaign.
To do this, apply the following steps:
Select Saved audiences from the drop-down list. The list of all saved audiences is displayed.
Click the desired audience.
Click Save step. A confirmation message is displayed.
Move on to the next campaign configuration steps: traffic allocation and third-party tool integration, if applicable.
You can also select a previously created audience and edit it.
Updating a saved audience
You can select a previously created audience, edit it and save your changes.
Editing a saved audience impacts all campaigns for which this audience is being used. We recommend saving a new audience rather than overwriting the existing one. If you are sure these changes aren't likely to bias the results of some of your campaigns, or if you want to apply your changes to all campaigns using this audience, you can update the audience.
To edit an existing audience, apply the following steps:
Select Saved audiences from the drop-down list.
Click the desired audience.
Then, click to edit the selected audience.
Change the existing criteria or add to them.
Click Save audience.
Choose between creating a new audience and overwriting the existing audience.
Creating a new audience
Click Create new.
Assign a label to it and follow the steps to save a custom audience.
Click Save.
Then, click Save step. A confirmation message is displayed.
Move on to the next campaign configuration steps: traffic allocation and third-party tool integration, if applicable.
Overwriting an existing audience
Click Overwrite. The audience is updated with your changes.
Click Save step. A confirmation message is displayed.
Move on to the next campaign configuration steps: traffic allocation and third-party tool integration, if applicable.
Whether you choose to overwrite the existing audience or to create a new one, the audience you have just saved is now available when you select the Saved audiences option using the drop-down list.
Related articles
Defining campaign targeting
Defining target pages
View ArticleYou have created your variations in our graphical editor and are ready to launch your test.
Before you do, you need to test or QA your test.
To test your test,you have 2 test modes:
Cookie targeting
IP inclusion targeting
IP inclusion targeting
This method allows you to limit your tests visibility to users who share a specific IP address, typically that of your organisation or company. This isvery practical if you want to receive a test in real condition but you want it to be only visible to other collaborators who need to validate the recipe before final upload.
this one
This test method isuseful if you want to test more complex test scenarios, such as multi-page tests that require navigating through several pages, or on different devices (PC, mobile, tablet).
You can find IP targeting in "Add Targeting" in the Visitors section.You can specify your IP address (which appears under the targeting name) or your range of IP addresses in the test targeting options. You can specify multiple IP addresses if necessary (e.g. your organisation, your branch or another technical service provider).You can combine this targeting criterion with others.
In Traffic Modulation, assign 100% of the traffic to the variation you want to test, so you can be sure of accessing to the desired page directly.
You start the test in production (it will only be visible on your IP) and open a browser window with the targeted URL. Indeed, to test by IP, you must empty these caches or test in private browsing to ensure you reach the desired variation.
Once the test is complete and the GO for deployment is given, be sure to remove IP targeting and save; also, be sure you change the modulation and publish it so that your script is updated.
Cookie targeting
This last method lets you test in real conditions and only on the browser to which you add the cookie.This is useful if you want to test more complex test cases, such as multi-page tests, and do not want to open the test to all your employees sharing the same IP from the start.
In this case, the test is activated but only displayed for users with a specific cookie on their browser. You define the name and value of this cookie yourself in the targeting interface and then create this cookie on your browser to be assigned to the test. The procedure to follow is detailed below.
Add a cookie targeting in your test settings.
Enter a cookie name and value as shown below. Make sure you give your cookie a neutral name like "cookie_test", "beta_test" or "test_ab". If you add a cookie name that is already on your site, the user will be tested. Do not forget to save your changes and publish your test in production.
Be sure you are assigned to the variation Assign 100% of the traffic to the variation you want to test so you are sure to see it. Publish your test and wait 2 minutes for your script to update.
Now you need to add the cookie to your browser
You can do this manually or by using the Edit this Cookie plugin.
- To add the cookie manually in your browser
To add the cookie manually, load the page targeted by your test in your browser, open your console (F12) and add the following line:document.cookie="cookiename=cookievalue". Press "Enter" then refresh your page, you will be assigned to the test and the variation. You can then check that everything is correct.
- To add the cookie with the "Editthiscookie plugin
You can also add this cookie by using a plugin (ex: Editthiscookie for Chrome). Once the plugin is installed, go to the page to be tested, click on the cookie to the right of your address bar and then on the "+". Add the cookies name and value. Confirm and refresh the page to be assigned to the test.
If you want to know which variation you are assigned to, see our online help page orif you are on framework 2.0.
View ArticleAB Tasty is a mobile application which enables you to manage campaigns created using AB Tasty on your mobile telephone.
The application features a notification system, which lets you know in real-time whenever an action is carried out on your AB Tasty account.
These notifications can be configured if you only want to receive information that interests you.
The notification center displays all the received notifications, listed as read and non-read.
For more on this, refer to The AB Tasty mobile application.
Disabling the mobile SDK
The notifications and the AB Tasty application interface are only available in English.
Using notifications
The mobile application notifications are broken down into three categories: Framework, Account and Campaign.
They are displayed in the form of push notifications on your phone. Clicking a notification automatically redirects you to the login screen (if you are logged in), and then to the notification center.
Example of a push notification on iOS
Framework
There are two types of notifications, which coincide with actions carried out on the AB Tasty framework. These notifications are triggered in the following cases:
When a user clears the Framework : Alert! AB Tasty has been deactivated on your account MYWEBSITE.COM
When a user re-enables the Framework: Alert! AB Tasty has been reactivated on your account MYWEBSITE.COM
Account
There are three types of notifications, which coincide with actions carried out a users account. These notifications are triggered in the following cases:
When a user creates an access profile: Account changes! Users have changed on your account [ABC]
When a user deletes an access profile: Account changes! Users have changed on your account [ABC]
When a user changes the status of an access profile: Account changes! Users have changed on your account [ABC]
Campaign
There are two types of notifications, which coincide with actions carried out on a campaign. These notifications are triggered in the following cases:
When a user launches a campaign: Launch pad activity! A campaign has been launched on your account [ABC]
When a user pauses a campaign: Launch pad activity! A campaign has been paused on your account [ABC]
Configuring notifications
You can choose the types of notifications you want to enable or disable.
To access the notification settings, apply the following steps:
Click the hamburger menu in the upper right-hand section of the screen.
Click Notification center.
Click the icon at the top of the notification screen:The notification management screen is displayed.
Enabling notifications
The first time you log into the application, a popup asks you to allow notifications from the AB Tasty mobile application.
If you accept, you will automatically be redirected to the notification center. If notifications are deactivated in your mobile phone settings, a second popup displays the following message:
Receive alerts. Be informed of status changes in your tests or account by signing up for push alerts. You will still have the option to disable these alerts later if you change your mind: Active notification alerts / Maybe later.
Disabling notifications
If you have enabled mobile application notifications, all three notification categories are enabled by default.
To disable one or more categories of notifications, apply the following steps:
From the notification center, click theicon at the top of the screen:The notification management screen is displayed.
Select the desired category and click ON/OFF to disable the related notifications:
The button is grayed out and notifications are disabled.
Viewing notifications
All received notifications are visible in the notification center.
To access it, apply the following steps:
Click the hamburger menu in the upper right-hand section of the main screen.
Click Notification center.
The notification center is a library that collects all the notifications received on the AB Tasty mobile application.
Each type of notification is represented by a different pictogram:
Framework:
Account:
Campaign:
Notifications are broken down into two groups:
unread notifications,
read notifications.
Then ordered by date of receipt, from the most recent to the least recent.
Click a notification to show the entire message as well as the possible actions.
For each notification, the application displays the following information:
the notification name,
the content,
the category (Framework, Account, Campaign)
the date and time on which the notification was received.
You can also click the available links to carry out the following actions:
See campaign: to view the campaign linked to the notification,
Mark as read: to mark the notification as having been read.
If no notifications have been received, the following message is displayed: Ooops, you have nothing here.
Related articles
The AB Tasty mobile application
View ArticleThe Overview tab of a campaign displays the main information and enables you to see straight away whether or not the campaign is ready for analysis. It shows two levels of information:
The progress level of your test campaign, which enables you to know whether or not it is ready for analysis;
Summary information regarding the criteria defined during steps 1,2, 4, 5 and 6 of the campaign configuration process.
Not only does the Overview tab enable you to track your campaign progress, it also lets you make sure the creation steps have been configured correctly.
For more on the mobile application, refer to The AB Tasty mobile application.
Managing notifications from the AB Tasty mobile application
Accessing the Overview tab
To access the Overview tab of an A/B test, apply the following steps:
Go to the campaign dashboard and click an A/B test:
The Overview tab is displayed.
So far, the Overview tab is only available for A/B tests.
Overview and progress level of the campaign
The top section of the screen displays the following information:
the name of the A/B test;
the ID of the A/B test;
the technical status (Live or Paused);
Use the button at the bottom of the screen to start or pause the test.
Campaign progress level card
The Campaign progress card indicates whether or not the A/B test is ready for analysis. It features the three following criteria: the traffic for the test as a whole ( Traffic ), the conversion rate on the main goal ( Conversions ) and the test duration ( Time ).
The card displays the progress level of traffic and duration indicators. The color varies depending on progress levels:
Less than 33% - Red/orangeThe test is far from being ready for analysis. The data collected so far is insufficient.
Between 34% and 99% - Yellow/orangeThe test isn't ready for analysis yet. The data collected so farisn'tsufficient enough to guarantee reliable results.
100% - Green/blueThe test is ready for analysis because all three criteria have been met.
Traffic
The Traffic section displays the number of unique visitors who have seen the test, as well as the number of visitors yet to be reached.
In order for campaign results to be reliable, it is preferable to wait until you have reached at least 5,000 unique visitors per variation.
Conversions
The Conversion section displays the number of conversions on the main goal as well as the number of conversions needed.
In order for campaign results to be reliable, it is preferable to wait until you have reached at least 500 conversions per variation on the primary goal.
Time
The Traffic section displays the number of days since test creation, as well as the number of days to go.
We recommend waiting at least 15 days before viewing the test results.
By default, the test creation date is displayed. You can change the test start date if you ran the QA process or if you didn't launch it immediately after creating it.
To do this, apply the following steps:
Click the icon .
Select a date on the calendar.
Click OK:
The date is updated.
Summary of the criteria
The last section of information is a summary of the criteria set up during steps 1 (main information), 2 (variation editor), 4 (targeting), 5 (traffic allocation) and 6 (3rd party integration) of campaign configuration and combines the following sections:
the Campaign details section;
the URL targeted section;
the Audience section;
the Traffic allocation section;
the 3rd party integration section.
Campaign details section
The Campaign details section displays the following information:
the number of variations;
the A/B test creation date;
the creator of the A/B test;
the original hypothesis of the A/B test.
URL targeted section
The URL targeted section displays the URL of the page(s) on which the changes made via the variation editor will be visible to your visitors.
The green dot indicates that the URL(s) specified in the platform will be included. The red dot, on the other hand, indicates that the URL(s) is/are excluded.
If no target page was defined during step 4, the URL configured during step 1 (main information) is displayed by default.
Audience section
The Audience section displays the targeting criteria, i.e. the categories of visitors who will see the changes made to your test.
The following information is displayed:
the audience name (in the case of a custom saved audience, which is therefore reusable);
the type of operator selected (AND and/or OR);
the list of the various targeting criteria defined.
If no audience was defined, all the users who visit the pages defined as target pages will see the test.
Traffic allocation section
The Traffic allocation section displays the breakdown of traffic between the original version and the variation(s), as well as the percentage of non-tracked visitors.
3rd party integration section
The 3rd party integration section displays the name(s) of the tool(s) that have been enabled for this test.
If no 3rd party tools were enabled for this test, nothing is displayed.
The information displayed in the Overview tab cannot be modified via the mobile application. To make changes to one or more of the displayed fields, you need to change the campaign configuration via the AB Tasty web platform.
Related articles
The A/B Tasty mobile application
Mobile application - Goals tab
View ArticleThe Image Matchmaker dynamic content enables you to highlight the image on your product page that generates the highest number of conversions.
Example: creating an Image Matchmaker widget
The widget is based on the three following functions:
a function that returns the number of images on your product page;
a function to be called up in order to highlight a given image;
a function that enables you to record a conversion for the related product page.
Once these elements have been entered, AB Tasty displays a random image for each visitor. At the same time, it records conversions and automatically detects the image that generates the most of them. This image is then selected by default to appear at the top of the product page and be highlighted.
The layout of images on a product page plays a major role in a visitors purchase decision. This widget is useful if youdon'tknow which image to highlight and you want to generate more conversions on the page.
The Image Matchmaker widget belongs to the Dynamic contentcategory, which is a chargeable option. To benefit from this widget, please contact your designated KAM.
Accessing the widget
Open the variation editor on the desired website.
Click Widgets in the toolbar on the right-hand side.
Browse to the Dynamic contentsection or filter on the widgets name.
Click the widgets card:The configuration form is displayed.
Configuring the widget
Once your changes have been applied:
Click Save to save your changes,
If necessary, you can click History in the toolbar to edit and make changes to your configuration.
List of options of the Image Matchmaker widget
Content tab
Options
Use
[JS Code] - Get number of image thumbs
Add the JavaScript code for recovering the number of images on your product page.
[JS Code] - Change current img with __INDEX__
Add the JavaScript code that matchesthe function for highlighting a given photo.
Add to cart button
Select the Call to action button on your page. It enables you to record conversions for this product page.
By default, the first two fields are pre-filled with a JavaScript code example. However, both the JavaScript code and the Call to action button are specific to your website and depend on how the latter was coded. You must therefore replace the original code with the code that matches your own website.
Related articles
View ArticleIn this example, we will describe the steps required to create a widget for highlighting the image that generates the most conversions on the page:
Image Matchmaker widget
Accessing the Image Matchmaker widget
Open the variation editor on the desired website.
Click Widgets in the toolbar on the right-hand side.
Enter Image Matchmaker in the search field.
Click the Image Matchmaker card.
You can now start configuring your modal. The Content tab is displayed by default.
Content tab
In the [JS Code] - Get number of image thumbs field, enter the JavaScript code for recovering the number of images on the page.In this case: document.querySelector(.swiper-wrapper).children.length;In the example above, the JavaScript code is broken down as follows:
document.querySelector(.swiper-wrapper).children.length;
Indicates that the search is being carried out throughout the entire document (i.e. the entire page).
document.querySelector(.swiper-wrapper).children.length;
Function that returns the first element in the document with a swiper-wrapper class.
document.querySelector(.swiper-wrapper).children.length;
Name of the class containing miniature images.
document.querySelector(.swiper-wrapper).children.length;
Function that indicates the need to select the children of elements with a swiper-wrapper class.
document.querySelector(.swiper-wrapper).children.length;
Function that enables you to count the number of child elements.
This function thus enables you to return the number of children in the swiper-wrapper class of the document, in other words, the number of miniature images included on the page.
In the [JS Code] - Change current img with __INDEX__ field, enter the JavaScript code that matches the position of the image highlighted on the page.In this case: document.querySelector(.gallery-thumbs. swiper-wrapper > .swiper-slide:nth-child(_INDEX_)).click();In the example above, the JavaScript code is broken down as follows:
document.querySelector(.gallery-thumbs .swiper-wrapper > .swiper-slide:nth-child(_INDEX_)).click();
Indicates that the search is being carried out throughout the entire document (i.e. the entire page).
document.querySelector(.gallery-thumbs. swiper-wrapper > .swiper-slide:nth-child(_INDEX_)).click();
Function that returns the first element of the document with the selector (.gallery-thumbs. swiper-wrapper > .swiper-slide:nth-child(_INDEX_)).
document.querySelector(.gallery-thumbs. swiper-wrapper > .swiper-slide:nth-child(_INDEX_)).click();
Name of the class containing the swiper-wrapper class. Gallery-thumb is thus the parent of swiper-wrapper.
document.querySelector(.gallery-thumbs.
swiper-wrapper > .swiper-slide:nth-child(_INDEX_)).click();
Name of the class containing the swiper-slide class. Swiper-wrapper is thus the parent of swiper-slide.
document.querySelector(.gallery-thumbs.
swiper-wrapper > .swiper-slide:nth-child(_INDEX_)).click();
Name of the class containing miniature images.
document.querySelector(.gallery-thumbs.
swiper-wrapper > .swiper-slide:nth-child(_INDEX_)).click();
Specifies the number of the child to be selected.
The number is returned thanks to the INDEX variable.
document.querySelector(.gallery-thumbs.swiper-wrapper > .swiper-slide:nth-child(_INDEX_)).click();
Variable that returns a number. This number coincides with the number of the miniature image the virtual click must be carried out on.
document.querySelector(.gallery-thumbs.swiper-wrapper > .swiper-slide:nth-child(_INDEX_)).click();
Function that enables a virtual click on the selected element.
This function thus enables a virtual click on a miniature image to change the image highlighted on the page.
Click Select element.
Select the Call to action button on your page. In this case, the Travel button.A contextual menu is displayed.
Click Select this element(if necessary, use the Select. parent or Select. children option to select the right element).The code that matches the selected element is displayed in the configuration form. In this case:BODY BUTTON
Click Save.
Related articles
View ArticleIn this example, we will describe the steps involved in adding a DisplayWeather widget to a web page and personalizing it.
Display Weather widget
Accessing the Display Weather widget
Open the variation editor on the desired website,
Click Widgets in the toolbar on the right-hand side,
Enter Weather in the search field,
Click the Weather card:The configuration form is displayed and the widget appears.
You can now start configuring the widget. The Layout tab is displayed by default.
Layout tab
Keep the layout of the widget horizontal,
Click the Content tab.
Content tab
Click Select element,
In the web page, select the element that will host the widget,A contextual menu is displayed.
Select the element,(if necessary, use the Select parent or Select children option to select the element properly).
Keep the temperature unit in degrees Celsius,
Keep the position of the widget after the host element,
Click the Style tab.
Style tab
Text and background
Click Font color and select a color from the palette or enter its hexadecimal value in the Hex field,
Leave the opacity at 100%,
Leave the default Background color.
Border
Move the Border thickness cursor to 1 px,
Move the Border radius cursor to 8 px.
Drop shadow
Keep the drop shadow and its default opacity,
Click Save.
Related articles
View ArticleThe DisplayWeather widget enables you to display the weather and temperature in the city where the visitors to your website are currently located.
Example of adding the Displey Weather widget to a website
Accessing the widget
Open the variation editor on the desired website,
Click Widgets in the toolbar on the right-hand side,
Browse to the Specialsection or filter on the widgets name,
Click the widgets card,The configuration form is displayed and the widget appears on the page.
Configuring the widget
During this configuration step, changes are displayed in real-time.
Once your changes have been applied:
Click Save to save your changes,
If necessary, you can click History in the toolbar to edit and make changes to your configuration.
List of options of the Display Weather widget
The first time you access the widget, red dots are displayed on the tabs to indicate that new options are available.
Layout tab
Options
Use
Horizontal
Display the weather icon, the temperature and the city on a horizontal line
Vertical
Display the weather icon, the temperature and the city on a vertical line
Content tab
Options
Use
Element
Select the element you want to host the widget
Temperature unit
Choose the temperature unit to be displayed (Celsius or Fahrenheit)
Position
Choose the position of the widget in relation to the element (before or after)
Style tab
Options
Use
Font color
Personalize the color of the font used to show the temperature and the city: use the palette to configure the hexadecimal value and opacity
Background color
Select a background color for the widget: use the palette to configure the hexadecimal value and opacity
Border color
Add a border and configure its color: use the palette to configure the hexadecimal value and opacity
Border thickness
Add a border and configure its thickness in pixels
Border radius
Configure the border radius of the modal in pixels
Drop shadow
Add a shadow around the widget
Drop shadow opacity
Configure the size of the drop shadow
Related articles
View ArticleOnce you have defined targeting and before you launch the campaign and make changes accessible to users, you need to run your click trackings through the QA process.
Running your click trackings through the QA process enables you to make sure click tracking is taken into account and visible in the campaign reports.
In a standard A/B test
To check that your click trackings have been deposited correctly in a standard A/B test, apply the following steps:
Open your Chrome browsers JavaScript console.
Go to the Network tab.
Check the Preserve log box in order for the data to be saved if you change pages.
Filter using the datacollectATor ariane.abtasty command.
Via the web page, click the tracked CTA.
Via the Headers tab, click the highlighted link.
Unfold the chevrons until you see the name of the CTA and the ID of the related test.
How do I set up a redirect test?
If click tracking wasn't deposited correctly, nothing will appear in the console when you click the CTA button. This can be due to a bad choice of selector during click tracking configuration in the variation editor.
In a redirect test
Click tracking works differently in the case of a redirect test because the pageisn'tdisplayed in the variation editor.
If the selectors of the elements to be tracked are identical, the test will work just like a standard A/B test. However, if the selectors of the elements to be tracked are different (different IDs, class, div, etc.), you will need to deposit click trackings on both variations and give them the same name in order for them to be displayed in the same reports line.
To deposit click tracking in a redirect test, apply the following steps:
Enter the URL of the page you want to redirect the visitor to in your browser.
Open Chromes JavaScript console and go to the Elements tab.
On the page, select the element you want to configure click tracking on.
In the code, copy the matching selector.
Return to the variation editor and open the click tracking configuration window.
Select an element at random on the page and click Click tracking.
Paste the selectoryou'vecopied from the console in the place of the selectoryou'veselected.
Enter a name for the tracking function (use exactly the same name as in the original version) and save.
To QA test the click trackings of a redirect test, follow the same steps as for a standard A/B test.
When you run checks in the console using the ABTasty.results function, it is normal for targeting to be rejected as the displayed pageisn'ttargeted.
To find out which campaign you are being redirected from, type the ABTasty.redirectedFrom command directly into the console. The campaign name is displayed.
Refer to the How do I set up a redirect test? support post for more information.
For more on this, refer to
Using the QA mode
View ArticleThe AB Tasty tag enables you to inject JavaScript code into your website. This code can be used to track conversions or to send data to AB Tasty. The aim is to obtain additional information on a test.
This code is applied to all pages where the AB Tasty tag is present, as long as at least one test is running.
To add JavaScript code,
Click Settings, then click Global Code.
Enter the code to be executed in the input window.
Click Save.
Do not add the opening and closing tags to your code (<script></script>).
By default, this code will run once "document.ready" is initialized in JQuery.
Code history
Each time you click Save, the code and its creation date are saved.
If necessary, you can reuse a previous version: simply copy the content of the saved code and paste it into the input window.
View ArticleWhen you configure an NPS survey using the NPS widget, visitor feedback and comments can be viewed directly in the campaign reports.
Results related to the NPS are shown in the reports NPS tab. If no widgets were configured in your campaign, the NPS tab is not displayed. However, if you have implemented the widget for one or more variations of the campaign (and collected feedback), the NPS tab is displayed in the campaign reports. Even if you delete the NPS widget later, all data in the form of collected feedback is saved in the campaign reports.
NPS (Net Promoter Score) widget
If you delete a variation containing an NPS widget while answers have already been collected, the data will still be counted in the campaign NPS. In order to reinitialize the data, you need to create a new campaign.
Accessing the reports analysis
To access the NPS analysis, apply the following steps:
Go to the dashboard and click the of the desired campaign:Reports open.
Click the NPS tab:The NPS results are displayed.
Information
The Score card displays the following information:
The NPS score calculated for the campaign. It is calculated automatically as a function of the percentage of detractors and promoters. The NPS is expressed as a number and can range from -100 to +100.
The score is calculated as follows: percentage of detractors minus percentage of promoters. Passivesaren'ttaken into account for the calculation as they are considered as neutral.
Results displayed
The NPS widget may be implemented on one or more variations of your campaign.
The NPS reports display the results for each variation the widget was implemented on.
Notes
For each variation, the first section (NPS notes) displays a bar showing the number of detractors in red, promoters in green and passives in yellow.
When you hover the mouse over the voter distribution bar, it displays the percentage for each category.
It also displays the variation ID and the summary of information configured in the widget:
The NPS question
The open-ended question
The two buttons located underneath the results enable you to carry out the following actions:
Open NPS widget: to view the widget in the campaign editor.
Export results: to export the widget results in CSV format.
The Show Graph button enables you to display a graphical representation of all the collected data. It enables you to view the evolution of your results over time and analyze trends.
Comments
The second section (NPS comments) shows the list of corresponding notes and comments in chronological order.
It also shows the following information:
The name of the variation the NPS widget was configured in;
The date on which the response was sent;
The country from which the response was sent.
If NPS widget is implemented on one variation only, the Variation name column is not shown.
You may also sort the results by date (chronological or antichronological order).
Interpreting results
To get an idea of your ranking in relation to other companies, some websites offer NPS comparisons by field. You can also contact your dedicated CSM for more information.
A negative rating means there are more detractors than there are promoters, and conversely, a positive rating means there are more promoters than there are detractors. However, a negative rating does not necessarily imply poor performance. This depends on the company type and field.
Generally speaking, a rating above 10 is considered to be good, a rating above 50 is considered to be excellent, and a rating above 70 is considered to be exceptional.
If possible, compare your rating with that of companies based in your country. The average ratings of certain countries such as the United States tend to be higher because visitors are more likely to give high scores.
Related articles
View ArticleThe SLA (Service Level Agreement) is the availability rate of the AB Tasty platform, its performances, as well as the time intervals required to correct any incidents that may occur on the platform.
In order to guarantee the highest level of availability of our tool, AB Tasty works with providers specializing in data hosting.
The service adopts a high-quality technical infrastructure based on redundant and resilient servers, in order to guarantee the best possible operating conditions.
AB Tasty offers two levels of SLA depending on your type of contract:
Simple SLA
Premium SLA
Tool availability
99%
99,9%
Average Tag loading time
Under 200 ms
Under 200 ms
Correction interval
8 hours to 7 days (depending on the type of incident)
6 hours to 5 days (depending on the type of incident)
For more on this, please refer to the AB Tasty SLA document provided to you when signing your contract.
View ArticleThis article details the main elements of the AB Tasty CRO platforms interface.
Start off by logging in to your user account with the credentials provided by the AB Tasty teams.
Once you are logged in, you will see the platform dashboard along with any previously created tests.
Using the dashboard
The interface is made up of the following elements:
The horizontal navigation menu
The configuration bar
The filters and organization tools of the test list
The list of tests or personalizations
The chat module
Using the horizontal navigation menu
Once your are logged in to AB Tasty, the test dashboard is displayed by default.
A horizontal navigation menu enables you to browse between the modules available on the AB Tasty platform.
The horizontal navigation menu includes the following 5 sections:
Campaigns
Audience
Insights
Statistics
Lab
Each section features several modules.
Campaigns
Audience
Insights
Statistiques
Lab
Test
Dashboard of saved audiences
NPS
Overview
Prototypes developed by the AB Tasty teams or their partners.
Personalization
Session recording
Data explorer
The modules included in each section are displayed at the top of the related page.
To access the other modules, simply hover over the section and click the desired module.
Campaigns section
Test module
This module enables you to create 5 types of tests:
A/B test
The purpose of this test is to compare the performances of several different versions of the same page based on goals specific to each company. The measured information can be related to a service subscription rate, the number of sales as well as the average purchase value. These versions are put to the test in a real-life environment: each visitor (having no knowledge of the test) is randomly assigned a variation when landing on the website. During subsequent visits, they remain assigned to the initial variation.
On a large scale, trends can be identified, thus highlighting the most efficient variation.
This type of test enables you to test your default page using two different versions and a 50/50 traffic allocation ratio. If you want to add a variation, you can do this directly in the editing interface. You can therefore create A/B/C tests, for instance, and vary traffic accordingly.
Predictive test
By default, predictive tests allocate traffic dynamically. Depending your selected goal, users are progressively directed towards the winning variation.
Multivariate test
This type of test enables you to test combinations of changes simultaneously. The idea is to change several elements on a page and to identify which of the possible combinations has the biggest impact on the tracked indicators.
Multi-page test
This type of test enables you to test changes on a series of pages, such as a purchase funnel. By default, traffic is divided equally. Users assigned to campaign A only see pages linked to campaign A. Conversely, users assigned to campaign B only see campaign B throughout the entire purchase funnel.
Each page to be modified (known as a sub-test) is entered in the editor.
Server-side test
A/B, multi-page and multivariate tests enable you to apply changes to your website using the AB Tasty variation editor. These changes are applied via the browser directly, i.e. on the client side.
Conversely, server-side tests are coded in the pages of your website or web application and executed directly by the server of your website or application. They are based on the AB Tasty API library.
Personalization module
Personalizations enable you to target a specific segment of visitors subjected to your variation. By default, traffic for the variation is set to 100%.
Audience section
The Audience section enables you to display the list of previously saved audiences. You may also archive and/or restore these audiences.
Insights section
NPS module
This module enables you to create satisfaction surveys for your visitors: a form enables them to recommend the website by giving it a rating (between 0 and 10) and leaving a comment.
This functionality is subject to licensing. To benefit from it, please contact your sales manager.
Session recording module
The session recording module enables you to save your visitors actions on your website in video format.
This functionality is subject to licensing. To benefit from it, please contact your sales manager.
Data explorer
This module enables you to extract all the data related to your website using a query form.
This functionality is subject to licensing. To benefit from it, please contact your sales manager.
Statistics section
Overview module
The overview offers a summary of the number of campaigns and visitors linked to your accounts activity.
Lab section
This section features projects developed by the AB Tasty Innovation team, AB Tasty employees as well as our partners. These projects enable us to test ideas before integrating them into the AB Tasty platform.
To access these projects, please contact your CSM or your AB Tasty sales manager.
Migration wizard
This module enables you to import tests created in the Optimizely platform into the AB Tasty platform.
Page Flow
This chart enables you to track visitors clickstream data, i.e. the types of pages viewed after the tested page. The pages are categorized as a function of their URL format.
Eye Tracking
This module simulates 40 visits using artificial intelligence and predicts the spots which the users eye will be drawn to when they first open a page.
There are 4 types of visualizations for interpreting the results:
The Attention Heatmap: a heatmap that renders the most viewed spots.
TheGaze Plot: an equivalent to the eye trajectory, i.e. the order in which elements are viewed by the visitors eye.
TheOpacity Map: a chart that applies a black layer to the page in a way that highlights the most frequently viewed elements and hides the lesser-viewed areas.
TheAesthetics report: a report that rates the site from 0 to 100 based on criteria related to color, clarity and balance.
Mapizy
This module enables you to organize the way you track your campaigns and manage them as projects on a separate dashboard. Each project can be linked to one or more campaigns and contains the initial hypothesis, the tracked KPIs and the results. The system features filters and prioritization to quickly identify experiences that are being designed, in progress or finished.
Lastly, each finalized project is displayed in the form of a history timeline and remains accessible for all users.
AB Tracking
This module enables AB Tasty customers to keep track of their support use and, if necessary, to request additional support days with just one click.
Three diagrams enable you to view the tracked time in the form of Hours per project, Hours per task and via a Consumption curve.
Requests for additional days are sent to the CSM in charge of the customer via Slack and the data is updated automatically in Salesforce.
Keyword discovery
This module enables you to
collect keywords related to products seen by a visitor on a given website,
create audience segments by combining several keywords and target the visitors that match these segments.
Related articles
Using the configuration bar
View ArticleWhen configuring a test or personalization, there are 6 steps you need to follow before you can start your campaign and make changes accessible to your users.Targeting definition is step 4 of the test campaign configuration process and step 2 of the personalization campaign configuration process.
If necessary, you may also configure the visitors who will see your changes, i.e. your campaign audience.
Once targeting is complete, you can run the QA process for your campaign via the targeting configuration page. When you run the QA process for your campaign, only you will see the configured changes, not your visitors. However, your campaign will look just like it would for your visitors: check that visual changes are displayed correctly, that targeting criteria are complied with and that click tracking is taken into account and visible in the campaign reporting section.
To do this, use the QA mode option via the targeting configuration page.
IP address targeting
The QA mode option is only available from version 2.4 upwards of the framework. For more information, please contact your CSM.
Displaying the targeting configuration screen
Test campaigns
From the dashboard, click, then 4 Targeting.
From the variation editor, display the left-hand pane of the campaign and click 4 Targeting.
Personalization campaigns
From the dashboard, click, then 2 Targeting.
From the variation editor, display the left-hand pane of the campaign and click 2 Targeting.
Enabling the QA mode
Start by defining your target pages and, if applicable, your campaign audience.
Then enable the QA mode to make sure your campaign is configured properly. To do this, apply the following steps:
Click to enable the QA mode for the campaign: The QA settings are displayed.
Enable the Target an IP address or the Target a cookie setting, or both depending on your needs.
Click Save step in the upper right-hand section of the screen.
For step 4 Traffic allocation, allocate 100 % of the traffic to the variation you want to check.
Play your test in production.
Open a private browser tab and enter your campaigns URL in the navigation bar.
Run your checks.
You must select at least one QA setting.
Onceyou'vefinished running checks, the campaign is ready to be launched for visitors:
Pause the campaign.
Disable the QA mode.
Check audience targeting.
Allocate the traffic as planned.
Delete the data provided during the QA process from the reporting page.
Play your campaign in production.
Targeting an IP address
When you enable the QA mode for your campaign, IP targeting is selected by default.
If thisisn'talready the case, click to enable IP targeting.
Configure the IP adress(es) you want to target.
Click Save step.
You can either configure your own IP address, one or more specific IP addresses or an IP range, and you can choose to include or exclude them from targeting.
For more information, refer to IP address targeting.
Targeting a cookie
Click to enable cookie targeting.
Enter a name and a value for the cookie in the relevant fields.
Click Save step.
You then need to create a cookie in your browser with the configured name and value.
For more information, refer to Cookie targeting.
Related articles
QA a test before rollout
Cookie targeting
View ArticleThe Data Explorer functionality enables you to run queries on the data of a specific AB Tasty account.
This means you can collect precise behavioral data linked to your campaigns.
How do I read the report provided by AB Tasty?
Data Explorer is an option. To benefit from this functionality, please contact your dedicated CSM.
Queries are run via a form. Two types of indicators are available: dimensions and metrics. Dimensions coincide with a description or feature of your data. For instance, you can collect data on the users visitor ID, the type of device they used, their browser, as well as their country or city.
Metrics coincide with the quantitative measurement of your data. For instance, you can find out the number of visitors, sessions, transactions, page views as well as the average price of a purchased item.
Dimensions and metrics can be combined, and you may select as many as you like.
When you run a query via the data explorer, AB Tasty queries the Universal collect (Ariane) database.
The results are displayed under the form, in a table that combines all the information. This raw data can be processed by data analysts and used to create statistics to complement the reporting function.
Creating a query
To create a query using the data explorer, apply the following steps:
Log in to AB Tasty at: https://app.abtasty.com/login,
From the dashboard, click Insights > Data Explorer.
Fill in the various fields.
To delete an indicator, click the cross to the left of it.To delete all indicators from a field, click the cross to the right of the field.
Click Run the query.
Filling in the form
To fill in the form, you need to enter the following fields:
Accounts
Use the drop-down list to select the account you want to collect information on. The accounts for which you have administrator status are displayed.
Start date
Select the date starting from which you want to collect information. To do this, enter a date manually using the YYYYMMDD format or use the calendar to select one.
End date
Select the date up to which you want to collect information. To do this, enter a date manually using the YYYYMMDD format or use the calendar to select one.
Dimensions
Dimensions coincide with a description or feature of your data.
You can select as many dimensions as you like from the following:
Category
Value
Description
General
Date
The date on which the session was opened.
Week
The week of the current calendar year.
Customer ID
The customer ID (unique number).
Is New Visitor
The visitors visiting the page for the first time.
Traffic source
Medium
How the user accessed the website (newsletter, etc.).
Referral path
The path via which the visitor accessed the website/page.
Source
The page which enabled the user to access the website/page.
Device
Browser name
The name of the browser used.
Browser version
The version of the browser used.
Device
The type of device used to view the website/page (Smartphone, tablet, computer).
Operating system
The operating system used.
Operating system version
The version of the operating system used.
Browser size
The size of the browser window (width x height format).
Flash version
The Flash version used.
Language
The chosen browser language.
Screen Colors
The color depth on the users screen.
Screen resolution
The resolution on the users screen.
Screen resolution width
The width of the resolution on the user's screen.
Geo network
Country
The country from which the user viewed the page/website.
Country ISO code
A two-character ISO 3166-1 country code for the country associated with the IP address.
Least specific subdivision ISO code
A string of up to three characters containing the region-portion of the ISO 3166-2 code for the region associated with the IP address.
Most specific subdivision ISO code
A string of up to three characters containing the region-portion of the ISO 3166-2 code for the region associated with the IP address.
Region
The State/region from which the user viewed the page/website.
City
The city from which the user viewed the page.
City ID
Users' city ID, derived from their IP addresses or Geographical IDs
Latitude
The approximate latitude from which the user viewed the page/website. Cities north of the equator have positive values and cities south of the equator have negative values.
Longitude
The approximate longitude from which the user viewed the page/website. Cities east of the prime meridian have positive values and cities west of the prime meridian have negative values.
Page tracking
Hit ID
The unique hit ID.
Hit number
The index of the hit in the current session.
Min hit number
Hit hour
The hour at which the hit is recorded.
Hit minute
The minute at which the hit is recorded.
Hit referer
The name of the reference hit.
URL
The complete URL from which the visitor landed.
Page Path
The page path.
Next Page Path
The next page path.
Hostname
The domain name.
Page title
The page title. Several pages can have the same title.
Is Entrance page
The page via which the visitor landed on the website.
E-commerce
Transaction ID
The transaction ID, provided by the e-commerce tracking method.
Affiliation
The transaction name.
Currency code
The code (based on the ISO 4217 standard) of the local currency with which the transaction was made.
Item count
The number of items in the transaction (better use the corresponding metric)
Item transaction ID
The transaction ID during an item purchase.
Name
The name of the product included in the transaction.
Category
The category of the product included in the transaction.
Product SKU
The identifier of the product purchased on the website.
Event Tracking
Event category
The event category.
Event Action
The type of action of the event.
Event Label
The event label.
Event Value
The total value of the events.
AB Tasty
Campaign ID
The ID of the AB Tasty campaign.
Variation ID
The ID of the AB Tasty campaign variation.
Platform or device
Hit type
The type of hit (such as campaign, pageview, event, etc.).
Hit Campaign ID
The campaign ID.
Hit variation ID
The ID of the variation viewed by the visitor.
Hit Queue time
The time difference (in milliseconds) between the moment the reported hit arrived and the moment it was sent.
Data Source
The data source of a result.
Custom variable
Custom Variable Index
The index of the custom variable.
Custom dimension
Custom Dimension Index
The index of the custom dimension..
Custom Dimension Value
The value of the custom dimension.
Custom metric
Custom Metric Index
The index of the custom metric.
Custom Metric Value
The value of the custom metric.
E-commerce
Transaction Revenue
The total transaction revenue.
Application Information
Screen Name
The name of the screen.
NetPromoterScore
NPS Score
Les rating (from 0 to 10) given by the visitors to the NPS survey.
NPS Feedback
The comments given to the NPS survey by the visitors.
Metrics
Metrics are the figures extracted from the database. They are expressed in the form of numbers. You can select as many as you like from the following:
Category
Value
Description
Sessions
Sessions
The total number of sessions.
Number of sessions per user
The total number of sessions divided by the number of users.
Percentage of new sessions
The percentage of new sessions.
Session duration
The duration (in seconds) of a user session.
Bounces
The total number of sessions for a unique page.
Bounce rate
The percentage of sessions of a unique page.
Avg session duration
The average duration (in seconds) of a user session.
Hits
The total number of hits for a user.
Users
Users
The total number of users.
New users
The number of sessions recorded as a new user.
Revisit
The number of times users revisit a specific page.
Page tracking
Pageviews
The total number of pages seen by a user.
Unique pageviews
The number of sessions during which a specific page was viewed at least once.
Pages / session
The average number of pages seen during a session, including repeated views of the same page.
Pages / user
The average number of pages seen by a user.
E-commerce
Transactions
The total number of orders generated by your website.
Unique transactions
The number of times a product (or set of products) was included in an order.
Revenue
The total revenue of the transaction (excluding shipping and tax).
Avg order value
The average revenue of an e-commerce transaction.
Revenue per user
The total revenue of the transaction (excluding shipping and tax) divided by the total number of users.
Shipping
The total shipping cost.
Tax
The total tax related to the transaction.
Transaction rate
The transaction rate.
Transaction rate per user
The transaction rate per user.
Items quantity
The total number of items purchased.
Unique purchases
The number of purchased products belonging to the same category.
Items revenue
The total cost of the transaction (excluding shipping and tax).
Items per purchase
The average number of items per transaction.
Avg item price
The average price of a purchased item.
Event tracking
Total events
The total number of events for a user across all categories.
Unique events
The number of unique events. Events with different sessions are considered as separate events.
NetPromoterScore
NPS Count
The number of users who gave a rating via the NPS widget.
NPS Promoters
The number of promoters (users who gave a rating of 9 or 10).
NPS Passives
The number of passives (users who gave a rating of 7 or 8).
NPS Detractors
The number of detractors (users who gave a rating of 0 to 6).
NPS
The final rating (% of detractors - % de promoters).
Base
Ghost
Selecting no specific metric.
The more dimensions and metrics you select, the longer the results take to load.
Filters
You can filter your search results. To do this, you need to use specific syntax. Refer to the list of operators available on the developer portal (refer to Data Explorer API ).
Sorting
Once you have chosen the dimensions and metrics you want to see, you can sort the results in ascending or descending order.
Choose at least one metric to enable value selection in the Sort field.
Max
Indicate the maximum number of results you want to see. The more information there is, the longer it takes for the results to load. If you want to limit loading time for the results, you may narrow down the number of results.
Viewing results
Search results are displayed underneath the form, as a JSON table. Depending on the volume of collected information, the results may take several minutes to load.
To export the results in CSV format, click the Export (CSV) button in the top right-hand section of the screen.
Related articles:
Developer portal - Universal Collect
Account information
Access rights and user management
View ArticleThe Session recording functionality enables you to save your visitors actions on your website in video format. This helps you understand their behavior on your website and identify users sticking points and browsing issues based on real-life situations.
Applying tags to your videos
This functionality is subject to licensing and depends on your traffic volume. To benefit from it, please contact your sales manager.
Accessing the videos
To accessing the videos, start by creating a recording on a given URL, then start the recording.
To do this,
Log in to AB Tasty at: https://app.abtasty.com/login.
Go to the dashboard and click Insights > Session recording.
Once the recording has been created and started, click View recordings: the list of recorded sessions is displayed.
A new line is created for each new session recording.
The following information is available for every session:
Whether or not the video is bookmarked
Visitors country and city
Date of visit
Duration of the recording in minutes and seconds
Activity level (high, average, low)
Operating system, device and browser used by the visitor
Manual, programmatic, behavioral and transactional tags used to categorize the video
Video play button
Viewing a video
To view a video, apply the following steps:
Go to the list of recorded sessions.
Decide on the session you want to view.
Click :The video opens in a window and starts automatically.
Click More details to view the information related to the video.
Click Back to close the information pane.
Click outside of the reader to close it and return to the list of recorded sessions.
The video playback interface includes the following elements:
The location, date, start time and duration of the video
Behavioral or transactional tags, and manual tags if applicable.
The URL of the visited page: click to open the web page
The playback progress bar: when rage click, error click or transaction type behaviors are identified, a different color is used to represent them.
For more on this, refer to Filtering by tag.
The start/pause buttons
The watch again button when the video ends
The button for reducing playback speed: click several times to reduce playback speed
The button for increasing playback speed: click several times to increase playback speed
The playback speed used (x1, x1.5, x2, x2.5, x3, x3.5, x4)
More details: enables you to open an information pane for the video, which includes the URL of the recorded page, the visitors device/browser/operating system and the behavioral and transactional tags applied to the video.
For more on this, refer to Applying tags to your videos.
Add a tag: enables you to manually add a tag to the video being watched.
For more on this, refer to Applying tags to your videos.
Viewing a specific action
The Session recording functionality automatically detects actions carried out by a visitor such as rage click, rage quit, error click as well as purchases made, i.e. transactions.
In this case, these actions are shown by the video player in two ways:
tags (or keywords),
Spots of color in the playback progress bar.
When viewing a video, you can highlight one of these actions by selecting the related tag. In this case, the color linked to the action is highlighted in the video progress bar. You can play the video and determine the point in the recording at which the action that interests you occurred.
To do this, apply the following steps:
Go to the list of recorded sessions.
Decide on the session you want to view.
Click to start the video.
Click the tag in the top left-hand section of the reader that matches the action you want to track: The color intensifies in the progress bar to help you spot when the action took place.
Related articles
Creating a session recording
Using the session recording dashboard
View ArticleThe Session recording functionality enables you to save your visitors actions on your website in video format. This helps you understand their behavior on your website and identify users sticking points and browsing issues based on real-life situations.
Using the session recording dashboard
This functionality is subject to licensing and depends on your traffic volume. To benefit from it, please contact your sales manager.
Several types of tag are available and can be applied to your videos:
Manual tags,
Automatic tags,
Programmatic tags.
These tags enable you to create keywords linked to your videos for sorting purposes and to easily identify the ones that interest you.
Manual tags
Manual tags can be added to an existing video. To access the videos, start by creating a recording on a given URL, then start the recording.
To do this:
Log in to AB Tasty at: https://app.abtasty.com/login.
Go to the dashboard and click Insights > Session recording.
Once the recording has been created and started, click View recordings: the list of recorded sessions is displayed.
Once it is created, you can filter videos containing a manual tag in particular.
For more on this, refer to Using the session recording dashboard.
Creating a manual tag
To create a manual tag on a video, apply the following steps:
Go to the list of recorded sessions.
Decide on the session you want to apply a keyword to.
Click :The video opens in a window and starts automatically.
Click More details: the videos information pane appears to the right.
In the Tags section, click Add a tag.
Enter the label you want to assign to the tag in the relevant field.
Hit Enter on your keyboard to create the tag: It is available in the information pane and in the top left-hand section of the video playback interface and is visible in the list of recorded sessions.
Deleting a manual tag from a video
Only manual tags may be deleted via the Session recording interface.
To delete a manual tag applied to an existing video, apply the following steps:
Go to the list of recorded sessions.
Click to open the video.
Click More details to open the information pane.
Click the cross to the right of the manual tag:The tag disappears from the information pane, as well as from the list of tags in the top left-hand section of the video playback interface.
Automatic behavioral tags
The Session recording functionality automatically assigns tags related to specific actions carried out by visitors to each video. If no implementations are necessary, these actions are detected automatically and added to the videos as tags.
The tags are visible for each video in the list of recorded sessions and in the video playback interface.
The actions concerned are:
Rage click: a succession of clicks on the same object, i.e. at least three successive clicks with less than 100 milliseconds between two clicks.
Error click: a JavaScript error which occurs when the visitor clicks on the website (error 404, for instance).
Rage quit: closing of the browser tab following a rage click on the web page.
Transaction: purchase made by the website visitor. Moreover, the transaction amount is also recorded and is displayed by hovering over the tag.
Programmatic tags
Automatic tags are akin to custom events. They occur during a browsing session and are captured automatically by a JavaScript call.
During this call, a tag is attached to the recording in progress. For instance, this means you can automatically record an add to cart or a visitor login action.
To create a programmatic tag, apply the following steps:
Place your cursor after the AB Tasty tag call in the code of your website.
Insert the following JavaScript code in the source code of your pages:
SR.tag(['tagName1', ' tagName2', 'tagName3' ]);
The last parameter between [] brackets coincides with a table featuring the list of tags linked to this video. Each element of the table must be declared as a string of characters between simple or double quotes.
You do not have to declare all your tags with a single call. You may call this script several times during the session, with a table containing only one value, i.e. your event name, as a parameter. Tags cannot be renamed: we therefore recommend defining a clear naming system for your tag labels.
Examples of programmatic tags coded in JavaScript
//automatic session recording tag for phone bugif($('.telephone-error').length>0){SR.tag(['phone-bug']);}
//automatic session recording tag for password bugif($('.password-error').length>0){SR.tag(['password-bug']);}
//automatic session recording tag for password bug with more detailsif($('.password-error').length>0 && $('.uppercase-error').length>0 && $('.number-error').length>0){SR.tag(['password-bug','uppercase-missing','number-missing']);}
//automatic session recording tag for user information//customer gender, type and loyaty cardSR.tag([window.datalayer[0].user_gender,window.datalayer[0].type,window.datalayer[0].user_loyalty_card]);
Filtering by tag
Tags linked to a video can be used to filter these videos in two different ways:
Via the list of recordings, using the Search field,
Via the video playback interface, to view a specific action during the recording playback.
Related articles
Creating a session recording
Viewing Session recording
View ArticleAB Tasty lets you save the data related to transactions made on your website (e.g. transaction amounts, payment methods, number of items purchased, etc.), along with information related to the purchased items (average cart value, item price, etc.).
This data is available in the reports of each campaign in the form of indicators or filters. For more on this, refer to New reporting: transaction indicators and e-commerce data.
To send transaction data to AB Tasty and display it in the reports, you need to add the transaction tag to your purchase confirmation page, after the generic AB Tasty tag.
Once the transaction tag is implemented on your website, you can go ahead and run the QA process. For more information, refer to QA the transaction tag.
Accessing the transaction tag
Go to the AB Tasty dashboard.
Click Global Code option, then click Settings>Tags implementation>Transaction tag.
Click Copy to clipboard and paste the code into the purchase confirmation page.
Change the settings based on your own data.
Tag composition
The transaction tag features two parts: the first enables the transmission of information related to the transaction (ID, name, amount, delivery fees, etc.) and the second enables the transmission of item or product details related to purchases made by customers visiting your website.
Transaction settings
The transaction settings coincide with the general information related to a purchase. If necessary, this information can be enriched with settings related to items.
The tid and ta settings must be declared during transaction tag implementation. The other settings are optional, however we recommend configuring them also in order to be able to apply the matching filters in the reports later on.
Parameter name
Meaning
Definition
Example
tid
Transaction ID
Coincides with the transaction ID.
tid: "OD564"
ta
Transaction affiliation
Coincides with the name assigned to the transaction as it will appear in the list of goals to configure.
ta: "Purchase"
tr
Transaction revenue
Coincides with the transaction amount. Includes taxes and delivery fees.
tr: 15.47
ts
Transaction shipping
Coincides with the delivery fees due.
ts: 3.5
tt
Transaction tax
Coincides with the taxes due.
tt: 2.60
tc
Transaction currency
Coincides with the currency used during the transaction.
tc: "EUR"
tcc
Transaction coupon code
Coincides with the discount coupon used during the transaction.
tcc: "Coupon"
pm
Payment method
Coincides with the payment method used during the transaction.
pm: "Paypal"
sm
Shipping method
Coincides with the delivery type.
sm: "Fedex"
icn
Item count number
Coincides with the total number of items purchased during the transaction.
icn: 12
Information related to the transaction amount and the currency is collected, however no currency conversion is applied. The values are displayed in the report just as they are collected on the websites.
For more on the JavaScript implementation of transaction settings, please refer to our developer documentation.
Item-specific settings
Information related to the purchased items can be linked to each transaction. In order to do this, you need to configure the item section of the transaction tag using the settings below in addition to those related to the transaction.
The tid and in settings must be declared. In particular, the tid setting must match the one declared for the main transaction.
Parameter name
Meaning
Definition
Example
tid
Transaction ID
Coincides with the transaction ID.
tid: "OD564"
in
Item name
Coincides with the item name.
in: "Shoe"
ip
Item price
Coincides with the item price.
ip: 3.5
iq
Item quantity
Coincides with the number of times an item was purchased during the transaction.
iq: 4
ic
Item code
Coincides with the items CKU (stock-keeping unit), i.e. the items reference code used for stock management.
ic: "SKU47"
iv
Item category
Coincides with the category the item belongs to.
iv: "Blue"
For more on the JavaScript implementation of settings related to items, please refer to our developer documentation.
Implementing the tag
We recommend implementing the transaction tag in the source code of your websites purchase confirmation page, as detailed above.
You can also implement the tag via a Tag Management System (TMS), which enables you to declare the transaction settings as well as settings related to items.
Finally, you may use the AB Tasty tag to automatically inject JavaScript instruction into your purchase confirmation page. In this case, you will use the Global Code functionality and won't need to modify your pages source code.
To use the Global Code option, apply the following steps:
Go to the test AB Tasty dashboard.
Click, then click Settings>Global Code.
Paste the transaction tag into the JavaScript code editor.
This editor enables you to add code to be applied to all pages containing the AB Tasty tag. You may then define the code to be injected into your purchase confirmation page.
Related articles
New reporting: transaction indicators and e-commerce data
QA the transaction tag
New reporting - Configuring goals
View ArticleOur program offers a method for selecting similar elements with just a few clicks. This can be very useful if, for example, you want to modify all the Add to cart buttons on a product listing page at once.You can use the similar function from the contextual menu.
When you select an element that shares a class with several other elements, this option is available as indicated below. You can then select all the elements sharing the same class with just a click.
View ArticleWhen configuring a test or personalization, there are 6 steps you need to follow before you can start your campaign and make changes accessible to your users.Targeting definition is step 4 of the test campaign configuration process and step 2 of the personalization campaign configuration process.
If necessary, you may enables you to configure the visitors who will see your changes, i.e. your campaign audience.
You must configure the page(s) on which the changes made via the variation editor will be visible to your visitors.
Once targeting is complete, you can run the QA process for your campaign via the targeting configuration page.
Displaying the targeting configuration screen
Test campaigns
From the dashboard, click Using the QA mode, then 4 Targeting.
From the variation editor, display the left-hand pane of the campaign and click 4 Targeting.
Personalization campaigns
From the dashboard, click, then 2 Targeting.
From the variation editor, display the left-hand pane of the campaign and click 2 Targeting.
Implementation
Campaign targeting configuration involves the following steps:
Configure an audience (optional step).
Select the target page(s) (mandatory step).
Audience
You must define at least one target page in addition to your audience.
There are several ways of configuring your audience :
Targeting all visitors,
Targeting a custom audience based on one or more targeting criteria and saving it if needed,
Using an existing audience.
Target pages
A URL is already defined by default: it coincides with the URL configured during step 1 - Main information. You can either use it as it is or change it as needed.
If necessary, configure the page URL:
Select the Include or Exclude operator,
Select the Corresponds exactly, URL ignoring parameters, Contains or Regular expression operator,
Enter the full URL of the page
Click Save step.
For more on configuring target pages as well as on the Apply when targeting conditions are met, All pages, Target by event, Target Code, Target by ID/Class/Element options, refer to Defining target pages.
Pour en savoir plus
Defining target pages
Defining your audience
Managing targeting criteria
View ArticleAB Tasty is a conversion rate optimization solution. It is based on the Saas model and its features include the implementation of A/B and multivariate tests as well as personalizations on your website, in view of improving your user experience.
Your test campaigns are implemented via a web platform, which can be accessed from any browser.
In order to access the AB Tasty interface, you will need a company-specific AB Tasty account, which you can log into with an email address and password.
Multiple users with specific access rights can log in to the account. (For more on this, refer to /hc/en-us/articles/200238417 )
Receiving account credentials
The account is created by the AB Tasty teams, along with the profiles authorized to use the account and log in to the platform.
When a new user is added to a customer account, they automatically receive an email with a login and password.
Access rights and user management
Logging in to the AB Tasty interface
To log into the AB Tasty interface, apply the following steps:
Click Log in in the credentials confirmation email,orOn the home page of the AB Tasty website.
Enter your email address in the login page that appears and click Next.
The process varies depending on whether you are using a secure connection (Single-Sign On) or a standard connection.
Secure connection
For security reasons, your company may choose to use SSO (Single Sign-On); a unique authentication system which enables you to connect to several platforms using the same email address and password.
When you use SSO, our platform takes care of linking AB Tasty to your professional portal.
Repeat steps 1 and 2 above.AB Tasty detects the domain of your address and automatically redirects you towards your company portal.
In the dedicated fields, enter your professional email address and password and click Log in:If you have access to the AB Tasty platform, the test dashboard is displayed.
Standard connection
Repeat steps 1 and 2 above.
Enter your password, then click Log in.The test dashboard is displayed.
If you have forgotten your password, click the Forgotten your password? link and enter your email address to receive a reset link and create a new password.
Logging in using multi-factor authentication (MFA)
Activate the multi-factor authentication (MFA) functionality via your account settings to configure an additional level of security during the login process (for more information, refer to Personal information).
Multi-factor authentication is only possible within the framework of a standard connection. If you are using single Sign-On, MFAisn'tnecessary as the connection is already secure.
Once configuration is complete, when logging in to the AB Tasty platform, apply the following steps:
Click Log in in the credentials confirmation email, or
Click Log in on the home page of the AB Tasty website.
Enter your email address and the provided password in the login page that appears.
Click Login, An authentication code is automatically sent via text message to the mobile number configured previously (for more on this, refer to Personal information>Multi-factor authentication (MFA))
Enter the 6-digit code in the relevant field,
Click Verify, The test dashboard is displayed.
Requesting a new code
The 6-digit code must be used within 2 minutes after the text message is received. If necessary, click the relevant link to receive a new code.
Saving the device
When multi-factor authentication is enabled, you can save the device used to log in to the platform.
To do this, during the second verification step, apply the following steps:
Enter the 6-digit code in the relevant field,
Check Dont ask for codes on this device,
Click Done,
You will no longer receive verification codes for this device and will be able to log in with just your email and password.
However, if you don't log in for 15 consecutive days, two-step authentication will be re-enabled and you will receive a verification code.
Learn more
User information
View ArticleAB Tasty is a mobile application which enables you to manage campaigns created using AB Tasty on your mobile telephone. This means you can carry out simple actions on existing personalizations or tests without logging into the AB Tasty platform.
This application is targeted towards people who want to retain control of their campaigns at all times. The AB Tasty mobile application enables you to review all your campaigns and, among other actions, to start or pause campaigns wherever you are and whatever the time of day.
The mobile application comes as a free option when you buy the AB Tasty web license and is compatible with iOS and Android (mobile only).
Using the dashboard
The applications interface is only available in English.
Accessing the application
To access the application, apply the following steps:
Using your mobile phone, go to the Play Store (Android) or the Apple Store (iOS).
Search for AB Tasty.
Download the application.
Open the application.
Enter your login in the Email field and your AB Tasty password in the Password field.
Click Log in.
You can also use the touch ID function (iOS) in order to login.
To login to the application, you need an AB Tasty account and to be the administrator of at least one account. Use the same credentials to log into the application.
If you have forgotten your password, click Forgot your password?.
Interface
Accounts
When you log into the application, if you are the administrator of two accounts or more, the list of existing accounts is displayed.
If you only administer one account, you will be taken straight to your campaign dashboard.
Dashboard
The dashboard features the following information:
the account name;
the number of live campaigns;
the list of existing campaigns.
Campaigns are always displayed in reverse chronological order and are loaded in sets of 10. When you reach the end of the tests, the following message is displayed: End.
To return to the top of the list, click the in the lower right-hand corner of the screen.
To refresh the page, tap and pull down and wait for the animation to end.
Menu
The hamburger menu in the upper right-hand corner enables you to carry out the following actions:
enable or disable the AB Tasty tag;
make changes to notification settings;
switch accounts;
log out.
Campaigns
When you click a campaign, the following information is displayed:
the icon related to the type of campaign;
the name of the campaign;
the status;
the number of visitors.
For security reasons, you will automatically be logged out of the application after 10 minutes of inactivity.
Main functionalities
The AB Tasty mobile application enables you to carry out simple actions on your existing campaigns:
Searching for a campaign
To search for a campaign:
Click the in the upper left-hand section of the screen
Enter the name of the campaign you want to search for:
The campaign is displayed.
If there are no matching search results, the following message is displayed:
Ooops ! You have no campaigns named x.
Filtering by test or by personalization
Unlike the AB Tasty website, you can filter your campaigns to display only tests (by clicking TEST) or only personalizations (by clicking PERSONALIZATION).
By default, the dashboard displays all the campaigns (ALL).
Just like on the AB Tasty website, a colored stripe on the left-hand side indicates the type of campaign: blue for A/B tests, yellow for multi-page tests, green for multivariate tests, blue for predictive tests and red for personalizations (refer to Using the dashboard ).
Starting and pausing a campaign
In order to start or pause a campaign:
Click the campaign.
Click the Play button to start your campaign (Push Play to make it live now) or the Pause button to pause it (Click to pause your campaign).
Refresh the home page to update its status.
Clearing and reloading the framework
If you think AB Tasty might be to blame for errors on your website, you can clear the framework (refer to Emptying the AB Tasty library in case of emergency ).
To clear the framework, apply the following steps:
Click the hamburger menu in the upper right-hand section of the screen.
Click Deactivate AB Tasty:
Click Deactivate AB Tasty again.
Click Confirm:
The AB Tasty tag is deactivated.
You can then reload the framework, i.e. reactivate the AB Tasty tag on your website to carry on running your campaigns.
To reload the framework, apply the following steps:
Click the hamburger menu in the upper right-hand section of the screen.
Click Activate AB Tasty:
Click Activate AB Tasty again.
Click Confirm:
The AB Tasty tag is reactivated.
Related articles:
Access rights and user management
Emptying the AB Tasty library in case of emergency
View ArticleThe Goals tab of a campaigns displays the main goal (transaction, pageview or action tracking) and the secondary goal (transaction) chosen in the goal configuration screen (step 3 of the campaign configuration process) of the AB Tasty platform.
The results related to each goal are displayed. For each goal, the Goals tab enables you to identify the best-performing variation(s).
For more on the mobile application, refer to The AB Tasty mobile application.
Mobile application - Overview tab
Accessing the Goals tab
To access the Goals tab of an A/B test, apply the following steps:
Go to the campaign dashboard and click an A/B test:The Overview tab is displayed.
Click the Goals tab to the right of the Overview tab.
So far, the Goals tab only applies for A/B tests.
Goal card
Each goal is presented in the form of a card and features the following information:
The goals nature (main or secondary)
The goals name (Menu click", for instance)
The goals category (Action tracking, for instance)
The goals displayed depend on the indicators selected in the goal configuration screen.
If the main goal is an Action tracking, pageview or transaction type goal, it will be displayed in the Goals tab of a campaign on the mobile application.
If the secondary goal is a transaction type goal, it will also be displayed.
If you have chosen goals that differ from the ones mentioned above, they will not appear in the Goal tab of the mobile application. However, you can view them in the campaign reports on the AB Tasty platform.
The cards are placed one after the other, from left to right. The primary goal card always appears first because it serves as a point of reference for the entire campaign and enables you to determine which variation takes precedence over the other(s).
The Goals tab displays one goal at a time.
To load another goal, hold it down and slide it to the left: the next goal is displayed along with its related data.
Results
When you select a goal, the related results are displayed.
Reports show the conversion rate as well as the improvement percentage of the campaign variation(s).
Its progress bars and color code enable you to easily identify the leading variation. The best-performing variation is shown in green and the worst-performing variation is shown in red.
Gain probability
The Explanation section displays the gain probability as well as an explanation as to which variation is the winner and what the odds are of obtaining these results again in the future.
The Gain probability enables you to ascertain the odds of a strictly positive gain on a variation compared to the original version. By default, the best-performing variation is displayed.
Use the button at the bottom of the screen to start or pause the test.
Related articles
The A/B Tasty mobile application
Managing notifications from the AB Tasty mobile application
View ArticleIntroduction
A/B Tasty is an intuitive A/B testing solution with advanced features. It allows you to modify website pages using a visual editor, without writing any code, and without technical knowledge. You can then measure which versions of your pages produce the best results for your objectives (pageviews, registrations, purchases, etc.). This quick start guide will help you as you create your first A/B test.
Using AB Tasty
There are five steps to setting up a test with AB Tasty:
Setting up the AB Tasty tag on all the pages of your site.
Creating the different versions of your pages ("variations") in AB Tastys WYSIWYG editor.
Configuring the testing options (in particular, the test target and the traffic affected by each variation)
Defining which indicators should be measured.
Running the test and reading the results.
Setting up the AB Tasty tag
Before you can run a test, you must install our tag on every page of your site. This is just a few lines of JavaScript. Dont worry, you only have to do this step once. learn more about reading and interpreting your test results Once the tag has been added, youdon'thave to worry about it anymore, because the same tag allows you to run all your future tests. Where do I find this tag and where do I install it? You can also consult our help section on technical questions if you have further questions.
Creating your variations with the editor
After the AB Tasty script has been added to your pages, log in to AB Tasty with your credentials. You can then access the Dashboard, which allows you to create your first test. This Dashboard will allow you to manage your tests in the future.To create your first test, click on the "Create" button. You will be invited to enter the URL of the page to be modified. After you click on the Save button, you are sent to the WYSIWYG editor, which will allow you to create your variations, modify your pages, and manage the test settings.A first variation, which is an exact copy of the original version, is created by default. You can navigate between the variations by using the tabs at the top of the editor. You can create as many variations as you wish by clicking on the New Variation button.Click on the "Variation 1" tab to activate it in the editor. When you move your mouse around on the page, you will see that the page elements are highlighted when you mouse over them. Left-click to select one of them. A contextual menu will appear, giving you several options to modify the selected element or refine your selection.Among the proposed modifications, you can:
Move the selected element,
Delete the element or hide its content,
Resize the element,
Change the text or HTML content of the element,
Change the styles associated with the element,
Change the selected links or images (jpeg, png or gif format),
Add elements (paragraphs, images, HTML code, etc.).
With the selection features, among other things, you can:
Expand the current selection,
Reduce the selection,
Select elements that are similar to the one that is selected.
Once you have selected an element, you can then apply a modification to it. Discover all the modifications offered in the editor. Use all of these features to modify your page as you wish. You can also use the advanced editing feature to edit the HTML code, modify the pages stylesheets, or add customized JavaScript/jQuery. To do this, click on the options Add CSS and Add JavaScript in the variation options.
Configure your test options
After you have prepared all of your variations, you need to configure the options that apply to the test. These are available from the left hand menu.They allow you to:
Target the pages on which your changes should be applied (ex: every page of one template),
Target the visitors who should see the test (ex: only visitors who come from one of your sponsored links),
Assign a percentage of your traffic to each variation.
To target your test, click on the "Targeting" link. You can access a window that will allow you to define certain target criteria on the page level or visitor level.You can target a test by URL, source type, visitor behavior, and more. Discover all the target methods offered. Finally, to define the percentage of your traffic to be allocated to each variation, click on the "Traffic Allocation" link. A window appears, allowing you to use sliders to attribute a specific percentage to each variation.If you have other questions, see our help section on setting up tests.
Setting up indicator tracking
Before you run your test, you need to define the objectives you wish to measure. In AB Tasty, you can measure three types of objectives:
Objectives of visitors engagement with your content. These objectives are measured with indicators like bounce rate, time spent on the site, and number of pageviews. These indicators are automatically calculated by AB Tasty, and youdon'tneed to set them up. Learn more about the engagement indicators.
Click objectives. You can easily measure the click rate on certain important elements you want to track, like your action buttons (ex: add to cart button). To do so, just select the element in the editor and choose the Track Clicks item. Give your click objective a name, and it will automatically be shown in the report interface when your test is run. Learn more about adding click tracking.
URL objectives. Similar to Google Analytics URL objectives, these objectives allow you to record that an objective has been met when a visitor sees a specific page (ex: checkout confirmation page). To create this type of objective, go to the tests report interface and click on the New objective button. You will see a window where you can indicate the URL formats of your objective pages. Learn more about adding a URL objective.
Reading the test results
After you have run your test, the results are shown in real time in the report interface. To see them, from the Dashboard, click on the Report button that corresponds to your test. The report interface is displayed in a new window like the one shown below.The main information displayed on the screen will allow you to quickly analyze your test results:
Test name
Launch date, number of visitors tested and test status (active, paused)
Test result sharing tools (send by email, PDF and Excel export, comment area, public address to access the results without an account)
List of objectives, with the following information for each:
Type of objective (action tracking, URL objective)
List of variations
Number of visitors for each variation
Number of conversions recorded for each variation
Corresponding conversion rate
Percentage of improvement over the original version
Statistical reliability of the data
You can also refine the test results by filtering your data through various criteria, such as the traffics origin, the visitors behavior, etc. Use the drop down menu below to adjust the filters for the analyses you want to perform.See our online help section to .
View ArticleThis is the list of all the targeting options available in AB Tasty along with how to use them and examples of their settings. The options are categorized by group:
URL targeting
Targeting based on traffic source
Behavioral targeting
Expert targeting
Browser targeting
URL Targeting
Purpose: default and required targeting allowing you to define pages that will be assigned to the test according to their URL format.
How to use it: specify a URL pattern, a target modifier (exactly matches, contains, regular expression) and/or an operator (Include, Exclude). You can find many resources on the Internet to learn how regular expression work and test your expressions (ex: http://rubular.com )
Sample settings:
Targeting based on traffic source
Type of source
Purpose: target only visitors who come from a specific type of source: direct access, referring sites, natural searches, paid searches (CPC Adwords).
How to use it: choose the source type in the drop down menu as well as the desired operator (Include or Exclude).
Sample settings:
Source
Purpose: target only visitors who come from a specific traffic source.
How to use it: specify the name of the source in the field as well as the desired operator (Include or Exclude). You can add several sources by clicking on the "+" button.
Sample settings:
Landing page
Purpose: target only visitors who have arrived at your site through a specific page.
How to use it: enter the URL or the URL pattern of the page through which the visitor entered the site to trigger the test on the page to be tested (the landing page is not necessarily the page being tested).
Sample settings:
Behavior targeting
Old/Returning visitor
Purpose: target only new or returning visitors. It is important to remember that this means new/returning visitors for testing purposes. When the test is started, all visitors are considered new visitors, because they have never seen the test before. Your pool of recurrent tested visitors will become progressively larger and the targeting will become more significant. If you wish to target old/returning visitors in reference to your web analytics tool, you should use cookie targeting instead, indicating the name of the cookie and the appropriate value.
How to use it: specify the name of the cookie that must be present on your site. Optionally, you can indicate the cookies value.
Sample settings:
Previous page
Purpose: target visitors who have seen a specific page just before the page being tested. This can be useful if the changes made to the test page have context only if the visitor comes from a specific page.
How to use it: as for URL targeting, indicate the URL of the previous page. You can use different methods to target this page (exactly matches, contains, regular expression).
Sample settings:
Minimum pages viewed
Purpose: target visitors who have seen, during their visit, a certain number of pages before the test page. This may be useful for targeting visitors who are already familiar with your site and who have already shown an interest in your offers/services.
How to use it: indicate the minimum number of pages that must have been seen in order to trigger the test. Use the Exclude operator to reverse the filters behavior.
Sample settings:
Number of visits
Purpose: target visitors who have visited your site several times. This may be useful for targeting visitors who have already shown an interest in your offers/services.
How to use it: indicate the minimum number of visits that must be made for the test to be triggered. Use the Exclude operator to reverse the filters behavior.
Sample settings:
Time since the first visit
Purpose: target visitors who are visiting your site for the first time in a certain amount of time. This may be useful for including or excluding recent visitors.
How to use it: indicate the number of days that must have passed since the users first visit for the test to be triggered. Use the Exclude operator to reverse the filters behavior (in this case, there must be no more than X days since the first visit to trigger the test).
Sample settings:
Time since the most recent visit
Purpose: target visitors whose last visit to your site occurred within a certain timeframe. This may be useful for including or excluding recent visitors.
How to use it: indicate the number of days that must have passed since the users last visit for the test to be triggered. Use the Exclude operator to reverse the filters behavior (in this case, there must be no more than X days since the latest visit to trigger the test).
Sample settings:
Same-day visit
Purpose: target visitors who have already visited the site today. This may be useful for targeting visitors who have already shown interest in your offers/services, and for taking advantage of their recent visit to offer them an incentive for conversion.
How to use it: check the box to activate the targeting.
Sample settings:
Expert targeting
Having the cookie
Purpose: only trigger your test if the user has a cookie in his browser. There are many potential usage cases. For example, you can validate your test by targeting a specific cookie (name/value pair) that you create in your browser, and allocating 100% of the traffic to your variation. To create a cookie, type an instruction in your browser like: document.cookie="validate_test=1". In another example, you are using Google Analytics and you want to target visitors coming from a specific source. You can target the Google Analytics cookie, placed on your site, which stores this information (cookies name: __utmz, value: utmcsr=example)
How to use it: specify the name of the cookie that must be present on your site. Optionally, you can indicate the value of the cookie. The value field accepts regular expressions.
Sample settings:
Geolocalization
Purpose: limit your test to a geographical area. We are using an IP geolocalization database provided by an external service (MaxMind) to offer this feature.
How to use it: first, indicate the country to target. Once you have chosen the country, you can refine your target by specifying a region and a city.
Sample settings:
JavaScript
Purpose: if URL targeting is not possible because no URL has an identical format, you can still set up the test to be triggered when a JavaScript variable is present, or if a JavaScript instruction returns a True result. For example, if there is a global variable, you can test for its existence as indicated in the example below.
How to use it: in the field, indicate the JavaScript instruction that must return True for the test to be triggered. JQuery instructions are acceptable.
Sample settings:
Customized variables
Purpose: target your test based on the value of certain variables that you define in your web analytics tool. If, for example, you define a customized variable as soon as a visitor logs in to your site and that variable indicates that the user is a buyer, we can recover this information to target your test (this requires configuration on our end, so contact us to set this up).
How to use it: indicate the name of the customized variable and the value that it must have to trigger the test.
Sample settings:
Browser targeting
Browser
Purpose: limit your test to a type of browser, or exclude a specific version of a browser if the changescan'tbe handled by that version (ex: CSS 3 rules in Internet Explorer < 9, ...).
How to use it: select a type of browser from the drop down menu (Firefox, Chrome, ...) and optionally, a version number. You can also indicate a specific User-Agent by selecting the "Custom" option.
Sample settings:
Browser language
Purpose: limit your test to a specific language group.
How to use it: select the language to target from the drop down list. Targeting is done based on the browser language, and is not related to the geographical location of the user. This option may be paired with geographical IP targeting to reach the desired targets.
Sample settings:
Device (PC, Telephone, Tablet)
Purpose: run tests only on mobile or tablet versions of your site.
How to use it: select the device type to be included or excluded in the test from the drop down menu. You have three choices: PC, telephone, or tablet. If you need to target a specific device model (ex: iPad), you would use a browser target instead, specifying a particular User-Agent. Note: tests are run on the mobile version of your website, and not the corresponding apps. At the present time, we do not handle tests on iPhone, iPad, or other apps.
Sample settings:
View ArticleThe AB Tasty program runs entirely on JavaScript (jQuery) and functions independently from server side development languages (PHP, ASP, JAVA, RUBY, .NET).Your site doesnt need to call the jQuery library to make AB Tasty work. Our program includes a version of jQuery by default to apply the changes to your pages. Therefore, youdon'thave to use jQuery.If you are already using jQuery, we will still load our own version in order to take advantage of the frameworks recent functions and updates. You can configure AB Tasty to not load its version of jQuery, and use yours instead. This will allow you to drop a few milliseconds off of your load time. To do this, go to your account settings, then in the "Library" tab, uncheck the "Add jQuery to my site" box. Important: in this case, the AB Tasty tag must be placed after your jQuery call in your pages source code.If your site already uses a JavaScript framework other than jQuery (ex: MooTools, Prototype, Script.aculo.us), there will be no compatibility problems, because we use jQuerys noConflict() function. Also, AB Tasty uses only local variables, not global variables.AB Tasty works in synchronous and asynchronous mode. The call to AB Tastys library works in synchronous mode in order to apply the changes as quickly as possible. But all the information collection happens in asynchronous mode, because the immediacy of these processes doesnt matter, as it does for the application of the changes.
View ArticleThe following information related to your user profile can be modified: your first/last name, the interface language and the enabling of multi-factor authentication (MFA).
To access this information, apply the following steps:
Click Logging in to the AB Tasty platform,
Then clickProfile,
Make the desired changes,
Click Save to save your changes.
Last name and first name
To change your last name and/or your first name, apply the following steps:
Enter the relevant information in the First name and/or Last name field,
Click Save:This information is visible when you click.
The email address cannot be modified via the interface. To add a new email address, please contact your CSM.
Interface language
The AB Tasty platform is available in 5 languages: French, British English, German, Spanish and American English.
You can configure the default language of the interface to suit your needs.
To do this,
Click the drop-down list of the Language field,
Select one of the 5 languages on the list,
Click Save to save your changes.The interface is updated and displayed in the selected language. When you next log in to the interface, the configured language will be used.
Changing the password
If necessary, the password can be changed manually.
To do this,
Enter your current password in the Old password field,
Enter a new password in the appropriate field,
Enter it again in the Confirm password field,
Click Save to save your changes.
If you enter different passwords in the New password and Confirm password fields, the Save button will remain inactive until both passwords are identical.
Multi-factor authentication (MFA)
To benefit from this option, please contact your sales manager.
Multi-factor authentication is a two-step process for verifying the identity of people who log in to the platform: via their email address, and via a verification code sent to them in a text message.
Enabling authentication
Click the Enable multi-factor authentication button,
Enter your mobile number in the window which appears,If necessary, use the drop-down list to select your countrys calling code.
Click Send,A text message with a verification code is sent to the configured number.
Enter the AB Tasty verification code in the relevant field,
Click Verify,The Multi-factor authentication is enabled option is displayed.
Once multi-factor authentication is enabled, users wanting to log in to the AB Tasty platform will be asked to provide their email address and password, as well as a verification code sent to them via text message.
For more information, refer to Logging in to the AB Tasty platform.
Disabling authentication
Click the Disable multi-factor authentication button,A confirmation message is displayed.
Click Yes, disable to confirm,If you don't want to disable multi-factor authentication, click Close.
Learn more
View ArticleDefining an audience for one of your campaigns means creating a group of users and assigning targeting criteria to them.
Only visitors who meet these criteria will see the changes configured in the test or personalization variations.
Principle
The Purchase frequency targeting criterion enables you to restrict the visibility of a campaign to visitors based on the frequency of the purchases made within a defined period of time.
You can also refine targeting by adding advanced criteria, thus defining the purchase frequency as a function of the:
payment method;
delivery method;
SKU code of the product;
product category;
transaction amount;
coupon used.
The Purchase frequency criterion is based on the transaction tag, which enables you to collect specific information on the buying patterns of users and is linked to the new collection.
Accessing the targeting criterion
To access the targeting criterion, apply the following steps:
Select Custom audience from the drop-down list.
Click Add a criterion.
Select Purchase frequency.
Defining target pages
Implementation
You need to have defined your target pages and created a user group beforehand.
To configure the Purchase frequency criterion, apply the following steps:
Go to the list of targeting criteria, place your cursor on Purchase frequency and click Add.
Select the type of interval from the first drop-down list: more than or less than.
In the Purchase(s) field, manually enter the number of desired purchases.
Select the interval from the second drop-down list: The last, more than or between.
In the Day(s) field, manually enter the value(s) depending on the chosen interval.
Save your targeting.
For data confidentiality reasons, you cannot target visitors who made purchases more than 365 days ago.
Advanced targeting
To access advanced targeting criteria, apply the following steps:
Click Add a variable.
Select the type of variable from the drop-down list: Payment method, Delivery method, SKU code, Product category, Amount, Coupon.
To add another variable, click Add a variable again. The AND selector is added automatically.
For extremely precise targeting, you can combine all 6 variables.
Variable type
Use
Payment method
The payment method used by the buyer (credit card, PayPal, gift card, etc.).
Delivery method
The delivery method chosen by the buyer (regular mail, pick-up location, in-store pick-up, etc.).
SKU code
The products unique code.
Product category
The category of the product purchased.
Amount
The transaction amount in numbers. The currency used here is the one configured for your website.
Coupon
The possible use of a coupon by the user or its title.
The chosen criteria apply to all purchases.
Based on payment method
To target a purchase based on the payment method used, apply the following steps:
Select Payment method from the first drop-down list.
Select matches or does not match from the second drop-down list.
In the Value field, manually enter a payment method (credit cart, PayPal, gift card, etc.).
Based on the delivery method
To target a purchase based on the delivery method used, apply the following steps:
Select Delivery method from the first drop-down list.
Select matches or does not match from the second drop-down list.
In the Value field, manually enter a delivery method (regular mail, pick-up location, in-store pick-up, etc.).
Based on the SKU code
To target a purchase based on the products SKU code, apply the following steps:
Select SKU code from the first drop-down list.
Select matches or does not match from the second drop-down list.
In the Value field, manually enter the code that matches the product you want to include or exclude from targeting.
Based on the product category
To target a purchase based on its product category, apply the following steps:
Select Product category from the first drop-down list.
Select matches or does not match from the second drop-down list.
In the Value field, manually enter the category of the product you want to include or exclude from targeting.
Based on the amount
To target a purchase based on the product price, apply the following steps:
Select Amount from the first drop-down list.
Select between, more than or less than from the second drop-down list.
In the Currency unit(s) field, manually enter an amount in figures.
The currency used here is the one that is used on your website.
Based on the coupon
To target a purchase based on the coupon used, apply the following steps:
Select Coupon from the first drop-down list.
Select matches, does not match, was used or was not used from the second drop-down list.
For the first two options, manually enter the exact coupon title in the Coupon code field.
Configuration example
TARGETING GOAL
All visitors who have made more than two purchases with in-store pick-up over the last two months.
CRITERION CONFIGURATION Last purchase
Value: more than
Number of purchases: 2
Interval: Less than
Number of days: 60
OPTION Add a variable
Variable: Delivery method
Setting: matches
Value: In-store pick-up
TARGETING GOAL
All visitors who have made at least ten purchases over the last twelve months.
CRITERION CONFIGURATION Last purchase
Value: more than
Number of purchases: 10
Interval: Less than
Number of days: 365
TARGETING GOAL
All visitors who have made at least four purchases in the Kitchen category, spending at least 50 over the last three months.
CRITERION CONFIGURATION Last purchase
Value: More than
Number of purchases: 4
Interval: Less than
Number of days: 90
OPTION Add a variable
Variable: Product category
Setting: matches
Value: Kitchen
AND
Variable: Amount
Setting: more than
Value: 50
TARGETING GOAL
All visitors who have purchased at least three products using a coupon between the last six months and the last twelve months.
CRITERION CONFIGURATION Last purchase
Value: More than
Number of purchases: 3
Interval: Between
Number of days: 180 and 365
OPTION Add a variable
Variable: Coupon
Setting: was used
Related articles
Defining your audience
View ArticleSometimes, you might want to launch a test after a user completes a certain action on your site, for example after they have clicked a certain button, or after they have spent a certain length of time on a given page.
You can condition a test in this way using the JavaScript function ABTastyStartTest. This function takes a single, unique parameter: the ID of the test you would like to launch. It must be called after the AB Tasty tag.
The function takes the following form:
ABTastyStartTest(testID); // where testID is the ID of the test to be launched
This function must be called as soon as each visitor has completed the action on which the test is conditioned. Note: the tested page must be the page on which the action takes place (you cannot test modifications on another page).
To create a test conditioned on an event, you must:
1) Create a standard test, applying your desired modifications
2) Tick the checkbox "Target by event" in the targeting options window, in the same box as the URL targeting options. Note that other targeting options will no longer be available
3) Set up the rest of your test as usual
4) Launch your test
5) Call the function ABTastyStartTest directly from your application whenever the event occurs.
For example, if you would like test 12345 (set up in advance) to be triggered by a click on a button, you can do this in the following way:
<button onclick='ABTastyStartTest(12345)'>Launch a test from this button</button>
You can use any other method which links this function to an event. For example, you could use jQuery, or a callback function might be used if your site uses AJAX.
View ArticleIf you want to conduct a test on only those pages contain a particular element, whose presence cannot be determined by URL, you can target by "ID/class/element".
All you need to do is identify, via the source code of your pages, the ID or class associated with the element in question, then indicate it in the test targeting window. With the help of a dropdown menu, you can also select from a list of all the classes or IDs defined in the page which is loaded in the editor.
Make sure that the element that you select here is specific to the pages that you want to target, and is not present on other pages, which would then be included in the test.
In the example below, the test is targeted on all the pages from the domain example.com containing an element with the class "detail".
View ArticleThis feature allows you to require the presence of one or more elements for the test to run. To apply this: select an element in the WYSIWYG editor, and then in the contextual menu, click on Add to targeting
When you click on "Add to targeting", a confirmation window pops up to tell you that the element has been added.
If you wish to delete an element that has been added to the targeting, go to the step 3 of your test to access the targeting options.
The window that appears contains all the targeted elements. Just delete the one or ones you wish to cancel.
View ArticleBesides URL targeting, you can target a test to only those visitors who come from a specific traffic source. So you can assign visitors to your tests when they come from your sponsored links, your Facebook ad campaigns, or a specific email campaign. You can use one of the four available sub-criteria:
Source: the source from which the visitor arrived on your site. This is calculated in the same way as in Google Analytics (domain name when the medium is the referrer, search engine if it is an organic medium). If your traffic acquisition campaigns are tracked properly, you can use these criteria, for example, to run a test only for visitors who come from one of your newsletters.
Originating keyword: the key search term or terms the visitor used to arrive at your site. For example, you can run tests for visitors who typed the name of your brand or its variations to access your site. On the flip side, you can target visitors who access your site through generic requests, using the Exclude operator and specifying your brand in the "Originating Keyword" field.
Landing page: apply the following configuration for your PPC (pay-per-click) campaigns.
Source type: the type of source from which the visitor arrived at your site. We distinguish four standard types of sources: direct access, referrer link, Google-sponsored link, natural search. The visitor is assigned to one of these source types based on a series of conditions performed on the referrer, like in Google Analytics.
It is important to note that the conditions relative to traffic acquisition are related to the visitor and not the page being tested.
View ArticleYou can use e-commerce data in the targetings of your various tests by creating segments.For example, you can target your tests to only those visitors who have bought a particular type of product or who have used a specific method of payment.
First, you must install the transaction tag. Refer to Installing the transaction tag for more information.
Setting-up the E-commerce option
To use the E-commerceoption in your targeting, do as follows:
Go to theTargetingstep of your test
Click onAdd targeting
Select Visitors behavior>E-commerce
Select the option E-commerce and click onAdd
Enter the variable and value of your choice
View ArticleDefining an audience for one of your campaigns means creating one or more groups of users and assigning targeting criteria to them.
Only visitors who meet these criteria will see the changes configured in the test or personalization.
Principle
The Data layer targeting criterion enables you to display or hide a variation from users as a function of the page they are viewing or the actions they carry out on your website based on the data available in your data layer.
In order to be able to use this targeting criterion, you need to configure your data layer via your account settings.
Integrating your Data layer into your AB Tasty account
The Data layer option is included in our commercial Growth offer. For more information, please contact your sales representative.
Accessing the targeting criterion
To access the Data layer targeting criterion, apply the following steps:
Select Custom audience from the drop-down list.
Click Add a criterion.
Click the Expert category.
Place the cursor on the Data layer criterion and click Add.
Ifyou'veconfigured one of the tag management solutions supported by AB Tasty (i.e. TagCommander, Tealium or Google Tag Manager), its name is coupled with the Data layer targeting criterion.
Implementation
You need to configure your data layer via your account settings beforehand.
The information included in your data layer coincides with a type of data or actions related to a variable or a label. It is available in the form of a key and a value in the targeting configuration interface.To configure this key/value pair, apply the following steps:
In the Key field, enter the type of data you are looking for.
Select the relevant operator from the drop-down list.
In the Value field, enter the desired variable.
If necessary, click Add a variable to configure an additional key/value pair.
Select the AN or OR Boolean operator as a function of the desired result.
Save your changes.
You do not need to be familiar with the structure of your data layer. The keys are collected automatically every 24 hours by the AB Tasty tag and the Key field has an auto-complete feature: the names of all the keys in the data layer are suggested as you type.
Configuration example
You are looking to display a discount coupon for all visitors viewing products worth over $200 in the Furniture category. In your data layer, product prices, for instance, are identified by the product_price key, and product categories by the product_category key.
In the Key field, enter product_price .
Select theHigher thanoperator from the drop-down list.
Enter200in theValuefield.
ClickAdd a variable.
In the Keyfield, enterproduct_category .
Keep the equals default operator.
EnterFurniturein the Valuefield.
Select the AND Boolean operator.
Save your changes.
Specific case of TMS in asynchronous mode
If you decide to implement your TMS in asynchronous mode, this may increase the flickering effect on your website.
This is why, as for the AB Tasty tag, we recommend implementing your TMS and your data layer in synchronous mode or even in server-side mode to avoid all risk of flickering on your website.
Related articles
View ArticleBefore you start a test, we recommend that you go over the following points in order to avoid wasting time debugging it when its running:
Check that the AB Tasty tag is present on all of the sites pages. If your site is not fully tagged, and one of your tests targets a page where our tag is not present, your modifications will not be applied to that page.
Verify the target of your test; this is the most common error. You must have a good understanding of the various URL formats on your site to correctly configure URL targeting. Use the Exactly matches, Contains, Regular Expression, Include, and Exclude operators judiciously to target the correct URLs. Your target must not be too broad or too specific, depending on the desired case.
Verify the other target options and the possible presence of excluded IPs at the testing or account level.
Use the preview feature available in the menu of each variation to test your changes on any page or browser. Refer to this article to learn how to use this feature: Verify a test before rollout
Reset your test to "live" on your live site by changing the target options. To do this, set your test to target only visitors who have a specific cookie (ex: check-test=1), allocate 100% of the traffic to one of your variations, and run the test. Load the page you wish to test, and delete your cookies. Use your browsers development console to recreate the cookie that will allow you to see the test. Enter the following command in the console: document.cookie = "check-test=1"; Reload the page to see the test, and check that everything is working properly. How do I know if a page is showing a test?
If youcan'tsee the test with the previous method, make sure the test is correctly targeted. Use the ABTastyTests and variations commands in the browser console to do this. For more details, read this article:
Make sure you have properly defined the tests objectives, whether they are click objectives (tracking action) in the editor, or URL objectives in the report interface. Remember that even though you can create URL objectives after the fact, youcan'tdo the same for tracking actions, which must be defined before the test is run.
If you start your test and see errors in the display, keep the following elements in mind when you are debugging:
If you modify one of your tests while it is running, you must validate the publication of the changes by clicking on the Publish button at the top right of the editor. Without this validation, your changes will not be taken into account.
After you have started a test or validated a change, it may take up to ten minutes for the script containing your changes to be updated on our CDN. So wait at least ten minutes before checking whether your changes have had the desired effect.
Your browsers cache content and your cookies may disrupt test debugging. Make sure to delete them before trying to see why your changesaren'tshowing up.
As a general rule, if you wish to make further changes to your pages such as changing block layout, it is recommended that you make these changes with JavaScript/jQuery code rather than using the graphical editors features. You can make your changes with fewer steps and avoid creating duplicate sets of changes that might overlap or cancel each other out.
View ArticleThe AB Tasty solution requires 2 cookies to be placed in the browser of users subjected to tests.
ABTastyThis cookie sends all test data (visitorID, test and variant IDs, timestamps).It has a lifespan of 13 months.
ABTastySession
This cookie allows us to identify a unique session. It allows us to determine that a new session has begun for a given user. It lasts for the length of the session.
The solution includes the possibility of modifying cookies length of validity. For this, go to Advanced settings, then go to Cookies.
If the user does not wish to participate in tests, they can opt-out by adding the #abtastyoptout=1 parameter at the end of the URL of the site in question.
For example:http://www.abtasty.com/#abtastyoptout=1
Using this parameter creates a cookie in the browser in order to store the opt-out information.Other than cookies, the AB Tasty tag stores the list of URLs visited locally in the browser via LocalStorage and SessionStorage. This storage allows us to perform complex visitor segmentation.
For AB Tasty, using cookies ensures that the solution can function correctly and guarantees that the tests carried out are reliable by recognising a visitor as unique each time they visit (remembers that it is the same visitor without actually knowing who it is). In particular, the cookies log which version of the test the visitor is using, with the sole purpose of being able to direct them back to the same version during future visits. This system allows us to avoid causing behavioural differences and consequently lead to misleading results. Under no circumstances do these cookies store any information that identifies visitors.
All the results obtained are compiled and remain fully anonymous. The results focus on user browsing and behaviour: number of visitors, visits, numbers of pages viewed and other information required to measure the performance of each webpage version during a test. They are used to improve the ergonomics and content of the sites visited.The AB Tasty solution uses "first party" cookies, i.e. they are set by the URL of the website using the AB Tasty service.
View ArticleYou can exclude an IP address or a range of IP addresses that will not be assigned to your test. For example, indicate your companys networks IP address and/or those of your partners so their visitsdon'tinfluence the results. You can exclude IP addresses in two places:
At the account level, to exclude IPs from all of the tests associated with this account. You can set this up in the account options.
At the test level, to exclude one or several IPs for this test only. You can set this up directly in the editor.
1) Excluding an IP at the account levelIn your account settings, choose the "Exclude IPs":
Click on the "Range of IP addresses" to exclude several IP addresses.
Then click on Add so the IP addresses will be excluded during your next tests. Excluding IP addresses is not retroactive, so your addresses will not be excluded for tests that are currently running or those that are already finished.2) Excluding an IP at the test levelGo to the targeting options of your test tab and click Visitors>IP address.
Click Add.Add the IP address to exclude or include, and click on OK.
To add a range of IP addresses, click on and add the various IP addresses to exclude or include. Excluding or including IP addresses through the editor is not retroactive, and will therefore only apply to new visitors to the test.
View ArticleCross-domain tracking helps you follow the user even if one or more pages are on a different domain name than the original one. Cross-domain tracking is necessary when a site has a page (payment confirmation, for example) that sends a user to an external domain.
This option is of the utmost importance if we wish to track the user and take advantage of statistics on this page that is outside of the site.
To set up cross-domain tracking, click on the "Settings" button in the menu, then click on the "Advanced" tab and go to the "Cross-domain tracking" section.
Just add a URL pattern as a setting for pages hosted on other domains. Then click on Add, and validate your change.
Here is an example of cross-domain tracking:
View ArticleBy default, the AB Tasty tag loads a static JavaScript file with the jQuery library onto your website. There are 3 options for configuring jQuery loading.
To do this, apply the following steps:
Click Settings, then Framework,
Go to the Load jQuery section,
Choose one of the three options:
Load AB Tastys jQuery
Do not use jQuery
Load my own jQuery
Loading options
Load AB Tastys jQuery
This option is enabled by default. It loads the AB Tasty jQuery library in addition to the potential existing library on your website.
Do not use jQuery
This option disables all jQuery libraries on your website.
Load my own jQuery
This option enables you to load only your version of jQuery and to disable the AB Tasty library. This decreases the weight of the AB Tasty script by 30 KB.
In this case, the AB Tasty tag must be placed after your jQuery call in the source code of your pages and you must be using version 1.7.1 of this framework or above.
View ArticleTo allow you to see whether AB Tasty is the cause of errors on your site, we have created a feature that allows you to empty the AB Tasty library.
What this does is delete the content of the JavaScript file that is normally called to apply the modifications. In other words, the AB Tasty tag is still present on your site, but the file it calls is empty of any JavaScript instructions, so it cannot cause any errors on your site.
If errors persist on your site after you have emptied the AB Tasty library, you can eliminate AB Tasty from your investigations and look for other sources of errors.
Heres how to empty the AB Tasty library:
ClickSettings.
Click Framework.
ClickClear framework.
The entire AB Tasty folder is emptied of its content within two minutes.
Important: emptying the AB Tasty library doesnt delete the tests from your account; they are just temporarily deactivated. The report data is not deleted either.
Once you have debugged your site, you should restore the AB Tasty library so you can continue to run your tests. To do so, just click on the warning message at the top of the interface. After a few minutes, AB Tasty will be functioning once again and your tests will start running.
View Article
Working at AB Tasty
Recently Asked Questions
- How long do the interviews usually take at Alexander Mann Solutions?
- What is Rippling's policy towards pets in the workplace?
- What are the most important soft skills to be successful at LA Fitness?
- How long after an interview at Rippling does it take to hear back?
- How long after an interview at Hygiena does it take to hear back?