Frequently Asked Questions – Technical Support
Real-time customer feedback for German webshops
Measuring load time and runtime overhead
FeedBackPro is engineered to add under 12ms to your Time to Interactive. Our asynchronous loader ensures the widget initializes only after your core content renders, keeping Core Web Vitals green.
Does the widget block the main thread?
No. We use requestIdleCallback and Web Workers for sentiment analysis. Typical TTI impact is 8–15ms on Shopify Plus stores running 14+ apps.
How much bandwidth does it consume?
The initial payload is 14.2 KB gzipped. Subsequent polling uses Server-Sent Events, averaging 0.8 KB per active session. We compress all JSON batches before transmission.
Can I throttle data collection?
Yes. Use the fbp_sample_rate config flag to collect 100%, 50%, or 25% of sessions without modifying the core script. Sampling preserves statistical significance while reducing API calls.
Supported environments and graceful fallbacks
FeedBackPro runs natively in all evergreen browsers and gracefully degrades in legacy environments without breaking your checkout flow or triggering CSP violations.
Which browsers are officially supported?
Chrome 90+, Firefox 88+, Safari 14+, and Edge 90+. We maintain a lightweight polyfill layer for IE11 on legacy corporate portals, disabling advanced animations automatically.
Does it work with headless crawlers?
Yes. The script detects navigator.webdriver and skips UI rendering, preserving your SEO score on Google Lighthouse and Screaming Frog. Crawl budget remains unaffected.
Mobile viewport adjustments?
The widget auto-scales to a 320px minimum width and disables parallax animations on devices with prefers-reduced-motion: reduce. Touch targets meet WCAG 2.2 standards.
Resolving overlays and event listener collisions
When multiple marketing tools compete for DOM control, FeedBackPro’s sandboxed container prevents z-index wars and event bubbling issues across your stack.
The widget overlaps my Klaviyo popup
Set z-index: 9998 in your dashboard settings. FeedBackPro listens for klaviyo_closed events to pause rendering automatically. You can also enable auto-stacking mode in the integration tab.
Click tracking duplicates with GA4
We route all interactions through the dataLayer with event: 'fbp_widget_action'. Exclude fbp_ prefixes in your GA4 event filters to prevent double counting. Debug mode shows exact payload structure.
Console throws "Cannot read property of undefined"
This usually occurs when loading before jQuery 3.6+ on WordPress. Add type="module" to the script tag or defer execution until domReady. Our loader now includes a native try-catch wrapper.
Still seeing unexpected behavior in your staging environment? Our engineering team monitors the support queue and responds within 4 hours during CET business hours.
Open a Support Ticket View API Documentation