# Conversion types

A conversion is a measurable action taken by a visitor on your website — something that signals success based on your goals.

Conversions can be anything from clicking a button to completing a purchase. In Optibase, you define what counts as a conversion, and we track how often it happens during your tests.

***

### Why it matters

Your tests are only meaningful if you know what you’re measuring.

By setting clear conversion goals, you can evaluate which variants drive real outcomes — like more signups, purchases, or deeper engagement. This is how you turn insights into improvements.

***

### Conversion Types in Optibase

{% embed url="<https://www.youtube.com/watch?v=x3sJi0hC3Ks>" %}

Optibase supports several conversion types to give you flexibility based on how your site works.

#### Click

{% embed url="<https://www.youtube.com/watch?v=P_F3dvLVsYA>" %}

Track when users click specific elements such as:

* Buttons
* Links
* Icons

> *Example: You want to measure how many people click the “Start Free Trial” button.*

***

#### Submit

{% embed url="<https://www.youtube.com/watch?v=SOxgnwh9DJE>" %}

Track when a user submits a form, such as:

* Contact forms
* Signup forms
* Lead capture forms

> *Example: You test a new headline on your lead-gen page and track how it affects form submissions.*

***

#### Page View

{% embed url="<https://www.youtube.com/watch?v=lrZj-dU3TuA>" %}

Track visits to a specific page. This is helpful when:

* You want to know if users reach a thank-you or confirmation page
* You’re measuring navigation flow

> *Example: A user clicks “Buy” and lands on a confirmation page — that page view counts as the conversion.*

***

#### Scroll Depth

{% embed url="<https://www.youtube.com/watch?v=qcthkSDjCbo>" %}

Track how far users scroll on a page (25%, 50%, 75%, or 100%). This helps measure engagement with longer content or product pages.

> *Example: You want to know if users are seeing your pricing section at the bottom of a landing page.*

***

#### Time on Page

{% embed url="<https://www.youtube.com/watch?v=NuaH6GJntqk>" %}

Track how long users stay on a page. This is useful for:

* Articles
* Product descriptions
* Feature comparisons

You can set a minimum time threshold, like 30 seconds or 2 minutes.

> *Example: You test a new product video and want to know if it holds users’ attention for at least 60 seconds.*

***

#### Programmatic

{% embed url="<https://www.youtube.com/watch?v=3Hy6EMqdI2s>" %}

Trigger conversions manually using JavaScript. This is best when:

* You’re tracking custom interactions (e.g., playing a video, clicking a 3rd-party widget)
* You need more control beyond standard UI events

Use the JavaScript function:\
\
`optibaseSendConversionEvent('yourConversionId')`\
\
You can also trigger server-side conversions by sending the same conversion event programmatically from your backend.

> *Example: You mark a conversion when a user completes payment via Stripe, even if the final step happens off-site.*

***

### How to create a Conversion

1. Go to the Conversions tab in your Optibase dashboard
2. Click Create Conversion
3. Choose a Conversion Type (Click, Submit, Page View, etc.)
4. Define the target element, page, or criteria
5. Give your conversion a clear name (e.g. “Pricing Page CTA Click”)
6. Save your conversion — it’s now ready to be used in a test

***

### Tips for Defining Conversions

* Set one primary goal per test to stay focused
* Use clear and specific names for conversions so they’re easy to track
* Use Programmatic conversions for advanced use cases or 3rd-party integrations
* Don’t overcomplicate — only track what matters to the outcome you care about

***


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.optibase.io/features/conversions/conversion-types.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.