Conditional Triggers
Better control over when a “view” is triggered.
If my A/B test is on a multi step form, it would track everyone who goes to the first step is ith the current setup. But I want to see the difference between steps to optimize.
Examples would be triggering:
On click
Element scroll into view (good for testing things on lower portions of pages)
On page load (default right now)
This would provide us with enhanced and focused data rather than having to sift through to find the real info we care about.
Log in to comment and vote
Comments3
Sergej
Jul 11, 2025
@Jayden Lowe good news, you can already achieve this with Optibase by using multiple different conversions.
If you want to track users who reach later steps in a multi-step form (rather than just page views), you can set up click conversions for buttons that lead to each step. That gives you precise control over what counts as a view.
As for what you described with “element scroll into view,” that’s possible using a scroll depth conversion. You can set the scroll trigger by entering a specific height in pixels, or just use a percentage like 50% to track when users reach a certain part of the page.
Hope that helps!
Jayden Lowe
Jul 21, 2025
@Sergej yes we can do it this way. However this makes the main screen showing conversion rate and P2BB irrelevant.
It’d be nice to not have to do the math ourselves and use the tool for this and have control over when we want a view triggered, rather than use a work-around on the tool by counting specific conversion types as a view.
Doing the setup you explained also makes the Shareable results redundant as the views shown there will not be accurate and others cannot adjust the selected conversions to see the data that actually matters. They’ll just be shown total conversions which in this case will include “views”
Sergej
Jul 22, 2025
Put it back “In progress” and will discuss with the team how we could approach this.