Using Plasmic as a white-labeled visual editor for A/B testing platform

Partners and experts
1

Hi Plasmic team,

I am helping my friend develop an A/B testing product for e-commerce businesses external websites and considering using Plasmic as our visual editor solution. Our key requirements are:

  1. White-labeling capability - We need to embed the visual editor into our platform
  2. URL parameter activation - Allow merchants to access the visual editor via URL parameter (e.g., ?visual=1)
  3. Multi-tenant support - Each merchant should have their own isolated editing environment
  4. Version control - Need to maintain different versions for A/B test variants
  5. Integration flexibility - Must be able to integrate with our A/B testing logic and analytics

From reading the bl!nk case study, it seems Plasmic could be a good fit. However, I’d like to confirm:

  • Is there an existing implementation or recommended approach for using Plasmic in an A/B testing context?
  • What’s the recommended way to handle version control for test variants?
  • Are there any limitations we should be aware of for this use case?

Any guidance would be greatly appreciated!

2

Hi,

About your requirements:

  1. White label capability: The platform does support it, but it requires an enterprise plan, you can read more about it at Plasmic as a white label builder | Learn Plasmic.
  2. URL parameter activation: I am not sure if I understand what you mean. Would you like to be able to attach a query parameter in a deployed page that would open the Plasmic Studio? Plasmic doesn’t mix the experience of the generated code and the studio, so we don’t have this capability.
  3. Multi-tenant support: That could be achieved if you self-host Plasmic, but natively, the editor only allows users to create teams/workspaces/projects and apply specified permissions to those resources.
  4. Version control: You can read more about versioning of Plasmic projects at Publishing projects | Learn Plasmic.
  5. Integration flexibility: You can read more about it at Split content: A/B testing, targeting and scheduling | Learn Plasmic and Split content setup | Learn Plasmic.
  • Is there an existing implementation or recommended approach for using Plasmic in an A/B testing context?

The links mentioned in 5. explain the recommended approaches.

  • What’s the recommended way to handle version control for test variants?

Plasmic considers A/B test data an extension of the project model, so the same rules about versioning in 4. apply to the data related to A/B test.

  • Are there any limitations we should be aware of for this use case?

None that I am aware of, but I may haven’t fully understood your use case. Please let me know if, with the additional information and references, you have other doubts.

1 Like