If you’re a B2B marketer or product manager, there’s a good chance you’ve tried to run a Qualaroo survey and hit a wall—maybe it doesn’t show up, or it shows up in all the wrong places, or the data looks off. You’re not alone. The Qualaroo survey tool can be really useful for collecting feedback, but getting it to play nicely with a typical B2B website isn’t always straightforward.
This guide is for folks who want to get Qualaroo surveys working reliably, without wasting hours on trial and error or chasing vague help docs. Let’s get right to the problems that actually trip people up, how to spot them, and what actually fixes them.
Common Survey Deployment Headaches (and How to Spot Them)
Before you start poking around in code or settings, it’s worth knowing the classic symptoms of a broken or badly configured survey. Here are the most common ones:
- Survey doesn’t appear at all
- Survey appears on the wrong pages
- Survey shows to the wrong users (or everyone)
- Survey loads slowly or blocks page rendering
- Responses aren’t being collected or look suspiciously low
- Survey is clashing with other scripts or site features
If any of these sound familiar, you’re in the right place.
1. Survey Not Showing Up? Start Here
You’d be amazed how often the survey simply doesn’t appear—and it’s usually a simple fix. Work through these steps before diving into the weeds:
1.1. Double-check the Qualaroo code
- Is the Qualaroo snippet actually installed? Sometimes it’s missing, or pasted onto a staging site but not production.
- Is it in the
<head>or<body>? Qualaroo recommends placing it just before the closing</body>tag. If it’s in the wrong place, it might not fire properly. - Is it behind a tag manager? If you’re using Google Tag Manager or another tool, make sure the trigger is set up right (e.g., fires on All Pages, not just homepage).
Pro Tip: Always view source (or use your browser’s DevTools) to confirm the snippet is really there and not commented out.
1.2. Check for JavaScript Errors
- Open DevTools (F12), go to the Console tab, and reload the page.
- Any red errors? An error in another script can stop Qualaroo from loading, and vice versa.
1.3. Are Ad Blockers Killing It?
- Many ad or privacy blockers nuke survey scripts by default. Check in an incognito window with extensions disabled, or try a different browser.
What to ignore: Don’t waste time tweaking survey settings if the script isn’t even firing. The code has to load first—everything else comes after.
2. Survey Appearing on the Wrong Pages
Let’s say the survey works but is showing up everywhere (or nowhere), or on pages you never intended.
2.1. Review Your Targeting Rules
- In the Qualaroo dashboard, check which URLs the survey is set to display on.
- Watch out for leading/trailing slashes, typos, or using “contains” when you really want “equals.”
Examples:
- /pricing matches only /pricing, but /pricing/ is technically different.
- The “contains” rule will show the survey on /pricing-old as well as /pricing.
2.2. Test Your URL Logic
- Open a private window and visit the exact pages you want to target.
- If it’s a single-page app, make sure Qualaroo is set to listen for dynamic page changes (not just the initial load).
2.3. Multiple Environments? Double-Check Domains
- If you’re running staging and production, make sure you’re not confusing the two in the dashboard setup.
- Surveys set to “example.com” won’t show on “staging.example.com” unless you add both.
Pro Tip: Don’t try to get clever by using wildcards unless you know exactly how Qualaroo parses them. When in doubt, be explicit with your targeting.
3. Wrong Users Seeing the Survey (Or Everyone Does)
Qualaroo’s targeting is powerful, but it’s easy to mess up. Here’s what to check:
3.1. Are You Using the Right Audience Filters?
- Device: Did you mean to show only on desktop, but mobile users are seeing it?
- Returning/New Visitors: Double-check how you’ve set these.
- Referrer: If you want to target users from a certain campaign, make sure your UTM parameters are correct.
3.2. Logged-In vs. Logged-Out Users
- Qualaroo itself can’t “see” your app’s user state unless you pass it custom properties.
- If you only want logged-in users, you (or a dev) need to set up custom targeting via JavaScript.
Example:
js
// Only show survey if user is logged in
if (window.isLoggedIn) {
_kiq.push(['showSurvey', { survey_id: '12345' }]);
}
3.3. Frequency Caps
- If someone’s already seen the survey (or dismissed it), Qualaroo might “hide” it for a set period.
- Try clearing cookies or use a fresh browser profile to test.
What to ignore: Don’t assume “it works for me” means it works for everyone. Test as many scenarios as you can—mobile, desktop, new visitor, returning, etc.
4. Survey Loads Slowly or Blocks the Page
Slow-loading surveys drive people nuts, and can hurt conversions. Here’s what you can actually do about it:
4.1. Audit Page Load
- Use Chrome DevTools > Network tab and watch for the Qualaroo script.
- Is it a big file, or stuck waiting for another resource?
4.2. Load Asynchronously
- Make sure the snippet is set to load async. This stops it from blocking other scripts.
- If you’re using a tag manager, double-check the loading behavior.
4.3. Competing Scripts
- Some A/B testing tools or chatbots compete for the same resources. Try disabling them temporarily to see if things improve.
Pro Tip: If survey speed is a big issue, consider limiting to critical pages only—or show a survey after a delay, not instantly.
5. Responses Aren’t Coming In (or Look Suspiciously Low)
So your survey is showing up, but hardly anyone is responding—or the numbers just don’t add up.
5.1. Are You Targeting Too Narrowly?
- Overly strict rules (like only targeting users who visit three specific pages in order) can kill your sample size.
- Loosen up the targeting and see if responses go up.
5.2. Are You Annoying Users?
- If you show surveys too often, or on every visit, people will learn to ignore or block them.
- Use frequency limits (once per user, or once per session).
5.3. Cookie Consent and Privacy
- On some B2B sites (especially in Europe), cookie banners or privacy tools may block Qualaroo until consent is given.
- Make sure Qualaroo is in the “allowed” category if you use a consent manager.
5.4. Test Across Browsers
- Some browsers (Safari in particular) can block third-party scripts by default. Always test in Chrome, Firefox, and Safari.
What to ignore: Don’t panic if response rates are low in the first few hours. Give it time—but if you see zero after a day, something’s wrong.
6. Qualaroo Clashing With Other Website Features
B2B sites are full of plugins—chatbots, popups, analytics. Sometimes, these don’t play nice together.
6.1. Overlapping UI Elements
- Use the browser inspector to see if the Qualaroo survey is being hidden “under” another element (like a sticky footer or chatbot widget).
- If so, tweak the z-index in your CSS.
6.2. Script Conflicts
- If another tool also injects surveys or modals, they can break each other. Try disabling one at a time to isolate the problem.
- Sometimes, Qualaroo’s CSS can override site styles. Check for broken layouts after enabling Qualaroo.
6.3. Too Many Surveys
- If you have multiple survey tools running (why?), pick one. Running several can annoy users and make debugging impossible.
Pro Tip: If you’re stuck, try using the browser’s “Incognito” or “Safe Mode” with most extensions off, to see what’s really happening.
Keep It Simple, Test Often, Iterate
Deploying Qualaroo surveys on a B2B website isn’t rocket science, but it does have a lot of little gotchas—most of which come down to targeting mistakes, script conflicts, or just plain user error. Don’t overthink it. Start with simple targeting, test on multiple devices and browsers, and ask for feedback from real users. If something feels broken, it probably is—so stay skeptical of “it should just work” answers.
Remember: simple rules, clear targeting, and frequent testing beat fancy setups every time. You’ll get better data and fewer headaches. Good luck!