Quick Checklist — Is This the Issue?
This is likely a cookie-access problem if both of these are true:
- Attendee reports seeing "No Response Given" for every question on the Review page, despite having answered them
- Admin-side data for that same session/evaluation shows responses staggered one per row, rather than grouped under a single attendee
If only one of these is present, look elsewhere first — this pattern specifically points to a cookie problem.
Symptoms
After completing the last question in a session evaluation, attendees land on a Review page to check their answers before submitting. In certain scenarios, they'll see "No Response Given" for every question — even though they definitely entered responses. This understandably confuses attendees and often leads to support inquiries.
Meanwhile, administrators can see the responses coming through, but they appear staggered — one response per row — rather than grouped together as a single attendee's submission.
Root Cause
If both symptoms are occurring together, the browser is likely unable to access cookies.
Conferences i/o uses cookies to recognize the same attendee across page loads. Since each evaluation question triggers a new page load, a browser that can't retain cookies looks, to Conferences i/o, like a different person on every question. Rather than reject the data, Conferences i/o passively accepts each response — which is why admins still see the data, just split across multiple "attendees" instead of consolidated under one.
When This Happens
The most common cause is that Conferences i/o has been embedded in another website or application via an HTML iframe. Some browsers — most notably Safari — apply default privacy settings that block third-party cookies in this embedded context.
Workarounds
- Not recommended: Asking attendees to enable third-party cookies in their browser settings manually. This puts the burden on attendees and isn't a reliable fix.
- Recommended: Follow our best practices guide for embedding Conferences i/o in an HTML iframe (attached below). This typically requires only a minor modification to the embedded URL and avoids the cookie issue entirely.