- Help Center
- Configuration
- Preview Issues
-
Getting Started
-
Configuration
- Targeting
- Split URL
- Product Testing
- Full Stack
- Experiment Management
- CSP Configuration
- Experiment Execution
- Reports
- Exit Popups
- GTM Integration
- Troubleshooting
- Performance Optimization
- Event-Triggered Changes
- Holdout Groups
- Split URL Pages
- URL Parameters
- DataLayer
- Menu Configurations
- Traffic Exclusion
- Experiment Scheduling
- Dynamic Element Changes
- Price Targeting
- Experience Scheduling
- Privacy
- Hash Changes
- Async Tracking
- Selective Installation
- CSS Selectors
- Vue.js Integration
- Page Content
- Multipage Split URL
- Organic Traffic
- Visual Editor
- Server-Side Testing
- Traffic Bucketing
- GDPR Warnings
- Statistical Confidence
- Browser Privacy
- Query Parameters
- Embedded Videos
- Tracking Code Execution
- Simultaneous Experiments
- Tags
- Deployments
- Disable Testing
- Locations
- Programmatic Bucketting
- Query Parameter Handling
- Convert Library
- Variation Previews
- Experiment Editing
- Opt-Out Script
- Data Reset
- Body Hiding
- Visit-Specific Variations
- Variation Styling
- Preview Issues
- Variation Editing
- Full-Site Testing
- Blinking Variations
- Cross-Domain Cookies
- Regex Support
- Conversion Tracking
- SPA Testing
- Project Setup
- Cross-Domain Tracking
- Geo-Targeting
- Analytics Tools
- Campaign Tags
- Previewing
- IDs
- Query String Targeting
- Bounce Rate Goals
- Bot Filtering
- Query String Variables
- Custom Audiences
- Redirects
- Baseline
- Tracking Code Location
- Secure Cookies
- AngularJS
- Cloudflare
- Code Installation
-
Track Goals
- Form Tracking
- Cookie Management
- iFrame Click Tracking
- Performance Optimization
- Revenue Tracking
- Interaction Goals
- Form Submissions
- Advanced Goals
- Lazy Loading
- Multi-Conversions
- URL Parameters
- Bounce Rate Goals
- DataLayer Integration
- Scroll Depth
- Social Interactions
- Page Views
- Marketo Forms
- Feature Analysis
- AJAX Forms
- Revenue Tracking via GTM
- Order Outliers
- Cumulative Revenue
- Goal Templates
- Adding Revenue Goals
- JS-Based Goals
- Goal Basics
- Google Analytics Goals
- Social Sharing
- Dynamic Goals
- Typeform Integration
-
Target Visitors
- Geolocation
- Interaction Goals
- Goal-Based Targeting
- Weather Targeting
- Cookie-Based Targeting
- Page Visits
- Audience Management
- Audience Segmentation
- Experiment Targeting
- Advanced Audience Creation
- Audience Templates
- Audience Creation
- Data Layer Integration
- Manual Activation
- JavaScript Conditions
- Device Targeting
- Language Targeting
- IP-Based Exclusion
- Visitor Management
- Page Tagging
- Cookies
-
Troubleshooting
- Google Warnings
- Visual Editor
- HTTPS Content
- Logs
- Support Options
- Bootstrap
- Cookie Blocking
- Change History
- Mobile Debugging
- AdWords
- Bot Exclusion
- Domain Issues
- Cloudflare Issues
- Monitoring
- Cloaking Penalties
- Goal Editor Issues
- Variations
- Snippet Performance
- Changes Not Saved
- Blocked Visual Editor
- Goal Testing
- Visual Editor Browsing
- Experiment Issues
- Installation Verification
- Data Leak Prevention
- Usage Limits
- Experiment Previews
- GA4 Revenue
- Chrome Debugger Logs
- SPA Errors
- Checkout JSON Error
-
Analyze Results
-
Integrations
- Google Analytics
- Cookie Consent Platforms
- Microsoft Clarity
- Plausible
- Marketo
- HubSpot
- Tealium
- Smartlook
- Klaviyo
- Salesforce CRM
- FullStory
- Snowplow Analytics
- Webflow
- GA4 Roles
- Amplitude
- Segment
- React
- BigCommerce
- WooCommerce
- Active Campaign
- Google Tag Manager
- Mixpanel
- Zapier
- Inspectlet
- Crazy Egg
- LanderApp
- Unbounce
- Instapage
- Drupal
- PrestaShop
- Magento
- Roistat
- Piano Analytics
- Heap Analytics
- Kissmetrics
- Mouseflow
- Adobe Analytics
- Clicky
-
Account Management
-
Developers
-
What's New
-
Common Questions
-
Shopify
Preview Doesn't Work or Is Not Showing Properly
THIS ARTICLE WILL HELP YOU:
Troubleshoot Common reasons for preview issues
Convert Tracking Code
-
The Convert tracking code (also sometimes referred to as project code snippet) is not installed on your website.
-
The Convert tracking code is installed, but not from the correct project. Each project in Convert Experiments has it's own tracking code. Make sure you add the code that belongs to the Project in which you created your Experiment.
-
Make sure the URL(s) in Active Websites in your Project Configuration matches the website you installed the Convert tracking code on.
Visual Editor URL
-
Preview is showing a different page than the target defined in the Site Area. That would be because the preview is based on the original URL you used when you first created the experiment. After creating the experiment, the Visual Editor URL can be modified by going to your Experience Summary, and under "Experiment", clicking the edit icon.
Conflict with Other Experiments
-
You have another experiment which has the same Site Area conditions and also has the status of Active, Completed or Paused.
This is because Live Preview ignores Audience conditions. For instance, if you have an experiment with an Audience defined for mobile users, and another experiment with an Audience defined for desktop users, and both with the same Site Area conditions, you could also be included in the other experiment when you do a Live Preview on either of these experiments.
Problems with Variation Code
-
If you have checked all of the above and still cannot resolve the issue, the problem is likely related to the Variation code:
-
If you made changes to the Variation using the Visual Editor functionality, it is possible that there is a conflict with the code on your website and you may need help from a developer on your team.
-
If you manually wrote the variation code, it is possible that there is an error there. Any error in the code would cause the code to fail to execute, therefore not rendering your variation.
-
Miscellaneous
When you use a Preview Link, we append parameters that look like this:
?convert_action=convert_vpreview&convert_e=121212121&convert_v=100111234.
Sometimes those parameters might be removed by your host or server. You can notice this if you look at the address bar in your browser. If you do not see these parameters, you are not in Preview mode. In that case, see Additional Information below.
Additional Information
- If in doubt, the most accurate way to view your variation code is to Activate the experiment and visit the site in a fresh Incognito window in Chrome. It is suggested that you create a QA test audience in order to test it yourself without visitors being inadvertently bucketed into the experiment before you are ready. See this article for more information on qa testing.
Once you have tested, you can reset the reporting back to zero.