# Class fields for A/B testing

**URL:** <https://forum.mautic.org/t/class-fields-for-a-b-testing/3861>\
**Category:** Ideas and Feature Requests\
**Created:** [May 23, 2016, 12:13am UTC](https://forum.mautic.org/t/class-fields-for-a-b-testing/3861 "2016-05-23T00:13:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![teamtmedia](https://avatars.discourse-cdn.com/v4/letter/t/71c47a/32.png) [@teamtmedia](https://forum.mautic.org/u/teamtmedia)\
**Post date:** [May 23, 2016, 12:13am UTC](https://forum.mautic.org/t/class-fields-for-a-b-testing/3861/1 "2016-05-23T00:13:13Z")

</div>

It is understandable that this system needs to be used by tech novices however it still needs to be documented for them by designers/developers. It would be nice to have the ability to set a class for each variant so that these can be pro-actively supported after implementation and to ensure that hybrid marketing/designer/developer agencies can reduce their workload with stylesheets rather than inline (and, therefore, messy) styles.  
  
  
  
This would seem to be a very easy to implement feature as it would only require 1 additional field in the edit window and 1 line of documentation in the theme documentation to support it. Hope this gains some interest.

---

<div class="post-metadata">

**Author:** ![teamtmedia](https://avatars.discourse-cdn.com/v4/letter/t/71c47a/32.png) [@teamtmedia](https://forum.mautic.org/u/teamtmedia)\
**Post date:** [May 23, 2016, 12:13am UTC](https://forum.mautic.org/t/class-fields-for-a-b-testing/3861/2 "2016-05-23T00:13:13Z")

</div>

It is understandable that this system needs to be used by tech novices however it still needs to be documented for them by designers/developers. It would be nice to have the ability to set a class for each variant so that these can be pro-actively supported after implementation and to ensure that hybrid marketing/designer/developer agencies can reduce their workload with stylesheets rather than inline (and, therefore, messy) styles.

This would seem to be a very easy to implement feature as it would only require 1 additional field in the edit window and 1 line of documentation in the theme documentation to support it. Hope this gains some interest.