The Performance Center enables you to monitor the size of your generic AB Tasty tag. It displays a list of seven guidelines to follow in order to enhance the tag’s performance on your account.
Good to know 💡
You can also check the tag’s size in the network tab of your browser by searching for the try.abtasty.com/identifier.js file.
From there, you can see the global performance of your AB Tasty tag. Next to "Performance guidelines", you find the number of improvements needed to achieve global performance:
- 0 improvements to go:
All guidelines are respected (optional points are not taken into account).
- Between 1 and 5 improvements to go:
At least one guideline is not respected (optional points are not taken into account).
Each guideline displays a status, showing whether it is currently respected.
Here are the seven points you must monitor to ensure good tag performance:
- Tag weight
- Heavy campaigns
- Targeting verification
- Old widget version
- Old campaigns running
- jQuery injection
- Global Code size
- Campaign loading
- Enablement of framework auto-reload (optional)
- Activation of cross-domain tracking (optional)
✅ Guideline: Tag weight should be under 125 kB.
📝 Explanation: A heavy tag is mechanically slower to download and thereby may affect your website performance.
⚙️ Resolution: Follow the guidelines listed below.
✅ Guideline: Campaigns should not contain too much code.
📝 Explanation: The more code you add to your campaigns, the larger it will be and the heavier the global tag. In addition, large chunks of code take time to be analyzed by the browser and this may slow your website and cause a flickering effect. We recommend that you do not manage heavy page reformatting with AB Tasty, and that you avoid inserting large files such as images or lists and tabs directly into the editor. If you need external resources, you can host them directly on your website.
⚙️ Resolution: Go to each listed campaign to review and pause them or remove unused code.
✅ Guideline: Only use the regular intervals verification option when necessary.
📝 Explanation: When setting up the targeting of your campaign, you can choose if you want your conditions to be verified on page load or at regular intervals until they are met. The latter option may be useful when some conditions trigger after the page loads, but this has a major impact on your website’s performance. This feature will be withdrawn at the end of the year (2021) and alternatives will be introduced. However, we recommend pausing or adapting the campaigns still using it.
⚙️ Resolution: Go to each listed campaign to review it and consider using the When the page loads option if possible.
Old widget version
✅ Guideline: Certain widget versions are outdated and should no longer be used.
📝 Explanation: We constantly update our widgets to make them lighter and more efficient. When running an old campaign or duplicating a campaign, you may have an old version of a widget that adds weight to your campaign and global tag.
⚙️ Resolution: Go to each listed campaign to review and reupload the latest version of the widget from the widget library.
Old campaigns running
✅ Guideline: Old campaigns should no longer be running on your account.
📝 Explanation: Letting a campaign run for several months is rarely best practice for the following reasons:
- The changes you made in your old campaigns may be different from what is now hardcoded on your website and you may have forgotten that these campaigns are still running.
- Old campaigns are adding unnecessary weight to the AB Tasty tag.
⚙️ Resolution: Hardcode the modifications of your campaign(s) on your website, pause the campaign(s) or replace them.
✅ Guideline: If you don’t need jQuery, remove the jQuery injection.
📝 Explanation: When using AB Tasty, you may want to create your campaigns using jQuery. To do this, you can either use the version of jQuery already implemented on your website or use AB Tasty to inject its own version directly into the tag (approximately 40 kB). We highly recommend you don’t select this last option as it will add a lot of additional weight to your tag.
⚙️ Resolution: Go to your account settings and select Do not use jQuery or Use my own jQuery.
Global Code size
✅ Guideline: Global Code should not contain more than 1,000 characters.
⚙️ Resolution: Open your Global Code and remove any code that is unused.
✅ Guideline: Set each individual campaign to be downloaded only once its targeting is valid (the deferred campaign feature).
📝 Explanation: By default, all your live campaigns are included in the AB Tasty tag. You may not want all your visitors to download all the campaigns. Using the deferred campaign feature allows you to purposely delay a campaign so that it is not included in the tag. For more information, refer to Using deferred campaigns.
⚙️ Resolution: For each campaign you want to defer, go to Advanced options (step 6) and select Deferred in the Tag Performance Optimization section.
Enablement of framework auto-reload (optional)
✅ Guideline: If this feature is not needed, disable it.
📝 Explanation: To handle Single Page Applications (SPA) and some other website technologies, the framework auto-reload feature is activated by default. This means the tag is looping every 100 milliseconds to ensure your visitors haven’t switched pages, which would lead to a reassessment of the targeting.
⚙️ Resolution: Go to your account settings and select Enable the automatic reload of the framework > No.
✅ Guideline: Disable this feature unless you are running your tag on several domains.
📝 Explanation: Cross-domain tracking can be useful if you are running the AB Tasty tag on several domains (not including subdomains). However, enabling this feature adds an additional piece of code to your tag.
⚙️ Resolution: Go to your account settings and delete cross-domain tracking if not needed.
What is it?
The Campaign Performances page is a feature on our platform that provides a detailed and campaign-centric view of your campaigns and their impact on your overall tag performance.
Where to find it?
It is a sub-page of the Performance Center, which is accessible by clicking on the right-side corner of your screen.
You can access it by clicking on the "Campaign Performances" tab in the main navigation menu.
Campaign performance features
This page shows all your recent campaigns, including those that are currently live, live in QA, or have been paused within the last 30 days. They are sorted in chronological order, with priority given to those that need optimization. With this page, you will be able to identify which campaigns need optimization and take action to improve their performance.
Some of the key features include:
- Loading method: This feature tells you the loading method the user has chosen for the campaign, whether it is loaded instantly or deferred. This information is provided for the user to confirm their choice.
- Widget version: This feature shows whether a campaign is using an outdated widget. Outdated widgets can affect the performance of your campaigns.
- Targeting verification: This feature checks if the campaign is using an outdated AJAX mode. An obsolete targeting method can negatively impact the performance of your campaigns.
- Campaign duration: This feature tells you if the campaign has been running for more than 12 months. A campaign that has been running for a long time may require optimization to keep its performance optimal.
How to read it?
The green/yellow color indicator on the page will indicate which campaigns need optimization. A yellow color indicates that optimization is needed. By viewing these key features, you can quickly identify which campaigns may be negatively impacting your overall tag performance, and take action to optimize them.
The page also provides an easy way to edit campaigns, and filter by type, status, and optimization, to help you navigate and optimize your campaigns efficiently.