FAQ
No questions match your search. Try using different keywords.
Insert the Convert Experiences snippet into the <head> of your site. For the best user experience and to completely prevent content flicker, the script should be loaded synchronously. While an asynchronous option is available to optimize for Core Web V-itals, synchronous loading is the recommended method for ensuring variations are applied instantly. Installation can be manual, via CMS (WordPress, Shopify, Magento), or through Google Tag Manager (GTM).
The entire process is documented here.
Yes, Convert Experiences 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 Experiences snippet directly in the <head> of your website.
The entire process is documented here.
Caveat: Deploying Convert Experiences 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 Experiences supports cross-domain testing and tracking, provided the subdomains or domains are added to the same Project under Active Websites, and the Convert Experiences tracking snippet is present on all properties.
Convert Experiences 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 Experiences supports SPAs by using a MutationObserver to automatically detect content changes. For modern frameworks, Convert Experiences offers dedicated packages, like for React, which integrate directly into the component lifecycle. Using these packages is the best practice, as it provides seamless, flicker-free experimentation with zero impact on Core Web Vitals.
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.
You can learn about this here.
Yes. Convert Experiences 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 Experiences 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 Experiences | 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 Experiences via Javascript API or webhooks and 3rd party integrations, enabling CRM events or call center conversions to be linked back to experiments.
You may learn more about it here.
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.
You can learn more about it here.
Yes. The Convert Experiences native Shopify app allows E-commerce stores to test pricing by product, collection, tag, or pattern, with adjusted prices carried through to checkout – not just on product and listing pages. The pricing displayed to purchasers for the variant SKUs is real. Not a workaround made possible with duplicated products.
You can stack discounts on a specific product, and they execute according to the priority set by you. This robust price testing is fully-facilitated on the front-end.
Yes. Feature flags are part of Convert’s Full Stack capabilities: all six SDKs support flags with typed defaults, so you can gate features server-side, roll them out to targeted audiences, and graduate a rollout into a measured experiment when you want statistical evidence.
Through the Request Approval System, available in beta on Pro and Enterprise plans. It’s an optional, per-account workflow: when a rule is on, activating, pausing, or modifying a live experience is held for review until a designated reviewer – an Owner, Account Manager, or Admin – approves the request. No one can approve their own change. Approval is tracked on the request, not the experience, so experience statuses stay exactly as they are. Especially designed to support agencies and multi-stakeholder cross-functional teams.
Six. As of 2026, Convert Experiences ships six production Full Stack SDKs: JavaScript (browser and Node.js), Android, iOS, PHP, Python, and Ruby. All six support A/B testing, feature flags, and experience bucketing, and they share bucketing parity – a visitor assigned to a variation in one runtime gets the same assignment in every other. And if you only test client-side, you don’t need an SDK at all: the tracking snippet covers the web.
Convert Experiences 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, natively – on both sides of the stack. For web experiences, add a “Bucketed in Experience” condition (under Visitor Data) to the audience of the experiment you want to gate: it only admits visitors who have not been bucketed into the test(s) you specify.
For Full Stack experiments, the SDKs evaluate a dedicated bucketed-into-experience audience rule. Reference the key of the experiment whose visitors you want to exclude, toggle negation on, and mutual exclusion is enforced during audience matching, with no code changes. The same rule without negation does the opposite: it deliberately layers a follow-up experiment onto the audience of an existing one.
Yes. Convert Experiences provides full-stack experimentation capabilities. While client-side testing is standard, our SDKs allow developers to run server-side tests, manage feature flags, and conduct hybrid experiments. Server-side and client-side tests can run in parallel, giving you complete flexibility to test across your entire technology stack.
Mobile app testing is possible using Convert Experiences’ Full Stack SDKs (JavaScript, PHP, Android, iOS, Python & Ruby) to implement server-side or hybrid experiments inside apps.
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 Experiences eliminates flicker by loading its tracking script synchronously within your site’s <head> tag. This method ensures that any experiment changes are applied before the page content is visible to the user. While an asynchronous script is also available for performance-focused setups, it uses a temporary body-hiding technique to reduce, rather than eliminate, potential 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 Experiences’ data will differ from platforms like GA4 because it focuses on unique visitors per experiment, whereas analytics platforms often focus on sessions. A variance of 5-10% is normal. Importantly, Convert Experiences enriches your analytics data by sending events that contain the experiment and variation a user has seen. This allows you to segment reports directly within GA4 or Adobe Analytics to analyze behavior based on your experiments.
Convert Experiences is designed for privacy compliance and operates without collecting personally identifiable information (PII). It supports consent-first workflows by allowing tracking to be blocked or delayed until a user gives permission. For advanced privacy needs, Convert Experiences also supports cookie-less tracking through a “Bring Your Own ID” (BYOID) feature, allowing you to maintain experiment consistency without relying on browser cookies.
Yes. Convert Experiences 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 Experiences 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 Experiences 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 Experiences fits your privacy framework.
Convert Experiences’ 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 Experiences also provides methods to minimize flicker and keep script size small through careful experiment and goal setup.
Convert Experiences 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 Experiences 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 Experiences 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 Experiences integrates indirectly through Segment, Stitch, or custom ETL. You can also use Convert Experiences’ API and webhooks to build custom data pipelines tailored to your BI or CDP setup.
Convert Experiences 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 Experiences tracking code in Script Manager, then configure revenue goals using BigCommerce e-commerce events.
Magento: Insert the Convert Experiences snippet into the theme header template and set up revenue goals based on order confirmation pages or purchase events.
Yes. Convert Experiences 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 Experiences by adding the snippet to the site header or through a tag manager.
Convert Experiences’ 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 Experiences with virtually any platform.
Learn more about Convert Experiences’ API here.
Convert Experiences’ 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 Experiences 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 Experiences 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 Experiences 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 Experiences 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 Experiences 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 Experiences 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 Experiences engineers reliability across four layers: exclusion of bot and internal traffic from experiment reporting, deterministic visitor bucketing, highly-available infrastructure with regularly tested disaster recovery, and privacy enforced by architecture. As of 2026, Convert Experiences has optimized 40,000+ websites over 15 years with zero security breaches.
Convert Experiences filters bots at ingest. A bot check runs on every request before any database write, so known bots such as search crawlers, AI crawlers, HTTP libraries, and monitoring tools are discarded before they are ever counted or bucketed. Convert Experiences also runs a Sample Ratio Mismatch check that flags when the observed traffic split diverges from your configured allocation.
Convert Experiences compares observed visitors per variation against your configured allocation using a Chi-square goodness-of-fit test that accounts for unequal splits. When the mismatch is large enough, the check triggers at 99% confidence, and Convert Experiences displays an SRM tag on the experiment report. SRM checking is enabled per project under Project Configuration > More Settings.
The Convert Experiences snippet is 93 KB gzipped at baseline, rising to roughly 95-110 KB with three to five experiments, delivered as a single upfront bundle with no hidden runtime fetches. Convert Experiences offers synchronous, asynchronous, and single-page-application loading options, so teams choose their own trade-off between flicker prevention and Core Web Vitals impact.
In July 2026, Convert Experiences ships six production SDKs. That includes JavaScript (client-side and Node), Android, iOS, PHP, Python, and Ruby. All six support A/B testing, feature flags, and experience bucketing. The mobile and server SDKs share bucketing parity with the JavaScript SDK, so a visitor is assigned consistently across runtimes.
Convert Experiences has been GDPR-compliant since May 2018 and is also CCPA- and LGPD-compliant. Convert Experiences uses first-party cookies, does not require personally identifiable information to operate, honors the Do Not Track header, and can withhold both cookie writing and experiment execution until a visitor consents.
Convert is ISO 27001 certified by InterCert and SOC 2 Type 2 attested. Convert Experiences is designed to support HIPAA compliance for covered entities and business associates, and follows PCI-DSS principles. Convert Experiences maintains a legacy of zero security breaches.
Convert Experiences hosts production servers and databases on Amazon Web Services, with the login site hosted separately on Hetzner for GDPR compliance, and runs on carbon-neutral servers. Production infrastructure is spread across two availability zones with regularly tested disaster recovery.
No. Every AI capability in Convert Experiences is opt-in and user-directed. The AI Wizard generates copy only when you select text and request it. Smart Recommendations and Convert Signals surface observations without changing anything. The Convert Experiences MCP server is reporting-oriented by default, with write access requiring deliberate configuration.
Convert delivers a median first-response time of under 2 minutes 44 seconds, against a SaaS industry average of 2.6 hours on Zendesk benchmarks. Support is in-house and staffed by experimentation specialists, and every Convert Experiences plan includes free onboarding.
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 Experiences 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 Experiences 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 Experiences, 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 Experiences 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 Experiences’ duration calculator to ensure you have adequate sample size and test length. QA thoroughly before launch using Convert Experiences’ 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 Experiences 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 Experiences 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.
Conservatively and transparently. Convert Intelligence® reads only the account data it needs to answer you, scoped to your account and your permissions; conversations are never visible to another account, and chat history is yours to clear at any time. Read more about the privacy aspects of Convert Intelligence here.
No. Convert Intelligence® proposes every change in the UI and executes nothing until you explicitly accept it. It is hard-blocked at the backend from modifying live experiences: it works on drafts and paused experiences only. The MCP Server defaults to read-only reporting mode, requires you to escalate access yourself, and validates every write before it reaches your account. AI-initiated changes are logged in change history, so there is always a trail.
Yes – and it has since 2025. The Convert Experiences MCP Server connects your experimentation data to Claude, Cursor, or any MCP-compatible client.: It’s available in two flavors – the hosted variant that works like any standard connector. And the local server variant that gives greater control to those who are technically inclined. The MCP server has 45 tools (for both retrieval of information and hands-on building work) in the hosted variant. The local version is a secure, 16-tool server. It starts in read-only reporting mode by default, validates every write against guardrails before it reaches your account, and carries Convert’s documentation inside it.
Convert Intelligence® is an AI assistant built into the Convert app. It explains and debugs experiment reports in plain language, creates and edits experiences, goals, audiences, and locations through conversation, answers platform questions from Convert’s own documentation, guides new users to a first launched experiment, edits draft variations in the visual editor by prompt, and suggests what to test next, grounded in CRO practice.
It is built to keep you in charge: every change it proposes requires your explicit acceptance before anything is saved, it is blocked at the backend – not just in the prompt – from ever touching a live experience, and everything is scoped to your account and your existing permissions.
Yes. If by prompt-driven experimentation you mean keeping the human in the loop and taking over tedious coding tasks that add 60% of overhead to the work of developers.
Our powerful MCP server is used by the most experienced experimentation agencies on the planet to set up granular, impactful reporting and to build experiment variations, with tools you already trust — like Claude Code and Cursor.
If you want AI to do it all – from start to finish, and use the output as production-ready variants, instead of prototypes – no. We do not encourage vibe experimentation.
Yes. Convert offers special discounts to NGOs working for the greater good. Get in touch to talk through your optimization requirements and join our ecosystem of Conscious Businesses.
Every script has a cost; ours is engineered to stay small and to run on clean infrastructure. The Convert snippet ships as a single upfront bundle (~93 KB gzipped at baseline) with no hidden runtime fetches, and all production infrastructure runs on carbon-neutral servers – operated by a company working toward 10x carbon negativity by 2028.
Convert commits 10% of top-line revenue – revenue, not profit – to conservation: 8% funds farmer-led afforestation with TIST, more than 94,000 trees planted so far, and 2% goes to climate action through Stripe Climate and our 1% for the Planet memberships. Convert is Climate Label Certified, runs its production infrastructure on carbon-neutral servers, operates fully remote with an active program to reduce travel emissions, and incentivizes the team to buy refurbished equipment over new.
The destination: 10x carbon negative by 2028, and 1,178,600 trees planted – enough shade to walk between Montreal and Cancun.