Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Expose Complete Event Order and Registration Data in the Cvent Connector

Answered
Hanna Ilchenko User

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.

Please sign in to leave a comment.

Comments

4 comments

Date Votes
  • Official comment
    Unnikrishnan Nair Fivetranner

    Hi Hanna,
    Thank you for the detailed breakdown of the gaps in the Cvent connector schema. This is a substantial set of improvements for event financial and attendee reporting, and we have added it to our feature improvements backlog.
    Given the scope, it would help to know which pieces matter most for your immediate reporting needs, for example the order-level financial measures or the registration group linkage.

    We will keep you updated on this thread as we make progress.

  • Jason Hausman User

    I want to add my strong support for this feature request, specifically prioritizing the event_order_item table.

    Without event_order_item, it is currently impossible to accurately calculate "Amount Due" or identify unpaid invoices in our data warehouse. Because Fivetran's current implementation relies on event_transaction to determine financial metrics, any order where payment is deferred (like "Invoice Me" or "Purchase Order") fails to generate a transaction record, resulting in a false $0 balance in the data warehouse.

    Access to the event_order_item table (via GET /orders/items) is critical. It provides the base orderAmount independent of the transaction ledger, allowing us to accurately calculate the true amountDue and effectively manage our accounts receivable and outstanding balances. This is our highest priority reporting gap.

  • Hanna Ilchenko User

    Hi Unnikrishnan,

    below is our suggested prioritisation based on business impact.

    Priority 1 – Critical for Event Performance & Revenue Reporting

    Our immediate need is to calculate event performance, revenue, and conversion metrics. To achieve this, the following capabilities are essential:

    • Order breakdown (admission fees, sessions, taxes, discounts, fees)
    • Product type classification for all order components
    • Session purchases and associated amounts
    • Linkage between cancellation/refund orders and the original order

    Without these capabilities, revenue reporting remains incomplete, as we cannot accurately determine what was purchased, how revenue was generated, or correctly account for cancellations and refunds.

    Priority 2 – Registration Attribution

    The next most important requirements are:

    • Group registration identifiers
    • Support for registrations completed on behalf of another attendee

    These capabilities are important for understanding attendee relationships, registration behaviour, and accurately reporting participation.

    Priority 3 – Business Keys & Integration Support

    • Object codes (Order Code, Event Code, Session Code, Admission Item Code, etc.)

    These are valuable for integrations, reconciliation, and business reporting, although they are not blocking our immediate reporting objectives.

    Priority 4 – Pricing Visibility

    • Admission item pricing and pricing history
    • Session pricing

    These enhancements would enable more detailed analysis of pricing strategies, discount effectiveness, and purchasing patterns.

    Priority 5 – Remaining Enhancements

    The remaining items, such as invoice information and event-level tax settings, would be beneficial but are lower priority compared to the requirements above.

    Regards,
    Hanna

  • Unnikrishnan Nair Fivetranner

    Update - we are working on adding these endpoints and data.