If you’re using Convert Experiences to run A/B tests on your form, you can track the performance of each version in Zuko by following these steps and setting a Custom Attribute for the Variants and Original.
Make sure the Convert tracking code is installed on your page.
Create a Zuko account and ensure that the tracking is successfully added to your form.
Open up your Convert account, and click the Edit button on your Variation:
From the Visual Editor, select the Custom JS and add this variable:
window.convertvariantzuko = 'variant_1';
You can change ‘variant_1’ - the latter should match the name you’ve given you variant. For example it might be called ‘Button Colour Change’ or something similar.
Now, every time that Variant loads, a variable is going to be set. Now you need to amend your Zuko tracking tag to look for this attribute and send it to Zuko.
Open your Zuko tracking script and add the following line:
.setAttribute('Convert Variant', window.convertvariantzuko || 'Not Set')
You can add this between the slug line and the form view event line.
‘Convert Variant’ can be changed - this is simply how this will appear in Zuko under the filter drop down menu.
You need to ensure that ‘window.convertvariantzuko’ exactly matches what you’ve set up in the JS variable in the previous step, otherwise the Zuko tracking script will error.
You should now be able to use the filter functionality in Zuko to view the performance of each variant.
If the user sees the variant of the page, an attribute of ‘variant_1’ will be pushed into Zuko, and you will be able to select it from the filter drop down menu in all of your reports.
If the user sees the original, an Attribute of ‘Not Set’ will appear in Zuko instead.
You can repeat the above for any form and any number of variants that you have set up in Convert, so you will be able to filter your Zuko data to examine how the form-fill behaviour differs across different versions of your form.