Appearance
Troubleshooting
Common issues and how to resolve them.
Quick Reference
| Symptom | Quick Fix | Section |
|---|---|---|
| Script not detected | Check it's in <head>, clear cache | Installation |
| Experiments not showing | Try incognito, check if set to Live | Installation |
| "Can't find location" error | Select a parent element, check for iframes | Editor |
| Prompt not working | Be more specific, avoid dynamic elements | Editor |
| Mobile looks wrong | Preview mobile before launch, use "on mobile only" | Editor |
| No data in dashboard | Verify script, check experiment is Live, wait 24-48h | Results |
| Results don't match GA4 | This is normal—relative comparison is still accurate | Results |
| Significance taking too long | Reduce variants, focus on high-traffic pages | Results |
| Preview looks slow/different | Use incognito, live is faster than preview | Preview |
Jump To
Installation Issues
Script not detected
Symptoms: Dashboard shows "Installation required" even after adding the script.
Check:
- Script is in the
<head>section, not<body> - Script is placed high in the
<head>(before other scripts) - No typos in the script snippet
- Page has been refreshed/cache cleared
Solution: Use browser DevTools (F12) → Network tab → search for "dalton" to verify the script is loading.
Experiments not showing
Symptoms: Script is installed but experiments don't appear on the page.
Check:
- Experiment is set to "Live" not "Paused"
- You're viewing the correct URL
- Cookie consent has been accepted (if required)
- You're not in a cached version of the page
Solution: Open an incognito window and visit the page. If experiments appear there, it's a caching issue.
Editor Issues
"Can't find location to place experiment"
Symptoms: Error appears when trying to create an experiment.
Common causes:
- Element is inside an iframe
- Element loads dynamically via JavaScript
- Element is inside a shadow DOM component
Solution: Try selecting a parent element, or verify the element exists in the static HTML.
Prompt not working / errors
Symptoms: AI returns an error or unexpected result.
Common causes:
- Element is dynamic (price, stock, selector)
- Prompt is too vague
- Element is complex (multi-nested components)
Solutions:
- Be more specific: "Make this one sentence" not "Make it shorter"
- Avoid dynamic elements like prices or inventory
- Try a simpler element first
Mobile view looks wrong
Symptoms: Experiment looks good on desktop but broken on mobile.
Cause: AI optimizes for the current view.
Solution:
- Always check mobile preview before launching
- Use "on mobile only" in prompts for mobile-specific changes
- Create separate prompts for mobile adjustments
Results & Dashboard Issues
No data showing
Symptoms: Dashboard shows zero sessions or conversions.
Check:
- Script is installed correctly
- At least one experiment is live
- Conversion goal is configured
- Sufficient time has passed (24-48 hours minimum)
Results seem inaccurate
Symptoms: Numbers don't match Google Analytics.
Possible causes:
- Different attribution windows
- Bot traffic affecting one tool differently
- Sampling differences
Solution: Dalton's relative comparison (variant vs baseline) remains accurate even if absolute numbers differ slightly from GA4.
Significance taking too long
Symptoms: Experiments running for weeks without reaching significance.
Common causes:
- Low traffic volume
- Low conversion rate (under 2%)
- Too many variants splitting traffic
Solutions:
- Reduce number of variants
- Focus on higher-traffic pages
- Consider using click-through rate instead of purchase for faster learning
Preview Issues
Preview looks different from live
Symptoms: Preview link shows slow loading or different styling.
Cause: Preview mode has additional debugging overhead.
Solution: Right-click preview link → Open in incognito. Live visitors see instant changes (<50ms).
Preview shows wrong variant
Symptoms: You keep seeing the same variant in preview.
Cause: Cookie persistence.
Solution: Use incognito mode or clear cookies to see different variants.
Still Need Help?
If you can't resolve an issue:
- Take a screenshot of the error
- Note the page URL and browser
- Contact support with these details
We typically respond within 24 hours on business days.