Open Forum

Hello!

We keep running into a recurring issue with Cvent reporting, and so far Support hasn't been able to offer a practical solution.

When we include the Attendee List opt-in/opt-out question during registration, there is no standard report that allows us to see who has opted out. Cvent has told us this information can only be pulled on the back end due to "security reasons," but this becomes extremely cumbersome when we are actively managing 20+ concurrent events.

From a security standpoint, this feels inconsistent-opting out of appearing on an attendee list doesn't seem materially different from opting out of attendee emails, which is reportable.

Use case example:
We do not publish our attendee lists until two weeks prior to the event, but our sponsors frequently ask in advance who is expected to attend. We can pull a manual attendee list report, but it still includes attendees who opted out, which creates a compliance issue. Sponsors also cannot access post-registration pages because they are not registered for the event.

Has anyone else run into this?

• Have you found a workaround or custom report?

• Are you handling this outside of Cvent?

• Has anyone successfully pushed back on the "security" limitation?

Any insight or best practices would be greatly appreciated.

Thank you so much!

Hi Andria,

We've confirmed that responses to the Attendee List Opt‑In/Opt‑Out widget are not currently available in standard or custom Cvent reports. At this time, the only way to obtain that data is via a backend "Attendee List Opt‑In/Opt‑Out" report that Cvent Support must run per event, which is why this has been framed as a security limitation rather than something Support can simply "turn on."

Because of this, our recommended workaround is to add a separate, reportable consent question during registration (for example, "Allow my details to be shared with event sponsors?") and then use a standard report like Invitee & Respondent Details filtered on that question. This gives you a clean, compliant list you can share with sponsors without needing repeated backend pulls from Cvent.

Hope that this helps!

Julianna

Hi Andria,

To your specific question: today there is no way to link or reconcile the Attendee List Opt‑In/Opt‑Out widget with a separate registration consent question in reporting. The widget responses are not exposed in standard reports; they only drive whether an individual appears on the attendee list itself. Because of that, if you collected consent in two different places, there isn't a system-driven way to see where a person answered differently and resolve that automatically.

Given your compliance requirements, the practical options today are:

• Option 1 – Use the widget as your primary consent:
  Continue to use the Attendee List Opt‑In/Opt‑Out widget to control who appears on the in‑product attendee list, and rely on Support‑run backend reports when you need a list for sponsors. This avoids conflicting consent points, but requires the manual report pulls you mentioned.

• Option 2 – Use a single, reportable consent and adjust the attendee list experience:
  Turn off the Attendee List Opt‑In/Opt‑Out widget and instead collect a single consent during registration (e.g., "Allow my details to be shared with event sponsors and displayed on the event attendee list"). You can then use standard reports filtered on that question as your single source of truth for both sponsor sharing and any attendee‑facing list you manage outside the widget. This removes the risk of conflicting answers, but does mean rethinking how the attendee list is surfaced.

Because there is no way today to report on or cross‑check the widget's responses, we don't recommend running both the widget and a separate consent question in parallel if strict compliance is required - you'd have exactly the scenario you describe, with no visibility into conflicts.

I know neither path is perfect given your volume and the need for an attendee list. I would recommend you connect with your Account Team to make sure your use case is fully captured as feedback for our product team, and to talk through which of the above approaches would be the lowest‑risk fit for your program in the interim.

Thanks,

Julianna