# What is Optibase {% hint style="info" %} **To start testing with Optibase, sign up for a free account here:** [**https://www.optibase.io/**](https://www.optibase.io/) {% endhint %} Optibase is an ultra-fast, platform-native Conversion Rate Optimization (CRO) suite. Designed specifically for Webflow and WordPress, Optibase allows you to eliminate guesswork by testing design and content changes directly within your favorite CMS—no complex custom code or "flicker effect" required. [Sign up for a free Optibase account](https://www.optibase.io/) *** ### Why Conversion Optimization Matters Most websites don't have a traffic problem; they have a conversion problem. Optibase helps you identify exactly what drives user actions, clicks, signups, and purchases, allowing you to test changes safely and quickly within your Webflow project or WordPress site. *** ### The Optibase Feature Suite #### 1. Advanced Experimentation * A/B Testing: Compare two versions of a specific element (like a button or headline). * Multivariate Testing (MVT): Test multiple variables simultaneously to see which combination of elements performs best. * Split Testing (URL-based): Redirect traffic between entirely different page layouts or structures. * AI Traffic Split: Let our AI automatically route more traffic to the winning variant in real-time, maximizing your conversions while the test is still running. #### 2. Visual Intelligence & Insights Understand *why* users aren't converting with built-in behavioral tools: * Heatmaps: See exactly where users click, move, and scroll on your pages. * User Recording Sessions: Watch replays of user journeys to identify friction points and bugs in your funnel. #### 3. Personalization & Targeting Deliver the right message to the right person at the right time: * Dynamic Personalization: Change content based on user data, behavior, or referral source. * Audience Restrictions: Limit your tests or personalizations to specific groups (e.g., "New Visitors only," "Users from the US"). *** ### Pro-Tips for Getting Started * Use AI Split for High-Stakes Tests: If you’re testing a pricing page, use AI Traffic Split to ensure you don't lose sales on a poor-performing variant. * Set Clear Audience Restrictions and make your data cleaner by excluding internal team traffic from your experiments. # Optibase Dashboard Overview {% embed url="" %} The Optibase Dashboard is your command center for Conversion Rate Optimization. Whether you are managing experiments on Webflow or WordPress, this guide will help you navigate the tools needed to measure performance and scale your growth. #### Workspace Management Located at the top left, the Workspace Switcher allows you to toggle between different brands or client projects. * Pro-Tip: Each workspace uses a unique script ID. Ensure your WordPress plugin or Webflow custom code matches the specific workspace you are currently managing. *** ### 1. Experiments & Tests The Tests page is your default view. Here, you can launch and monitor A/B Tests, Multivariate Tests, and Split Tests. #### Analyzing Test Results Clicking into any experiment reveals a deep-dive into user behavior: * Variant Performance: A real-time comparison showing which version is winning. * AI Traffic Split Status: Monitor how our AI is routing traffic to the highest-performing variant. * Segmentation Data: Break down results by Location, Screen Size, Operating System, and Browser. * Audience Restrictions: View or edit the rules that determine which users enter the test. *** ### 2. Behavioral Intelligence (Heatmaps & Recordings) *(New Section: Essential for SEO/GEO)* Understand the "Why" behind your data: * Heatmaps: Access visual overlays showing where users click and scroll on your Webflow or WordPress pages. * Session Recordings: Replay actual user journeys to spot friction points that A/B testing alone might miss. *** ### 3. Conversions & Goals The Conversions page is where you define success. * Define Goals: Set up tracking for button clicks, form submissions, or custom events. * Copy Attributes: Easily grab the `data-optibase` attributes needed to link your site elements to your conversion goals. * Conversion Analytics: See a detailed log of which browsers and devices are driving the most value. *** ### 4. Site-Wide Analytics While the "Tests" page focuses on experiments, the Analytics tab provides a global view of your site's health: * Total Traffic: Monitor page views across your entire domain. * Audience Insights: A high-level breakdown of your global visitor demographics and technology stacks. *** ### 5. Workspace Settings & Integrations This section ensures your data is clean, secure, and integrated with your existing tech stack. #### Data Accuracy & Privacy * Domain Whitelist: Protect your data by only allowing Optibase to track authorized domains (prevents staging or local sites from skewing results). * IP Blacklist: Block your team's IP addresses so internal testing doesn't count against your "Tested User" limits or conversion data. * IP Collecting: Toggle IP storage to stay compliant with local privacy laws like GDPR. #### Team & Collaboration * Members & Roles: Invite developers or marketers and assign permissions (Admin, Editor, or Viewer). * Billing: Manage your subscription and monitor your usage limits in real time. #### Ecosystem Integrations * Google Analytics 4 (GA4) & Mixpanel: Sync your Optibase experiment data with your favorite third-party analytics tools. * Public API: Access your API keys for custom data workflows or advanced integrations. # Installation Guide: Adding the Optibase Script To enable A/B testing, Heatmaps, and Personalization, you must add the Optibase script to your website. This single snippet powers all features across your entire workspace. #### Step 1: Locate Your Unique Script 1. Log in to your account at [app.optibase.io](https://www.google.com/search?q=https://app.optibase.io). 2. Navigate to Workspace Settings in the sidebar. 3. Select the Custom Script tab. 4. Click on the code block to copy your unique snippet.
*** #### Step 2: Where to Place the Script For Optibase to function correctly, the script must be placed inside the `` tag of your website. Critical Requirement: You must place the script on every page where you want to run tests or track conversions. We recommend adding it to your global site settings. **Recommended Placement:** Paste the script as the very start of your `` tag. HTML ``` ... ... ``` *** #### Step 3: Platform Specific Instructions **For Webflow Users** 1. Open your Project Settings. 2. Go to the Custom Code tab. 3. Paste your Optibase script into the Head Code section. 4. Publish your site to all domains. **For WordPress Users** 1. Log in to your WordPress Dashboard. 2. Ensure you have the Optibase WordPress Plugin installed. 3. Navigate to the Optibase settings and paste your script ID *** #### Why the `` placement is required * Zero Flicker: Loading the script early ensures that variants are applied before the page renders. This prevents users from seeing the original version for a split second. * Accurate Tracking: This allows Optibase to record page views and user sessions the moment the page begins to load. * Split Test Support: Necessary for instantaneous URL redirects during split tests. # How the Optibase Script Works The Optibase Custom Script is the engine that powers your entire optimization suite. It is a lightweight JavaScript snippet that handles live testing, behavioral tracking (Heatmaps/Recordings), and conversion attribution in real time. Without this script installed, Optibase cannot run tests, capture heatmaps, or track conversions. *** ### Core Technical Functions #### 1. Dynamic Test Logic On every page load, the script performs a secure handshake with Optibase servers to: * Identify active experiments for the specific URL. * Evaluate Audience Restrictions (Geo-location, Browser type, OS, etc.). * Determine if the user should be included in a test or a personalization campaign. #### 2. A/B & Multivariate Testing (No-Flicker Technology) To ensure a seamless user experience, the script: * Scans the page for elements containing `data-optibase-test-id` and `data-optibase-variant-id`. * Assigns the user to a specific variant. * Instant Reveal: It removes the `display:none` style from the chosen variant and deletes non-selected variants from the DOM. * Pro-Tip: Ensure your "Main Variant" is the only one visible by default in your Webflow or WordPress editor to prevent a flash of unstyled content. #### 3. URL-Based Split Testing For redirect-based experiments, the script: * Checks if the current URL is a "Split Test" entry point. * Decides whether to keep the user on the current page or trigger an immediate redirect. * Context Preservation: If a redirect occurs, it appends `splitTestId` and `splitVariantId` parameters to the URL so the destination page knows which experiment is active. #### 4. Behavioral Intelligence & Analytics The script is also responsible for your site’s "Intelligence" features: * Heatmaps: Maps user clicks, scrolls, and mouse movements. * User Recording Sessions: Captures the visual journey of a user to find friction points. * Analytics: Collects page view data and interaction events. > Note: Page views only count toward your plan limits if an active or eligible test is present on the page. #### 5. Conversion Attribution The script automatically attaches event listeners to track: * Click Conversions: (`data-optibase-click-conversion-id`) * Form Submissions: (`data-optibase-submit-conversion-id`) * Event Logic: When a user converts, the script attributes that success to all active A/B variants the user has seen during that session. *** ### Debugging and Developer Controls You can control how the script behaves in your specific browser using URL parameters. This is essential for testing your setup before going live. | **Action** | **URL Parameter** | **Result** | | ------------------- | --------------------------- | ------------------------------------------------ | | Enable Debug Mode | `?optibaseEnableDebugMode` | Shows step-by-step logic in the browser console. | | Disable Debug Mode | `?optibaseDisableDebugMode` | Stops logging to the console. | | Disable All Scripts | `?optibaseDisableScript` | Blocks all tests and tracking in your browser. | | Re-enable Script | `?optibaseEnableScript` | Restores normal script behavior. | *** ### Summary of Capabilities The Optibase script is a multi-purpose tool that: 1. Determines test eligibility based on audience and URL. 2. Renders the correct A/B or Multivariate variant instantly. 3. Redirects users for Split Tests. 4. Records heatmaps and user session replays. 5. Tracks conversions and sends data to your Optibase Dashboard. # Managing Workspaces and Teams {% embed url="" %} In Optibase, a Workspace is a dedicated, isolated environment for your optimization projects. Each workspace maintains its own unique set of experiments, conversion goals, team members, and subscription plans. This structure is ideal for agencies managing multiple clients or companies running separate tests across Webflow and WordPress environments. *** ### 1. Creating and Navigating Workspaces #### How to Add a New Workspace 1. Click the Workspace Dropdown menu in the top-left corner of the Optibase dashboard. 2. Select "Add new Workspace +". 3. Enter a descriptive name for your project or client. 4. Instant Setup: Your new workspace is created immediately on the Free plan, which includes a default monthly tested user limit (typically 10,000 users). #### Switching Between Environments To change projects, open the workspace dropdown and select the desired name. The dashboard will instantly display the membership roles, active plans, and usage stats for that specific environment. *** ### 2. Team Collaboration (Unlimited Members) Optibase is built for teamwork. Unlike many CRO platforms, we do not charge for additional seats. You can collaborate with your entire team or invite clients at no extra cost. #### How to Invite Members 1. Click the Gear Icon (Settings) next to your workspace name. 2. Navigate to the Members section. 3. Enter the email address of your teammate or client. 4. Assign a Role: * Owner: Full control over settings, billing, and member management. * Editor: Can create and launch tests but cannot manage billing. * Viewer: Read-only access to view reports and analytics. 5. Click Invite. Once they accept, they will have access to all experiments within that specific workspace. *** ### 3. Pricing and Workspace-Based Billing To provide maximum flexibility for agencies and enterprises, Optibase uses a Workspace-Based Billing model. * Isolated Subscriptions: Each workspace has its own independent plan and usage limits. This allows you to bill individual clients or departments directly. * Owner Accountability: Only the Workspace Owner is responsible for the subscription and billing details. * No "Per-Seat" Fees: You can invite an unlimited number of members to any workspace without increasing your monthly cost. * Scalability: You can upgrade or downgrade individual workspaces at any time via the Billing tab in settings based on the traffic needs of that specific project. *** ### 4. Platform-Specific Setup Note Every workspace generates a unique Custom Script. If you are running tests on both Webflow and WordPress for the same brand, you can use the same workspace script. However, if you are managing two different clients, you must create two separate workspaces to ensure their data and tracking remain completely isolated. # Conversions ## Conversions In Optibase, Conversions are the specific, measurable actions you want users to take on your website. They are the "North Star" metrics for your A/B tests and personalizations. Without a conversion, you are simply changing your design; with a conversion, you are optimizing your business. Whether you are building on Webflow or WordPress, Optibase allows you to track these actions with zero impact on site performance. *** ### Why Conversions are the Core of Optibase The goal of any experiment is to see how changes affect user behavior. By defining conversions, you allow the Optibase engine to: * Identify Winners: Determine which headline, button, or layout actually drives revenue. * Calculate Significance: Our statistical engine uses conversion data to tell you when a test result is reliable. * Optimize via AI: When using AI Traffic Split, the system automatically sends more traffic to the variants that are converting at the highest rate. *** ### Types of Conversions Optibase offers a versatile range of tracking methods to fit any business model. Depending on your goals, you can choose from several conversion types: {% embed url="" %} | Conversion Type | Best Used For... | Example | | --------------- | -------------------------------------------------------------------------------------------- | ------------------------------------------ | | Click | Button clicks and link interactions. | "Buy Now" or "Get Started" buttons. | | Submit | Capturing leads or signups. | Newsletter subscriptions or Demo requests. | | Page Views | Confirming a user reached a specific URL. | "Thank You" pages or Order confirmation. | | Scroll depth | Track how far down a page a visitor scrolls | User scrolls 75% | | Time on page | Measure user retention by triggering a conversion only after a user stays for a set duration | User stays for 30s | | Custom Events | Complex user behaviors or interactions. | Custom | | Server-Side | Actions that happen off-page or in the backend. | Successful payments or CRM updates. | *** ### Understanding the Conversion Lifecycle Managing conversions in Optibase follows a simple three-step logic: #### 1. Definition You first define the conversion in Optibase. This is where you name the conversion and determine its "value" to your project. This centralized definition allows you to reuse the same conversion across multiple A/B tests. #### 2. Connection (The "Glue") Once defined, you connect the conversion to your website. * Webflow/WordPress: This is usually done by adding a small "data attribute" to your element (e.g., `data-optibase-click-conversion-id`). Either with the Webflow app or manually. * Server-Side: This is done via our API or webhooks for actions that don't happen directly in the browser. #### 3. Attribution When a user triggers a conversion, Optibase automatically "attributes" that success to the specific test variant the user was viewing. This is how you get your Conversion Rate (%) data. *** ### Best Practices for High-Impact Tracking * Focus on Macro-Conversions: While tracking button hovers is interesting, focus your primary tests on "Macro" goals like sales or signups that directly impact your bottom line. * Avoid "Double Counting": Ensure your conversion triggers are unique. For example, if you track a form submission, you usually don't need to also track the "Submit" button click. * Test the Connection: Always use the Optibase Debug Mode (`?optibaseEnableDebugMode`) to verify that your conversions are firing correctly before starting a live experiment. # 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="" %} Optibase supports several conversion types to give you flexibility based on how your site works. #### Click {% embed url="" %} 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="" %} 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="" %} 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="" %} 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="" %} 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="" %} 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 *** # Create a Conversion *If you using Webflow then you should follow the guide here:* [Optibase Webflow App](/webflow-app/optibase-webflow-app) *How to connect a Conversion:* [Connect a Conversion](/features/conversions/connect-a-conversion)\ \ To measure the impact of your tests, you’ll need to create and configure conversions — actions that indicate success, like form submissions, button clicks, or page views. ❗️If you’re using Webflow, follow this guide instead: 👉 Setting up Conversions in Webflow *** ### How to create a Conversion 1. Go to the Conversions page from the left-hand menu in your Optibase dashboard
2. Click the New Conversion button in the top-right corner
3. Give your conversion a clear name 4. Choose a Conversion Type from the following:
*** #### Conversion Types **Page View** Track when users load a specific URL. You’ll need to: * Enter the exact URL (or pattern) where the conversion should trigger **Scroll Depth** Track how far down a page users scroll. You’ll need to: * Set the target URL * Choose the scroll depth (in percentage or pixels) that should trigger the event **Time on Page** Track how long users stay on a specific page. You’ll need to: * Set the target URL * Define the minimum time (in seconds) that qualifies as a conversion **Click** **(requires connection to a page element)** Tracks clicks on a specific button, link, or element. **Submit** **(requires connection to a page element)** Tracks when a user submits a form. > After you create a Click or Submit conversion, you’ll need to connect it to an element on your page. **Programmatic** Trigger a conversion manually using JavaScript or from your server. Use this when: * You want to track custom user actions that aren’t tied to page structure * You need to fire conversions from backend logic or 3rd-party tools To trigger the conversion, use this function in your frontend code:\ `optibaseSendConversionEvent(userFriendlyConversionId)` JavaScript function.\ \ You can also trigger this conversion in two other ways:\ \ You can set up a Programmatic Conversion with Google Tag Manager: [Trigger Conversions with GTM](https://docs.optibase.io/integrations/trigger-conversions-with-gtm) You can also trigger this conversion from the server: [Server-side Conversions](https://docs.optibase.io/how-to-setup-optibase/server-side-conversions) *** ### Managing Conversions Once a conversion is created, you can click on it to: * Edit its values (e.g. URL, scroll depth, time) * Delete it if it’s no longer needed You can reuse the same conversion across multiple tests or assign different conversions to different test goals. # Connect a Conversion *If you using Webflow, then you should follow the guide here:* [Optibase Webflow App](/webflow-app/optibase-webflow-app) Once you’ve created a Conversion inside the Optibase web app, you’ll need to connect it to your website so Optibase can track when it happens. ### Why connection matters Some conversion types (like clicks and form submissions) rely on being linked to specific HTML elements. Others (like page views or scroll depth) work based on the URL alone and don’t need any extra setup in your code. *** ### Click Event If you want to trigger a conversion when a user clicks an HTML element (like a button or link), you need to: 1. Go to the Conversions page in the Optibase app 2. Find the Click Conversion you created 3. Copy the data-optibase-click-conversion-id from the table 4. Add that attribute to the element on your website Before: ``` ``` After: ``` ``` This tells Optibase to fire the “sign\_up” conversion when this element is clicked. *** ### Submit Event If you want to trigger a conversion when a user submits a form, follow the same steps, but use the data-optibase-submit-conversion-id attribute: 1. Copy the ID from your Submit Conversion in the dashboard 2. Add it to the \
element Before: ``` ...
``` After: ```
...
``` Optibase will now send a conversion event when the form is submitted. *** ### Programmatic Conversion This type of conversion is triggered via JavaScript or your backend, not by clicking or submitting elements. Use this when: * You need full control over when a conversion is triggered * The conversion happens outside the DOM (e.g. Stripe payment, API response) Trigger it using: ``` optibaseSendConversionEvent('sign_up') ``` You can set up a Programmatic Conversion with Google Tag Manager: [Trigger Conversions with GTM](https://docs.optibase.io/integrations/trigger-conversions-with-gtm) You can also trigger this conversion from the server: [Server-side Conversions](https://docs.optibase.io/how-to-setup-optibase/server-side-conversions) ### Page View, Scroll Depth, and Time on Page These conversion types do not require any changes to your HTML. They work automatically based on the URL and settings you define when creating the conversion: * Page View: Fires when the page loads * Scroll Depth: Fires when the user scrolls to a certain depth * Time on Page: Fires after the user spends a set amount of time on the page Just make sure the script is installed, and Optibase handles the rest. # Server-side Conversions Optibase exposes an API endpoint you can call from the server to trigger a Conversion. #### Endpoint **URL**: `https://app.optibase.io/api/script/conversionEvent` **Method**: `POST` #### Headers * **Content-Type**: `application/json` #### Request Body The body must be a JSON object that contains the following fields: * **publicApiKey** (string): [#public-api-key](#public-api-key "mention") * **userFriendlyConversionId** (string): [#user-friendly-conversion-id](#user-friendly-conversion-id "mention") * **testedUserId** or **testedUserExternalId** (string): [#tested-user-id](#tested-user-id "mention") or [#tested-user-external-id](#tested-user-external-id "mention") **Sample Request Body** ```json { "publicApiKey": "clv3047v70dsat664sgrzwotq", "userFriendlyConversionId": "serverside_conversion", "testedUserId": "clr6hq6y70001qv4jpwag4asd" } ``` or ```json { "publicApiKey": "clv3047v70dsat664sgrzwotq", "userFriendlyConversionId": "serverside_conversion", "testedUserExternalId": "id123" } ``` ### Public API Key You can find it by going to your Workspace settings -> Public API Keys ### User-Friendly Conversion ID Create a Programmatic Conversion and copy the ID by clicking on the copy field in the trigger column:
### Tested User ID When a user visits your page, the Custom Optibase Script generates a Tested User ID for the user. You will need to get this ID from the Optibase Script and store it on the server to call the Optibase API Endpoint later and trigger a Conversion for this specific user. You get this from each user separately with custom JavaScript on the website where you have the Optibase Script setup. The Optibase Script assigns the generated Tested User ID to a global variable you can read with the custom JavaScript. The global variable is `window.optibaseTestedUserId` which is a string. ### Tested User External ID Alternatively, you can assign an External ID to the Tested User by calling `window.optibaseSetTestedUserExternalId(externalId: string): Promise` The External ID is usually the ID you have assigned to your user in your database. If you do that, you can call the Optibase API Endpoint with that new External ID, and you don't have to store the Tested User ID mentioned above. The Tested User External ID will then also be assigned to the global variable `window.optibaseTestedUserExternalId`. # Tests # Test Types {% embed url="" %} Optibase offers three primary testing methods to help you optimize your conversion rate. Choosing the right one depends on the scale of your changes and the volume of traffic your site receives. *** ### 1. A/B Test (Variant Groups) The most popular choice for testing specific elements on a single page. An A/B test (or A/B/n test) is used when you want to compare different versions of specific elements without changing the entire page. * When to use: Testing button colors, headlines, hero images, or CTA copy. * How it works: You keep your page structure identical but swap out specific components for different users. * Best Practice: Only run one A/B test per page at a time. If you run multiple independent A/B tests on the same page, your data may become skewed because the system cannot account for how the different tests interact with each other. *** ### 2. URL Split Test Best for comparing entirely different layouts or user journeys. A URL Split Test (or Redirect Test) splits your traffic between two or more separate URLs at a percentage you define (e.g., 50/50). * When to use: Testing a complete homepage redesign, comparing a long-form landing page vs. a short-form version, or testing entirely different checkout flows. * How it works: Optibase redirects a portion of your traffic from the "Control" URL to a "Challenger" URL. * Advantage: It is ideal for "radical redesigns" where the changes are too complex to implement as simple element swaps on a single page. *** ### 3. Multivariate Test (MVT) "A/B Testing on steroids"—for advanced users with high traffic. A Multivariate test allows you to test multiple elements on the same page simultaneously to see which combination of changes performs best. * When to use: When you want to test how your Headline, Hero Image, and CTA button interact with each other. * How it works: You create "Variant Groups" for each element. Optibase then automatically generates every possible combination (e.g., Headline 1 + Image 2 + CTA 1) and tracks which specific pairing drives the most conversions. * Traffic Requirement: Because MVT creates many combinations, you need significantly more traffic than a standard A/B test to reach statistical significance. # What is a Tested User A Tested User is someone who visits your website and is included in at least one Optibase test. Once a user is part of a test, Optibase tracks their behavior and attributes any relevant conversion events to the variant(s) they were shown. This helps you understand how different variants influence user actions — reliably and accurately. *** ### How Tested Users Work When a user visits your site, Optibase randomly assigns them to a variant in an active test. To ensure consistency, the same user will continue to see the same variant on future visits. > *Example: If a user is assigned Variant B of your homepage headline test, they’ll always see Variant B until the test ends.* *** #### Keeping Variants Consistent Tested Users always see the same variant version of any test they’ve previously been assigned to — even if they: * Leave the site and return later * Visit from a different page * Reload or navigate away This ensures the testing experience is consistent and that the data collected remains valid. *** #### Tracking Across Subpages When a user completes a Conversion Event (e.g. clicking a button, submitting a form, completing a purchase), Optibase attributes that conversion to all variants the user was exposed to, even if the conversion occurred on a different page. > *Example: A user sees Variant A on the homepage, then later signs up on the pricing page. That conversion is credited to Variant A.* *** #### Cross-Domain Tracking #### (Business & Professional Plans Only) If your project spans multiple domains, Optibase can continue tracking the same user across those domains — as long as the same Optibase custom script is installed on each site. > *Example: A user lands on your blog at blog.yoursite.com, then visits app.yoursite.io to sign up. Optibase connects the journey as one tested user.* *** # What is a Variant *How to create an A/B Variant:* [Create an A/B Variant](/features/tests/create-an-a-b-variant) *How to create a Split Variant:* [Create a Split Variant](/features/tests/create-a-split-variant) A variant is an alternative version of something on your website — a section, component, or full page — that you test against your original to see which performs better. Variants are the building blocks of A/B Tests and Split Tests in Optibase. You create them to test ideas, measure results, and improve conversion performance based on real user behavior. *** ### Why it matters Variants help you move from guessing to knowing. Instead of assuming what users prefer, you can test design, layout, or copy changes and let the data tell you what works best. Every variant is an opportunity to increase conversions, improve user experience, and reduce friction. *** ### Types of Variants in Optibase #### A/B Test Variants (Variant Group In an A/B Test, each variant represents a small change to a specific part of your page — without creating a new URL. You can test things like: * A new button color * Updated headline text * Reordered content * Different image or icon Visitors are randomly shown one of the variants. You track which version leads to more conversions. **Main Variant** The Main Variant is the original version of the page in an A/B Test. It’s: * The default version shown when the test is in Draft * The fallback when a test is restricted by geo, browser, or device rules > *Example: You create a Main Variant with a red “Get Started” button and a Variant A with a blue one. Optibase will show one or the other to users and track which leads to more signups.* *** #### Split Test Variants (URL-Based) In a Split Test, each variant is a completely separate Webflow page with its own URL. This type of test is best when you want to compare: * Entirely different layouts or designs * Alternative landing pages * Separate page flows or structures Users are randomly directed to one of the variant URLs, and Optibase tracks which page performs better based on your conversion goals.
**Entry Variant** The Entry Variant is the primary page that acts as the entry point for your Split Test. It works like this: * If a user lands on the Entry Variant URL, Optibase decides whether to keep them there or redirect them to another variant * If a user lands directly on a non-entry variant (e.g. from a paid ad), no redirection occurs — the test still tracks performance > *Example: You create two landing pages with different content structures. The Entry Variant is your main campaign page. Visitors might be redirected to the alternate version based on test settings.* ### Summary: A/B vs Split Variants | Scope | One section or element | Full page (different URLs) | | ------------------ | ---------------------- | -------------------------- | | Setup location | Within the same page | Across separate pages | | Main/Entry variant | Main Variant | Entry Variant | | Use case | Test small changes | Compare different layouts | ### Tips for Working with Variants * Name your variants clearly so you can track what was tested * Only test one change per A/B Test for clean results * Use Split Tests when your changes affect the whole user journey * Set clear conversion goals before publishing a test * Start simple — don’t overcomplicate with too many variants *** # What is a Test/Variant Group In Optibase, a test helps you figure out what works best on your website by comparing different versions of your content — called variants — and tracking which version leads to more conversions. There are three main types of tests in Optibase: * A/B Tests (Variant Groups) * URL Split Tests * Multivariate Tests *** ### Why it matters Running tests lets you make data-informed decisions about your site design and content. Instead of guessing what works, you can test it — and improve conversions without blindly redesigning pages. *** ### Test Types in Optibase #### 1. A/B Test (Variant Group) An A/B Test, also called a Variant Group, is where you test one specific change. You start with a base version (your control), then create one or more variants with a small change: * A different button color * New headline text * Swapped image or icon * Tweaked form layout When visitors land on your site, each one is randomly shown one of the variants. Optibase tracks how each performs based on the conversion goal you set. > *Example: You test a green “Buy Now” button vs. a blue one to see which drives more purchases.* *** #### 2. URL Split Test A URL Split Test lets you compare entirely different pages. Each variant is a separate Webflow page (with its own URL), and you direct traffic between them to compare performance. This is useful when: * Testing different layouts or flows * Comparing two landing pages * Validating a full-page redesign > *Example: You test a long-form sales page vs. a short, punchy version to see which one converts better.* *** #### 3. Multivariate Test A Multivariate Test allows you to test multiple elements on the same page at once — for example, testing a headline, an image, and a button together. Each element you want to test is placed in its own Variant Group, which works like a mini A/B Test. Optibase then creates combinations of all possible variants and measures: * How each Variant Group performs on its own * How combinations of changes perform together > *Example:*\ > *Headline A + Button B + Image C vs.*\ > *Headline B + Button A + Image C, etc.* This helps you understand not just individual changes, but how they interact. *** ### Additional Testing Options Optibase lets you control exactly who sees your tests by setting audience restrictions. You can limit exposure based on: * Location (Geo-Restriction) Target visitors from specific countries or regions. Ideal for localized content or region-specific offers. * Screen Size Restrict tests to certain viewport widths — for example, only users on mobile screens or large desktops. Helpful for responsive design changes. * Operating System Show tests only to users on a specific OS like macOS, Windows, iOS, or Android. Great for testing platform-specific behavior or styling. * Browser Limit tests to users on specific browsers such as Chrome, Safari, Firefox, or Edge. Useful when debugging or optimizing for browser quirks.
> *Example: Want to test a new layout for desktop users on macOS using Safari? You can target that exact audience.* These filters help you run more precise and relevant experiments — especially when testing features that behave differently across environments. *** ### Tips for Success * Use A/B Tests for small, focused changes. * Use Split Tests when comparing entire layouts or flows. * Use Multivariate Tests when testing multiple elements at once — but keep combinations manageable. * Set clear conversion goals before starting a test. * Avoid testing too many things at once unless you have high traffic volume. # Create a Test/Variant Group *If you using Webflow, then you should follow the guide here:* [Optibase Webflow App](/webflow-app/optibase-webflow-app) To run an A/B Test, Split Test, or Multivariate Test in Optibase, you first need to create a Test — this is where you define what you’re testing, how, and under which conditions. ### How to create a Test 1. Go to the Tests page from the left-hand menu
2. Click the New Test button in the top-right corner
3. Enter a name for your test 4. Select a Test Type: * A/B Test (Variant Group) * Split Test (URL-based) * Multivariate Test 5. Click Create
*** ### Multivariate Test Setup If you’re creating a Multivariate Test, you’ll need to define one or more Variant Groups. Each Variant Group: * Represents one element on the page you want to test * Functions like a mini A/B Test inside the larger Multivariate structure For each element you want to test: 1. Create a Variant Group 2. Add at least two Variants (e.g. headline A vs. headline B) Optibase will automatically generate all combinations of variants across the Variant Groups to test how different changes perform together. *** ### Managing Test Status You can change the status of a test from the top-right corner of the test page. * Draft – The test is not live and won’t run * Active – The test is live on your website * Paused – The test is temporarily stopped but not deleted A test must be set to Active for it to appear on your site and for variants to be shown to users. *** ### Create Variants After creating a test, you’ll need to define the actual Variants that users will see. * A/B Variants: [Create an A/B Variant](/features/tests/create-an-a-b-variant) * Split Variants: [Create a Split Variant](/features/tests/create-a-split-variant) *** ### Audience Restrictions You can control who sees your test by setting optional restrictions. These are configured in the test sidebar or under Test Settings. #### Supported restriction types: * Location (Geo-Restriction) Limit test visibility to users from specific countries or regions. Useful for localized campaigns or regional content testing. * Screen Size Show the test only on certain viewport widths. Ideal for running desktop-only or mobile-only tests. * Operating System Target users based on their OS, such as Windows, macOS, iOS, or Android. * Browser Run tests only in selected browsers (e.g. Chrome, Safari, Firefox, Edge). Helpful when testing browser-specific issues or styles. These restrictions ensure your tests run only for the relevant audience — improving data quality and control. *** ### Test Settings Inside the Settings tab of your test, you can: * Change the test name * Delete the test * Review or update all restriction rules # Connect an A/B Variant *If you using Webflow then you should follow the guide here:* [Optibase Webflow App](/webflow-app/optibase-webflow-app) *Note: This is relevant for both A/B Tests and Variant Groups.* Once you have created a Variant inside the Optibase web app, you need to connect it to an actual HTML element inside your website. This way, Optibase knows which HTML element belongs to which Variable/Test. To connect a Variant to an HTML element, you need to add two custom attributes to the HTML element. One is the `data-optibase-test-id` , and the other is `data-optibase-variant-id`. If any of these are missing, your Test will not work. You can find the `data-optibase-test-id` under the Test title on the Test Page:
You can find the `data-optibase-variant-id` in the Variants table under Trigger
You can copy them simply by clicking on them. ## Main Variant When you first create a Variant, it will be marked as "Main". This Variant will be visible by default. This means that if a test is restricted or in Draft, this is the Variant that will be shown. To connect the Main Variant, you simply need to add the custom attributes to the HTML element inside of your page. Before: ```

Original Title

``` After: ```

Original Title

``` ## Non-main Variant After the Main Variant, you should create a new Variant inside of the web app the same way you created the Main one. All Variants created after the Main Variant should be hidden by default. To connect a non-main variant, you should: 1. Copy of the HTML element connected to the main 2. Add the custom attributes of the newly created Variant to the copied HTML and hide it using the inline style: `style="display:none"` Before: ```

Original Title

``` After: ```

Original Title

Alternate Title

``` Notice the different `data-optibase-variant-id` and the inline display style is set to none. Your variants are now set up. You can set the Test to Active to start running it. *Note: If you want to stop showing an A/B Variant to the users because it is underperforming, but don't want to delete it because you want to keep the data, you can simply disconnect it.* # Create a Split Variant *If you using Webflow then you should follow the guide here:* [Optibase Webflow App](/webflow-app/optibase-webflow-app) The first Variant you create in a Split Test will be the Entry Variant. An Entry Variant will be the entry to your Split Test. When a user lands on the Variant, they will either stay on the page or be redirected. If a user lands on a non-entry Variant, they will not be redirected. 1. To set up a Variant, navigate to the page of the Split Test by clicking on it on the "Tests" page:
2. Click on the "New variant" button:
3. Name your variant and define the Variant URL. If you are performing the Split Test on a single domain and will not be redirecting the user to a different domain, you can select the "Same domain path" option. If you select this option, you should only define the Path, not the whole URL.\ \ Example URL: `https://example.com/landing`\ Example Path: `/landing`
A Split Variant doesn't need to be connected to any HTML elements on your page. When a user lands on a website, the custom script you have added to your website will check that URL/Path and handle the Split Tests. *Note:* By clicking on the Variant you can: * Change the name and URL of the Variant. * Reset the Variant Conversion Events and Page Views. * Delete the Variant. *Note: Currently you can not stop showing a Split Variant to the users without deleting it. This is a feature that is coming soon.* # Create an A/B Variant *If you using Webflow then you should follow the guide here:* [Optibase Webflow App](/webflow-app/optibase-webflow-app) *How to connect an A/B Variant:* [Connect an A/B Variant](/features/tests/connect-an-a-b-variant) A/B Variants are different versions of an element that you want to test on the same page. They’re used in both A/B Tests and Variant Groups (inside Multivariate Tests). ### How to create an A/B Variant 1. Go to the Tests page
2. Click on the A/B Test you want to add a variant to
3. On the test page, click the New Variant button 4. Enter a name for your variant
5. Click Create\
Once created, the variant will appear in the list under that test. *** ### Connect the variant to your website You should now connect this Variant to an element on your page. Read about how to do that here: [Connect an A/B Variant](/features/tests/connect-an-a-b-variant) To display the variant on your site, you need to connect it to a specific HTML element. Each element must be tagged with both: * data-optibase-test-id * data-optibase-variant-id Optibase will automatically: * Show one variant to each user * Remove all other variants from the page * Track which version the user saw *** ### Variant options and actions Clicking on a variant gives you several management options: * Rename the variant * Reset its conversion and page view data * Delete the variant entirely * Disconnect the variant (stops showing it to users but keeps the data) > Use disconnect if the variant is underperforming but you still want to analyze its historical results. *** ### Variant performance metrics Each variant tracks the following automatically: * Page Views: How many times the variant was shown to users * Conversions: How many conversion events were triggered while this variant was active * Conversion Rate: Shown in parentheses (Conversions / Page Views) * P2BB: [Probability to Be Best (P2BB)](/features/tests/probability-to-be-best-p2bb)The probability this variant is the top performer based on Bayesian stats You can filter conversion performance using the “Filter by conversion” dropdown above the results. # Connect Conversions to a Test Connecting conversions to your test is essential for measuring performance. It tells Optibase what success looks like, so you can compare variants and identify which one drives the most meaningful actions.
### How to connect conversions 1. Open the Test Go to the Tests page and select the test you want to connect conversions to. 2. Go to the Conversions tab Inside the test view, click the Conversions tab in the top navigation. 3. Select or create a conversion * If you’ve already created a conversion, use the dropdown to select it * If you don’t have one yet, click Create Conversion to define a new one 4. Bind the conversion to the test Once selected, the conversion will be linked automatically to the test. Optibase will start tracking how each variant performs against this goal.
*** ### Additional notes * You can connect multiple conversions to a single test * One conversion will be used as the primary metric in your test results * Make sure all conversion events are set up and working on your site before linking them *** ### Why it matters By linking conversions to a test, you’ll unlock: * Variant performance tracking * Conversion rates per variant * P2BB (Probability to Be Best) analysis * A clear view of which variant wins All of this will show up in the Results tab for the test once it’s running. # Set up restrictions {% embed url="" %} Optibase allows you to control who sees your test by setting restrictions based on geography, device type, operating system, and browser. This ensures that your tests only run for the right audience — improving relevance and accuracy.
### How to access restrictions 1. Go to the Tests page 2. Click on the test you want to configure 3. In the test dashboard, open the Restrictions section All restriction types are optional. If none are set, your test will run for all users by default. *** ### Restriction types Control which countries can see the test. * Default: All countries are included * To target specific countries: * Click on Country under Geo Restrictions * Select one or more countries from the list > Use this to run localized tests or exclude traffic from regions with low relevance. *** #### Screen Size / Device Type Choose which device types should be included in the test: * Phone * Tablet * Desktop You can toggle each option on or off based on your test goals. > Ideal for mobile-optimized experiences or desktop-only UI experiments. *** #### Operating System Restrictions Limit your test to specific operating systems: * Mac OS * iOS * Windows * Android * Linux * Other Use this when testing OS-specific features, styles, or bugs. *** #### Browser Restrictions Control which browsers will display the test: * Chrome * Safari * Firefox * Edge * Internet Explorer * Opera * Other Browser restrictions are useful for: * Ensuring compatibility before full rollout * Targeting users on browsers with known behavior differences *** ### Tips for better targeting * Geo Restrictions: Run localized messaging or language tests * Device/Screen Restrictions: Optimize layouts for mobile or desktop users * OS Restrictions: Target platform-specific functionality * Browser Restrictions: Isolate behavior or design differences in specific browsers These filters help you run more precise experiments and avoid skewed results from irrelevant user segments. # Schedule a Test Scheduling a test in Optibase is simple and ensures your tests run automatically during the specified time period. Here’s how to set it up:
**Steps to Schedule a Test** 1\. Open the test you want to schedule from your dashboard. 2\. Click on the Status dropdown for the test. 3\. Choose the Scheduled option from the dropdown menu. 4\. Set Start and End Dates: • Specify the Start Date and End Date for your test. • The test will automatically begin on the selected start date and stop on the selected end date. 5\. Confirm and save your schedule to apply the changes. **Additional Notes** • You can update or adjust the schedule at any time before the test starts. • If you need to manually start or stop the test, you can change the status back to Active or Draft from the same menu. With these steps, Optibase will take care of running your test within the specified timeframe, making it easier to plan and automate your experiments! # Auto Stop a Test {% embed url="" %} Optibase lets you automatically stop a test when certain criteria are met. This ensures you don’t keep running tests longer than needed, saving time and traffic.
*** ### How to enable Auto Stop 1. Open your test in the Optibase Web App 2. Click the Auto stop button in the test header 3. Enable one or more conditions from the list 4. Set the values for each condition 5. Close the panel — your settings are saved automatically *** ### Available auto-stop conditions You can stop a test when any of the following conditions are true: * When conversions equals Stop the test when total conversions across all variants reach a specific number *Example: Stop at 1000 conversions* * When conversion rate is Stop the test when a variant reaches a specific conversion rate *Example: Stop if a variant hits 5%* * When tested users reach Stop the test when a specific number of unique tested users have seen the variants *Example: Stop after 1000 tested users* * When P2BB is Stop the test when a variant reaches a given Probability to Be Best (P2BB) *Example: Stop if a variant hits 95% P2BB* > You can use any combination of these rules — the test will stop as soon as one is satisfied. *** ### What happens when a test auto-stops? * The test status changes to Paused * No more traffic is distributed to variants * The best-performing variant (based on current results) is shown to all users * You can still view historical results and restart the test if needed # AI Optimize traffic Optibase’s AI Optimize Traffic feature automatically adjusts how traffic is distributed between your variants, based on performance, to help you reach better results, faster.
*** ### What it does When enabled, AI Optimize Traffic uses real-time test data to: * Monitor conversion performance of each variant * Dynamically allocate more traffic to the better-performing variants * Still collect data on all variants (just in different proportions) This means your high-performing variants get more exposure while you’re still testing. *** ### How to enable it 1. Open the test where you want to optimize traffic 2. In the test header, toggle on AI Optimize Traffic Once turned on, Optibase will take over traffic split management and begin rebalancing traffic intelligently based on conversions. *** ### How it works with test types * Works with both A/B Tests and URL Split Tests * Can be used alongside Auto Stop and Alerts * Does not guarantee a fixed percentage split — it adapts over time *** ### Notes * You can toggle AI Optimize Traffic off anytime to return to a fixed 50/50 split or your manually defined distribution * This feature helps accelerate winning outcomes, especially for tests with high traffic volume *** # Set alerts for tests {% embed url="" %} Optibase lets you set Alerts to monitor your test progress and get notified when specific performance conditions are met — without automatically stopping the test.
This helps you stay informed and act quickly when something important happens. *** ### How to set up alerts 1. Open the test you want to monitor 2. Click the Alerts button in the test header 3. Toggle on any of the available alert conditions 4. Enter your threshold values 5. Close the panel — your settings are saved automatically *** ### Available alert conditions You can choose to be alerted when: * Conversions equals Get notified when total conversions across all variants reach a certain number *Example: Alert at 1000 conversions* * Conversion rate is Be alerted when any variant hits a specific conversion rate *Example: Alert when conversion rate reaches 5%* * Tested users reach Alert when the number of tested users reaches a threshold *Example: Alert when 1000 users have been tested* * P2BB is Alert when any variant reaches a specific Probability to Be Best *Example: Alert at 95% P2BB* > Alerts will only notify you — they will not stop or change the test status. *** ### Where alerts appear * Alerts are displayed directly in the Optibase Web App * You can also receive notifications by email (coming soon) *** ### Tips * Use alerts to monitor tests during ad campaigns or traffic spikes * Combine alerts with Auto Stop to automate decision-making and stay in control *** # Preview Variants {% embed url="" %}
Before making a test live, you can preview each variant to make sure everything looks and works as expected. This is especially useful for double-checking layout, content, and interactions in Webflow. *** ### How to preview a variant 1. Open the Optibase Web App 2. Navigate to the Test that contains the variant you want to preview 3. Click the Preview/Force Icon next to the variant 4. A modal will appear with a preview URL * Input the base URL of your website (where the test runs) * Click Copy to copy the full preview URL 5. Open the link in a browser to view the variant live > The preview URL includes a special optibaseVariants search param that forces Optibase to load the specific variant. *** ### Example preview URL ``` https://example.com?optibaseVariants=hero_headline:variant_b ``` You can also preview multiple variants from different tests by chaining them: ``` https://example.com?optibaseVariants=hero_headline:variant_b;cta_button:variant_a ``` *** ### Notes * Previewing does not affect your test data — no page views or conversions are tracked * You can share preview URLs with clients or teammates for feedback * If nothing changes on the page, double-check that the variant is connected properly # Force Variants {% embed url="" %}
The Force Variant feature lets you send users to a specific variant directly using a URL parameter. This is useful when you want a controlled group of users (like ad traffic) to always see the same version of a test. *** ### Common use cases * A/B testing multiple ad campaigns with fixed landing page content * Running a demo or client presentation that always shows a specific variant * QA and debugging specific variant setups *** ### How it works To force a variant, Optibase uses a special URL parameter: ``` optibaseVariants=test_id:variant_id ``` When a user visits a page with this parameter in the URL, Optibase will: * Bypass random variant selection * Show the specified variant * Maintain this variant for the user for the duration of the session *** ### How to generate a Force Variant URL 1. Go to the Variants tab inside your test in the Optibase dashboard 2. Click the Preview / Force icon next to the variant you want to force 3. A modal will appear with two options: * Preview: Opens the URL for manual testing * Force: Generates a link with the variant forced via query param 4. Enter the URL where the test will run 5. Click Copy to copy the full forced URL Example URL: ``` https://example.com?optibaseVariants=header_text:variant_b ``` When users visit this link, they will be shown variant\_b of the header\_text test. *** ### Forcing multiple variants You can force multiple variants from different tests by chaining them using a semicolon: ``` optibaseVariants=header_text:variant_b;footer_cta:variant_a ``` Each test\_id:variant\_id pair should be separated with ;. *** ### Notes * Force Variant overrides random selection but only applies during that session * This does not affect test data or variant assignment for other users * Users who receive a forced variant still count as Tested Users and trigger conversions as normal # Filter test results by a specific time period Optibase lets you filter test results by date to focus on specific time ranges. This is especially useful for analyzing performance during campaigns, seasonal traffic spikes, or troubleshooting sudden changes in results.
*** ### How to filter by date 1. Open your test Navigate to the Tests page and click on the test you want to analyze. 2. Go to the Results tab Click the Results tab to view performance data. 3. Set the date range Use the From and To date pickers at the top of the results section to define the time period you want to view. 4. View filtered results Once selected, the report will update to show only data collected within the chosen range. *** ### Additional notes * You can reset the date range to return to viewing the full test duration * This filter applies to all result metrics, including: * Page Views * Conversions * Conversion Rate * P2BB * Useful for comparing before and after changes or isolating campaign-specific impact *** ### Tips for using date filters * Use during ad campaigns to measure targeted traffic performance * Analyze performance dips or spikes tied to specific days * Compare weekdays vs. weekends, or different user behavior patterns over time *** # Share test results {% embed url="" %} Sharing test results with someone else in Optibase is quick and easy. Follow these steps: 1\. Navigate to Your Test 2\. Click on “Share Results” 3\. Generate and Copy the Link: • A popup will appear with the following message: *“Share Results: The link below will allow anybody with access to the link to view the results of this test. Only you will be able to edit the test.”* • Click to generate the link and copy it. 4\. Share the copied link with the person you’d like to give access to the results. **Additional Notes:** • The shared link provides view-only access to the test results. • Only the test owner can make edits or changes to the test. \ This feature makes it easy to collaborate and share insights with your team or stakeholders! # Probability to Be Best (P2BB) {% embed url="" %} Probability to Be Best (P2BB) is a statistical metric used in A/B testing to estimate how likely it is that a particular variant is the best-performing option in a test. P2BB is calculated using Bayesian statistics, which take into account both the observed results and the uncertainty in the data. It helps you make informed decisions about which variant to choose based on probability, not just raw conversion rates. *** ### Why it matters Unlike simple metrics like conversion rate, P2BB accounts for uncertainty and variation in your data. It gives you a clearer signal about which variant is likely to win — especially helpful when results are close or data is limited. *** ### How to interpret P2BB * Expressed as a percentage A higher percentage means a higher likelihood that the variant is the best performer. *Example: P2BB of 80% means there’s an 80% chance that this variant is better than the others.* * Compares variants directly You can directly compare which variant is leading. *If Variant A has a P2BB of 70% and Variant B has 30%, Variant A is more likely to be the better choice.* * Supports better decision making Use P2BB to decide which variant to keep, ship, or iterate on — especially when combined with other business data. *** ### When to determine a winner #### P2BB is dynamic P2BB updates as new data comes in. Early on, it may fluctuate significantly. As more traffic flows through the test, the values stabilize. #### It’s not absolute P2BB shows probability, not certainty. It’s a guide, not a guarantee. Consider it alongside other metrics like lift, conversions, and sample size. #### Use with other metrics P2BB is most effective when paired with: * Conversion rate trends * Traffic volume * Statistical confidence * Business impact #### Wait for 95% confidence We recommend waiting until a variant reaches a P2BB of 95% or higher before calling it a winner. This helps avoid premature decisions based on randomness or small sample sizes. *** ### Example You’re testing two homepage designs: * Variant A reaches a P2BB of 75% * Variant B has a P2BB of 25% This means Variant A currently has a 75% chance of being the better-performing design — but it’s not yet conclusive. You should continue the test until one variant reaches at least 95% P2BB for high confidence in the result. # Export Test Data Optibase makes it easy to export all your test data for external reporting, backup, or deeper analysis.
*** ### How to Export Data 1. Go to your Workspace Settings 2. Click on the Export section from the sidebar 3. Choose what data you want to export: * Conversions – Download all defined conversions * Tests – Export a full list of all created tests * Variants – Select a test and download all variants within it * Results – Select a test and download its result metrics * Tested Users – Filter by test and date range * Views – Export view data with filtering options * Conversion Events – Export all triggered conversion events Click Download after making your selection. Exports may take up to 5 minutes. Don’t close the tab during this process. *** ### Scheduled Results Export You can enable automatic exports of test results to your email. 1. Scroll to the Scheduled Results Export section at the bottom of the Export page 2. Use the dropdown to enable scheduling (e.g., daily, weekly) 3. The export will be sent to the email associated with your account or the email you specify You can opt to send it to yourself or teammates for ongoing performance monitoring. *** # Personalizations Personalization allows you to tailor your website’s experience for specific audiences. While A/B testing helps you find the best version for everyone, Personalization ensures that the right visitor sees the right content based on who they are and how they browse. *** ### How Personalization Works Instead of randomly splitting traffic between variants, Personalization uses Audience Rules to determine which version of a page a visitor should see. For example, you can show a "Free Shipping" banner only to returning visitors from a specific country, while new visitors see a standard "Welcome" message. *** ### 1. Create a New Personalization To get started, navigate to the Personalization tab in your Optibase sidebar and click Create New. #### Basic Info Give your personalization a clear name that describes the use case (e.g., "Mobile Promo - California Users"). This name is internal and helps you identify the experiment in your analytics. *** ### 2. Set Up Audience Rules The core of personalization is defining who sees the tailored content. You can combine multiple rules to create highly specific segments. Available audience conditions include: * Location: Target visitors by country, region, or city. * Device & Tech: Filter by browser (Chrome, Safari, etc.), operating system (iOS, Windows), and screen size (Mobile vs. Desktop). * User Behavior: Target "New" vs. "Returning" visitors. * Referrer: Show content based on where the user came from (e.g., a specific UTM campaign or social media site). ### 3. Assign Variants Once your audience is defined, you will connect your design variants: 1. Default Variant: This is the "Control" version shown to everyone who does not meet your audience rules. 2. Personalized Variant: This is the tailored experience shown only to the specific audience you defined in Step 2. After connecting your variants and setting your goals (conversions), click Start Personalization. The Optibase script will now automatically: 1. Identify the visitor's attributes (location, device, etc.). 2. Check if they match your Audience Rules. 3. Instantly serve the correct variant without any "flickering" or layout shifts. ### Best Practices * Start Simple: Begin with broad personalizations like "Mobile vs. Desktop" before moving into complex geographic or behavioral rules. * Monitor Analytics: Even though this isn't a traditional A/B test, Optibase still tracks conversions for each personalized segment so you can measure the impact of your tailored content. # Heatmaps Heatmaps are a visual analytics tool that helps you understand how users interact with your pages. Instead of looking at raw numbers, heatmaps use a color-coded system—ranging from "cold" blue to "hot" red—to show you exactly where users are looking, clicking, and scrolling. ### How Heatmaps Work Heatmaps aggregate the behavior of hundreds or thousands of visitors into a single visual overlay. This allows you to spot patterns that would be impossible to see in standard analytics: * Click Maps: Identify which buttons, links, or images get the most engagement—and catch "dead clicks" where users click on non-interactive elements. * Scroll Maps: See how far down the page users actually go. This helps you determine if your most important content (like a CTA) is being missed because it’s placed too low. * Move Maps: Track cursor movement to see which areas of the screen capture the user's attention and interest. ### Ways to Create Heatmaps in Optibase There are two primary ways to generate heatmaps, depending on whether you want to analyze a single page or compare different test versions. #### 1. URL-Based Heatmaps If you want to analyze a specific page on your site (like your homepage or a pricing page), you can create a standalone heatmap. 1. Navigate to the Heatmaps tab in the sidebar. 2. Click Create New. 3. Enter the URL of the page you want to track. 4. Ensure the Optibase script is installed on that page. Once active, Optibase will begin gathering data from every visitor who lands on that specific URL. #### 2. Test-Based Heatmaps The most powerful way to use heatmaps is within an A/B test. When you are testing different designs, you need to know *why* one variant is outperforming another. * Automatic Generation: You can toggle Heatmaps ON within the settings of any A/B test. * Variant Comparison: Optibase will automatically create individual heatmaps for every variant and variant combination in that test. * Behavioral Insights: This allows you to compare behavior side-by-side. For example, you might see that users in "Variant B" are clicking the CTA more because they aren't getting distracted by a large hero image that was present in "Variant A." ### Why Use Heatmaps? * Determine User Behavior: Stop guessing what users like. Visual data shows you exactly what captures their interest. * Identify Friction: Spot areas where users get confused or lose interest and drop off. * Optimize Layouts: Use scroll data to place your most important messages where the majority of your audience will actually see them. * Validate Test Results: Use heatmaps to provide context to your A/B test winners, making it easier to explain "the why" to your team or clients. # User recording sessions While Heatmaps show you where users aggregate, User Recordings allow you to see the individual "human story" behind the data. By watching reconstructions of real user sessions, you can pinpoint exactly where visitors get confused, frustrated, or stuck. ### What are User Recordings? User Recordings (also known as session replays) are reconstructions of a visitor's journey on your site. They capture: * Mouse movements and clicks * Scrolling behavior * Page navigation * Mobile taps and swipes Watching a recording is like sitting next to your user as they browse, giving you advanced behavioral data that numbers alone can't provide. ### Ways to Enable Recordings Just like Heatmaps, there are two ways to capture session data in Optibase. #### 1. URL-Based Recordings If you want to monitor a specific page—like a high-traffic landing page or a complex checkout flow—you can set up a recording manually. 1. Go to the User Recordings tab in the left sidebar. 2. Click Create New. 3. Enter the specific URL you wish to record. 4. Optibase will begin capturing every session for users who visit that exact path. #### 2. Test-Based Recordings To understand why one A/B test variant is winning over another, you can enable recordings directly within your test settings. * Auto-Capture: Toggle the "Recordings" setting to ON inside any active test. * Test Context: This automatically records every "Tested User"—meaning anyone who is part of your experiment. * Segmented Insights: You can then filter recordings by variant to see how users interact with "Variant A" versus "Variant B." ### Advanced Behavioral Data User Recordings go beyond basic tracking to show you high-intensity signals: * Rage Clicks: Spot when a user clicks a button or element repeatedly out of frustration. * Dead Clicks: Identify links or buttons that don't work or aren't intuitive. * Navigation Loops: See if users are getting stuck in a circle between pages because they can't find what they need. ### Why use User Recordings? * See the "Why": If a test shows a high bounce rate, a recording might reveal a technical bug or a confusing layout shift that the analytics didn't catch. * Zero Guesswork: Instead of assuming why users aren't clicking your CTA, you can watch them scroll right past it or hover over it without clicking. * Support & Debugging: Use recordings to see exactly what happened before an error occurred, making it easier for your team to replicate and fix issues. # Analytics Optibase Analytics provides an automatic, high-level overview of your website's performance. As soon as the Optibase script is installed and published on your site, we begin gathering data to give you a clear picture of your traffic and user behavior—no extra configuration required. While Optibase is known for testing, this dashboard is designed to be your one-stop shop, allowing you to replace other complex analytics platforms with a single, streamlined view. *** ### How it Works The moment your site goes live with the Optibase script, it begins monitoring every interaction. This data is collected automatically and populated into your Analytics dashboard, found in the left sidebar. Unlike traditional platforms that require manual "event" setup for every small detail, Optibase tracks the essential metrics out of the box, focusing on helping you increase both revenue and conversion rates. *** ### Core Metrics Captured The Analytics dashboard displays a comprehensive breakdown of your project's health: * Page Views: Tracks every visit to every specific page across your website. * Visitor Volume: See exactly how many unique individuals are coming to your site. * Device Breakdown: Understand your audience split between Mobile, Desktop, and Tablet to ensure your site is optimized for the right screens. * Geographic Location: See where in the world your visitors are accessing your site from. * User Behavior: Monitor the basic path users take before they hit your conversion goals. ### Why use Optibase Analytics? #### 1. Zero-Manual Setup You don’t need to be a data scientist to get insights. Because the analytics are tied to the same script used for your Heatmaps, Recordings, and A/B tests, all your data lives in one place. #### 2. Automatic Page Discovery Optibase automatically detects new pages as they receive traffic. You can view the performance of specific URLs within your project without having to register them manually. #### 3. Integrated Insights By seeing your general analytics alongside your Conversion Tracking and User Behavior data, you can stop "guessing" what works. You can easily see how overall traffic trends correlate with the success of your active experiments. ### Privacy and Performance Optibase Analytics is built to be privacy-compliant and lightweight. * No Speed Impact: Our asynchronous script ensures that gathering analytics never slows down your page load or hurts your SEO. * Clean Data: We filter out common bots and "junk" traffic to ensure your page view counts reflect real human interest. # General *** If you are using Optibase with Webflow, please follow this guide instead: [Optibase Webflow App](/webflow-app/optibase-webflow-app) *** Optibase needs just one thing to start working: the Optibase custom script installed on your site. Once added, the script handles test logic, variant assignment, and conversion tracking automatically. *** ### 1. Get your custom script 1. Log in to your [Optibase dashboard](https://app.optibase.io) 2. Go to Workspace Settings 3. Copy the Custom Script provided for your workspace
*** ### 2. Add the script to your website Make sure: * The script is placed before the closing \ tag * It uses the correct data-optibase-id from your dashboard * You only include one copy of the script per page *** ### 3. Verify the installation After installation: 1. Open any page where the script is installed 2. Add ?optibaseEnableDebugMode to the URL Example: 3. Open the browser console (right-click → Inspect → Console tab) 4. You should see debug logs from the Optibase script If the script is working correctly, you’ll see messages about: * Loaded test IDs * Selected variants * Conversion listeners *** ### 4. Start testing Once the script is live: * You can create A/B Tests, Split Tests, and Conversions from the Optibase dashboard * All variant logic and tracking will run automatically for visitors *** # IP Blacklist Use the IP Blacklist feature to exclude specific IP addresses from data collection. This is helpful when you want to prevent internal traffic — like your team, agency, or testers — from affecting test data.
*** ### How it works * Users from blacklisted IPs will still see tests and variants * However, their actions will not be counted toward: * Tested users * Conversions * Page views * Any test metrics *** ### How to add an IP 1. Go to Workspace Settings 2. Click IP Blacklist from the left-hand menu 3. Enter the IP address in the input field 4. Click Add IP to blacklist You’ll see a list of all blacklisted IPs once added. *** ### When to use this * Exclude internal teams from A/B test data * Prevent test manipulation from known testers * Clean up analytics by removing non-customer traffic *** # IP Collecting The IP Collecting setting allows you to store the IP address of each tested user to improve tracking accuracy, enable geo-location insights, and enhance debugging during test analysis.
*** ### How it works * When enabled, Optibase stores the IP address of each user who participates in a test. * Collected IPs are viewable in the Events screen of the app. * This feature helps with: * More accurate location-based testing * Debugging and isolating unusual traffic * Enhanced filtering and segmentation of data *** ### How to enable 1. Go to Workspace Settings 2. Click IP Collecting from the menu 3. Toggle the Collect IP addresses option on or off You can turn this feature off at any time by unchecking the toggle. *** ### Privacy Note Be mindful of data privacy regulations (like GDPR) when enabling IP tracking. If you’re unsure, consult your legal team to confirm compliance based on your region or audience. *** *** # Domain Whitelist The Domain Whitelist feature lets you control which domains are allowed to send data to Optibase. This is useful for improving security and preventing data from being collected from unintended environments.
*** ### How it works By default, Optibase will gather data from any domain where the custom script is installed. When you add domains to the whitelist, only those domains will be allowed to send data. All others will be ignored — even if the script is present. *** ### How to whitelist a domain 1. Go to your Workspace Settings 2. Click on Domain Whitelist 3. Enter your domain (e.g. yourwebsite.com) 4. Click Add domain to whitelist Once added, Optibase will only collect data from the domains listed here. > ℹ️ If the whitelist is empty, data will be collected from all domains where the script is installed. *** Use this setting to prevent accidental data pollution from staging, development, or cloned sites. # Custom integrations Optibase supports integrations with the tools you already use, so you can sync data, trigger conversions, and extend your experimentation workflow. *** ### What you can do with integrations * Send conversion events to third-party analytics and ad platforms * Trigger conversions from external sources like Google Tag Manager or your backend * Use your own identifiers by assigning external user IDs * Analyze performance alongside other tools in your marketing or product stack *** ### Need a custom integration? We offer support for custom workflows. If you’re using a specific tool or need help connecting Optibase to your stack, [contact our support team](mailto:support@optibase.io). # Active Variants API If you wish to determine programmatically what variant Optibase has shown to the user, you can use the following global variable and function exposed by the Optibase Custom Script. ## window\.optibaseActiveVariants Optibase Custom Script sets a global variable `window.optibaseActiveVariants` when all the tests have been loaded, and the variants have been chosen and displayed. The variable is an array of active variants with a type of: ```typescript type ActiveVariants = { userFriendlyTestId: string userFriendlyVariantId: string }[] ``` The variable will only be set once the variants have been chosen and displayed. Before, the variable will be `undefined`. *Note: Only Variants for Active and non-restricted Tests will be included. If the Main Variant is shown by default for a Test because the Test it is restricted or inactive, it will not be included in the* optibaseActiveVariants. ## window\.optibaseAddActiveVariantsListener Optibase Custom Script sets a global function `window.optibaseAddActiveVariantsListener` that accepts a callback that will be triggered once the `window.optibaseActiveVariants` have been set. The function is of type: ```typescript type OptibaseAddActiveVariantsListener = ( callback: (optibaseActiveVariants: ShownVariant[]) => void ) => void ``` You can use this to set a listener that will be triggered once the optibaseActiveVariants have been set. # MCP Server ## Connect Optibase to AI Assistants Optibase integrates with AI assistants like **Claude** and **Cursor** through the Model Context Protocol (MCP). This lets you ask questions about your A/B tests, analytics, heatmaps, and conversions in natural language — and get instant answers from your actual data. ### Getting Started #### Claude Desktop 1. Open Claude Desktop settings and navigate to the **MCP Servers** section 2. Add a new server with the following URL: ``` https://my.optibase.io/api/mcp ``` 3. The first time you use it, a browser window will open asking you to log in and select a workspace 4. Once connected, you can start asking questions about your data #### Cursor 1. Open Cursor settings and go to **MCP Servers** 2. Add a new server: * **Name**: Optibase * **Type**: HTTP * **URL**: `https:///api/mcp` 3. Log in when prompted and select your workspace #### Other MCP-Compatible Clients Any client that supports the MCP protocol can connect using the server URL above. Authentication is handled automatically via OAuth — you'll be prompted to log in and pick a workspace on first use. *** ### What Can You Do? Once connected, just ask your AI assistant questions in plain English. Here's what's possible: #### Analyze Your A/B Tests Ask about test performance, compare variants, and get actionable recommendations. * "Show me all my active A/B tests" * "What are the results for my homepage headline test?" * "Which variant is winning in my pricing page test?" * "Compare conversion rates across all variants for my checkout flow test" * "How has my hero section test performed over the last 30 days?" * "Show me results for my landing page test filtered by desktop users only" * "Which of my tests have enough data to declare a winner?" #### Review Website Content & Suggest Improvements The assistant can fetch your live test pages and analyze the actual content of each variant. * "Fetch the page for my hero section test and tell me what each variant looks like" * "Suggest copy improvements for the losing variant in my homepage headline test" * "What are the differences between variant A and B in my CTA button test?" #### Explore Your Traffic & Analytics Understand how visitors interact with your site across pages, devices, and geographies. * "What are my top 10 most visited pages?" * "Show me daily traffic trends for the last month" * "How many tested users did I have each month this year?" * "Break down traffic to /pricing by country" * "Compare mobile vs desktop traffic on my landing pages" #### Understand Your Heatmaps Get engagement summaries from your heatmap data without looking at screenshots. * "List all my heatmaps" * "What's the click and scroll data for my homepage heatmap?" * "Compare mobile vs desktop engagement on my product page" #### Track Conversions Review your conversion goals and how they perform across tests. * "List all my conversion goals" * "Show me daily conversion trends for my signup form test" * "Which tests are connected to my 'Purchase' conversion?" #### Segment Your Audience Break down your test visitors by country, device, browser, or operating system. * "What devices do visitors in my pricing page test use?" * "Break down visitors by country for my homepage headline test" * "Show me the browser distribution for my checkout flow test" #### Get Strategic Insights Combine multiple data points and ask for high-level recommendations. * "Give me a summary of all my running experiments" * "Analyze my pricing page test and recommend what I should do next" * "Which tests should I stop and which should keep running?" * "What patterns do you see across my recent test results?" *** ### Tips * **You don't need to know tool names** — just ask naturally. The AI will figure out which data to pull. * **Filter by date** — ask for "last 7 days", "this month", or any specific date range. * **Filter by segment** — narrow results by country, device type (phone/tablet/desktop), browser, or OS. * **Combine questions** — ask follow-up questions to dig deeper into any result. * **Ask for recommendations** — the AI can analyze your data and suggest next steps, not just report numbers. # Google # Google Analytics 4 ### GA4 Script Tag If you have added the GA4 Script Tag directly to your page's HTML, Optibase will automatically detect it and trigger an event when a Variant is shown to a user. You do not need to connect Google Analytics to Optibase for that to happen; if you have Google Analytics set up on your website in that way, that is Optibase's default behavior. The event that Optibase will send will have the name: `optibase_variant_shown`, event\_category `optibase`, and event\_label: `{testId:variantId}`. ### Google Tag Manager If you have added GA4 through the Google Tag Manager, you must manually set up the trigger and a custom tag. Follow this guide to do that: [Google Analytics 4 with GTM](/integrations/google/google-analytics-4-with-gtm) ## Audiences You can connect your Google Analytics account and property to Optibase by going to the integrations page in the Optibase Web app. As mentioned before, you do NOT need to connect Google Analytics to Optibase to start collecting events mentioned above. Connecting your Google Analytics account and property to Optibase allows you to create audiences for Variants automatically through Optibase. More about Google Analytics Audiences: To automatically create an audience for Variants in a Test for Google Analytics: 1. Connect the Google Analytics account and property you have setup above. 2. Navigate to the Optibase Test you want to import into Google Analytics, go under settings, and click Create Audiences. 3. This will create an Audience for each Variant in that Test. The audience will include everybody who has seen the Variant. 4. You should then see the newly created audiences in Google Analytics.
5. You can then click on the Audience to see analytics about users who saw a specific Variant. Important: It will take 24h/48h for the audiences to accumulate new users. ## Create an Audience for Variant You can also create an Audience for a Variant when you are creating a Variant:
# Google Analytics 4 with GTM *Note: This is only needed if you have GA4 setup through GTM. If you have added the GA4 script tag directly in your HTML, the Optibase events will be sent automatically.* #### Guide: Setting Up a GTM Trigger for Optibase Variant Shown Event This guide will walk you through setting up a Google Tag Manager (GTM) trigger that fires when an Optibase variant is shown. Additionally, we will create a tag that sends an event to Google Analytics 4 (GA4). **Step 1: Access GTM and Create a New Trigger** 1. **Log in to your GTM account** and open the container you want to configure. 2. **Navigate to Triggers** in the left-hand menu. 3. Click on the **New** button to create a new trigger. 4. **Name your trigger** (e.g., "Optibase Variant Shown Trigger"). 5. Choose **Trigger Type: Custom Event**. **Step 2: Set Up the Custom Event Trigger** 1. In the **Trigger Configuration**, set the **Event Name** to a custom name, such as `optibase_variant_shown`. 2. Choose **This trigger fires on: All Custom Events**. **Step 3: Create a Custom HTML Tag to Listen for Optibase Variants** 1. **Navigate to Tags** in the left-hand menu. 2. Click on the **New** button to create a new tag. 3. **Name your tag** (e.g., "Optibase Variant Listener"). 4. Choose **Tag Type: Custom HTML**. 5. Add the following HTML and JavaScript code to the HTML field: ```html ``` 6. **Set the tag to fire on All Pages**. **Step 4: Create Variables to Capture Event Data** 1. **Navigate to Variables** in the left-hand menu. 2. Click on the **New** button to create a new variable. 3. **Name your variable** (e.g., "`event_category`"). 4. Choose **Variable Type: Data Layer Variable**. 5. Set the **Data Layer Variable Name** to `event_category`. 6. Repeat steps 2-5 to create another variable for `event_label`. **Step 5: Create a GA4 Event Tag to Capture the Variant Data** 1. **Navigate to Tags** in the left-hand menu. 2. Click on the **New** button to create a new tag. 3. **Name your tag** (e.g., "GA4 Optibase Variant Event"). 4. Choose **Tag Type: GA4 Event**. 5. Select your GA4 configuration tag in the **Configuration Tag** field. 6. Set the **Event Name** to `optibase_variant_shown`. 7. In the **Event Parameters** section, add the following parameters: * **Parameter Name**: `event_category` * **Value**: `{{event_category}}` * **Parameter Name**: `event_label` * **Value**: `{{event_label}}` 8. Click on **Triggering** and add the custom event trigger you created in Step 1 (e.g., "Optibase Variant Shown Trigger"). **Step 6: Publish Your Changes** 1. Click on the **Submit** button in the top right corner of the GTM interface. 2. Follow the prompts to publish your changes. **Final Check** * **Preview your GTM container** to ensure that the custom event fires correctly when an Optibase variant is shown. * **Check GA4** to verify that the events are being recorded as expected. By following these steps, you will have set up a GTM trigger that listens for Optibase variant events and sends the relevant data to GA4. # Trigger Conversions with GTM You can follow these detailed steps to set up Google Tag Manager (GTM) to trigger a Programmatic Conversion when a conversion event happens. This setup will involve creating triggers, tags, and potentially variables in GTM. ## Step 1: Define the Conversion Event in GTM First, you must define what constitutes a "conversion" in your context. This could be a page visit, form submission, button click or any other user interaction. ## Step 2: Create a Trigger for the Conversion Event 1. **Go to Google Tag Manager Dashboard.** 2. **Click on 'Triggers' in the left sidebar.** 3. **Click 'New' to create a new trigger.** 4. **Set up the trigger:** * Choose a trigger type that matches your conversion event. For example, choose "Form Submission" for form submissions or "Click" for button clicks. * Configure the trigger with the necessary filters to capture your conversion event accurately. For example, if it’s a button click, you might need to specify certain button properties (like the button's ID or text). ## Step 3: Create a Custom JavaScript Tag 1. **Go to 'Tags' in the GTM dashboard and click 'New'.** 2. **Click 'Tag Configuration' and choose 'Custom HTML'.** 3. **Enter the custom JavaScript code:** ```html ``` Replace `'yourUserFriendlyConversionId'` with the actual ID or a variable that dynamically determines the ID based on the context of the conversion. ## Step 4: Add a Trigger to the Tag 1. **In the same 'Tag' configuration screen, click 'Triggering'.** 2. **Select the trigger you created in Step 2.** 3. **Save the tag.** ## Step 5: Test Your Tag 1. **Go back to the GTM main dashboard and click 'Preview'.** 2. **Navigate to your site where the conversion event can be triggered.** 3. **Ensure the tag fires when the event occurs. Check the output in the GTM preview pane to confirm that the custom JavaScript function is being called as expected.** ## Step 6: Publish Changes Once you are satisfied that the tag is working correctly in the preview mode, go back to GTM: 1. **Click 'Submit' to create a new version.** 2. **Name your version and describe the changes.** 3. **Click 'Publish' to make your changes live.** This setup ensures that every time the specified conversion event happens, your custom JavaScript function `optibaseSendConversionEvent` is called with the specified `userFriendlyConversionId`. Adjust the conversion ID dynamically using GTM variables if the ID should vary based on the conversion context. # BigQuery BigQuery Sync allows you to export Optibase experiment and analytics data directly to your Google BigQuery warehouse. This enables deeper analysis, custom reporting, and integration with your workflow ### Prerequisites Before setting up the integration, make sure you have: * A **Google Cloud Platform (GCP)** account * A **BigQuery project and dataset** * Permissions to create **service accounts and keys** in Google Cloud * Access to your **Optibase workspace settings** *** ## Step 1: Create a BigQuery Dataset 1. Go to **Google Cloud Console** 2. Navigate to **BigQuery** 3. Select your **Project** 4. Click **Create Dataset** 5. Enter the following details: | Field | Value | | ------------- | ------------------------------------ | | Dataset ID | Choose a name (e.g. `optibase_data`) | | Data location | Choose your preferred region | 6. Click **Create dataset** *** ## Step 2: Create a Service Account 1. Open **Google Cloud Console** 2. Navigate to **IAM & Admin** 3. Click **Service Accounts** 4. Click **Create Service Account** Fill in: | Field | Value | | -------------------- | ------------------------------------------------- | | Service account name | `optibase-bigquery-sync` | | Description | Service account used for Optibase BigQuery export | Click **Create and Continue** *** ## Step 3: Grant Required Permissions Assign the following role to the service account: * **BigQuery Data Editor** This allows Optibase to write experiment data into your dataset. Click **Continue**, then **Done**. *** ## Step 4: Create and Download the Service Account Key 1. Go to the **Service Account** you just created 2. Open the **Keys** tab 3. Click **Add Key** 4. Select **Create new key** 5. Choose **JSON** 6. Click **Create** A JSON key file will be downloaded to your computer. You will use this file to authenticate Optibase with BigQuery. *** ## Step 5: Configure BigQuery Sync in Optibase 1. Log in to **Optibase** 2. Navigate to: **Workspace Settings → Integrations → BigQuery** 3. Click **Connect BigQuery** Fill in the following fields: | Field | Description | | -------------------- | ----------------------------------- | | Project ID | Your Google Cloud project ID | | Dataset ID | The dataset you created earlier | | Service Account JSON | Upload the downloaded JSON key file | 4. Click **Save** *** ## Step 6: Verify the Connection After saving the integration: 1. Optibase will validate the credentials 2. If successful, the BigQuery connection will be activated 3. Data exports will begin automatically based on your workspace configuration New experiment and analytics data will start appearing inside your **BigQuery dataset tables**. *** ## Data Available in BigQuery The BigQuery export includes: * Experiment impressions * Experiment conversions * Visitor identifiers * Variant assignments * Event timestamps * Experiment metadata This allows you to combine Optibase data with your internal analytics and BI tools. *** ## Troubleshooting #### Permission errors Make sure the service account has: **BigQuery Data Editor** access to the dataset. #### Dataset not found Verify that the **Dataset ID** and **Project ID** are correct. #### Invalid JSON key Ensure you upload the **original JSON key file** generated in Google Cloud. # Mixpanel If you have added the Mixpanel Script Tag directly to your page's HTML, Optibase will automatically detect it and trigger an event when a Variant is shown to a user. You do not need to connect Mixpanel to Optibase for that to happen; if you have Mixpanel set up on your website in that way, that is Optibase's default behavior. The event that Optibase will send will have the name: `optibase_variant_shown`, and properties variantId and testId. An example of an event you should see in Mixpanel:
You can then use these events to create Insights in Mixpanel to compare the behavior of visitors who saw different variants. An example would be an Inisight setup like the one below, where we filter by a specific test ID to only see visitors who saw a specific test. We then create a breakdown based on the variant ID.
# Marketo Complete these steps in your Marketo instance before configuring the integration in the Optibase dashboard. {% stepper %} {% step %} ## Create an API Role Marketo requires a dedicated role with API permissions. 1. Go to **Admin → Users and Roles** 2. Click **New Role** 3. Give it a name (e.g. `Optibase API`) 4. Enable the following permissions: * **Access API** * **Read-Write Lead** * **Read-Write Activity** 5. Save the role {% endstep %} {% step %} ## Create an API-Only User 1. Go to **Admin → Users and Roles** 2. Click **Invite New User** 3. Fill in a name and email 4. On the Roles step, assign the role created in Step 1 5. Check **API Only** 6. Complete the invite {% endstep %} {% step %} ## Create a LaunchPoint Service This generates the Client ID and Client Secret used by Optibase. 1. Go to **Admin → Integration → LaunchPoint** 2. Click **New → New Service** 3. Fill in: * **Display Name**: `Optibase` * **Service**: `Custom` * **API Only User**: select the user created in Step 2 4. Click **Create** 5. Click **View Details** on the new service — copy the **Client ID** and **Client Secret** {% endstep %} {% step %} ## Find Your Munchkin ID 1. Go to **Admin → Integration → Munchkin** 2. Copy the **Munchkin Account ID** (format: `XXX-XXX-XXX`) {% endstep %} {% step %} ## Create the Custom Activity Type Optibase sends a custom activity to Marketo each time a visitor is exposed to a test variant. 1. Go to **Admin → Marketo Custom Activities** 2. Click **New Custom Activity** 3. Fill in: * **Name**: `Optibase Variant Seen` * **API Name**: leave as auto-generated * **Description**: `Fired when a visitor is assigned and exposed to a test variant in Optibase` 4. Set the **Primary Attribute**: * **Name**: `Test ID` * **API Name**: `testId` * **Data Type**: `String` 5. Add the following **Secondary Attributes** (click **Add Attribute** for each): | Name | API Name | Data Type | | ------------ | ------------- | --------- | | Variant ID | `variantId` | String | | Variant Name | `variantName` | String | | Test Name | `testName` | String | | Workspace ID | `workspaceId` | String | | Origin URL | `originUrl` | String | | View ID | `viewId` | String | > The **API Name** values must match exactly as shown — Optibase uses these to map data. 6. Click **Create** 7. Click **Approve** on the activity — it will not be usable until approved 8. Note the **Activity Type ID** shown in the Custom Activities list — you will need this in the Optibase dashboard {% endstep %} {% step %} ## Set Up the Lookup Field The **Lookup Field** is the Marketo Lead field that contains the same value you pass to Optibase as the user's external identifier. When Optibase receives: ```javascript optibase.setTestedUserExternalId(externalId) ``` it will search Marketo for a lead where: ``` {Lookup Field} = {externalId} ``` ### Example If your application calls: ```javascript optibase.setTestedUserExternalId("user_123") ``` then the Marketo lead must contain: | Marketo Field | Value | | ------------- | ---------- | | `externalId` | `user_123` | If your application calls: ```javascript optibase.setTestedUserExternalId("john@example.com") ``` then the Marketo lead must contain: | Marketo Field | Value | | ------------- | ------------------ | | `email` | `john@example.com` | The value stored in Marketo must exactly match the value being sent to Optibase. ### Option A — You pass the user's email address as `externalId` If the value passed to Optibase is the user's email address: ```javascript optibase.setTestedUserExternalId("john@example.com") ``` then you can use Marketo's built-in `email` field. Enter: ``` email ``` as the Lookup Field in the Optibase dashboard. No additional Marketo field setup is required. ### Option B — You pass any other identifier as `externalId` If the value passed to Optibase is not an email address (for example a customer ID, CRM ID, user ID, or account ID), you must create a Marketo Lead field that stores that same value. 1. Go to **Admin → Field Management** 2. Click **New Custom Field** 3. Fill in: * **Object**: `Lead` * **Type**: `String` (or `Integer` if your identifier is numeric) * **Name**: any name you prefer (e.g. `External ID`) * **API Name**: note this value exactly (e.g. `externalId`, `crmUserId`, `customerId`) 4. Click **Create** Enter the field's **API Name** as the Lookup Field in the Optibase dashboard. ### Example Application: ```javascript optibase.setTestedUserExternalId("user_123") ``` Marketo: | Field | Value | | ------------ | ---------- | | `externalId` | `user_123` | Optibase Lookup Field: ``` externalId ``` > The Lookup Field must contain the same value that your application passes to `optibase.setTestedUserExternalId(...)`. If the values do not match, Optibase will not be able to find the correct Marketo lead. **If you leave the Lookup Field blank** in the Optibase dashboard, Optibase defaults to: ``` externalId ``` In that case, create a Marketo Lead field with API Name: ``` externalId ``` and store the same external identifier value that you pass to Optibase. {% endstep %} {% step %} ## Configure in Optibase Go to **Optibase Dashboard → Settings → Integrations → Marketo** and enter: | Field | Where to find it | | ---------------- | ------------------------------------------------------------------------------------------ | | Munchkin ID | Admin → Munchkin → Munchkin Account | | Client ID | LaunchPoint → View Details | | Client Secret | LaunchPoint → View Details | | Lookup Field | The API name of the field you chose in Step 6. Leave blank to use the default `externalId` | | Activity Type ID | Admin → Custom Activities (the number shown next to your activity) | Click **Connect** — Optibase will verify the credentials before saving. {% endstep %} {% endstepper %} ## How it works after setup * When a visitor is identified in the app with the external identifier provided by your application, Optibase associates that identifier with the visitor * Optibase looks up the lead in Marketo using the **Lookup Field** and the provided `externalId` * If no lead exists, one is created automatically with that field set to the `externalId` * Each test variant the visitor has been exposed to is sent to Marketo as an **Optibase Variant Seen** custom activity attached to that lead * Previously seen variants from before identification are backfilled automatically ## Troubleshooting **Connection fails on save** * Double-check the Munchkin ID format (`XXX-XXX-XXX`) * Ensure the Client ID and Secret are from the LaunchPoint service, not from another integration * Confirm the API-only user has the role with all three permissions **No activities appearing on leads** * Confirm the custom activity is in **Approved** status * Confirm the Activity Type ID in Optibase matches the one in Marketo Admin **Lead not found / created with wrong field** * Confirm the Lookup Field API name matches exactly (case-sensitive) what is in Marketo Field Management * Confirm the `externalId` your app passes to Optibase matches the value stored on the lead in Marketo for that field # PostHog If you’re using PostHog alongside Optibase, you can easily track conversions by integrating Optibase’s data attributes into PostHog. Here’s how you can set it up: ## Identify the Conversion Attribute in Optibase: In Optibase, locate the data attribute associated with the conversion event you want to track (e.g., a button click or form submission). ## Set Up the Conversion Event in PostHog: • Navigate to Data Management in your PostHog dashboard. • Go to Actions and create a new action to track the desired event. • Use the HTML Selector Match option to identify elements based on the Optibase data attribute. • For example: If Optibase assigns data-optibase-conversion="get-started" to a button, use this selector in PostHog to track clicks on that button. Once the PostHog action is set up with the Optibase attribute, any interaction with the element will now trigger events in both Optibase and PostHog. ## Test Your Setup: • Visit the page where the conversion is set up. • Trigger the action (e.g., click the button or submit a form). • Check both Optibase and PostHog to ensure the events are being recorded as expected. # Amplitude ### Setup Unlike some integrations, Amplitude requires a one-time connection in your Optibase dashboard. 1. Go to your Optibase dashboard → **Settings** → **Integrations** 2. Find the Amplitude section and click **Connect** 3. Select your region — **United States (US)** or **Europe (EU)**. This must match the region of your Amplitude project. 4. Paste your **Amplitude API key**. You can find it in Amplitude → Settings → Projects → your project → General 5. Click **Connect**. Optibase will verify the key before saving. {% hint style="info" %} **Note:** This integration is available on paid plans only. {% endhint %} ### Testing the Connection Once connected, you can verify the integration is working by clicking Test Connection in the Amplitude integration settings. This sends a test event to your Amplitude project. You should see an event named `optibase_connection_test` appear in Amplitude under your project's event stream shortly after. ### Adding Amplitude to Your Page Include the Amplitude browser SDK on your page **before** the Optibase script: ```html ``` Replace `YOUR_AMPLITUDE_API_KEY` with your Amplitude project API key and set the `serverUrl` to match your region. ### Event Details #### optibase\_variant\_shown When a variant is assigned to a visitor, Optibase sends an event named `optibase_variant_shown` to Amplitude with the following properties: | Property | Description | | ----------- | ------------------ | | `testId` | ID of the A/B test | | `variantId` | Assigned variant | #### optibase\_conversion\_triggered Sent when a visitor triggers a conversion event. | Property | Description | | -------------- | ----------------------------------------------- | | `conversionId` | The ID of the conversion as defined in Optibase | *** ### Analytics Setup Once events are flowing into Amplitude, they can be used across Event Segmentation, Funnel Analysis, and User Lookup. A typical starting point is using `optibase_variant_shown` as a segmentation filter to isolate visitors by experiment and variant, then layering in `optibase_conversion_triggered` or any of your own events to measure downstream behaviour. # Segment ### Setup 1. Go to your **Segment workspace** → **Connections** → **Sources** → **Add Source** 2. Search for **HTTP API** and select it 3. Give the source a name (e.g. `Optibase`) and click **Add Source** 4. Copy the **Write Key** from the source overview page 5. Go to your **Optibase dashboard** → **Settings** → **Integrations** 6. Find the Segment section and click **Connect** 7. Paste your **Write Key** and select the region of your Segment workspace 8. Click **Connect** The Segment workspace region defaults to **United States (US)**. If your Segment workspace is EU-based, select **Europe (EU)** to ensure data is routed to the correct regional endpoint. See [Regional Segment | Twilio](https://www.twilio.com/docs/segment/guides/regional-segment) for how to set up an EU workspace in Segment. *** ### Event Details Optibase sends data to Segment server-side via the HTTP API source. Three types of calls are made automatically — no additional code is required on your page. #### Identify Sent when a visitor is seen for the first time. | Field | Value | | ------------- | ------------------------------ | | `anonymousId` | Optibase's internal visitor ID | | `userId` | Your own user ID (if provided) | Context is also included where available. *** #### Experiment Viewed Sent when a visitor is assigned a variant for the first time. | Property | Description | | ------------ | ----------------------------------- | | `test_id` | The ID of the A/B test | | `variant_id` | The variant assigned to the visitor | *** #### Conversion Triggered Sent when a visitor triggers a conversion event. | Property | Description | | ----------------- | ------------------------------------------------------------------ | | `conversion_id` | The conversion's ID in Optibase | | `conversion_type` | The type of conversion (e.g. `CLICK`, `PAGE_VIEW`, `PROGRAMMATIC`) | | `origin_url` | The page where the conversion occurred | If a conversion is configured as **one per visitor**, duplicate events are suppressed and Segment will only receive the first conversion per visitor. *** ### Using the Data in Segment Once connected, experiment data is available across your Segment workspace like any other source. You can connect your HTTP API source to a variety of destinations to further analyse the data — including analytics platforms, data warehouses, CRMs, and marketing tools. All events — Identify, Experiment Viewed, and Conversion Triggered — are forwarded automatically to any destination connected to your HTTP API source. No additional configuration in Optibase is required. # Segment # Stripe If you use Stripe for checkouts, standard client-side conversion tracking may not work because the final transaction occurs on Stripe's domain rather than your own. To track these conversions accurately, you can pass the Optibase User ID through to Stripe and use a Webhook to notify Optibase when a payment is successful. ### How it works 1. Capture: You retrieve the Optibase User ID from the browser. 2. Forward: You pass this ID to Stripe as a `client_reference_id`. 3. Notify: Stripe sends a webhook to your server upon successful payment. 4. Convert: Your server sends a server-to-server request to Optibase to record the goal. ### 1. Forward the ID to Stripe To link a Stripe session to an Optibase user, you must include the Optibase User ID in your Stripe Checkout link or API call. #### Using Stripe Payment Links If you are using pre-defined Stripe Payment Links, you can use a script to automatically append the ID to your buttons: ``` window.addEventListener('load', () => { const userId = window.optibaseTestedUserId; if (!userId) return; // Find all Stripe links and append the client_reference_id const links = document.querySelectorAll('a[href*="checkout.stripe.com"]'); links.forEach(link => { const url = new URL(link.href); url.searchParams.set('client_reference_id', userId); link.href = url.toString(); }); }); ``` #### Using Stripe API (Server-side) If you create Checkout Sessions via the Stripe API, include the ID in the `client_reference_id` parameter: ``` const session = await stripe.checkout.sessions.create({ client_reference_id: optibaseUserId, // Pass the ID from the frontend payment_method_types: ['card'], line_items: [{ price: 'price_H5ggY', quantity: 1 }], mode: 'payment', }); ``` ### 2. Set up the Webhook Once a purchase is completed, Stripe sends a `checkout.session.completed` event. You need a simple webhook listener to capture this and notify Optibase. Endpoint: `https://app.optibase.io/api/script/conversionEvent` Method: `POST` #### Example Payload Your server should send the following JSON to Optibase: ``` { "userId": "the_client_reference_id_from_stripe", "eventName": "Stripe Purchase", "value": 49.99 } ``` ### 3. Create the Conversion in Optibase For the conversion to be recognized, create a matching conversion event in your Optibase dashboard: 1. Go to your Project Settings > Conversions. 2. Create a new conversion. 3. Select Programmatic. 4. Enter the Event Name (e.g., `Stripe Purchase`). This must exactly match the `eventName` sent by your webhook. ### Recommendations * Global Placement: Place your JavaScript in the global header or site-wide settings to ensure the Stripe links are updated regardless of which page the user is on. # Optibase Webflow App {% hint style="info" %} **You can find the Optibase Webflow App here:** [**https://webflow.com/apps/detail/optibase**](https://webflow.com/apps/detail/optibase) {% endhint %} The Optibase Webflow App is a replacement for the Optibase Web App. It offers a "no code" option for setting up Conversions, Tests, and Variants. A quick video on how to setup an A/B test in Webflow with Optibase: {% embed url="" %} *** ### What it does The Webflow App is a full-featured alternative to the Optibase Web App. It’s designed for Webflow users who want to build and manage experiments without touching custom code. With the Webflow App, you can: * Create and manage A/B Tests, Split Tests, and Multivariate Tests * Set up and connect Conversions to elements using a visual interface * Create and assign Variants without editing HTML manually * Preview tests and view test IDs directly inside the Designer *** ### Why use the Webflow App * No-code setup Everything is integrated directly in Webflow — no need to manually copy IDs or edit HTML. * Visual variant mapping Select elements visually instead of assigning attributes by hand. * Faster workflow Save time switching between platforms by managing your experiments in one place. *** # Add the custom script Before you can run tests or track conversions in Optibase, you need to add the Optibase script to your Webflow project. This allows Optibase to run on your site and communicate with the server.
*** ### How to install the script in Webflow 1. Select and copy your custom script * Click to copy the script block provided (includes your unique workspace ID) 2. Open your Webflow Site Settings * In Webflow, click the Webflow logo (top left) * Click Site Settings 3. Paste the script into the Head * From the left sidebar, click Custom Code * Scroll to the Head code section * Paste the Optibase script here 4. Save and publish * Click Save Changes * Then click Publish to apply the update to your live site *** ### Example script snippet ``` ``` > Make sure you’re using the Public script with the correct data-optibase-id. *** ### Verify installation Once you’ve published your site: 1. Open your live website in the browser 2. Return to the Optibase dashboard 3. Click the Check button to confirm the script was detected If the script is running correctly, you’ll see a confirmation that Optibase has detected activity from your site. *** # Create a Conversion *How to connect a Conversion:* [Connect a Conversion](/connect-a-conversion) To create a Conversion, name it and click "Create": You should now connect this Conversion to an element on your page. Read about how to do that here: [Connect a Conversion](/connect-a-conversion)
The Optibase Webflow App lets you create and connect conversions without writing any code. Use conversions to track actions like clicks, form submissions, or page views — so you can measure which variants drive results. *** ### How to create a conversion 1. Open the Optibase Webflow App Make sure the app is installed and you’re inside the Webflow Designer. 2. Go to the Conversions tab Click the Conversions tab in the app sidebar. 3. Click “New Conversion” * Give your conversion a name * Choose a conversion type (e.g. Click, Submit, Page View, etc.) * Click Create *** ### Next step: connect the conversion Once the conversion is created, you’ll need to connect it to an element on your page (for Click or Submit types). This lets Optibase know which user interaction should trigger the conversion. *** # Create a Test/Variant Group
In the Optibase Webflow App, you can create A/B Tests, Split Tests, or Multivariant Tests directly inside the Webflow Designer — without writing any code. *** ### How to set up a test 1. Open the Optibase Webflow App Make sure the app is installed and you’re working inside the Webflow Designer. 2. Go to the Tests tab Click the Tests tab in the app sidebar. 3. Click “New Test” * Enter a name for your test * Choose a test type: * A/B Test (Variant Group) * Split Test (URL-based) * Multivariant Test * Click Create # Create a Split Variant Split Variants are used in URL-based Split Tests to compare entirely different Webflow pages. Each variant is a standalone page, and Optibase randomly sends users to one of them to measure which performs better.
*** ### How Split Tests work * The first variant you create is the Entry Variant. * When a user lands on this page, Optibase decides whether to: * Keep them on that page * Or redirect them to another variant If a user lands directly on a non-entry variant (e.g. via a paid ad), they will not be redirected, but the visit and conversions will still be tracked. *** ### How to create a Split Variant 1. Open the Optibase Webflow App inside the Webflow Designer 2. Go to your existing Split Test 3. Click Add Variant 4. Enter a name and select the Webflow page that will act as the variant 5. Click Create Your selected page will now be treated as a variant in the Split Test. *** ### Do I need to connect anything? No. Split Variants do not require you to connect elements or add attributes. As long as the Optibase custom script is installed on the site, the platform will: * Detect the page path * Apply test logic * Track views and conversions *** ### After setup After creating the Entry Variant, make sure to: * Add at least one more variant to compare * Set the test status to Active to begin running *** ### Variant actions For each Split Variant, you can: * Rename the variant * Change the associated Webflow page * Reset conversion and page view data * Delete the variant > Note: You cannot currently pause or disconnect a Split Variant without deleting it. This functionality is coming soon. # Create an A/B Variant *How to connect an A/B Variant:* [Connect an A/B Variant](/connect-an-a-b-variant) To create an A/B Variant, name it and click "Create":
You should now connect this Variant to an element on your page. Read about how to do that here: [Connect an A/B Variant](/connect-an-a-b-variant) You can also: * Change the name of the Variant. * Reset the Variant Conversion Events and Page Views. * Delete the Variant. * See variant results: * Page Views: How many times a variant was shown. * Conversions: How many conversion events were triggered while this variant was shown. * In the parenthesis, you will also see the conversion rate (conversion events / page views). * P2BB: [Probability to Be Best (P2BB)](/features/tests/probability-to-be-best-p2bb) * Click on the Variant to see a detailed breakdown of results for different Conversions. *Note: If want to stop showing an A/B Variant to the users because it is underperforming, but don't want to delete it because you want to keep the data, you can simply disconnect it.* ## Main Variant When you first create a Variant, it will be marked as "Main". 1. Select the Webflow Element you want to act as the Main Variant: 2. Click "Connect": ## Non-main Variant After the Main Variant, you should create at least one more Variant. To connect the Non-main Variant: 1. Duplicate the exact Webflow Element that you previously connected in the Main variant: 2. Select the duplicated Webflow element: 3. Click "Connect" below: The Variant you have selected in the Optibase App is the one currently visible in the Webflow Editor. You can edit it while it's visible. *Note: The Variant that is last selected and visible when you publish your site is the one that will be visible by default on your site. This means that if a test is restricted or in Draft, this is the Variant that will be shown.* *Note: If you want to stop showing an A/B Variant to the users because it is underperforming, but don't want to delete it because you want to keep the data, you can simply disconnect it.* # Types of Content You Can Connect Optibase makes it easy to connect and test virtually any type of content in your Webflow project. Here’s a detailed list of the elements you can connect: **Basic Elements** • **Text Fields** (e.g., headings, paragraphs, text links, text blocks) • **Images** (including image containers) • **Buttons** • **Rich Text Blocks** • **Block Quotes** **Media Elements** • **Video Embeds** (including YouTube and Vimeo) • **Lottie Animations** • **Spline Scenes** • **Rive Animations** **Layout and Structural Elements** • **Div Blocks** • **Grid Layouts** • **Columns** • **Lightboxes** • **Quick Stacks** **Components and Interactives** • **Forms** (including form blocks and labels) • **Dropdown Menus** • **Sliders** • **Tabs** It’s as straightforward as selecting the element in your Webflow Designer, clicking “Connect,” and letting Optibase handle the rest. You can easily A/B test content changes across these elements to see what resonates best with your audience. # Installing the WordPress Plugin The Optibase WordPress plugin is the fastest way to connect your site to your workspace. By using the plugin, you avoid manual code editing—simply upload the file, add your API key, and the Optibase script will handle the rest. ### 1. Download the Plugin First, you need to grab the latest version of the Optibase plugin: 1. Visit the [Optibase Download Page](https://www.optibase.io/optibase-webflow-app-wordpress-plugin-download). 2. Click Download for WordPress. 3. A `.zip` file will download to your computer. Keep this file zipped; do not extract it. ### 2. Upload to WordPress Once you have the file, head over to your WordPress Admin dashboard: 1. Navigate to the Plugins tab in the left-hand sidebar. 2. Click Add New Plugin at the top of the page. 3. Click the Upload Plugin button. 4. Drag your downloaded `.zip` file into the box or click Choose File to select it. 5. Click Install Now. 6. Once the installation is complete, click Activate Plugin. ### 3. Connect via API Key After activation, you will see a new Optibase item in your left-hand sidebar. To link it to your account, you need your Public API Key. 1. Open your [Optibase Dashboard](https://www.google.com/search?q=https://app.optibase.io) in a new tab. 2. Go to Settings in the bottom left corner. 3. Click on Public API Key and copy the key provided. 4. Return to your WordPress site and paste the key into the API Key box. 5. Hit Save Changes. ### What’s Next? Your WordPress site is now successfully connected to Optibase! The tracking script is loading automatically across your site, and you are ready to begin. * Go to your Dashboard: You can now start creating A/B tests and Personalizations. * Verify Connection: In your Optibase settings, you can verify that the script is being detected on your live WordPress URL. # Creating an A/B Test {% embed url="" %} If you are not using the Webflow App, you can create and manage A/B tests directly from the Optibase dashboard. This manual method gives you full control over how variants are triggered on any website. *** ### 1. Create the Test 1. Navigate to the Tests page in your Optibase dashboard. 2. Click Create Test. 3. Name your test: Use a descriptive name (e.g., `CTA Button Color`). 4. Select Type: Ensure A/B Test is selected by default and click Next. *** ### 2. Connect a Conversion To measure which version wins, you must link the test to a goal. 1. Search for your existing conversion (e.g., `Get Started Clicked`). 2. Select it and click Next. * *If you haven't created a conversion yet, you'll need to set one up first in the Conversions tab.* *** ### 3. Define Your Variants Now, create the different versions you want to compare. 1. Click Create Variant and give it a name (e.g., `Blue`). 2. Repeat for your other versions (e.g., `Red`). 3. Traffic Split: By default, traffic is split equally. You can adjust this—for example, sending 80% to `Blue` and 20% to `Red` if you want to test a new idea cautiously. *** ### 4. Add Custom Attributes to Your Site For Optibase to know which elements to swap, you must add two specific HTML attributes to your website's elements. #### The Required Attributes: | **Attribute** | **Value** | **Description** | | -------------------------- | ---------------- | -------------------------------------------------- | | `data-optibase-test-id` | `your-test-name` | Identifies which test the element belongs to. | | `data-optibase-variant-id` | `variant-name` | Identifies which specific variant this element is. | #### Implementation Example: If you are testing a button, your HTML should look like this: HTML ``` ``` > Pro Tip: Only the "Main" variant should be visible on your live site. All other variants should have `style="display:none"` added to them. The Optibase script will automatically reveal the correct one and remove the others when a user lands on the page. *** ### 5. Go Live 1. Go back to the test page in the dashboard. 2. Change the status from Draft to Active. 3. (Optional) Toggle Auto-stop to automatically end the test once a statistically significant winner is found. *** ### Summary of Settings * Restrictions: You can limit the test to specific locations, screen sizes, or browsers. * Results: Once the test is active, click the Results tab to see real-time data on which variant is driving more conversions. # URL Split Testing {% embed url="" %} A URL Split Test (also known as a Redirect Test) allows you to split traffic between two or more entirely different URLs. This is the ideal method for testing radical changes, such as a completely redesigned homepage or a new landing page structure, rather than just changing individual elements. *** ### 1. Create the Test 1. Navigate to the Tests page in your Optibase dashboard. 2. Click Create Test. 3. Name your test: Use a clear name that identifies the comparison (e.g., `Old vs New Homepage`). 4. Select Type: Choose URL Split and click Next. *** ### 2. Connect a Conversion Select the goal you want to use to determine the winner. 1. Search for your conversion event (e.g., `Get Started Clicked`). 2. Click Connect Conversion, then click Next. *** ### 3. Configure Your URL Variants Unlike A/B tests, URL split tests do not require you to add custom attributes to your elements. Instead, you simply provide the paths for the pages you want to compare. 1. Define the Control (Original): * Give it a name (e.g., `Old Home`). * Enter the Variant Path (e.g., `/` for the homepage). * Click Create Variant. 2. Define the Challenger (New): * Give it a name (e.g., `New Home`). * Enter the Variant Path for the new page (e.g., `/new-home`). * Click Create Variant. > Note: The Optibase script handles the redirection automatically. When a user lands on the original path, Optibase will instantly decide whether to keep them there or redirect them to the new path based on your traffic settings. *** ### 4. Set Your Traffic Split By default, traffic is split 50/50. However, if you want to be more cautious with a new design, you can adjust the weight. 1. Click on Traffic Split at the top. 2. Adjust the percentages (e.g., 80% to `Old Home` and 20% to `New Home`). 3. Click Save. *** ### 5. Activate the Test Your test is created as a Draft by default. To begin redirecting users and collecting data: 1. Open the test in your dashboard. 2. Change the status from Draft to Active. 3. (Optional) Enable Auto-stop to automatically end the test once a winner is found. *** ### Targeted Testing You can further refine your split test by using the Restrictions settings: * Location: Only test users in specific countries. * Device/Browser: Limit the redirect to desktop users or specific browsers to ensure your new design performs well on those platforms first. # Publishing & Monitoring Tests {% embed url="" %} Once your A/B test is designed and tagged, the final step is to launch it and monitor the data until you have a statistically significant winner. Optibase provides flexible scheduling and clear probability metrics to help you make confident decisions. *** ### 1. Publishing Your Test When you create a test, it begins in Draft mode. To start showing variations to your visitors, you have two options: * Active: Set the status to Active to start the test immediately. * Scheduled: Choose a specific date and time for the test to launch automatically. This is ideal for coordinating experiments with marketing campaigns or product launches. You can manage the lifecycle of your test at any time by switching the status to Paused, Archived, or Finished. *** ### 2. Setting Auto-Stop and Alerts To prevent manual monitoring, you can automate the conclusion of your experiment: * Auto-Stop: Set a specific threshold (e.g., 2,000 tested users) at which the test will automatically cease. * Alerts: If you prefer to review the data yourself before ending a test, set an alert to notify you when your traffic threshold is reached. *** ### 3. Monitoring Results The results tab provides a real-time breakdown of how each variant is performing. While you will see charts and analytics immediately, the most important metric to watch is the Probability to be Best. #### Understanding Statistical Significance It is tempting to end a test as soon as one variant looks like it’s winning, but early data can be misleading. To ensure your results are accurate, follow these guidelines: 1. Traffic Volume: Let the test run for at least a few hundred users. If your site has high traffic, aim for a few thousand users to smooth out statistical "noise." 2. The 95% Threshold: Do not declare a winner until the Probability to be Best reaches 95% or higher. 3. Timeframe: Ensure the test runs long enough to account for weekly cycles (e.g., weekend behavior vs. weekday behavior). *** ### 4. Ending the Test Once a variant has maintained a 95%+ probability over a sufficient sample size: 1. Set the test to Finished. 2. Make the change permanent: Update your website's actual code or design to reflect the winning variant. 3. Remove the Optibase attributes from your site once the winning version is hard-coded. # Bricks Builder {% embed url="" %} Running A/B tests in Bricks Builder is highly efficient thanks to its native support for custom HTML attributes. This allow you to test different layouts, sections, or components without writing any custom code. *** ### 1. Create Your Test in Optibase 1. Navigate to your Optibase Dashboard and click Create Test. 2. Name your test: Use a descriptive name (e.g., `Two Variant Test`). 3. Select Type: Choose A/B Test (best for testing different layouts or sections on the same page). 4. Click Next. *** ### 2. Define Your Conversion Goal A conversion is your "marker of success"—the specific action you want users to take. 1. Click Create Conversion. 2. Name it: e.g., `button` (or something more specific like `demo-button-clicked`). 3. Type: Select Click (the most common goal for button tests). 4. Count once per user: Check this if you want to ensure that one user clicking multiple times doesn't skew your data. Leave it unchecked for e-commerce sites. 5. Click Create Conversion. Copy the Goal Attribute: `data-optibase-click-conversion-id="button"` *** ### 3. Tag Your Elements in Bricks Builder Open your page in Bricks Builder. You can test entire sections by duplicating them and applying the Optibase attributes. #### Step 3a: Add the Test and Variant IDs For each section (Variant) you want to test, go to the Settings > Attributes panel in Bricks: | **Attribute Name** | **Value for Variant 1** | **Value for Variant 2** | | -------------------------- | ----------------------- | ----------------------- | | `data-optibase-test-id` | `two-variant-test` | `two-variant-test` | | `data-optibase-variant-id` | `variant-1` | `variant-2` | #### Step 3b: Add the Conversion Attribute Select the button or element inside your sections that should trigger the goal: 1. Go to Settings > Attributes. 2. Add Attribute Name: `data-optibase-click-conversion-id` 3. Value: `button` *** ### 4. Launch and Monitor Once your attributes are saved and your Bricks page is published: 1. Return to Optibase and set the test status to Active (to start immediately) or Scheduled. 2. Visual Verification: Open your live site. You should only see one of the two sections. 3. Results: Monitor the Results tab to see real-time data on conversion rates and the probability of each variant being the "best." *** ### Advanced Management Features * Targeting & Restrictions: Narrow your test audience by location, screen size (Mobile vs. Desktop), OS, or browser. * Site-Wide Analytics: Monitor your overall traffic trends to see which devices and locations are driving the most engagement across your entire project. * Agency Workspaces: If you manage multiple clients, create separate Workspaces for each. This keeps data, billing, and team members organized and isolated. * IP Management: Use the IP Blacklist in Workspace Settings to exclude your own office traffic from test data. * Events Feed: View a live feed of activity to ensure your data is accurate and identify any unusual patterns. # Elementor {% embed url="" %} Running A/B tests on an Elementor site is straightforward with Optibase. Note that this requires Elementor Pro, as you must be able to add custom HTML attributes to your widgets and sections. *** ### 1. Create Your Test in Optibase 1. Navigate to your Optibase Dashboard and click Create Test. 2. Name your test: For example, `CTA Test`. 3. Select Type: Choose A/B Test (used for testing variations on the same page). 4. Click Continue. *** ### 2. Define the Conversion Goal A conversion is the marker of success—the action you want your visitors to take. 1. Name the conversion: e.g., `CTA`. 2. Type: Select Click (most common for buttons). 3. Count once per user: Enable this for lead generation to prevent multiple clicks from a single user from skewing your data. 4. Click Create Conversion. The Conversion ID: `CTA` *** ### 3. Tag Elements in Elementor In Elementor, you will apply attributes using the Advanced > Attributes panel. > Important: Elementor uses a specific format for attributes. Instead of `key="value"`, you must use a pipe symbol: `key|value`. #### Step 3a: Add the Conversion Attribute Select the buttons or elements you want to track and add the following in the Attributes box: data-optibase-click-conversion-id|CTA #### Step 3b: Add Test and Variant IDs Create your variants in Optibase (e.g., `first` and `second`). Tag each version of your element in Elementor with its specific ID and the shared Test ID: | **Attribute Key** | **Value for Variant 1** | **Value for Variant 2** | | ----------------- | -------------------------- | ----------------------- | | Test ID | \`data-optibase-test-id | cta-test\` | | Variant ID | \`data-optibase-variant-id | first\` | Note on Structure: If you are testing a whole section rather than just a button, place the Test ID and Variant ID on the Section/Container and the Conversion ID on the button inside it. *** ### 4. Launch and Verify Once your attributes are saved and the Elementor page is published: 1. Return to the Optibase Dashboard. 2. Set the test status to Active to start immediately. 3. Verification: Open your site in an Incognito window. You should only see one of the variants. 4. Check Results: Perform a test click and check the Results tab in your dashboard to see the data track in real-time. *** ### Advanced Management Features * Targeting: Use Restrictions to limit your test to specific locations, devices, operating systems, or browsers. * Automation: Set your test to Auto-stop after a certain number of users (e.g., 500+) or set up Email Alerts for specific conversion rate milestones. * Agency Workspaces: Organize different clients into separate Workspaces to keep data, billing, and team permissions isolated. * Global Insights: Beyond specific tests, use the Analytics tab to monitor site-wide traffic and visitor behavior. # Divi {% embed url="" %} Setting up A/B tests in WordPress using the Divi Builder is a seamless process with Optibase. By using Divi’s built-in "Attributes" panel, you can easily define your variants and track performance without writing custom code. *** ### 1. Create Your Test in Optibase 1. Navigate to your Optibase Dashboard and click Create Test. 2. Name your test: For example, `Button Test`. 3. Select Type: Choose A/B Test (used for testing multiple versions of an element on the same page). 4. Click Next. *** ### 2. Define the Conversion Goal A conversion is your "marker of success"—the specific action you want users to take. 1. Click Create Conversion. 2. Name it: e.g., `btn`. 3. Type: Select Click (the most common goal for button tests). 4. Count once per user: Check this if you are an agency or lead-gen site where one conversion per person is standard. Leave it unchecked for e-commerce. 5. Click Create Conversion. Copy the Goal Attribute: `data-optibase-click-conversion-id="btn"` *** ### 3. Tag Your Elements in Divi Open your page in the Divi Builder. Ensure you have both variants of your element (e.g., a Green Button and a Pink Button) ready on the page. #### Step 3a: Add the Conversion Attribute For both buttons: 1. Open the Button Settings > Advanced > Attributes. 2. Click Add Custom Attribute. 3. Attribute Name: `data-optibase-click-conversion-id` 4. Value: `btn` #### Step 3b: Add Variant and Test IDs Create your variants in the Optibase Dashboard (e.g., `green` and `pink`) and add the following attributes to each specific button in Divi: | **Attribute** | **Value for Green Button** | **Value for Pink Button** | | ------------- | ------------------------------------- | ------------------------------------- | | Test ID | `data-optibase-test-id="button-test"` | `data-optibase-test-id="button-test"` | | Variant ID | `data-optibase-variant-id="green"` | `data-optibase-variant-id="pink"` | *** ### 4. Launch and Verify Once your attributes are saved and the Divi page is published: 1. Return to Optibase and set the test status to Active (or Scheduled for a future date). 2. The "Single Variant" Check: Visit your live page. If you only see one of the two buttons, the Optibase script is working correctly and hiding the other variant. 3. Live Verification: Perform a test click on the visible button. Check the Results tab in your dashboard; you should see the conversion tracked immediately. *** ### Advanced Dashboard Features * Targeting & Restrictions: Narrow your test audience by location, device type (Mobile vs. Desktop), OS, or browser. * Site-Wide Analytics: Monitor your overall traffic trends to see which devices and locations are driving the most engagement across your entire project. * Agency Workspaces: If you manage multiple clients, create separate Workspaces for each. This keeps data, billing, and team members organized and isolated. * Export Functionality: Need to present data to a client? You can export your raw test results directly from the settings tab. # Gutenberg {% embed url="" %} Using Optibase with the WordPress Block Editor (Gutenberg) is a simple way to optimize your pages. Because Gutenberg does not support custom HTML attributes by default, this guide includes the extra step needed to tag your blocks correctly. *** ### 1. Prerequisites Before you start, ensure you have the following installed: * Optibase WordPress Plugin: Connects your site to your workspace. * Attributes for Blocks Plugin: A free utility (linked in our dashboard) that allows you to add custom attributes to standard Gutenberg blocks like buttons and sections. *** ### 2. Create Your Test in Optibase 1. In your Optibase Dashboard, click Create Test. 2. Name your test: (e.g., `Button Test`). 3. Select Type: Choose A/B Test and click Next. *** ### 3. Set Up Your Conversion Goal 1. Name the conversion: (e.g., `btn`). 2. Type: Select Click. 3. Count once per user: Keep this checked for most leads/sign-up tests. 4. Click Create Conversion. Copy the Goal Attribute: `data-optibase-click-conversion-id="btn"` *** ### 4. Tag Your Gutenberg Blocks Open your WordPress page editor and create the two buttons (or sections) you want to test. 1. Select the first button: Go to the Advanced tab in the block settings sidebar. 2. Add Attributes: Under "Additional Attributes," add the following: * Goal: `data-optibase-click-conversion-id` with value `btn` * Test ID: `data-optibase-test-id` with value `btn-test` * Variant ID: `data-optibase-variant-id` with value `btn1` 3. Select the second button: Repeat the process, but change the Variant ID value to `btn2`. \[Image: Gutenberg sidebar showing the Advanced > Additional Attributes section with Optibase tags] *** ### 5. Launch and Verify Once your page is saved and published: 1. Return to Optibase and set the test status to Active. 2. The "Single Button" Check: Visit your live page. If only one button is visible, the script is working correctly and hiding the other variant. 3. Live Verification: Perform a test click on your button and check the Results tab in your dashboard. You should see the "Tested User" and "Conversion" counts update almost immediately. *** ### Pro Features * Auto-Stop: Configure your test to automatically end when a specific conversion rate (e.g., 9%) is achieved. * Targeting: Use Restrictions to only run the test for users on specific browsers or in certain geographic locations. * Data Accuracy: Use the IP Blacklist in Workspace Settings to exclude your own office traffic so your test results remain pure. * Domain Whitelist: Secure your account by ensuring your tracking script only runs on your authorized domains. # Oxygen {% embed url="" %} Running A/B tests in WordPress using the Oxygen Builder is highly efficient with Optibase. By utilizing Oxygen's "Attributes" panel, you can easily define which elements to test and track. *** ### 1. Create Your Test in Optibase 1. Open your Optibase Dashboard and click Create Test. 2. Name your test: For example, `Button Test`. 3. Select Type: Choose A/B Test (best for testing specific elements on the same page). 4. Click Next. *** ### 2. Define the Conversion Goal A conversion is your marker of success—the action you want the user to take. 1. Click Create Conversion. 2. Name it: e.g., `Button Click`. 3. Type: Select Click (most common for button tests). 4. Count once per user: Check this for lead generation or sign-ups to keep your data accurate. Leave it unchecked for e-commerce. 5. Click Create Conversion. Copy the Goal Attribute: `data-optibase-click-conversion-id="button-click"` *** ### 3. Tag Elements in Oxygen Builder In Oxygen, you will need two versions of your element (e.g., two different buttons). You must add three specific attributes to these elements via the Advanced > Attributes panel. #### Step 3a: Add the Conversion Attribute Select both elements in Oxygen and add the conversion attribute from Step 2. This tells Optibase to track clicks on both variants. #### Step 3b: Add Variant and Test IDs Create your variants in the Optibase Dashboard (e.g., `btn1` and `btn2`) and add the following attributes to your elements in Oxygen: | **Attribute** | **Value for Button 1** | **Value for Button 2** | | ------------- | ------------------------------------- | ------------------------------------- | | Test ID | `data-optibase-test-id="button-test"` | `data-optibase-test-id="button-test"` | | Variant ID | `data-optibase-variant-id="btn1"` | `data-optibase-variant-id="btn2"` | > Pro Tip: In Oxygen, make sure the variant you want to hide by default is set to `display: none`. Optibase will handle the logic of showing the correct variant to the correct user. *** ### 4. Go Live Once your attributes are saved and the Oxygen template is published: 1. Return to the Optibase Dashboard. 2. Set the test status to Active to start immediately, or Scheduled for a future launch. 3. Monitor Progress: Use the Results tab to track which variant is performing better. *** ### Advanced Workspace Features * Targeting & Restrictions: Narrow your test audience by location, screen size (mobile vs. desktop), OS, or browser. * Auto-Stop & Alerts: Configure your test to automatically end or send an email alert once a specific conversion rate (e.g., 8%) is achieved. * IP Management: Use the IP Blacklist in Workspace Settings to exclude your own office traffic from test data. * Workspaces: For agencies or freelancers, use separate Workspaces for each client to keep projects, billing, and team members organized. * Domain Whitelisting: Ensure only your authorized domains can trigger the Optibase script to protect your data integrity. # Breakdance {% embed url="" %} Running A/B tests in WordPress using the Breakdance page builder is straightforward with Optibase. By using custom attributes, you can test different elements, such as buttons or sections, to see which version drives the most conversions. *** ### 1. Create Your Test in Optibase 1. Open your Optibase Dashboard and click Create Test. 2. Name your test: For example, `Button Test`. 3. Select Type: Choose A/B Test (used for testing variations on the same page). 4. Click Next. *** ### 2. Connect Your Conversion Goal A conversion is your marker of success—the action you want the user to take. 1. Click Create Conversion. 2. Name it: e.g., `Button`. 3. Type: Select Click (the most popular for button testing). 4. Count once per user: Check this if you only want to count one conversion per person (standard for lead gen) or leave it unchecked for e-commerce where users might convert multiple times. 5. Click Create Conversion. Copy the Goal Attribute: `data-optibase-click-conversion-id="button"` *** ### 3. Configure Variants in Breakdance In the Breakdance editor, you will need two versions of your button (Button 1 and Button 2). You must add three specific attributes to these elements so Optibase knows how to handle them. #### Step 3a: Add the Conversion Attribute Select both button variants in Breakdance and add the conversion attribute you copied in Step 2. This tells Optibase to track clicks on these specific elements. #### Step 3b: Add Variant and Test IDs Back in the Optibase Dashboard, create your variants (e.g., `button-1` and `button-2`) and copy the following attributes to your buttons in Breakdance: | **Attribute** | **Value for Button 1** | **Value for Button 2** | | ------------- | ------------------------------------- | ------------------------------------- | | Test ID | `data-optibase-test-id="button-test"` | `data-optibase-test-id="button-test"` | | Variant ID | `data-optibase-variant-id="button-1"` | `data-optibase-variant-id="button-2"` | *** ### 4. Launch Your Test Once your attributes are saved in Breakdance and the page is published: 1. Return to the Optibase Dashboard. 2. Set the test status to Active (to run it immediately) or Scheduled (to start it at a specific time). 3. Monitor Results: Use the Results tab to see which button is winning. *** ### Pro Features & Tips * Auto-Stop & Alerts: Set up email alerts or trigger an automatic stop when your conversion rate reaches a specific milestone (e.g., 7%). * Targeting & Restrictions: Limit your test to specific locations, screen sizes, operating systems, or browsers to ensure your data is as clean as possible. * Workspace Organization: If you are an agency, create separate Workspaces for each client to keep their data, billing, and team members isolated. * Accuracy Tools: Use the IP Blacklist in settings to exclude your own IP address and your team's traffic from the test results. # Conversions # Can I connect multiple conversions to a single test? Yes, in the Optibase web app (app.optibase.io), go to the Results tab of your test and connect multiple conversions. This allows you to track different user actions such as clicks, form submissions, and page views in the same experiment, helping you understand performance across various goals. # How do I check which buttons are connected to a conversion event? Currently, Optibase doesn't display all connected elements in the UI. We recommend testing this on your staging environment by manually clicking the buttons to verify conversion triggers. # How do I view which conversion event was triggered? Navigate to the Results tab in the web app and select the conversion event dropdown. Each event shows the count of triggers per variant. # Do I need to re-add conversion tracking for each new test? No, once you've created a conversion event, you can reuse it across multiple tests by connecting it in the Results tab of any new test. You can also create new conversions as needed. # 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 Conversions May Not Be Recording in Optibase If your conversions aren’t being recorded in Optibase, the most common reason is an issue with the script installation. ## Steps to Fix Conversion Recording Issues: #### 1. Double-Check Script Placement: • Ensure the Optibase script is properly installed in the head code section of your project settings. This is critical for accurate tracking. • If the script is placed in the footer or added incorrectly, it may not function as expected. ### 2. Verify Conversion Setup: • Confirm that the conversion you’re trying to track is properly configured in the Optibase dashboard or Webflow app • Ensure the element you’re tracking has the correct data attributes linked to the conversion. ### 3. Test the Conversion: • Trigger the conversion action on your site and check the Optibase dashboard to see if it registers. • Use browser developer tools or inspect the console for any errors related to the Optibase script. If everything looks correct and conversions still aren’t recording, feel free to reach out to us with details or a Loom video of your setup. We’ll help you troubleshoot further! # Tests # 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. # Why Conversions or Results May Not Be Visible in the Results Tab If you’re unable to see any conversions or results in the Results tab, here are a few steps to troubleshoot the issue: ## 1. Ensure Conversions Are Connected: Navigate to your test, go to the Results tab, and confirm that a conversion is selected. Without a connected conversion, the results won’t show up. ## 2. Verify Conversion Tracking: • Check that the conversion event is properly set up on your site. • Ensure the Optibase script is installed in the head code section of your project settings. • Test the conversion action (e.g., button click or form submission) to confirm it’s being recorded. ## 3. Check Test Activity: Ensure the test is active and receiving traffic. If there’s no traffic, conversions won’t be recorded.
If you’ve reviewed these steps and the issue persists, record a Loom video of your setup and share it with us. This will help us understand the problem and provide a solution quickly. # Why are conversion events double counted in my test? This can happen if the 'Count only once per tested user' feature is not enabled. Without this setting, Optibase will log a conversion every time the action is performed, even by the same user. Enable this setting to prevent skewed data from repeated actions by the same individual. # Why do I see flickering between A/B variants? Flickering typically means the Optibase script is not installed correctly or not loading early enough. Make sure it is placed at the very top of the section in your Webflow or custom site settings. This ensures that the correct variant is shown before the original content loads. # Can I test elements across all pages on my website? Yes, the best way is to create a component that contains the test element and reuse that component across your pages. You can then apply your A/B test to this component and Optibase will handle consistency across all user sessions. # Can I redirect traffic between two different URLs using Optibase? Yes, you can use the URL Split Test feature in Optibase to split traffic between two URLs. This is useful when testing landing pages, product pages, or different content to determine which performs better. You just need to ensure the Optibase script is installed on both URLs and then set up the split test in the dashboard. # How do I set up a multivariate test in Optibase? To set up a multivariate test, go to your Webflow project, install the Optibase Webflow app, and define your variants by selecting multiple elements within a single component. Make sure to keep variants logically grouped for meaningful results. # Why is the wrong variant showing when I preview using the variant URL? If the wrong variant appears when using preview URLs, make sure you're using an incognito window and have cleared cookies and cache. The script may cache a previous session, affecting the view. # How can I force a specific variant to display for debugging? You can use the `?optibaseVariants=test_name:variant_name` query string in your URL to force a specific variant for testing purposes. # Can I run multiple tests on the same page? Yes, you can run multiple tests on a single page, but avoid overlapping elements between tests as this could produce unreliable results. # Is it possible to set traffic allocation dynamically during a test? At the moment, you must set your traffic split when creating the test. If you'd like to adjust it later, you’ll need to edit the test settings manually in the dashboard. # How can I test different CTAs that exist across 50+ pages? You can create a component with CTA variants and reuse it across your site. Apply the A/B test to that component to ensure a consistent test experience sitewide. # What happens when a test reaches statistical significance? If the feature "turn off when a winner is found" is checked, Optibase will automatically stop the test and show only the winning variant to future visitors once a variant exceeds 95% probability and 300 tested users. # Can I filter out specific IPs or users from test results? Currently, Optibase does not support IP-based filtering. We recommend testing in staging and excluding it from the production whitelist. # Do I need to connect a conversion event to a test for it to be tracked? No. Conversions are always tracked if the script is active, but only connected conversions to a test will appear in the results tab of a test and give conversion count for that specific test. # How do I test different product pages with different pricing? Use a URL Split Test. Set each product page as a variant and assign traffic percentage. Use geo-targeting if the pricing differs by region. # Can I test hero images with multiple slides in each variant? Yes, but load times may affect flicker. Optimize image sizes and ensure your script is installed correctly to reduce loading delays. # Why does a variant not show even with 100% traffic assigned? Clear your cache and test in an incognito window. Also ensure no other tests are running that might override the current variant. # Can I export test results? Yes. Use the Export button in the Results dashboard to download CSV files with your test performance data. # How do I test a new user journey that starts on different landing pages? Use a URL Split Test to distribute users between different landing pages. Then set up conversions to measure funnel progression. # How can I preview the test without affecting analytics? Use a staging domain or force preview with the query parameter method. Staging previews don’t count toward production analytics. --- [Next Page](/llms-full.txt/1)