Expose Complete Event Order and Registration Data in the Cvent Connector

Current Cvent connector implementation does not expose several key data elements required for meaningful event reporting and measurement. It does not provide the data required to calculate and report on critical business metrics such as order value, pending revenue, event performance, conversion rates, discount utilization, and overall attendee spend.

To fix the gaps we suggest to revise the schema as follows:

Gap	Proposed Schema Change
Order amounts (total ordered, paid, due)	Enrich `event_order` with order-level financial measures. `event_order` should remain a header-level entity containing references to attendee, event, order status, total ordered amount, amount paid, amount due, invoice number, and other order-level attributes.
Original ↔ cancellation order relationship	Add a self-referencing relationship on `event_order` (e.g. `original_order_id`) to link cancellation/refund orders back to the original order.
Order breakdown (admission fees, sessions, taxes, discounts, fees)	Add a new `event_order_item` table. Each row would represent an individual line item associated with an order. This would enable proper itemised reporting and attribution of revenue components.
Product type classification	Within `event_order_item`, expose the purchased product type (Admission Item, Session, Tax, Fee, Discount, etc.) and associated amounts.
Admission item pricing	Create a dedicated `admission_item` dimension rather than embedding admission item attributes within `attendee`.
Admission item price history	Create an `admission_item_pricing` table. Admission items often have multiple prices over time (early bird, standard, promotional, member/non-member pricing, etc.), making this naturally a one-to-many relationship.
Session pricing	Enrich `session` with pricing attributes or introduce a dedicated session pricing entity if Cvent maintains multiple pricing records per session.
Paid session purchases	Expose session purchases through `event_order_item` rather than only attendee-related structures.
Group registrations	Add `group_id` (or equivalent) to `attendee` to allow attendees belonging to the same registration group to be identified.
Registrant on behalf of attendee	Add a dedicated relationship table linking registrants and attendees. This should reference existing contact entities via `registrant_contact_id.`
Object codes	Expose business codes (Order Code, Event Code, Admission Item Code, Session Code, etc.) on all entities where Cvent provides them.
Invoice information	Add invoice number to `event_order`.
Event tax settings	Expose event-level tax configuration from `event`.

Community

Expose Complete Event Order and Registration Data in the Cvent Connector

Comments