General Guide: See Events Not Firing for universal debugging steps.
Duda-Specific Causes
Configuration Issues
- Native integration not enabled
- Wrong tracking ID entered
- Code in wrong location (Head vs Body HTML)
Publishing/Cache Issues
Code Conflicts
- Multiple tracking implementations
- JavaScript errors from widgets
- Consent management blocking scripts
Ecommerce-Specific
- dmAPI not available on page
- Wrong page type for events
- DOM selectors not matching theme
Diagnostic Steps
Step 1: Verify Integration Settings
- Go to Site Settings in Duda editor
- Check native integrations (GA, GTM, Meta Pixel)
- Verify IDs are correct
Step 2: Check Head/Body HTML
- Go to Site Settings > Head HTML
- Verify tracking code is present and correct
- Check Body HTML for additional scripts
Step 3: View Page Source
- Visit your live site (not editor preview)
- Right-click > View Page Source
- Search for your tracking code/IDs
- Confirm code is in correct location
Step 4: Check Browser Console
- Open DevTools (F12)
- Go to Console tab
- Look for JavaScript errors (red messages)
- Check for blocked resources
Step 5: Test with Debug Tools
- GA4 Realtime reports
- GA Debugger extension
- GTM Preview Mode
Meta Pixel:
- Meta Pixel Helper extension
- Events Manager Test Events
GTM:
- GTM Preview Mode
- Tag Assistant extension
Duda-Specific Fixes
Fix 1: Clear CDN Cache
After making tracking changes:
- Go to Site Settings > Advanced
- Find CDN/cache settings
- Clear cache
- Wait a few minutes
- Test on live site
Fix 2: Republish Site
- Make any minor edit in editor
- Click Publish
- Wait for publish confirmation
- Test on live site (not preview)
Fix 3: Use Native Integrations
If manual code isn't working, try native:
- Remove manual code from Head/Body HTML
- Use Site Settings > integrations
- Enter only your tracking ID
- Publish and test
Fix 4: Fix Code Placement
Correct placement:
- GTM head code → Head HTML
- GTM noscript → Body HTML
- GA4/Meta Pixel → Head HTML
Common mistake: Putting all code in Head HTML (noscript should be in Body).
Fix 5: Check Consent Settings
If using a consent management:
- Check consent tool is configured correctly
- Verify tracking fires after consent
- Test by granting consent manually
Fix 6: Debug dmAPI (Ecommerce)
For ecommerce events:
// Test in browser console on product page
console.log(window.dmAPI);
console.log(window.dmAPI.getProductInfo());
If dmAPI is undefined, you're not on an ecommerce page or ecommerce isn't enabled.
Common Issues & Solutions
| Issue | Cause | Solution |
|---|---|---|
| No events at all | Integration not enabled | Enable in Site Settings |
| Works in preview only | Not published | Publish site |
| Intermittent tracking | Cache issues | Clear CDN cache |
| Ecommerce events missing | Wrong page type | Check dmAPI availability |
| Duplicate events | Multiple implementations | Remove duplicates |
| Events blocked | Consent management | Check consent config |
Testing Checklist
- Tracking IDs are correct
- Code is in correct location (Head/Body HTML)
- Site is published (not just saved)
- CDN cache is cleared
- Code appears in page source
- No JavaScript errors in console
- Events appear in platform dashboards
- Tested in incognito mode
- Tested on different browsers
- Ecommerce: dmAPI is available