A patch enables you to temporarily correct an element on your website, either to fix an issue or to bypass a long release process for a UX improvement.
A patch lets you quickly force a fix (remove a functionality, change wording, update wrong information) and ensure its visibility to all your traffic.
It also enables you to rapidly push a winning variation (from an A/B test) into production without the help of your technical team. This way, developers can take some time to deploy a qualitative and optimal new functionality without losing time to market. When the fix goes in production, you can pause your patch campaign and archive it.
A patch is not a personalization for the following reasons:
- There is no data collected: no reporting, no goals, no tracking. The only provided information is the number of unique visitors who have seen the patch (in the dashboard).
- There is no specific segment: a patch is displayed to all your visitors and all your traffic. But you can use the trigger library if needed (to display the patch on mobile devices only, for instance).
🚩 Heads up
We recommend letting your patch campaign run for the shortest time possible. Indeed, the fix you made is on AB Tasty’s side and can be outdated. When you have the available resources, you should hardcode the modifications directly on your website.
The patch campaign is accessible from the test dashboard via the Create dropdown menu.
Here are some tips for a successful set-up:
- MAIN INFORMATION: We recommend adding a description to your campaign to add useful information you want to share with your team. For example: “This patch will fix a typo error on product # 447 158”.
In the URL field, enter the URL you want to load in the editor.
- EDITOR: Make your changes as usual via the code (JS, CSS) or visual editor. You can’t add trackings because patch campaigns have no reporting and are aimed at following performance. To create commercial messages, create a personalization campaign.
You can’t create other variations because the aim is to create a unique fix.
- GOALS: This type of campaign doesn’t allow you to configure any goals.
Segment: You can’t choose a specific visitor segment; your campaign will be visible to all your visitors.
Page(s): Define the page(s) you want to patch by selecting the right saved page(s), custom page(s), custom code, Id/class/element criteria.
Trigger: This section is optional but useful to display your campaign according to specific conditions (for instance a specific device or region, a number of pages viewed).
- TRAFFIC ALLOCATION: This step is not available for patch campaigns, meaning that 100% of your traffic will see your patch.
- QA: QA is a fundamental step to make sure that the correction(s) appear correctly. For more information, refer to Using the QA assistant.
🚩 Heads up
In AB Tasty, you can display campaigns even if your visitors have not yet given their consent. For patch campaigns, no data is collected but, by default, they are displayed only when the visitor has given their consent. To display patches to all visitors including those who have not yet given their consent, go to Settings > Cookies > Cookie deposit and check the Patch box. For more information, refer to Managing your visitors’ Privacy.
💡 Use cases
Use case 1: Creating a patch from scratch
You can create a patch from scratch, for example:
- To correct a typographical error
- To modify a legal mention
- To add a health message
- To hide a CTA (e.g.: when experiencing a stock shortage)
Use case 2: Transforming a winning test variation into a patch
To transform a winning test variation into a patch, apply the following steps:
- From the dashboard, hover over the test you want to use as a reference for your patch.
- Click and Duplicate.
- Choose Patch from the first dropdown menu.
- Choose the variation you want to push to 100% of your users (the winning one) and validate:
Your patch appears in the test dashboard.
Your campaign set-up is imported from the source test but you can add or modify information if needed. Make sure you have a description of your patch campaign.
⭐ Good to know
You can also duplicate the winning variation of a multipage test into a patch. In this case, you must create one patch per page as this type of campaign does not allow you to have several pages.
Need additional information?
Submit your request at firstname.lastname@example.org
Always happy to help!