Hello, we have a plus customer who wants to A/B test our checkout extension. Basically, the will have two themes. One with our app badges and one without. The rest of the pages are simple to do with an A/B test app as it automatically switches between the two themes. However, since checkout is outside the theme,what would be the best way to achieve this ? Basically hide extension on control, and show extension on test variant.
I saw a post about referencing attributes to show/hide extension
Currently, there is no built-in functionality for A/B testing with Checkout Extensibility - ie: it’s not possible to create a rule to display specific customisations (in your case badges) to one group of customers and hide the customisations to another group. This is a feature request that our product team is aware of, and are exploring support for, but there’s no roadmap or timeframe for sharing right now.
Thanks Liam. I was wondering if we could use Attributes
The customer uses intelligems for their A/B testing program and I am working with them to see if intelligems can or does add any kind of attribute to the cart which is propagated to checkout and whether we can access those attributes in our checkout extensions.
We’ve worked with a use-case like this where a block was supposed to be shown on checkout if the user added a gift message on cart page. Used cart attributes for this and can confirm it works well
Additionally, you can connect with intelligems to understand if they have an API that returns the current version (control or test) of A/B test for a user if passed with user’s checkout token (or cart token). Just assuming, if they store this data on their end and if its not currently being shown the cart attributes, this is something i think you can have a discussion with them about
