This site was built to compliment the existing NetSuite Professionals Slack Community by adding a means for members to easily find answers to common questions and to create a searchable database of those questions and answers.

NetSuite Professionals

What are some A/B testing options for SKINS in SCA?

If you refer to do on the fly a/b testing of sc/sca skins:

Skins in sc/sca are basically a collection of variables and variable values that are used in sass stylesheets that are then compiled into regular css (which is the styling language your browser understand, as opposed to sass)

As it needs compilations i find imho that A/B testing of that something that would require “core” customization (if possible at all). At least that’s my initial impression just by thinking the mechanisms on how it all gets compiled.





<@U658H85S9>  couldn't you use themes instead of the skins.
So effectively create two or more themes.
On our new build on 19.2 we will be creating two different themes depending on the two types of customers we have.

Then with some sort of variable you assign a user to a given theme eg if user id is odd show theme X if even show theme Y. You would also need to track the usage by passing custom event data into GA so you see which is better from a holistic point of view (eg product impressions, clicks, conversions etc

<@UHQFWH30Q> another option would be to use a A/B testing tool to essentially override to look &amp; feel. We are currently using this method on our current live Elbrus site. We are using the Monetate tool but any A/B testing tool would be fine.

Only consideration would be the slight flicker as the look &amp; feel changes.

themes or skins same story. Css is one of the bulkiest assets (and currently one of the first loaded). Changing stuff so it loads one stylesheet or another is what i would consider a deep change for SCA, specially if you are compiling your site with aconcagua+ tools (with extrnsibility tools)

The extensibility tools don’t give you that kind of power to combine two different sass for the same website domain and application. 

what you describe below with a regular a/b testing tools is another story. It’s simple, and achiveable. But a full switch theme/skin switch on the fly isn’t imho.

pre aconcagua i can see it happening, by tweaking ssp files and gulp tools (although tecnically there were no themes or skins back tjen). All the compilation tools were in your local emvironment and were more open to tweaks.