FAQ
Insert the Convert snippet into the <head> of your site. The script is asynchronous to minimize flicker and page load impact. Installation can be manual, via CMS (WordPress, Shopify, Magento), or through Google Tag Manager (GTM).
The entire process is documented here.
Yes, Convert supports GTM deployment, though it is not the preferred method. Customers can grab the tracking snippet from Project → Configuration, create a new Custom HTML Tag in GTM, add var _conv_prevent_bodyhide = true; before the snippet, and then publish their GTM workspace. For optimal performance, we recommend placing the Convert snippet directly in the <head> of your website.
The entire process is documented here.
Caveat: Deploying Convert through Google Tag Manager may result in flicker of original content.
In the dashboard, create a Project → create a new Experience and select A/B Test → enter the target/original URL → build variations with the Visual or Code Editor → set goals and configure Audience & Site Area targeting → QA test using Preview or QA mode → switch status from Draft to Active to launch.
The entire process is documented here.
Yes. The Visual Editor supports point-and-click text, image, style, and layout changes. Code Editor is optional for advanced edits.
Yes. Convert supports cross-domain testing and tracking, provided the subdomains or domains are added to the same Project under Active Websites, and the Convert tracking snippet is present on all properties.
Convert primarily uses 1st-party cookies, and for cross-domain flows it forwards cookie values (_conv_v, _conv_s) between domains to maintain visitor consistency. This forwarding can be disabled in project settings if not required.
The entire process is documented here.
Yes. Convert supports SPAs. Its new tracking script uses MutationObserver to detect content changes automatically. You can also trigger experiments with JavaScript conditions, manual activation (executeExperience), or the Convert React package for React apps.
More info on the matter can be found here.
Exclusion can be done by IP filtering, custom query parameters, cookies, or user agent targeting rules.
Know how this is done here.
Goals are defined in the “Goals” section. Options include: URL visits, clicks on elements, custom JS triggers, revenue-based e-commerce metrics, and advanced goals using 40+ filters.
Yes. Convert tracks revenue and transactions through manual revenue goals, e-commerce data layers, or integrations with Shopify/Magento. Cart abandonment is tracked using funnel-drop goals, comparing visitors who start checkout but do not complete a purchase.
Learn how to use Advanced Goals here.
Convert Experiences is dedicated to A/B testing & personalizations. While GA4 and Adobe Analytics are recognized analytics platforms that measure user activity across all the touchpoints of a website (or online property).
Think of Convert as task-specific analytics (meant for test reporting), and GA4 and Adobe Analytics as the source of quantitative data experimenters rely on to hypothesize.
| Feature | Convert | GA4 | Adobe Analytics |
|---|---|---|---|
| Tracking Model | Uses a client-side JavaScript snippet to track unique visitors and goals related to active experiments. | Uses a privacy-centric, event-based model where every user interaction is an event. | Uses a highly customizable, event-based model, with manual configuration of custom variables. |
| User Tracking | Identifies a unique visitor to a specific experiment, tracking them with a cookie that lasts up to six months by default. It counts each user only once per experiment. | Measures users and sessions. A session expires after 30 minutes of inactivity, meaning a user can generate multiple sessions in a short time. | Tracks visitors across devices using visitor IDs and provides flexible segmentation. |
Yes. Offline events (stored in an online database) can be sent to Convert via Javascript API or webhooks and 3rd party integrations, enabling CRM events or call center conversions to be linked back to experiments.
Convert Experiences sends variation data into GA4 using events and custom dimensions, allowing direct correlation with GA’s e-commerce reports. You can further visualize this data using Looker Studio.
Convert supports A/B tests, Split URL (redirect tests), Multivariate tests (MVT), Multi-Page tests, full-stack experiments, and personalization campaigns (Deploys).
Multi-arm bandits and sequential testing are also available.
Experiments can run in parallel. Conflicts are managed by experiment priority, audience targeting, and site area rules. To avoid cross-experiment contamination, you can configure mutual exclusivity so that visitors in one experiment are excluded from others.
The entire process is documented here.
Yes. You can run experiments that don’t target the visitors (traffic) of other tests conducted across your website by creating a new Audience → using the ‘Visitor Cookie’ option from the filters list → entering the variation ID of the test(s) that should be excluded.
The entire process is documented here.
Yes. Convert offers client-side testing by default, with APIs and SDKs for server-side or hybrid setups. Both can run in parallel.
Convert is designed primarily for websites and web apps. Mobile app testing is possible using Convert’s Full Stack SDKs (e.g., JavaScript, Node.js, React Native) to implement server-side or hybrid experiments inside apps, but native in-app A/B testing is not a core feature yet.
An experiment tests multiple variations against a control to determine a statistically significant winner. A personalization campaign (Deploy) applies predefined changes to a specific audience segment, usually informed by test results or marketing strategy, without statistical testing.
Convert uses SmartInsert™ asynchronous script loading, which applies variations before content paint to reduce flicker.
Users can manage experiment priorities and avoid overlap by defining mutually exclusive conditions. This can be done in the UI using audience and location targeting so that a visitor only qualifies for one experiment. Additionally, custom JavaScript conditions can be applied to enforce priority rules and ensure one experiment runs before another when needed.
Convert and GA4/Adobe Analytics use different tracking methodologies, so their numbers will not match exactly.
By default, Convert counts unique visitors to experiments and only the first conversion per visitor for a goal (if needed, counting multiple conversions per unique visitor is possible), while GA often counts sessions and multiple conversions. Discrepancies also arise from cookie handling, consent management, bot filtering, reporting latency, and time zone differences. A 5–10% variance is common and expected when implementations are correct.
Convert is designed to be GDPR and CCPA compliant. It uses first-party cookies for tracking, does not collect personally identifiable information (PII), and anonymizes visitor data.
All servers are hosted in the EU (Frankfurt, Germany) to ensure data residency. Convert also respects browser privacy settings such as Do Not Track (DNT) and Global Privacy Control (GPC). These measures, combined with project-level privacy configurations, help customers maintain compliance with global privacy laws.
Yes. Convert supports cookieless testing through its BYOID (Bring Your Own ID) API, which lets you use your own identifiers (such as login IDs, device fingerprints, or first-party session data) to keep visitors in the same variation, even without cookies.
If no identifier is provided and cookies are blocked, each visit is treated as a new visitor. Convert also supports consent-mode testing, where you can choose between immediate experience delivery (variations show instantly but tracking is delayed until consent) or full-privacy protection (experiments only run after explicit consent)
Convert adapts to your consent strategy. In immediate delivery mode, experiments display without delay but data collection waits for consent. In full privacy protection mode, experiments and tracking are blocked until explicit consent is given. This flexibility allows you to balance compliance requirements with user experience, ensuring that Convert fits your privacy framework.
Convert’s tracking snippet is small (~50kB) and optimized for performance. On average, it adds about 100ms to load and 200ms for experience processing. You can choose synchronous loading, which ensures perfect user experience with no flicker but has moderate impact on Core Web Vitals, or asynchronous loading, which reduces impact on SEO and performance metrics but may introduce flicker.
Convert also provides methods to minimize flicker and keep script size small through careful experiment and goal setup.
Convert offers a wide range of integrations. Native integrations include Google Analytics (Universal and GA4 via gtag.js or GTM), Adobe Analytics, Mixpanel, Amplitude, Heap, Segment, Hotjar, Crazy Egg, Clicky, FullStory, and Kissmetrics. For advanced workflows, Convert supports data export via APIs, webhooks, and GTM Data Layer, making it possible to connect with BI platforms such as Looker Studio, Power BI, and BigQuery.
Review the 90+ integrations here.
Yes. Convert supports data export to BI dashboards and CDPs. You can send experiment and variation data to BigQuery through GA4/GTM or via Segment pipelines, and then visualize it in tools like Looker Studio, Power BI, or Tableau. For Snowflake and other warehouses, Convert integrates indirectly through Segment, Stitch, or custom ETL. You can also use Convert’s API and webhooks to build custom data pipelines tailored to your BI or CDP setup.
Convert can be added to these e-commerce platforms by installing the tracking snippet and setting up revenue goals: Shopify: Install the Convert Experiences Shopify app to automatically place the snippet and connect purchase events for revenue tracking.
BigCommerce: Add the Convert tracking code in Script Manager, then configure revenue goals using BigCommerce e-commerce events.
Magento: Insert the Convert snippet into the theme header template and set up revenue goals based on order confirmation pages or purchase events.
Yes. Convert provides a WordPress plugin for quick installation, or you can paste the tracking snippet directly into the header.
Other CMS platforms such as Drupal, Joomla, and HubSpot CMS also support Convert by adding the snippet to the site header or through a tag manager.
Convert’s secure REST API allows full programmatic control, including creating and managing projects, experiments, variations, and goals, as well as exporting reports and updating traffic allocation. Webhooks let you stream triggered experiment and variation data, in real time, to external systems such as analytics tools, CRMs, or BI dashboards.
Together, these features make it possible to build custom data pipelines, automate experiment management, and integrate Convert with virtually any platform.
Learn more about Convert’s API here.
Convert pricing is based on Monthly Tested Users (MTUs), which are the number of unique visitors exposed to experiments in a month. A visitor is only counted once, even if they enter multiple experiments during the same month. Plans are structured around MTU tiers, and higher tiers unlock greater capacity for projects, experiences, and goals.
Review our no-surprises pricing here.
A tested user is a unique visitor who is exposed to at least one experiment or personalization in a monthly billing cycle. If a visitor enters multiple experiments or personalizations in the same month, they are still counted only once toward your Monthly Tested Users (MTU) quota.
They are counted once per month, regardless of how many experiments they enter.
Pricing tiers are based mainly on Monthly Tested Users (MTUs). All plans include the core experimentation features—such as advanced targeting, triggers, customizable goals, reporting, and SRM checks. The main differences between plans are in capacity and support: higher tiers allow more projects, more active experiences per project, additional team seats, and enhanced support options.
Convert offers predictable pricing under $500/month based on Monthly Tested Users (MTUs), with access to all core experimentation features and strong privacy compliance.
VWO and Optimizely often restrict features, split them into costly modules, or charge significantly higher prices, making Convert a more affordable and transparent option for CRO teams.
Yes. Convert Experiences provides a 15-day free trial with full access to all features for a limited MTU quota.
Yes. Enterprise plans are available with custom MTU volumes, contract redlining, data segregation, BYOID (Bring Your Own ID) capabilities, dedicated support, and SLAs.
Yes. Convert is designed to support CRO agencies by allowing multiple client accounts to be managed as separate Projects under one main account. The number of active projects and domains depends on the pricing plan, but all plans include unlimited collaborators with role-based permissions to control access. This structure makes it easy for agencies to organize experiments and reporting across multiple clients in a single platform.
Convert offers a Visual Editor for quick experiment setup without heavy developer involvement, advanced goal tracking, and seamless integrations with analytics tools like GA4, Adobe Analytics, Mixpanel, and Segment.
All plans include the full experimentation feature set, built-in SRM checks for data accuracy, GDPR/CCPA compliance options, and unlimited team collaborators with role-based permissions — making it easy for small teams to run reliable, privacy-compliant experiments at scale.
Convert supports agencies with features like flexible traffic allocation, 90+ integrations with analytics and marketing tools, unlimited collaborators and import/export templates (to standardize how tests & goals are set up). Agencies can manage multiple client projects within one account, organizing them separately while maintaining centralized billing and oversight.
This structure helps CRO agencies and consultants simplify reporting and scale experimentation programs across clients.
Convert includes a built-in code editor for custom JavaScript, HTML, and CSS, along with a secure REST API and SDKs for server-side and hybrid testing. Developers can use QA mode, preview links, and debugging consoles to validate experiments before launch. Custom goal tracking can also be implemented via JavaScript, giving developers full flexibility to design, test, and measure complex experiences.
Live chat typically responds within minutes. For enterprise customers, Convert offers personal account managers, enhanced support services, and custom SLA commitments.
Convert includes free expert-guided onboarding (for Pro & Enterprise plans), self-service onboarding (for Growth customers), QA checklists, and experiment validation.
Convert is consistently rated higher on G2 for support responsiveness and technical depth. Optimizely and VWO rely more on slower ticket systems.
Convert holds GDPR/CCPA compliance and high reviews on G2 (4.7/5) and TrustRadius (9.9/10).
Founded in 2009, Convert serves SMEs & CRO agencies across e-commerce, SaaS, and publishing.
Independent CRO consultants, marketing & growth leaders of lean teams, and developers who code A/B tests benefit from using the platform.
Convert publishes clear pricing based on Monthly Tested Users (MTUs) rather than feature gating or hidden fees, and plans scale predictably without forced upgrades. On the data side, Convert documents its privacy practices in detail: it uses EU-based servers, relies on first-party cookies, anonymizes visitor data, and respects browser privacy settings such as Do Not Track (DNT) and Global Privacy Control (GPC). This transparency helps customers understand both costs and compliance from the start.
Convert supports flexible statistics with both Frequentist and Bayesian approaches, plus a Sequential Frequentist option with always-valid confidence. In the Frequentist model, results are expressed with confidence levels, showing the likelihood that observed differences reflect a real effect rather than chance. In the Bayesian model, results include Chance to Win (the probability a variation outperforms control), Risk (the probability it underperforms), and Expected Uplift (the sustainable improvement if selected). Frequentist reporting appeals to teams familiar with traditional A/B testing, while Bayesian reporting offers more intuitive, decision-focused probabilities.
Learn more here.
Yes. Convert supports segmentation of results by device type, browser, operating system, geography, traffic source, and custom attributes defined in your project. You can also enrich reporting with CRM or first-party data by passing identifiers through custom attributes or integrations.
In Convert, interpretation depends on the statistical model you choose.
With the Bayesian model, focus on Chance to Win (probability a variation outperforms control), Risk (probability it underperforms), and Expected Uplift (sustainable improvement if implemented). With the Frequentist model, use confidence levels to assess whether observed differences are reliable.
Sequential Frequentist reporting provides always-valid confidence for continuous monitoring. Across all models, Convert also provides SRM checks to ensure test data integrity before making decisions.
Start by defining one primary goal to avoid cherry-picking results. If you are running a standard Frequentist test, use Convert’s duration calculator to ensure you have adequate sample size and test length. QA thoroughly before launch using Convert’s preview and QA tools. For reliable insights, let tests run through full business cycles, monitor SRM checks, and keep designs simple to reduce noise.
Common pitfalls include: stopping Frequentist tests early and calling underpowered results, running too many goals per experiment instead of focusing on one primary goal, forgetting to exclude internal traffic, and not enabling SRM detection. Other mistakes to avoid are ending tests before they capture full business cycles, and overcomplicating experiment designs.
Start by building a structured experimentation program: prioritize hypotheses based on impact and effort, then validate them in Convert using either Bayesian or Sequential Frequentist statistics for reliable results. Use audience targeting and personalization to apply learnings across segments. Leverage SRM checks and QA tools to ensure test quality, and integrate Convert data with analytics or BI platforms to feed insights into long-term strategy. This continuous cycle of testing, learning, and applying results is the key to sustained conversion rate growth.