Zyro Troubleshooting: Common Issues and Fixes

Troubleshoot common Zyro issues including performance problems and tracking failures.

Common issues you may encounter with your Zyro site and how to diagnose and fix them.

Performance Issues

Zyro sites are optimized for speed, but custom code and third-party integrations can impact performance. Core Web Vitals affect both user experience and SEO rankings.

Largest Contentful Paint (LCP)

LCP measures loading performance. Zyro-specific LCP issues include:

Unoptimized images in Zyro templates
Custom code blocking render in header
Third-party scripts loading synchronously
Multiple tracking pixels without GTM
Heavy AI-generated content

Target: LCP under 2.5 seconds

Cumulative Layout Shift (CLS)

CLS measures visual stability. Zyro-specific CLS issues include:

Images without dimensions in custom sections
Dynamic content loading
Custom fonts without font-display
Third-party widgets causing shifts
Zyro template updates affecting layout

Target: CLS under 0.1

General Performance Best Practices

Template Selection:

Use modern Zyro templates
Leverage AI website builder for optimized structure
Test template performance before committing
Consider mobile-first templates

Custom Code Management:

Minimize custom JavaScript
Use async/defer for all external scripts
Consolidate tracking through GTM
Remove unused custom code
Test code impact on performance

Image Optimization:

Use Zyro's image optimization features
Compress images before uploading
Use appropriate image formats (WebP when possible)
Avoid extremely large images
Leverage Zyro's CDN

Third-Party Scripts:

Use GTM to manage all tracking codes
Delay non-critical scripts
Remove unused integrations
Monitor script impact on load time

For general performance concepts, see the global performance hub.

Tracking & Analytics Issues

Events Not Firing

Common causes of tracking failures on Zyro:

Custom code not saved or site not published
JavaScript errors in custom code
Ad blockers preventing pixel loads
Incorrect tracking IDs
Code placement issues (header vs. footer)
Zyro plan limitations

Common scenarios:

GA4 not showing real-time data
Meta Pixel shows errors in Pixel Helper
GTM tags not firing
Events firing multiple times

Tracking Best Practices

Consolidate Through GTM:

Install GTM once in header code
Add all tracking pixels through GTM
Easier to manage and update
Better performance
Test changes before publishing

Test Thoroughly:

Use browser extensions (GTM debugger, Meta Pixel Helper)
Test in incognito/private browsing
Test across different browsers
Test on mobile devices
Verify in platform analytics
Use debug modes when available

Monitor Continuously:

Check analytics platforms weekly
Set up custom alerts
Monitor data quality
Review conversion tracking

For general tracking concepts, see the global tracking hub.

Common Zyro-Specific Issues

Custom Code Not Working

Problem: Code added to Zyro settings doesn't execute.

Common Causes:

Code not saved in settings
Site not published after adding code
JavaScript syntax errors
Code added to wrong location (footer vs header)
Conflicts with existing code

Diagnosis:

Open browser console (F12)
Look for JavaScript errors
Check if code is present in page source
Verify code location in Zyro settings

Fix:

Ensure you clicked Save in Website code settings
Publish site after making changes
Fix JavaScript syntax errors
Move code to header if in footer (or vice versa)
Wrap code in DOMContentLoaded event listener

Free Plan Limitations

Problem: Cannot add tracking code.

Limitation: Zyro Free plan doesn't allow custom code injection.

Workaround: None - must upgrade to paid plan.

Solution:

Upgrade to Unleash, eCommerce, or eCommerce Plus plan
Minimum: Unleash plan for custom code access
Recommended: eCommerce plan for full features

AI Website Builder Issues

Problem: AI regenerates content and breaks tracking.

Expected Behavior: Zyro's AI may update page structure.

Solution:

Use generic selectors that work across variations
Avoid targeting specific element IDs
Test tracking after AI regenerations
Use GTM for more flexible tracking

Template Updates Breaking Code

Problem: Zyro template update changes HTML structure.

Cause: Template updates may modify element classes or structure.

Solution:

Test tracking after template updates
Use flexible selectors
Document all custom code
Keep backups of working code

Form Tracking Issues

Problem: Contact form submissions not tracked.

Cause: Zyro forms may submit without clear success indicator.

Solution: Track form submission via event listener:

document.addEventListener('DOMContentLoaded', function() {
  var forms = document.querySelectorAll('form, .zyro-form');

  forms.forEach(function(form) {
    form.addEventListener('submit', function() {
      // Track with GA4
      gtag('event', 'form_submit', {
        form_name: 'contact_form'
      });

      // Track with Meta Pixel
      fbq('track', 'Lead');
    });
  });
});

Mobile vs Desktop Tracking Discrepancies

Problem: Different tracking behavior on mobile vs desktop.

Causes:

Mobile browsers handle scripts differently
Touch events vs mouse events
Mobile ad blockers more aggressive
iOS tracking restrictions (ITP)

Solutions:

Test thoroughly on mobile devices
Use touch events in addition to click events
Implement Server-Side Tracking
Use Google Consent Mode for iOS compliance

Debugging Tools

Browser Developer Tools

Chrome DevTools (F12):

Console: Check for JavaScript errors
Network: Verify tracking requests sent
Application: Check localStorage, cookies
Sources: Debug custom JavaScript

Common Console Checks:

// Check if GA4 loaded
typeof gtag !== 'undefined'

// Check if Meta Pixel loaded
typeof fbq !== 'undefined'

// Check GTM data layer
console.log(dataLayer)

// View all tracking requests
// Filter Network tab by: "collect", "fbevents", "gtm"

Zyro-Specific Tools

View Custom Code:

Right-click on your site
View Page Source (Ctrl+U)
Search (Ctrl+F) for your tracking IDs
Verify code is present and correct

Test Custom Code:

// Add to console to test code snippets
(function() {
  // Your custom code here
})();

Analytics Debugging Tools

Browser Extensions:

Platform Tools:

GA4 DebugView (Admin → DebugView)
Meta Events Manager Test Events
GTM Preview Mode

Performance Testing Tools

Google PageSpeed Insights
WebPageTest
GTmetrix
Chrome DevTools Lighthouse

Getting Help

Zyro Support Channels

Zyro Help Center:

support.zyro.com
Comprehensive knowledge base
Step-by-step guides

Zyro Support:

Email support for all paid plans
Live chat for higher-tier plans
Response typically within 24 hours

Zyro Community:

User forums
Share experiences
Get community help

Third-Party Platform Support

For Tracking Issues:

When to Hire a Developer

Consider hiring help when:

Complex custom functionality needed
Multiple tracking integrations conflicting
Advanced e-commerce tracking required
Performance issues persist
Custom integrations beyond standard tracking
Server-side tracking implementation needed

Prevention Best Practices

Documentation

Document Your Setup:

List all tracking codes installed
Note GTM tags and triggers
Record custom code additions
Keep tracking ID reference
Document custom events

Testing Workflow

Before Adding Code:

Test code in isolated environment
Check for JavaScript errors
Verify syntax is correct
Ensure no conflicts

After Adding Code:

Save settings in Zyro
Publish site
Test in real-time
Check browser console
Verify with debugging tools
Test on mobile device

Monitoring Routine

Weekly:

Check analytics platforms for data
Verify conversion tracking
Review error logs

Monthly:

Audit installed tracking codes
Remove unused integrations
Review performance metrics
Update documentation

Quarterly:

Full tracking audit
Performance optimization review
Update tracking implementations
Test all conversion paths

Common Error Messages

"gtag is not defined"

Cause: GA4 code not loaded or syntax error.

Fix:

Verify GA4 code is in Header code
Check Measurement ID is correct
Ensure site was published
Check for JavaScript errors blocking load

"fbq is not defined"

Cause: Meta Pixel code not loaded.

Fix:

Verify pixel code is in Header code
Check Pixel ID is correct
Ensure site was published
Test without ad blockers

"dataLayer is not defined"

Cause: GTM container not loaded.

Fix:

Verify GTM code is in Header code
Check Container ID (GTM-XXXXXX)
Ensure site was published
Check for errors blocking GTM

Next Steps

Performance Issues:

Tracking Issues:

Debug Events Not Firing

Prevention:

Document your setup
Test before and after changes
Monitor regularly
Keep tracking codes updated

For general troubleshooting concepts, see the global issues hub.

返回顶部