# Launching A Price Test {% hint style="info" %} All documentation on price testing can be found on [this page](/test/price-testing.md). To give us feedback on our documentation, please use [this form](https://form.typeform.com/to/M8H02KI2). {% endhint %} The launch process is straightforward but requires careful attention. Once launched, tests cannot be edited, making this final review critical. #### 1. Final review * Review all settings match your test plan * Check the product list and prices for accuracy * Verify traffic allocation aligns with your risk tolerance #### 2. Click launch 1. Click the **Launch test** button 2. Review the confirmation dialog carefully 3. Confirm the launch to activate your test 4. Your test status immediately changes to "Active" #### 3. What happens immediately * Shopify catalog updates: Product prices update to the highest test price for consistency * Visitor assignment begins: New visitors start being randomly assigned to test groups * Price adjustments activate: Your configured prices appear through data attributes * Data collection starts: Test reporting begins tracking visitor behavior ### Post-launch validation The period immediately after launch is crucial for catching any issues before they affect many customers. This real-world validation ensures everything works correctly for actual visitors, not just in preview mode. ### Step 1: Incognito browser testing Testing as a real visitor provides the most accurate validation of your live test. Incognito mode ensures you experience exactly what new customers will see. #### Open an incognito/private window Start fresh with private browsing to: * Ensure no cached preview sessions interfere * Simulate a first-time visitor experience * Get assigned to both sides of a test #### Visit your homepage Resist navigating directly to test products. Instead: * Start from your homepage like a real customer * Browse naturally through your site * Verify assignment happens correctly from any entry point #### Check your assignment As you navigate: 1. Visit a test product page 2. Note the price displayed (reveals your variant) 3. Close the current window and open another incognito window 4. Repeat until you've seen both variants 5. Confirm random assignment is working ### Step 2: Validate both experiences Once you've accessed both variants, systematically verify each performs correctly throughout the customer journey. #### Product browsing Navigate as a customer would and verify: * [ ] Product pages display correct variant prices * [ ] Collection pages show consistent pricing * [ ] Search results reflect assigned prices * [ ] Quick view modals maintain price consistency #### Add to cart flow Test the critical conversion path: * [ ] Add test products to cart * [ ] Cart shows correct test prices immediately * [ ] Mini cart/drawer displays accurate prices * [ ] Quantity changes calculate properly #### Checkout process Complete the checkout journey: * [ ] Proceed through checkout steps * [ ] Prices remain consistent throughout * [ ] Tax calculations use test prices * [ ] Stop before payment completion ### Step 3: Cross-device validation Real device testing reveals issues that browser emulation might miss. Different devices can render prices differently or have unique interaction patterns. #### Mobile testing Using your actual phone: 1. Clear browser data completely 2. Visit site in regular browser (not apps) 3. Navigate naturally to test products 4. Add items to cart 5. Verify responsive design maintains accuracy #### Tablet testing Tablets often have unique considerations: * Test both landscape and portrait orientations * Verify touch interactions work smoothly * Check cart functionality with gestures * Ensure price display adapts to screen size ### Step 4: Team validation Multiple perspectives catch issues you might miss alone. Coordinate with team members for independent verification. Team members should confirm: * Different people see different variants (random distribution) * Prices display correctly for their assignment * No error messages or warnings appear * Site performance remains normal * User experience feels seamless ### First hour monitoring The first hour after launch is critical for catching immediate issues. Stay vigilant across multiple checkpoints. #### Technical health checks Monitor these indicators: * Browser console for JavaScript errors * Page load times remain normal * Cart abandonment rates stay stable * Checkout completion rates unchanged #### Test distribution verification Confirm proper traffic splitting: * Both variants receive visitors * Distribution matches configuration (e.g. 50/50) * Geographic distribution remains normal * Device types follow typical patterns #### Customer feedback monitoring Keep communication channels open: * Monitor customer service for pricing questions * Check social media for confusion mentions * Review live chat transcripts * Watch for support ticket increases ### Success indicators Your test is running successfully when: ✅ Visitors consistently see assigned prices throughout their journey\ ✅ Cart and checkout calculate correctly with no errors\ ✅ No technical warnings in monitoring tools\ ✅ Traffic splits match configured percentages\ ✅ Data flows properly into reporting dashboard ### Next steps With your test successfully launched and validated, establish a monitoring routine to ensure continued success. #### Immediate actions * Set daily check-in reminders for the first week * Brief your team on expected timelines * Prepare for the patience required #### Looking ahead Remember that valid insights require time: * Most tests need 1-2 weeks minimum * High-consideration products may need longer * Resist making decisions on early data * Plan your first analysis checkpoint *** > Remember: The first 48 hours are critical for ensuring test stability. Stay vigilant for issues that could invalidate your results, but resist making any interpretation decisions based on early data. Statistical significance takes time, and premature conclusions often lead to poor decisions. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.shoplift.ai/test/price-testing/launching-a-price-test.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.