> For the complete documentation index, see [llms.txt](https://docs.elevateab.com/elevate-helpcenter/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elevateab.com/elevate-helpcenter/faq/frequently-asked-questions.md). # Elevate A/B Testing FAQ Answers to common Elevate A/B Testing questions on Shopify: setup, store speed, SEO, order tracking, running experiments, and privacy. ## Getting Started ### What can I test with Elevate A/B Testing? You can test pricing, page layouts, product images, shipping rates, checkout elements, themes, and custom code changes. Elevate A/B Testing supports price testing, product testing, page testing, split URL testing, theme testing, shipping testing, product image testing, checkout testing, content testing, and custom code testing. See the [Introduction](/elevate-helpcenter/getting-started/introduction.md) for the getting started guide for each test type. ### Do I need to manually install any scripts on my theme? No. Elevate A/B Testing automatically installs its Liquid Snippet on your theme. There's no manual code editing required. If you switch themes, the snippet is reinstalled automatically when you open the app or launch an experiment. ### Can my developers test Elevate A/B Testing on a development store? Yes. After installing the app on a development store, reach out to us via email at or use the live chat, and we can grant access for testing purposes. This lets your team explore Elevate A/B Testing's capabilities before rolling out changes to your live store. ### What Shopify plans does Elevate A/B Testing work with? Most experiment types work on every Shopify plan, including price experiments. The exceptions are: * **Checkout experiments and Checkout Personalizations**: require Shopify Plus * **Shipping experiments**: require carrier-calculated rates, available on Shopify Advanced, Shopify Plus, or as a Shopify add-on Price experiments do need a **Standard** or **Premium** Elevate A/B Testing plan. The Elevate A/B Testing **Basic** plan includes Split URL, Page, Content, and Theme experiments only. *** ## Performance & SEO ### Does Elevate A/B Testing have any performance impact on my store? The impact is minimal. The Elevate A/B Testing script is lightweight and executes in milliseconds. Performance testing typically shows a 1–2 point impact on page speed scores, a marginal tradeoff for flicker-free experiment delivery. See [Anti-Flicker](/elevate-helpcenter/analyze/tracking/anti-flicker.md) for details on how the script is optimized. ### Will testing affect my search engine listings or SEO? No. Elevate A/B Testing's testing is invisible to search engines. The script doesn't run for known search engine bots, and the experiments don't create duplicate content issues or affect your page rankings. *** ## Tracking & Attribution ### Does Elevate A/B Testing track post-purchase upsells? Yes. Post-purchase upsell orders are tracked and attributed to the experiment variation the visitor was assigned to. ### Does Elevate A/B Testing track orders made with one-click checkout payment solutions? Yes. All orders are tracked regardless of the checkout method used: standard checkout, Shop Pay, Apple Pay, Google Pay, and other accelerated checkout options are all captured. ### Will Elevate A/B Testing remove UTM parameters when a visitor is redirected for a test? No. When a visitor is redirected as part of an experiment, for example to the product copy in a Product Experiment or to another page in a Split URL experiment, UTM parameters are preserved and passed through to the destination URL. Your marketing attribution and analytics tracking remain intact. ### How does Elevate A/B Testing handle customers who switch devices? Elevate A/B Testing assigns visitors to experiment variations using a browser cookie. If a visitor switches to a different device, they may be assigned to a different variation since the cookie doesn't transfer across devices. This is a standard limitation of all client-side A/B testing tools. In practice, most visitors complete their journey on a single device, so cross-device switching rarely affects results significantly. See [Visitor Attribution](/elevate-helpcenter/analyze/tracking/visitor-attribution.md) for how visitors and orders are matched to variations. ### Why don't my Elevate A/B Testing numbers match Shopify or Google Analytics exactly? Every analytics platform measures things slightly differently: how they define visitors vs. sessions, how they filter bots, and how they attribute orders. Small discrepancies are normal and expected. See [Analytics Discrepancies](/elevate-helpcenter/analyze/tracking/analytics-discrepancies.md) for a detailed breakdown of why numbers vary and what to do about it. *** ## Running Experiments ### How many variations can I test in one experiment? Up to five, including the control. That is your control plus up to four alternatives, and the limit is the same on every Elevate A/B Testing experiment type. Each extra variation splits your traffic further, so every variation takes longer to reach a reliable result. Start with the control and one alternative unless your store has the traffic for more. ### How do I edit something on a live test? Navigate to the experiment and select the **Overview** tab, where you can make adjustments. If the test has been running for a while and has significant data, consider starting a new experiment instead, because mid-test changes can affect the validity of your results. For minor changes early in a test (before much data has been collected), editing is generally fine. ### How long should I run my experiment? There's no fixed answer: it depends on your traffic volume and the size of the effect you're testing. Let the experiment run until it reaches a definitive statistical significance status. Ending early can lead to unreliable results. As a rough guide, most experiments need at least 3 days and a minimum number of conversions before any conclusions can be drawn. ### Can a visitor be in multiple experiments at the same time? Yes. Visitors can participate in multiple experiments simultaneously, as long as the experiments don't conflict. However, if you enable [Traffic Isolation](/elevate-helpcenter/experiment-setup/traffic-isolation.md) on an experiment, visitors in that experiment will be excluded from other isolated experiments. ### What happens when I pause an experiment? Traffic splitting stops immediately and all visitors see the original experience. Your existing data is preserved, and nothing is lost. You can resume the experiment at any time. See [Experiment Lifecycle](/elevate-helpcenter/experiment-setup/experiment-lifecycle.md) for details. ### Can I resume an experiment after marking it as complete? Yes. You can resume a completed experiment to collect more data. The experiment goes back to Running status and continues from where it left off, and existing variation assignments are preserved. *** ## Data & Privacy ### What data does Elevate A/B Testing collect about my visitors? Elevate A/B Testing collects anonymous behavioral data only: page views, cart interactions, checkout activity, and completed purchases. No personal information (emails, phone numbers, names, addresses) is collected or stored. See the [Web Pixel](/elevate-helpcenter/analyze/tracking/web-pixel.md) page for details. ### Is Elevate A/B Testing GDPR compliant? Elevate A/B Testing collects anonymous behavioral data only, and its web pixel runs in Shopify's strict sandbox mode. On experiments launched with Shopify server events, Shopify does not send events for shoppers who decline tracking consent, so those shoppers are not counted as visitors. Their orders can still be recorded. To hold Elevate A/B Testing's visitor and session IDs back until a visitor accepts analytics in your cookie consent banner, turn on **Require Consent Before Storing Visitor IDs**. ### Does Elevate A/B Testing store visitor IDs before a visitor gives cookie consent? By default, yes. Elevate A/B Testing stores an anonymous visitor ID so it can recognize the same visitor from page to page. To hold the visitor and session IDs back until a visitor accepts analytics in your cookie consent banner, go to **Settings**, then **Store Setup**, then **Tracking**, and turn on **Require Consent Before Storing Visitor IDs**. It works with Shopify's cookie banner and with banner apps that record consent through Shopify's Customer Privacy API. The setting does not stop experiments. Visitors are still assigned to a variation, and the cookies that remember the variation (`ABTL` and `ABAU`) are still set before consent. Turn the setting on only if your experiments were created after September 29, 2026, because older experiments cannot track visitors reliably with it on. See [Experiment and Store Settings](/elevate-helpcenter/advanced-settings/experiment-and-store-settings.md) for details, and [What Cookies Does Elevate A/B Testing Set?](/elevate-helpcenter/analyze/tracking/cookies-and-consent.md) for the list of cookies and storage keys.