CVENT Custom Fields
Answered
Which connector?:
Additional details:This suggests the issue is with how the Fivetran connector sources attendee segment data rather than a limitation of the Cvent API.
-
Official comment
Hi Ryan,
Thanks for the suggestion. On checking this API, it needs an input of all segments to bring the attendee list. These segments are created for every event or do you reuse segments - this would help us understand if we can limit fetching dat for newly created segments only?
Thanks. -
The audience field is a multi-select list of pre-defined options including current investors, prospective investors, financial advisors, etc. I’ve attached the list of currently available options. There is also an “other” box with freeform text entry.
-
Hello @Unnikrishnan Nair,
The request here is for the Fivetran connector to support audience segment data. Regardless of whether new audience segments are created, existing segments are updated for current events, or segments are deleted, the underlying need remains the same—access to accurate audience segment information through the connector.
As Ryan noted, it appears the connector is currently returning NULL values because it does not seem to be using the correct endpoints. However, the audience segment data is clearly accessible through the Cvent REST API (documentation: https://developers.cvent.com/docs/rest-api/overview).
For example:
Step 1: Retrieve audience segment data
https://developers.cvent.com/documentation#tag/Audience-Segments/operation/listAudienceSegmentsPostFilterStep 2: Retrieve attendees associated with or dissociated from those segments
https://developers.cvent.com/documentation#tag/Audience-Segments/operation/listSegmentAssociatedAttendeesThis suggests the limitation is in how the connector is sourcing the data rather than in the Cvent API itself.
I want to echo Ryan’s request—supporting audience segment data would be extremely valuable for downstream analytics and reporting.
Please sign in to leave a comment.
Comments
3 comments