In Webtrends Optimise we have 2 options for building out experiences. Each option has its limitations and advantages and this document will help you understand those and give an indication of which you need to use.
Advanced Code Editor
A raw code environment where you can write HTML, CSS, and JavaScript directly to modify a website.
Pros:
Benefit | Description |
Precise control | You can target any element or behavior on the page exactly as needed, down to the pixel or logic level. |
Custom logic | Great for testing dynamic features, conditional logic (e.g., “if user scrolls, then show banner”), or custom analytics triggers. |
Scalability | Code-based edits can be versioned, reused, and integrated with CI/CD pipelines. |
Testing types available | ABn, Split, Target, Baseline and MVT |
Cons:
Drawback | Description |
Requires coding skill | Not accessible to non-developers; increases the need for QA and developer resources. |
Risk of breaking site | Miswritten code can cause layout issues or JS errors, especially on complex pages. |
Longer setup time | More manual work to write, test, and debug—even for simple changes like a text update. |
Best For:
Complex experiments (e.g., new checkout flows)
Advanced targeting logic
High-traffic, high-stakes tests where performance and precision matter
Organizations with front-end dev support
Visual Editor
A WYSIWYG (What You See Is What You Get) interface for point-and-click editing — changing copy, etc.
Pros:
Benefit | Description |
Fast and easy | Make changes without writing code—great for quick tests or marketing-driven updates. |
Non-technical access | Marketers, designers, and product managers can run experiments without involving developers. |
Good for simple tests | Ideal for editing headlines, swapping images, hiding/showing elements, etc. |
Testing types available | Abn and Targets |
Cons:
Drawback | Description |
Limited control | Can struggle with deeply nested elements, JS-heavy components, or mobile responsiveness. |
Can be fragile | Edits are often implemented by injecting code on the client side—may break if the DOM structure changes. |
Performance impact | Slower load times or visible “flicker” may occur as scripts modify the DOM after the page loads. |
Best For:
Copy or image swaps
Quick experiments led by non-developers
MVP-level testing
Validating concepts before investing in engineering time
When to Choose Each
Situation | Choose Advanced Code Editor | Choose Visual Editor |
Need to test conditional logic or dynamic behavior | ✅ Yes | ❌ No |
Team lacks front-end dev support | ❌ Not ideal | ✅ Perfect |
Editing a static banner or CTA text | ❌ Overkill | ✅ Ideal |
Running complex tests on single-page apps (SPA) | ✅ Required | ❌ Limited capability |
Need pixel-perfect responsiveness or performance tuning | ✅ Yes | ❌ No |
Prototyping a quick concept | ✅ Maybe | ✅ Easy and fast |
Summary:
Editor Type | Use For | Who It's For |
Advanced Code Editor | Complex, custom, scalable tests | Developers, technical experimenters |
Visual Editor | Quick, simple UI changes | Marketers, product teams, non-coders |