Simvoly Troubleshooting: Common Issues and Fixes | OpsBlu Docs

Simvoly Troubleshooting: Common Issues and Fixes

Debug analytics issues on Simvoly — custom code injection limits, funnel page tracking, white-label domain configurations, and built-in analytics...

Simvoly is a website and funnel builder with white-label capabilities. Analytics troubleshooting on Simvoly is constrained by the platform's managed hosting model: you have limited code injection points, no server access, and the platform's funnel system creates unique tracking challenges for multi-step conversion flows.

Simvoly-Specific Debugging Approach

Since Simvoly is a managed platform, all debugging happens through the Simvoly dashboard and browser-side inspection.

Verify Code Injection Points

Simvoly provides specific locations for custom code:

  1. Settings > Custom Code > Header Code: Global <head> injection
  2. Settings > Custom Code > Body Code: Global pre-</body> injection
  3. Page-level code: Individual page settings for per-page scripts
  4. Funnel step code: Each funnel step can have its own custom code
// In browser console on your Simvoly site
document.querySelectorAll('script').forEach((s, i) => {
  const src = s.src || '(inline: ' + s.textContent.substring(0, 40) + '...)';
  if (src.includes('gtag') || src.includes('gtm') || src.includes('analytics') ||
      s.textContent.includes('gtag') || s.textContent.includes('dataLayer')) {
    console.log(`Script #${i}:`, src);
  }
});

Check Plan Restrictions

// Verify analytics code is actually present in the served HTML
fetch(window.location.href)
  .then(r => r.text())
  .then(html => {
    console.log('GTM present:', html.includes('googletagmanager'));
    console.log('GA present:', html.includes('gtag') || html.includes('google-analytics'));
    console.log('Custom code sections:', (html.match(/<!-- Custom/g) || []).length);
  });

Most Common Simvoly Analytics Issues

1. Custom Code Stripped on Lower Plans

Symptoms: Code entered in Settings > Custom Code does not appear in the rendered page.

Root cause: Simvoly restricts custom code injection to paid plans. Free or basic plans may not include this feature.

Fix: Upgrade to a plan that supports custom code injection. Check your plan's feature list in Simvoly's pricing page.

2. Funnel Steps Not Tracking as Separate Pages

Symptoms: Multi-step funnels show only one pageview. Individual funnel steps are not tracked as separate page views.

Root cause: Simvoly funnels can use client-side step transitions that do not change the URL or trigger full page loads.

Fix: Add step-specific tracking in each funnel step's custom code:

// Add to each funnel step's page-level custom code
// Step 1
gtag('event', 'page_view', { page_path: '/funnel/step-1', page_title: 'Funnel - Step 1' });

// Step 2
gtag('event', 'page_view', { page_path: '/funnel/step-2', page_title: 'Funnel - Step 2' });

// Thank you page
gtag('event', 'page_view', { page_path: '/funnel/thank-you', page_title: 'Funnel - Complete' });
gtag('event', 'conversion', { send_to: 'AW-XXXXXXX/XXXXXX' });

3. White-Label Domain Tracking Mismatch

Symptoms: Analytics data splits between the Simvoly subdomain and the white-label custom domain. Cookie-based tracking breaks.

Root cause: White-label Simvoly sites can be accessed via both yoursite.simvoly.com and yourdomain.com. If analytics cookies are set for one domain, they are not shared with the other.

Fix:

gtag('config', 'G-XXXXXXX', {
  cookie_domain: 'yourdomain.com',
  linker: {
    domains: ['yoursite.simvoly.com', 'yourdomain.com']
  }
});

4. Built-in Simvoly Analytics Counting Differently

Symptoms: Simvoly's dashboard shows different visitor counts than Google Analytics. Numbers do not match.

Root cause: Simvoly includes its own analytics dashboard that uses different methodology (may count bots, include preview visits, or use different session definitions).

Fix: This is expected. Use GA as your source of truth for external reporting. Simvoly's built-in analytics is useful for quick checks but should not be compared directly to GA numbers.

5. Form Submission Events Not Triggering

Symptoms: Simvoly form submissions complete successfully but no form submission event fires in GA.

Root cause: Simvoly forms submit via AJAX. The form submission does not trigger a page load or a standard form submit event that GA's enhanced measurement can detect.

Fix: Use Simvoly's form submission callback to fire GA events:

// Add to the page with the form
document.addEventListener('simvoly-form-submitted', function(e) {
  gtag('event', 'generate_lead', {
    event_category: 'form',
    event_label: e.detail?.formName || 'contact_form'
  });
});

// Alternative: observe the success message appearance
var formObserver = new MutationObserver(function(mutations) {
  mutations.forEach(function(m) {
    if (m.target.classList?.contains('form-success') || m.target.textContent?.includes('Thank you')) {
      gtag('event', 'generate_lead', { event_category: 'form' });
    }
  });
});
formObserver.observe(document.body, { childList: true, subtree: true, attributes: true });

Environment Considerations

  • Managed hosting: No server access, no FTP, no SSH. All changes through the Simvoly dashboard
  • CDN-served: Simvoly sites use a CDN. Custom code changes may take several minutes to propagate after saving
  • SSL included: All Simvoly sites get automatic SSL. No mixed-content issues
  • White-label: Simvoly's white-label feature means your clients' sites run on Simvoly infrastructure but appear as your own product. Analytics must account for this additional domain layer
  • Funnel vs website mode: Simvoly treats funnels and websites differently in its builder. Analytics configuration may need to be applied separately for each

Performance Issues

  • LCP Issues - Builder-generated layout rendering and CDN delivery timing
  • CLS Issues - Layout shifts from funnel step transitions and dynamic form elements

Tracking Issues

  • Events Not Firing - Debug plan restrictions, funnel step tracking, and AJAX form submissions
Nach oben