❓FAQs

Why do conversions in the Webflow app appear to disconnect randomly, and are these conversions still being tracked?

The most common instance occurs when you connect a conversion to an element on a page and then navigate to a different page. The Optibase Webflow App can only see the elements on the current page, so it does not know if there is another element connected to a conversion on a different page. However, don't worry—conversions on different pages will continue to be collected. If you navigate back to the original page, you will see the conversion connected again.

Another instance occurs when you connect a conversion to an element inside a component. The Optibase Webflow App can only see the elements inside a component if the editor is focused on it. If you move the focus back to the whole page, the app does not know if another element is connected to a conversion inside one of the components. This is a limitation of Webflow's current API. But again, don't worry; conversions inside components will continue to be collected.

Why can't I see detailed metrics like average "Time on Page" and "Scroll Depth"?

We currently support conversions with specific triggers. Thus, you can trigger a conversion at a particular "Time on Page" or "Scroll Depth" and track how many users meet that trigger. However, you cannot see the numerical average values for "Time on Page" or "Scroll Depth".

That feature is coming the the future.

Why can you see views in the views tab for pages that don't have a test?

The platform only includes pages involved in A/B testing in the actual results. The general Views table collects all views from every page. A server call is made, and a view is collected for every page because the script needs to call the server to determine what tests must be run for that page. If there are none, no test will be run, but the server still keeps track of the view that occurred.