- Help Center
- Troubleshooting
- Checkout JSON Error
-
General
-
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
-
Shopify
-
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
- 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
How to correct the "Error: convert_attributes is empty or invalid after parsing" console or a JSON error when starting a checkout?
Here's a single sentence summary of the article: To fix the "Error: convert_attributes is empty or invalid after parsing" console error and enable proper purchase tracking in the Convert Manual Shopify Integration...
When using the Convert Manual Shopify Integration, you may encounter an error in the console that says "Error: convertattributes is empty or invalid after parsing" or a JSON-related error during the checkout process. This issue typically occurs when the experiment data is not properly written to the localStorage.convertattributes parameter. Additionally, purchase tracking will not work correctly when this error occurs.
Why does this happen?
This error often appears because the browser doesn't allow data to be written to localStorage when the user moves between different domains or subdomains. For example, if a customer starts on www.shop.com and then moves to checkout.shop.com for the checkout process, the browser treats these as separate domains and restricts data sharing.
How to fix it:
To resolve this issue, you need to adjust the domain settings in your Convert account to allow data sharing across all subdomains of your shop. Here's how to do it:
- Log in to your Convert account.
- Navigate to the Convert App.
- Select your project.
- Go to Configuration > Active Websites.
- Add a wildcard entry for your domain. For example, if your shop is on shop.com, add "*.shop.com" as an entry.
- Remove all other entries related to your domain (like www.shop.com, checkout.shop.com, etc.).
- Save your changes.
By adding the wildcard entry (*.shop.com), you're telling Convert to treat all subdomains of shop.com as part of the same site. This allows the experiment data to be shared across these subdomains, resolving the localStorage issue and enabling proper purchase tracking.
After making this change, test the checkout process again using a fresh incognito browser session. An incognito (or private) browsing session ensures you're starting with a clean slate, without any existing cookies or cached data that might interfere with the test. The error should no longer appear, and the Convert Manual Shopify Integration should work correctly across all pages of your shop, including proper purchase tracking.
If you continue to experience issues after making this change and testing in an incognito session, please contact Convert support for further assistance.