Voog Troubleshooting: Common Issues and Fixes | OpsBlu Docs

Voog Troubleshooting: Common Issues and Fixes

Debug analytics issues on Voog — Liquid template injection, built-in analytics, multi-language site structure, and custom JavaScript limitations.

Voog is an Estonian website builder focused on multi-language sites, using a Liquid-based template engine. Analytics issues on Voog typically involve the Liquid template system, the platform's built-in analytics feature conflicting with third-party tracking, and the multi-language URL structure fragmenting data across language versions.

Voog-Specific Debugging Approach

Voog uses Liquid templates (similar to Shopify). You can edit templates through the Voog admin design editor, which gives you control over the HTML structure including script injection.

Check Template Code Injection

// In browser console, verify analytics is present
console.log('GA loaded:', typeof gtag === 'function');
document.querySelectorAll('script[src*="gtag"], script[src*="gtm"]').forEach(s => {
  console.log('Analytics script:', s.src);
});

// Check for Voog's built-in analytics
console.log('Voog analytics:', document.querySelector('script[src*="voog"]')?.src || 'none');

Verify via Voog Admin

  1. Log into Voog admin > Design > Edit HTML/CSS
  2. Check the layout file (usually layout.tpl) for analytics code
  3. Verify the code is in the <head> section, not inside a Liquid conditional that might exclude some pages

Most Common Voog Analytics Issues

1. Liquid Template Variable Conflicts

Symptoms: Analytics code partially renders. JavaScript contains unexpected Liquid output or is missing portions.

Root cause: Voog's Liquid template engine processes all content in .tpl files. If your JavaScript contains patterns that look like Liquid tags ({{ }} or {% %}), they get processed.

Fix: Use the {% raw %} tag to prevent Liquid processing:

{% raw %}
<script async src="https://www.googletagmanager.com/gtag/js?id=G-XXXXXXX"></script>
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('js', new Date());
gtag('config', 'G-XXXXXXX');
</script>
{% endraw %}

2. Built-in Voog Analytics Conflicting

Symptoms: Double-counted visits or inconsistent data between Voog's statistics and Google Analytics.

Root cause: Voog includes its own analytics dashboard (accessible via the admin panel's Statistics section). While it typically does not conflict technically with GA, both systems track visitors independently.

Fix: Voog's built-in analytics cannot be disabled, but it should not interfere with GA. If you see actual script conflicts, check for third-party Voog plugins that may inject additional tracking.

3. Multi-Language URLs Splitting Data

Symptoms: Analytics shows separate entries for /en/about, /et/about, /ru/about. Traffic is fragmented by language.

Root cause: Voog's core feature is multi-language support, creating separate URL paths per language. Each language version appears as a different page in GA.

Fix: Normalize URLs and track language as a custom dimension:

// In your layout.tpl
var pagePath = window.location.pathname.replace(/^\/(en|et|ru|de|fr|fi|lv|lt)\//, '/');
gtag('config', 'G-XXXXXXX', {
  page_path: pagePath,
  custom_map: { dimension1: 'page_language' }
});
gtag('event', 'page_view', {
  page_language: '{{ page.language_code }}'
});

4. Page-Specific Templates Missing Tracking

Symptoms: Analytics works on most pages but blog posts, product pages, or specific page types are untracked.

Root cause: Voog uses different layout templates for different page types. If analytics is in layout.tpl but blog posts use blog_article.tpl with a different layout, they may miss the tracking code.

Fix: Ensure analytics is in the main layout that all page types reference:

{%- comment -%} In layout.tpl - this is the base template for all pages {%- endcomment -%}
<head>
  {{ site.header }}
  {% raw %}
  <script async src="https://www.googletagmanager.com/gtag/js?id=G-XXXXXXX"></script>
  <script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}
  gtag('js', new Date());
  gtag('config', 'G-XXXXXXX');
  </script>
  {% endraw %}
</head>

5. Voog's Preview Mode Tracking Visits

Symptoms: Preview visits during content editing inflate pageview counts.

Fix: Detect Voog edit/preview mode:

// Detect Voog edit mode
var isVoogEdit = document.querySelector('.edy-site-header') !== null ||
  window.location.search.includes('editmode') ||
  document.cookie.includes('voog_edit');

if (isVoogEdit) {
  window['ga-disable-G-XXXXXXX'] = true;
}

Environment Considerations

  • Managed hosting: Voog is a fully managed SaaS platform. No server access
  • Liquid templates: Similar to Shopify's Liquid but with Voog-specific objects and filters. Not all Shopify Liquid patterns work in Voog
  • Estonian focus: Voog is popular in the Baltic region. Default language options reflect this. Ensure your analytics handles Eastern European character sets
  • Custom domains: Voog supports custom domains with automatic SSL. DNS propagation during setup can cause temporary tracking gaps
  • Ecommerce: Voog has built-in ecommerce features. Product and order tracking requires Voog-specific Liquid variables

Performance Issues

  • LCP Issues - Liquid template rendering and multi-language page resolution
  • CLS Issues - Layout shifts from language switcher and dynamic content blocks

Tracking Issues

  • Events Not Firing - Debug Liquid template conflicts, multi-language URL routing, and edit mode leakage
Back to top