How to Fix Jimdo Tracking Events Not Firing | OpsBlu Docs

How to Fix Jimdo Tracking Events Not Firing

Fix GA4, GTM, and pixel events not firing on Jimdo — Creator vs Dolphin code injection differences, header widget placement, and site publish debugging

Common causes and solutions for tracking events that don't fire correctly on Jimdo websites (both Creator and Dolphin).

For general tracking troubleshooting, see the global tracking troubleshooting guide.

Quick Diagnosis Checklist

Before diving deep, check these common issues:

  • Ad blocker disabled (for testing)
  • Incognito/private mode (clear cache)
  • Browser console has no errors (F12)
  • Code saved in Jimdo (clicked Save button)
  • Site published (changes published after saving)
  • Correct code section (Head vs. Body)
  • Tracking ID correct (no typos)
  • GTM container published (if using GTM)
  • Test on different browser (rule out browser-specific issues)

Jimdo-Specific Tracking Limitations

Code Placement Issues

Jimdo Creator:

  • Full access to Head and Body sections
  • Can add page-specific code
  • More flexibility but also more ways to make mistakes

Jimdo Dolphin:

  • Limited to global analytics settings
  • Restricted code placement
  • Cannot add page-specific tracking easily
  • Less prone to placement errors but less flexible

Platform Restrictions

Both platforms:

  • Cannot edit core template files
  • Cannot modify Jimdo's built-in JavaScript
  • ✓ CAN add tracking code to Head section
  • ✓ CAN use GTM for advanced tracking

Workarounds:

  • Use GTM for all tracking (recommended)
  • Implement events via GTM custom HTML tags
  • Use GTM triggers for page-specific events

Common Jimdo Tracking Issues

1. Code Not Saved or Published

Most common issue: Code added but not saved or published.

Symptoms:

  • Code doesn't appear in page source
  • Tracking pixels never load
  • No events in analytics platforms

Diagnosis:

Step 1: Check if code is saved

  1. Go back to Jimdo editor
  2. Navigate to Settings → Analytics (or Edit Head)
  3. Verify code is still there

Step 2: Check if site is published

  1. Look for "Publish" or "Publish Changes" button
  2. Verify last publish date
  3. Publish if needed

Step 3: Verify in page source

  1. Visit your live site
  2. Right-click → View Page Source
  3. Search (Ctrl/Cmd + F) for your tracking ID
  4. If not found → code not saved/published

Fix:

  1. Re-add code to correct section
  2. Click Save
  3. Click Publish or Publish Changes
  4. Wait 1-2 minutes for changes to propagate
  5. Clear browser cache and test

2. Code in Wrong Section

Problem: Tracking code added to wrong section (Body instead of Head).

Symptoms:

  • Tracking loads late or inconsistently
  • Some events missing
  • Performance issues

Diagnosis:

Check where code is placed:

Jimdo Creator:

  • Correct: Settings → Edit Head (or SEO section)
  • Wrong: Body code section (for most tracking)
  • Wrong: Individual page code (unless intentional)

Jimdo Dolphin:

  • Correct: Settings → Analytics → Head section
  • Wrong: Body section (if available)

View page source to verify:

<head>
  <!-- Tracking code should be HERE -->
  <script>gtag('config', 'G-XXX');</script>
</head>
<body>
  <!-- NOT here for GA4/Meta Pixel/GTM base code -->
</body>

Fix:

  1. Remove code from wrong section
  2. Add to Head section
  3. Save and publish

3. JavaScript Errors

Problem: JavaScript errors preventing tracking code from executing.

Symptoms:

  • Code appears in source but doesn't fire
  • Browser console shows errors
  • Some tracking works, some doesn't

Diagnosis:

Step 1: Open browser console

  1. Press F12 (or right-click → Inspect)
  2. Go to Console tab
  3. Reload page
  4. Look for red error messages

Common errors:

// Syntax error
Uncaught SyntaxError: Unexpected token

// Undefined variable/function
Uncaught ReferenceError: gtag is not defined

// Script blocked
Failed to load resource: net::ERR_BLOCKED_BY_CLIENT

Step 2: Identify error source

  • Click on error to see filename
  • Check if it's your tracking code
  • Note error message details

Fix based on error type:

Syntax errors:

// Wrong (missing quote)
gtag('config', 'G-XXXXXXXXXX);

// Correct
gtag('config', 'G-XXXXXXXXXX');

Undefined errors:

// Wrong (using gtag before it's loaded)
gtag('event', 'click');
<script async src="gtag.js"></script>

// Correct (load script first)
<script async src="gtag.js"></script>
...later...
gtag('event', 'click');

Blocked errors:

  • Ad blocker blocking request
  • Disable ad blocker for testing
  • Use different browser

4. Incorrect Tracking IDs

Problem: Wrong tracking ID format or typo.

Symptoms:

  • Code loads but events don't appear in analytics
  • DebugView shows no activity
  • Meta Pixel Helper shows red icon

Diagnosis:

Verify ID formats:

GA4 Measurement ID:

  • Format: G-XXXXXXXXXX
  • NOT UA-XXXXXXXXX (Universal Analytics - deprecated)
  • Example: G-ABC123XYZ0

Meta Pixel ID:

  • Format: 16-digit number
  • Example: 1234567890123456
  • NOT Business Manager ID or Page ID

GTM Container ID:

  • Format: GTM-XXXXXXX
  • Example: GTM-ABC123

Check in page source:

  1. View page source
  2. Search for your ID
  3. Verify correct format
  4. Check for typos

Fix:

  1. Get correct ID from platform:
    • GA4: Admin → Data Streams → Measurement ID
    • Meta: Events Manager → Pixel ID
    • GTM: Container → Container ID
  2. Update code in Jimdo
  3. Save and publish

5. Ad Blockers

Problem: Browser extensions or ad blockers preventing tracking.

Symptoms:

  • Works in incognito mode
  • Works on mobile but not desktop
  • Meta Pixel Helper shows "not loaded"
  • Network tab shows blocked requests

Diagnosis:

Check for ad blocker:

  1. Look for ad blocker icon in browser
  2. Open Network tab (F12 → Network)
  3. Reload page
  4. Look for red/blocked requests to:
    • googletagmanager.com
    • google-analytics.com
    • facebook.net

Test without ad blocker:

  1. Disable ad blocker temporarily
  2. Open incognito/private window
  3. Test on different browser
  4. Test on mobile device

Fix:

For testing:

  • Disable ad blocker
  • Use incognito mode
  • Test on mobile

For users:

  • Ad blocker blocking is normal
  • Cannot prevent for all users
  • Accept some data loss
  • Consider server-side tracking (advanced)

Google Analytics 4 Issues

GA4 Not Tracking Page Views

Diagnosis:

1. Check if GA4 code is present

View page source and look for:

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

2. Verify in browser console

// Check if gtag is loaded
console.log(window.gtag);
// Should return: function() {...}

// Check data layer
console.log(window.dataLayer);
// Should return: Array with events

3. Use GA4 DebugView

  1. Add to your tracking code:
gtag('config', 'G-XXXXXXXXXX', {
  'debug_mode': true
});
  1. Go to GA4 → Admin → DebugView
  2. Navigate your site
  3. Events should appear in real-time

Common fixes:

Missing async attribute:

<!-- Wrong (blocking) -->
<script src="https://www.googletagmanager.com/gtag/js?id=G-XXX"></script>

<!-- Correct (async) -->
<script async src="https://www.googletagmanager.com/gtag/js?id=G-XXX"></script>

Wrong Measurement ID:

// Wrong (UA property)
gtag('config', 'UA-XXXXXXXXX');

// Correct (GA4 property)
gtag('config', 'G-XXXXXXXXXX');

Duplicate implementations:

  • Remove old UA code
  • Remove duplicate GA4 code
  • Use only one implementation method

GA4 Custom Events Not Firing

Problem: Custom events (button clicks, form submits) not tracking.

Diagnosis:

Check event code:

// Event tracking code
document.querySelector('.button').addEventListener('click', function() {
  gtag('event', 'button_click');
});

Common issues:

1. Selector doesn't match:

// Check if element exists
console.log(document.querySelector('.button'));
// Should return: <element> (not null)

2. Event listener not attached:

// Code runs before DOM ready
document.querySelector('.button').addEventListener(...);
// ERROR: Cannot read property of null

// Fix: Wrap in DOMContentLoaded
document.addEventListener('DOMContentLoaded', function() {
  document.querySelector('.button').addEventListener('click', function() {
    gtag('event', 'button_click');
  });
});

3. GTM implementation better:

Instead of direct code, use GTM:

  1. Install GTM on Jimdo
  2. Create Click trigger for button
  3. Create GA4 Event tag
  4. Test in GTM Preview mode

See GA4 Event Tracking for details.

Meta Pixel Issues

Meta Pixel Not Loading

Diagnosis:

1. Install Meta Pixel Helper

  • Chrome Extension
  • Visit your site
  • Check icon:
    • Green = Working
    • Yellow = Warnings
    • Red = Errors
    • No icon = Not loaded

2. Check browser console

// Check if fbq is loaded
console.log(window.fbq);
// Should return: function() {...}

3. Check page source

Look for:

<script>
!function(f,b,e,v,n,t,s){...}
fbq('init', 'YOUR_PIXEL_ID');
fbq('track', 'PageView');
</script>

Common fixes:

Wrong Pixel ID:

// Wrong (not 16 digits)
fbq('init', '123');

// Correct (16-digit number)
fbq('init', '1234567890123456');

Syntax error:

// Wrong (missing quote)
fbq('init', 'PIXEL_ID);

// Correct
fbq('init', 'PIXEL_ID');

Ad blocker:

  • Meta Pixel commonly blocked
  • Disable for testing
  • Test in incognito mode

Meta Pixel Events Not Firing

Problem: PageView works but custom events don't fire.

Diagnosis:

Check Meta Events Manager:

  1. Go to Events Manager → Test Events
  2. Enter your Jimdo URL
  3. Perform action (click button, submit form)
  4. Event should appear in real-time

Common issues:

1. Event code not attached properly:

// Check if button exists
console.log(document.querySelector('.cta-button'));

// If null, selector is wrong

2. Event fires too early:

// Wrong (before DOM ready)
document.querySelector('.button').addEventListener('click', ...);

// Correct (after DOM ready)
document.addEventListener('DOMContentLoaded', function() {
  document.querySelector('.button').addEventListener('click', function() {
    fbq('track', 'AddToCart');
  });
});

3. Missing parameters:

// Wrong (invalid parameter format)
fbq('track', 'Purchase', {
  value: "$99.99", // Should be number
  content_ids: 123 // Should be array
});

// Correct
fbq('track', 'Purchase', {
  value: 99.99,
  content_ids: ['123'],
  currency: 'USD'
});

Google Tag Manager Issues

GTM Container Not Loading

Diagnosis:

1. Check page source

Look for GTM code in <head>:

<script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':
new Date().getTime(),event:'gtm.js'});...})(window,document,'script','dataLayer','GTM-XXXXXXX');</script>

And in <body>:

<noscript><iframe src="https://www.googletagmanager.com/ns.html?id=GTM-XXXXXXX"></iframe></noscript>

2. Check browser console

// Check if GTM is loaded
console.log(window.google_tag_manager);
// Should return: object with container info

3. Use GTM Preview Mode

  1. GTM → Preview
  2. Enter Jimdo URL
  3. Should connect and show Tag Assistant

Common fixes:

Container ID incorrect:

// Verify format: GTM-XXXXXXX
// Check in GTM: Workspace → Container ID

Code not in Head section:

  • Move GTM code to Head (not Body)
  • Jimdo Creator: Settings → Edit Head
  • Jimdo Dolphin: Settings → Analytics → Head

Jimdo changes not published:

  • Save code in Jimdo
  • Click Publish button
  • Wait 1-2 minutes
  • Clear cache and test

GTM Tags Not Firing

Problem: GTM loads but tags don't fire.

Diagnosis:

1. Use GTM Preview Mode

  1. GTM → Preview
  2. Connect to your site
  3. Navigate and trigger events
  4. Check Tag Assistant:

2. Check container published

  • GTM → Workspace
  • Look for "Workspace Changes" banner
  • If present: Click Submit → Publish
  • Always publish after making changes

3. Check trigger conditions

  • Click on tag in Preview mode
  • View "Firing Triggers" and "Blocking Triggers"
  • Verify conditions are met
  • Check variable values

Common fixes:

Container not published:

  1. GTM → Submit
  2. Add version name
  3. Click Publish

Trigger conditions not met:

// Example: Trigger fires when Page Path contains "/contact"
// But page URL is "/contact-us"
// Fix trigger condition to match actual URL

Variables return undefined:

// Check data layer structure
console.log(window.dataLayer);

// Verify variable path matches data
// Data Layer Variable: pageType
// Data Layer: dataLayer.push({'pageType': 'home'})

Tag has JavaScript errors:

  • Check Console for errors
  • Fix syntax in custom HTML tags
  • Test tag code separately

Jimdo Platform-Specific Issues

Creator vs. Dolphin Tracking

Jimdo Creator issues:

Page-specific code not working:

  • Code added to individual page
  • Should be in global Head for site-wide tracking
  • Use page-specific code only for page-specific events

Custom code conflicts:

  • Multiple custom scripts conflicting
  • Jimdo template JavaScript interfering
  • Solution: Simplify, use GTM

Jimdo Dolphin issues:

Limited code access:

  • Cannot add page-specific code
  • Must use GTM for advanced tracking
  • Analytics settings only support basic code

Template restrictions:

  • Cannot customize certain elements
  • Limited selector options
  • May not work with all event tracking

Finding Jimdo Selectors

Problem: Event tracking code can't find elements.

Solution: Use browser DevTools to find selectors

  1. Right-click element → Inspect
  2. View element's class or ID
  3. Use in selector

Example:

<!-- Element in HTML -->
<button class="cc-button cc-cta">Click Me</button>

<!-- Selector in JavaScript -->
document.querySelector('.cc-button')

Common Jimdo Creator classes:

  • .cc-button - Buttons
  • .cc-form - Forms
  • .cc-image - Images

Common Jimdo Dolphin classes:

  • .c-button - Buttons
  • .c-form - Forms

Note: Classes vary by template - always inspect to verify.

Debugging Workflow

Step-by-Step Process

  1. Verify Basic Setup

    • Code in page source
    • Tracking ID correct
    • No JavaScript errors
    • Site published

  2. Test Page Load

    • Clear cache and reload
    • Check if pageview fires
    • Verify in analytics platform
    • Test in incognito mode

  3. Test Events

    • Click buttons → Check events
    • Submit forms → Check events
    • Custom interactions → Check events

  4. Check Data Quality

    • Event names correct
    • Parameters populated
    • Values formatted correctly

  5. Fix Issues

    • Highest priority first
    • One change at a time
    • Test after each fix
    • Document what worked

  6. Verify Fixes

    • Test in incognito
    • Test on mobile
    • Test different browsers
    • Monitor for 24-48 hours

Testing Tools

Browser Extensions

GA4:

Meta Pixel:

GTM:

  • Built-in Preview mode (best option)

Platform Tools

GA4 DebugView:

  • Real-time event debugging
  • See all parameters
  • GA4 → Admin → DebugView

Meta Events Manager Test Events:

  • Real-time event testing
  • See event details
  • Events Manager → Test Events

GTM Preview Mode:

  • See tags, triggers, variables
  • Debug container issues
  • GTM → Preview

Browser Console Commands

Check if tracking loaded:

// GA4
console.log(window.gtag);

// Meta Pixel
console.log(window.fbq);

// GTM
console.log(window.google_tag_manager);

// Data Layer
console.log(window.dataLayer);

Monitor data layer:

const originalPush = window.dataLayer.push;
window.dataLayer.push = function() {
  console.log('Data Layer Push:', arguments[0]);
  originalPush.apply(window.dataLayer, arguments);
};

When to Get Help

DIY Troubleshooting Exhausted

If after following this guide:

  • Events still not firing
  • Can't identify root cause
  • Complex custom implementation needed

Consider Professional Help

When to hire:

  • Time-sensitive launch
  • Complex e-commerce tracking
  • Multiple integrations failing
  • Custom event requirements
  • GTM advanced setup needed

Where to find help:

  • Freelance platforms (Upwork, Fiverr)
  • Analytics consultants
  • GTM specialists
  • Web developers familiar with Jimdo

Support Resources

Jimdo Support:

  • Platform issues
  • Code placement questions
  • Publishing problems

Analytics Platform Support:

Next Steps

Integration Guides:

Performance Issues:

For general troubleshooting strategies, see Tracking Troubleshooting Guide.

For privacy issues related to tracking, see Privacy Troubleshooting.

Back to top